SSAnalyzer for SourceSafe by TSASG - Team Training Opportunities

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.

Team Training Opportunities

By identifying those less-than-best practices that some of your team members may be using, you can quickly provide some basic training/instruction that should reduce or eliminate problems in the future. Here are some suggestions:

Situation	Possible training
Rollbacks of shared files causing unwanted branching	Ensure that all team members understand that Rollbacks of shared files cause immediate branching of that file, thereby ending the shared-ness of the file and causing problems. Since this is a shared file, you must use caution. Some alternatives may be: If you just need to undo the changes for this project, pinning should be considered. If the changes must be undone for all projects that share this file, then: Review all projects that share this file to determine potential impact. Check-out the version you wish to rollback to. Check-in this version as the latest version. These steps will keep the file from being branched. If differences are more extensive, then other options are: use of #define use of derived class, if appropriate modify code to accept parameters (use default parameter to avoid impact on other projects)
Duplicated files being added to repository	Ensure that all team members understand the proper procedures in building a new project. Our suggestions: Create the project. Create and new files that are needed Place the new project under SourceSafe control. If its a test project, you can always delete it later. Iterate through compile and link cycles to identify missing libraries, shared files, etc. Find the proper files to share and do so. Beware of files with duplicate names that may be the wrong file. If you find that the duplicated files only differ slightly, then consider these options are: use of #define use of derived class, if appropriate modify code to accept parameters (use default parameter to avoid impact on other projects)

Download a free trial version now.

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

Privacy