Baselines are snapshots of a repository package taken at a point in time. These snapshots are stored in a format called XMI, which is an XML format. These files must be stored so that they can be recalled and used for comparisons at a future time. There are two primary places to store baselines:
- In the current repository - this is the default location
- In a Reusable Asset Service - a Reusable Asset Service needs to be nominated as the location
Baselines are by default stored in the repository so when, for example, you create a Baseline of a Requirements Package at a given milestone, the 'snapshot' would by default be stored in the same model as the Requirements. This type of storage is practical and sufficient for small, isolated project teams, but for larger teams and endeavors, Enterprise Architect provides some mechanisms to store the Baselines as reusable and universally accessible snapshots available to any project or organizational team, anywhere in the world. This reusable storage is particularly useful in this age of innovation and agility, where geographically independent teams need to share information and reuse existing assets at Internet speed. The facility uses the Reusable Asset Server (RAS), which is Cloud-based (including on the home premises) and provides sophisticated mechanisms to manage these valuable corporate assets.
Management of the Baselines differs depending on the option selected. A librarian or administrator typically decides which option is most appropriate for a given repository and team. Factors such as whether the Baselines need to be made available to a distributed audience and whether dependency analysis is required would be considerations in this decision.
Settings > Model > Options > Baseline
Specify Reusable Assert Server for Baselines
To store baselines in a Reusable Asset Server, you need to define this on the 'Baseline' page of the 'Manage Model Options' dialog, where you specify Cloud connection and storage details and options.