Version Control Best Practices for Enterprise （版本控制企业的最佳实践）.pdf

Version Control Best Practices for Enterprise Architect All Material © Sparx Systems, 2010 Table of Contents Glossary3 Introduction4 Why Should I consider version controlled models?4 What does version control mean in Enterprise Architect?4 Team Deployment: Centralized or Distributed5 Scenario 1: Centralized Team6 Recommended process for version controlling models7 Recommended process for rolling back (undoing) changes8 Scenario 2: Distributed Team using local models8 Recommended process for version controlling models9 Managing cross-Package dependencies9 Recommended processes for submitting changes safely10 Recommended process for rolling back (undoing) changes14 Scenario 3: Multiple Site Locations15 Appendix A: Enterprise Architect meta-data that is not stored in the Version Control Repository.. 16 Appendix B: Built-in Collaboration and Change Management Tools16 Appendix C: Applying Version Control to Packages17 2 Glossary Baseline (Model Baseline): In Enterprise Architect, a Baseline refers to a snapshot of a Package at a particular point in time. The snapshot is stored in the Model Repository as compressed XMI and forms the basis of Enterprise Architects Compare and Merge functionality. Check-in: The process of submitting your changes to the Version Control Repository. In Enterprise Architect, you execute this command on a Package that you have checked out. This then updates the Version Control Repository with your changes and releases your editing lock on that Package. Check-out: The process of retrieving the latest version of a file from the Version Control Repository. Executing this command from Enterprise Architect will overwrite the selected Package with the latest version and lock that