Manage Baselines

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 and these files must be stored so that 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 is expedient and sufficient for small, isolated project teams, but for larger teams and endeavors Enterprise Architect provides some powerful mechanisms to store the Baselines as reusable and universally accessible snapshots available to any project or organizational team, anywhere in the world.  This 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.

A librarian or administrator would typically make the decision about which of these options is most appropriated 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. The management of the baselines differs depending on the option selected.

Specify Reusable Assert Server for Baselines

To