This application provides limited support for 2 code management (CM) systems:
Before changes can be made to a local copy of the Method Library, the source files that make up that library must be writable. Code management systems usually maintain local files with read-only permissions unless those files have been explicitly marked for editing by being checked-out. Source files in the Method Library must be checked-out before they can be edited.
Note: Users in CM-integrated environments should be aware that relatively simple changes to method library elements may affect more than one source file. This implies that multiple files may have to be checked-out before individual method elements can be modified.
Information from the method library is cached in memory when a new library is opened. If library source files are updated by a separate application the version cached in memory will not be refreshed. In that situation you should reload the entire method library. Alternately the library files can be updated from within the Resource perspective.
As soon as the method library is opened two files will be created
(.lock and .project)
at the same level as library.xmi.
These two files should NOT be placed under version control.
The complex data model and highly interrelated content in a typical method library impose special considerations for code management systems. The roles played by various team members in a distrbuted development environment also have an impact on code management hierarcy and access permissions.
The usage model for this application assumes one person on the team fills
the role of Content Architect.
The Content Architect is responsible for developing method content at a high level and will therefore make
changes to a key file called plugin.xmi
This file contains element ids, presentation names, brief descriptions, and relationships.
There is one plugin.xmi for each method plug-in.
This usage assumption implies unique access permisions be granted to the Content Architect.
The usage model further assumes there are multiple Content Developers who develop method content
based on their expertize in various specializations.
Content Developers will therefore make changes to individual .xmi files which are the physical
representation of content elements.
The actual method content is stored in the rich text fields that make up individual elements.
This usage assumption has implications for sharing files with equal access permisions amoung all Content Developers.
Finally, if someone on the team is filling the role of Process Developer that person may require unique access permisions to certain files. Processes are stored in two units: one that contains the model and one that contains the textual documentation.