|
SSAnalyzer is a software tool specifically designed to help software development managers at all levels to identify and easily correct common, yet costly, conditions within Visual SourceSafe.
These conditions are typically, yet unintentionally, caused by users through the normal use of SourceSafe. A couple of
poor user procedures can lead to costly debugging and recovery efforts.
Features and benefits
- Within minutes, import your SourceSafe repository transactions into an MS-SQL database
- Provide global view of projects and files from several key aspects
- Provide GUI to assist user in quickly identifying and correcting several potential and costly problems:
- Different files with same file name.
- Files inappropriately branched due to a rollback of a shared file
- Deleted but unpurged projects
- Deleted but unpurged files
- Provide valuable and quick clean up options on SourceSafe in order to obtain:
- Reduced maintenance costs by eliminating unintended code/file duplication
- More accurate reporting by various third party packages (CodeReports, SourceVizor) by eliminating unintended code/file duplication
- Faster SourceSafe response time due to reduced number of projects and files in the repository
- Identify undesireable coding habits (copy and modify vs. refactoring vs. use of #define) that individual developers may be employing. (Need some training)
The Need for SSAnalyzer
If you have used Visual SourceSafe for a while as we have, you already realize it is quite easy for both novice and experienced users to use SourceSafe in ways that cause unintended file branching and duplication. Once done, these unintended branched/duplicated files lead to rapidly increasing maintenance costs. SourceSafe itself provides no means to
easily identify or correct these problems because the SourceSafe interface was designed to look at a single project and a single file at a time.
Analysis of a number of SourceSafe repositories indicate that as much as 20% of all unique files are
unintentionally duplicated/branched files. Let's get a feel for what this means by following two scenarios and
exploring your options to remedy the problems.
Problem Scenario #1: Unintentionally duplicated files
Problem Scenario #2: Unintentionally branched files
Can it get worse? Yes!
What should we do? The Manual Approach
What should we do? SSAnalyzer
What's the impact of SSAnalyzer? SSAnalyzer Impact
How else does SSAnalyzer help? SSAnalyzer Help
How soon can SSAnalyzer help? How soon?
What's the cost justification for buying SSAnalyzer? Here's how.
What else can SSAnalyzer do or provide?
Are there any security concerns? Click here
SSAnalyzer Overview Click here for overview
|
