The following table describes the function of specific files and the implications for making changes to these files in a version-controlled environment.
| File | Usage |
|---|---|
| library.xmi | This file contains a reference to every plug-in in your method library. When you create new packages or processes, EPF Composer does not modify this file. This file is modified only when a plug-in is created. This file is shared by all plug-ins in your method library, so you need to be especially careful to coordinate changes being made by different individuals. |
| plugin.xmi | There is one plugin.xmi file for each plug-in. This file contains a reference to every content element in the plug-in, in addition to the presentation names, brief descriptions, and relationships for each element, such as guidance, inputs or outputs (tasks), performing role (tasks), work products responsible for (role), and so on. It also contains the definition of what is included in each standard category in addition to the definition and contents of each custom category. When more than one person works on a plug-in, you need to be especially careful about coordinating changes to this file and any files that it references. |
| method content element.xmi | There is one file per method content element. It contains the descriptive text for the method content element for all fields except the name, presentation name, and brief description. The file name (<method content element>) is the same as the 'name' field for the element. (One exception to this: if you create a second method content element with the same name and that element is located in the same directory in your library, EPF Composer will append '2' to the end of the actual file name. The appended '2' will not appear in the name field.) |
| model.xmi | There is one model.xmi file for each process (capability pattern or delivery process). This file contains a reference to the descriptors (role, task, and work product), in addition to the names and brief descriptions for each of them. However, the brief description and presentation name for the process itself is kept in the plugin.xmi. |
| content.xmi | There is one content.xmi file for each process (capability pattern or delivery process). This file contains the descriptive text for the descriptors of the process elements, with the exception of the names, presentation names, and brief descriptions. |
| configuration.xmi | There is one configuration.xmi file for each configuration. Files of this type reside in the \configurations folder. They specify what is included in each configuration, including which content packages, which process packages, and which processes (capability patterns and delivery processes) are included, as well as the specification of what is included in each view. |
| .lock | This is a temporary file located at the same level as library.xmi. It should not be placed under version control. |
| .project | This is a temporary file located at the same level as library.xmi. It should not be placed under version control. |
| models.xmi | There is one models.xmi file for each method library. This file contains references to all estimating models and estimating factors in the method library. This models.xmi file resides under folder called estimation. This file is modified when a new estimating model is created, an existing estimating model is renamed, a new default estimating factor is created, or one of the default estimating factors is modified. This file is created in the second step of the estimating model wizard when a user clicks Next. Rational ClearCase prompts to "add to source" two elements, a folder named estimation and the models.xmi file. Select the Keep checkout option and click OK to add to source control. This file is shared by all estimating models in the library, so care must be taken to coordinate changes made by anyone who uses it. |
| diagram.xmi | All diagrams are stored in this file. |