SSAnalyzer for SourceSafe by TSASG

News Release - 2005.09.10

TSA Software Group (TSASG) announces the release of SSAnalyzer 1.0.

SSAnalyzer is a unique tool for Visual SourceSafe that will identify and assist the user in correcting improperly branched or duplicated files.

Using advanced text algorithms to identify non-effective file differences (formatting, comments, etc), SSAnalyzer displays effective vs. non-effective changes for closely matching files, making it much easier for the user to find those few REAL differences among thousands of lines of code.

Typical file and code redundancy can be reduced by an average of 20%, greatly reducing maintenance problems, increasing the speed of SourceSafe, and enhancing the accuracy of third-party source code reporting packages.

SSAnalyzer is unique because it is the only product on the market that provides a repository-wide view of the following aspects of your code base:

Aspect	Potential Problem
Duplicated File Names (Evil Twins)	Were these files duplicated when they should have been shared? If these files should have been shared but were instead copied, you just added to your maintenance effort and cost. Are they now divergent and by how much? The longer you wait to correct the problem, the worse it will get as different changes are applied to each file. The efforts and costs continue to increase. What is the best action to remove the duplication? How many projects are affected? SSAnalyzer provides tools to assist you. Which users are causing the problem? You need to identify them and provide training.
Branched Files	Were these files explicitly branched (Branch), or were they implicitly branched (Rollback)? In SourceSafe, a rollback of a shared file results in a new branch, essentially creating a new development path for that file. This is not what is typically intended and many users do not realize this. Your maintenance effort and cost just went up. Are they now divergent and by how much? The longer you wait to correct the problem, the worse it will get as different changes are applied to each file. The efforts and costs continue to increase. What is the best action to remove the branching? How many projects are affected? SSAnalyzer provides tools to assist you. Which users are causing the problem? You need to identify them and provide training.
Deleted, but unpurged, Projects and Files	How much are these items slowing your everyday SourceSafe response time? Developers frustrated by slow response times are less productive. Do you have the time to review every project manually to address this problem? SSAnalyzer provides a global view. How would you be impacted if any of these files/projects were incorrectly recovered and used?

Download a free trial version now.

CM, testing, dupe, purged, enhancement, support, expert, QA, reseller

Privacy