Modifying a predefined template

The predefined templates that are included with the Lifecycle Project Administration user interface are XML files. You can download and modify these files to create customized lifecycle projects and project areas.

1. In the user interface, click Templates.
2. In the Actions column cell for the template that you want to download, click , the Download template icon.
3. Locate the template XML file in your file system and open it in an XML editor. Save the file under a different name.
4. In the Template Description section, edit the dc:identifier, dc:title, and dc:description tags to specify a unique template identifier, new title, and helpful description. Optionally, edit the entries in the locales tag to specify the locales in which the template is available.
5. In the Project Areas section, add or remove projectArea tags to specify application project areas to create. Use the id attribute to specify the application type (rtc.project, rrc.project, rqm.project). To specify the process templates that are available to create a project area, use the processTemplate tag. The following example specifies that users can choose the Scrum or Formal Project Management template to create the change and configuration management project area:

   <projectArea id="rtc.project>
   			<processTemplates>
           <processTemplate>
               <dc:identifier>scrum2.process.ibm.com</dc:identifier>
               <dc:title>Scrum</dc:title>
           </processTemplate>
           <processTemplate>
               <dc:identifier>formalpm.process.ibm.com</dc:identifier>
               <dc:title>Formal Project Management Process</dc:title>
           </processTemplate>
       </processTemplates>
       <dc:subject>Change Management</dc:subject>
       <domain ref="http://open-services.net/ns/cm#"/>
   </projectArea>
   

6. In the Project Associations section, add or remove projectAreaAssociation tags to specify the associations to establish between the project areas. Use the sourceDomain and targetDomain tags to indicate the direction of the linking. Use the linkType tag to indicate the relationship between the artifacts being linked to each other. The following example specifies that artifacts created in the requirements management project area can be linked to artifacts created in the Change and Configuration Management project area. The linkType tags indicate that the Requirements Management artifacts (requirements) are implemented by the Change and Configuration Management artifacts (work items). See Supported link types for the full list of link types.

   <!-- RRC implemented-by RTC -->
   		<projectAreaAssociation>
   			<sourceDomain ref="#rrc.project"/>
   			<linkType>implemented-by</linkType>
   			<targetDomain ref="#rtc.project"/>
   		</projectAreaAssociation>
   	
   		<!-- RTC implements RRC -->
   		<projectAreaAssociation>
   			<sourceDomain ref="#rtc.project"/>
   			<linkType>implements</linkType>
   			<targetDomain ref="#rrc.project"/>
   		</projectAreaAssociation>

7. In the lifeCycleProjects tag, update the list of project areas to be created in the lifecycle project. In the following example, the <lifeCycleProjectContext> tag entries identify three project areas to be created, one in each of the IBM® Engineering Lifecycle Management applications.

   <lifeCycleProjects>
   		<lifeCycleProject id="lpa.project">
   			<dc:title>${request.param.projectName}</dc:title>
   			<dc:description>${request.param.lpaProjectDescription}</dc:description>
   			<lifeCycleProjectContext ref="#rrc.project"/>
   			<lifeCycleProjectContext ref="#rtc.project"/>
   			<lifeCycleProjectContext ref="#rqm.project"/>
   		</lifeCycleProject>
   	</lifeCycleProjects>

8. Save the template XML file.