Graduating from microsoft visual sourcesafe to ... - PVCS - Synergex

More documents

Recommendations

Info

G R A D U ATING FROM MICROSOFT ® VISUAL SOURCESAFE TO MERANT ® S C M Business ROI with Merant Beginning with implementation of PVCS Version Manager, your teams will produce higher quality software, faster. Changes and revisions can be taken in stride and integrated with fewer errors. Developers can reuse more components and access distributed assets. They safely engage in time-saving concurrent and remote development. PVCS Version Manager is the foundation for an effective SCM infrastructure, and can be integrated with other products in the Merant family, including tools for change and issue management, process management, code and content management and deployment for web teams, and more. Depending on the scope of SCM investment you choose, the ROI you can expect from Merant SCM include the following: Shorter Development Schedules and Reduced Costs • Software assets (code, documentation, tests, etc.) are protected from accidental loss and unintentional overwrites • Software builds are automated • The next release can be developed while simultaneously maintaining current release • Code reuse and component engineering are increased, resulting in more development productivity and less rework Support for Distributed and Remote Development • Development resources, wherever they are located, regardless of platform, can access PVCS Version Manager via browser access • Your SCM archives and disciplines can now scale to match any size team, from one to thousands • A single archive keeps all data secure and uncorrupted — no need to split projects across databases if you don’t want to • The entire team can use the same SCM tool and the same data repository—no need to create manual workarounds with spreadsheets and status documents. Higher Application Quality • Many Change Control Board tasks are automated so required tasks cannot be lost • Wo r k f l o w, promotion levels and status benchmarks are managed and communicated automatically • Defect information is automatically captured and tracked the first time around — fewer missed fixes, less rework and retesting • Version control and baseline/release management enable roll back to “good” versions when a production problem is encountered • Automate processes to reduce human error and ensure that steps are not skipped M E R A N T 3
G R A D U ATING FROM MICROSOFT ® VISUAL SOURCESAFE TO MERANT ® S C M • Eliminate unauthorized changes • Optimize scheduling and increase product auditability Track Project Status with Comprehensive Reporting • Perform analysis to determine the impact, effort and cost of proposed changes before they are undertaken • Gather and analyze metrics to help improve your development processes Auditability and Accountability • Automate the paper trail to record who changed what, when and why • Define, track and navigate relationships between items (functional spec, design spec, source code, object code, executable, tests, test results, change request, engineering change order, etc.) Scenarios Where Merant Makes a Difference In addition to the ROI benefits discussed above, developers who actually work with the application will appreciate how PVCS Version Manager protects their progress and frees them from mundane manual tasks. PVCS Version Manager is better for team development in several common kinds of projects: Enhancement Pr o j e c t s . Your teams may spend as much time enhancing existing applications as they expend writing new ones. Such projects are an example of complicated change management. While the code requiring modification is being checked and fixed, there is usually ongoing standard maintenance occurring to the base code. This creates a classic need for parallel development, which involves two separate paths of coding, one to accomplish the enhancement, and the other for ongoing maintenance to the baseline. Visual SourceSafe has difficulty with this because it needs to force a completely new project whenever you need to branch an existing file, whereas PVCS Version Manager does not. Visual SourceSafe is also prone to data corruption as project data grows. Core Development Pr o j e c t s . Distributed development projects typically have separate front/back end components under development simultaneously. This means such projects need both a strong source code management tool and change request management. The PVCS Professional suite integrates version control (PVCS Version Manager component) and change management (PVCS Tracker component) to capture and organize development issues, while associating the issues with the appropriate development files for update. PVCS Professional also includes PVCS Configuration Builder to automate and speed new builds. Visual SourceSafe has no such capabilities. Additional tools would have to be purchased for issue tracking and builds, tools which may or may not integrate with Visual SourceSafe. Cross Platform/Heterogeneous Projects. With Visual SourceSafe, you must work in Windows. In contrast, PVCS Version Manager provides heterogeneous support and inte- 4 M E R A N T
Page 1 and 2: GRADUATING FROM MICROSOFT ® VISUAL
Page 3 and 4: G R A D U ATING FROM MICROSOFT ® V
Page 7: G R A D U ATING FROM MICROSOFT ® V

Graduating from microsoft visual sourcesafe to ... - PVCS - Synergex

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?