Tool Mentor: Create a new Process Template |
This tool mentor describes how to create a new process template for the Jazz team process component based on a process created in Rational Method Composer.
Tool: Rational Team Concert (RTC)
Main Description
The IBM Rational Team Concert (RTC) Team Process Component provides the foundation for Jazz's process enactment support. This tool mentor describes how you can create a new Jazz process template for a process that you have modeled and documented in IBM Rational Method Composer (RMC) or EPF Composer (EPFC). #### How to create a new process template This tool mentor assumes that the Jazz server has been set-up and connected. Follow the steps described in the online help (Section: Collaborating > Working with projects, teams, and process) to create a new process template. The template will appear in the Process Template Explorer view and the Process Template Editor will open. Initially, there is a single iteration created in the 'development' development line. Modify the process iterations by using the Duplicate, Edit, Create and Delete buttons located in the process iteration section. Review the delivery process that you have created in IBM Rational Method Composer to analyze the breakdown structure and to decide which of the iterations and activities you want to represent in the template's development line. Refine the template in the Process Specification tab. You need to provide details for the following parts which can retrieve from information in the RMC delivery process: Role Definitions: This part of process specification allows you to define the roles that particiapte in your projects. You can identify the roles in the Process Template by reviewing the roles in the Team Allocation View of your RMC delivery process. Select the top-level element in your delivery process' breakdown structure and switch to this tab either in the published site or RMC's process editor to see the list of all roles used in your process. Project Configuration: This is the part of the process specification in which you configure the project environment. It comprises of three main parts: Project Area Initialization: requires you to define the initial set of work items to be generated during project initialization and define the roles to perform the process. To identify the initial set of work items, you should start by reviewing in RMC your delivery process' first iteration's tasks and activities in the delivery process and decide which tasks should be created as work items during project initialization. Hint: look for these flags: planned=true, optional=false because these tasks always have to be performed for an iteration, so why not let RTC create them for you. Permissions: Based on the role descriptions in your RMC process decide which roles shall be allowed to perform tool operations in which way. See this page for more details on assigning permissions: Role and Permissions. Configuration Data: To identify the work item types that shall be defined in your Process Template, review your work products in your RMC method configuration and delivery process and decide which of these you want to track as work items. Team Configuration: This part of the process specification defines lifecycle specific tool configuration and behavior. Permissions: To identify which roles needs permissions to perform which operation in which way review the responsibility and descriptions of tasks or tool mentors performed by the roles in the RMC method configuration and delivery process. Process Behavior: For each iteration in the process specification, define process rules which will be enforced by the Operation Preconditions and and Followup Actions during the project's lifecycle or only in a specific iteration. See SCM Team Precondition for more detail and use Build Operation Preconditions, SCM Team Precondition and Work Item Preconditions as a starting point to selecting the preconditions you want to configure in your Process Template. You can also review the work products in your RMC process that correspond to Jazz component such as Workitem component and Build component to identify the process rules that can be enforced by the Operation Preconditions available. Iteration Type: Define iteration types by reviewing the capability patterns in your RMC method configuration. Typically, capability patterns that define an iteration or course granular activity that is performed in an iterative way are good candidates for iteration types. Define the permissions and process rules which will be enforced in an iteration of a particular type. Note: The easiest way to modify the process specification is by copying the process specification from the Jazz built-in process template such as the EclipseWay process template and OpenUP/Jazz process template and tailor them based upon your needs. Modify the Process Iterations in the Process State tab to reflect the change in the Process Specification. The first part is for declaring all the Iteration Type that have been specified in process template. The second part is for defining the complete breakdown of the development-line including Iteration Type assignment and defining the initial 'current iteration'. The development-line identified here is the same as Process Iteration breakdown. You can also set the current iteration for the process state by selecting the Set Iteration as Current icon ( ) in the process iteration section of the Process Template Editor. To link your published method configuration created with Rational Method Composer (RMC) or Eclipse Process Framework Composer (EPFC) to your process template for documentation perform the following steps: Publish your method configuration and create a zip-file with the published pages (That is, zip-up the entire publication directory). Upload the zip-file file to the Jazz server using the Simple File view that you can open by clicking the Simple Files link in the Process Content URL section located in the overview page of Process Template Editor. In the Simple Files view right-click on <your server connection> and select Upload New File > Upload Select the location of the process content zip-file and click OK. Now you need to link the uploaded zip-file to the process template by creating a URL in the Process Template Editor to the published site inside the zip file. Start doing this by first clicking the Browse button. In the Select Archive File dialog, select the file that you just uploaded. The initial file path will appear in the field. Complete this file with the path to the index.htm file inse the zip-file. For example, in the following image the index file path is MAM/index.htm because the zip file contains a directory called MAM to which the RMC site was published. Save the process template by clicking the Save button or Ctrl+S.
More Information
Checklists | Build Operation Preconditions SCM Team Precondition Work Item Preconditions
Guidelines | Configuration Data Project Area Initialization Role Definitions
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.