Version Control Best Practices for Enterprise Architect

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 Architect's 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 Package for your exclusive editing. Commit: Submit your changes to the Version Control Repository without releasing your editing lock on the related file(s). In Enterprise Architect, this is equivalent to executing the " Put Latest " command. DBMS: Database Management System. Enterprise Architect supports several relational DBMS products to host the Model Repository. A DBMS is commonly used when the Model Repository is accessed by several concurrent users. Model Repository: Enterprise Architect's storage mechanism for model information. If multiple users concurrently edit the same model, the repository is usually DBMS-based. In distributed team environments where concurrent model access is not possible, local EAP files are usually deployed instead. Enterprise Architect can use your Version Control System to transfer information between the Model Repository and a Version Control Repository to propagate changes amongst team members. Package: The primary organizational construct in Enterprise Architect models, roughly equivalent to a 'folder' in the file system. A Package may be a model's Root node, a View or a sub-Package. Version Control Repository: The storage mechanism used by the Version Control System to store revisions – specifically, model revisions. Version Control System: The third-party product that manages revisions of your model data. Enterprise Architect supports several Version Control Systems (such as CVS, Subversion and SCC-compliant products) and provides the user interface needed to move data between the Model Repository and the Version Control Repository. XMI: XML Meta-data Interchange. An open standard file format that enables the interchange of model information between tools. Enterprise Architect uses this file format to serialize a Package's model information to facilitate storage in the Version Control Repository. When you apply version control to a Package in Enterprise …