How to customize process and project templates in Rational Requirements Composer 4.0

This page describes a usage or software configuration that is not supported by IBM.

This article provides step-by-step instructions for extending the Rational Requirements Composer process and project templates based on industry/domain.


Rational Requirement Composer has process templates and project templates. For the Requirements Management project areas, you must specify process and project templates. In the user interface, the process and project templates appear in the order in which you specify them. Process templates include collections of roles, practices, rules, and guidelines used to organize and control the flow of work. Project templates can be defined to include many kinds of project information such as artifacts, artifact templates, artifact types and attributes, links between artifacts, link types, folder structure, tags, and shared saved filters. Organizations may have varying requirements for project governance, so the customization of process and project templates may be necessary. Also, different teams may want to adapt different processes and folder structure for their projects, which may present a need for customizing the process and project templates.

Many teams find it challenging to get a project started quickly, to get team members oriented, to set up and configure tools, and to take advantage of proven patterns of success to do their jobs. Many other teams are required to document their processes for compliance reasons, and show that they follow that process. For these reasons, RRC allows you to customize the process template and also create new project templates. Every ISU will follow a specific process, and will have standard artifacts managed inside a standard folder structure. For example, Banking ISU will have a set of roles defined, and permissions assigned to each of those roles. Banking ISU will also follow a standard folder structure for managing the artifacts. We can customize the existing process template and project template for the Banking ISU. Thus, these customized templates, when shared with teams, would help them to start their project quickly.


This topic assumes that you have installed the Rational solution for Collaborative Lifecycle Management (CLM) 2012 and Rational Team Concert (RTC) 4.0, and have deployed the process templates in the CLM applications. This topic also assumes that you know the basic concepts of project configuration, team configuration and are familiar with project area management in the CLM web UI.

RRC Process Template

Rational Requirement Server Template (RRST) is the only pre-defined process template existing in RRC. This pre-defined template can be modified according to the project needs. You must have Administrator role in the project to customize the template. Process template has different components such as Overview, Timelines, Roles, Permissions, Access Control, Configuration Data and Process Description. Each of these components can be customized according to your project needs. Rational Requirements Server Template has four roles with associated permissions:

  • Administrator
  • Author
  • Commenter
  • Project Snapshot Administrator

Exporting Rational Requirements Server Template

  1. Navigate to application administration page (https://[fully qualified hostname]:9443/rm/admin).
  2. Click on Administration > Manage Templates .
  3. On the Manage Templates page, click on Export Rational Requirements Server Template (RRST).
  4. Save the exported template in the local directory.

Importing and Configuring RRS Template in RTC client

  1. Start RTC client 4.0. Establish repository connection to RTC CLM 2012.
  2. Open Process Template view. Right click on the repository and then click Import.
  3. Import Process Template window opens. Browse the saved RRS Template folder. Click Finish.
  4. In the Process Template view, double-click Rational Requirements Server Template to customize.
  5. On the Overview tab of the process template, in the Process ID field, overwrite the existing process ID with RRC Banking Template.
    Overview screen capture
  6. On Process Configuration tab, you can define the Roles and Permissions for the RRC Banking Template.
  7. Banking Requirements Template has the following roles with associated permissions:

    • Everyone (default)
    • IT CIO
    • Operation Head
    • Operation Senior Manager
    • Operation Assistant
    • IT Project Head
    • Lead Architect
    • Analyst
    • Process Head
    • Process Lead
    • Executive
    • Process Assistants

    You can also customize Roles and Permissions in RRC Web.

  8. On Process Configuration tab, expand the Project Configuration section and click Permissions.

    Assign Permissions for each of the role and click Save.

  9. Process Configuration screen capture

    Project Configuration allows you to define the permissions and initial process for the project area.A project area can contain team areas that inherit the project area’s process, roles, permissions and operational behavior. Team areas may modify the permissions and the operational behavior they inherit from the project area.

Exporting the RRC Banking Template into destination directory

  1. In the Process Template view of RTC Client, right click on RRC Template for Banking Application and click on Export.

  2. On the Export Process Template window, choose the destination directory and click Finish. You will find a file named RRC Banking Template in the destination directory. Add this existing template to RRC Banking

Importing the RRC Banking Template into RRC Web

  1. Navigate to application administration page (https://[fully qualified hostname]:9443/rm/admin for Requirements Management).

  2. On Manage Template page, click on Import Template and browse the exported archive RRC Banking

    Import Template screen capture

  3. . After the import is complete, you can see the RRC Banking Template on the Process Template page.

    RRC Process Template screen capture

    Creating a project area using RRC Banking Template

    1. Navigate to application administration page (https://[fully qualified hostname]:9443/rm/web for Requirements Management).
    2. Click on Project Areas menu under Requirements Management section.
    3. Click on Create Project Area to create a new project area.
    4. Name the project area as My Banking Project.
    5. Select RRC Banking Template in the Process section.
    6. Add the members and administrator to the project area. Click on Save.
    7. After saving the project area, process roles have to be assigned to the members of the project area.
    8. Process Roles screen capture

    9. Click on Process Roles. You can add the process roles to each of the members of the project in Process Roles editor. Click OK.
    10. Process Roles Editor screen capture

    11. Save the project area.
    12. Under Roles and Permissions tab, you will see the roles and permissions created for this project area. These roles and permissions are inherited from the RRC Banking Template.
    13. ** You can also add new roles for this project area in the web.

      Project Area screen capture

    RRC Project template

    Project template can be created from an existing project and the elements of the project can be selected to include in the template. These elements can be included or excluded: artifacts, artifact templates, artifact types and attributes, links between artifacts, link types, folder structure, tags, and shared saved filters. Templates once created cannot be modified.

    To create and manage project templates, the user must have JazzAdmins repository permissions, an Analyst client access license, and the Administrator role in the project.

    Create a base project with the standard folder structure

    1. Navigate to application administration page (https://[fully qualified hostname]:9443/rm/web for Requirements Management).
    2. On the Administration icon, click on Create Project Area.
    3. Name the project area as Sample Banking Req Project. Click Next.
    4. Create Requirements Project screen capture

    5. Select the template for the project area. Click Finish
    6. Select Project Template screen capture

    7. In the Artifacts page, create the folder structure by right clicking the Sample Banking Req Project.
    8. Folder Structure screen capture

      *Place some standard artifacts such as Use case specification document, Glossary etc in the folders.

    9. On the Administration icon, click on Manage Project Properties.
    10. On Manage Project Properties, click on Templates tab.
    11. Create New Template, by clicking on New Template tab.
    12. New Template screen capture

    13. Select the Base Project for the template. Here the base project is Sample Banking Req Project. Name the template as “Banking Project Template”. Select all the elements to include for this template. Click OK.
    14. New Project Template screen capture

    15. You can see the newly created Banking Project Template in the Templates section.
    16. **RRC 4.0 provides the feature to download the project template. Like process templates, project templates can also be exported and shared with other repositories.

    Create a new project area using Banking Project Template (base project)

    1. On the Administration icon, click on Create Project Area.
    2. On the New Project Window , provide the project name as Requirement Project for Banking Domain. Click Next.
    3. Choose Banking Project Template for the project area Test Project for Banking ISU. Click Finish.
    4. Banking Project Template screen capture

    5. After several moments, Requirement Project for Banking Domain project area will be created with the folder structure inherited from Banking Project Template.
    6. Requirment Project for Banking Domainscreen capture

    Benefits of Customizing RRC Process template and Project template

    1. Teams enforcing customized templates to initialize project area will be able to start their project quickly since the customized template will have the roles and permissions and also the project structure specific to the ISU.
    2. Customized templates can be shared across project areas. Using templates to create new projects saves time by reducing the amount of redundant work that’s involved to produce the same project initialization.
    3. Templates customized will have ISU specific project structure, which will assist the team to store real time artifacts in respective folders without the need to freshly create them from scratch. Also packages, project structures, internal default artifacts in the template will follow the standard best practices, thereby allowing user to follow the similar standards while creating future real time artifacts.

    **Disclaimer: RRC does not use process templates the same way as RTC/RQM. Also, editing the default process template may cause upgrade challenges in the future.

    For more information

    About the author

    Suma S R is a member of Tata Consultancy Services IBM Rational Technology Excellence Group (TEG). The Tata Consultancy Services IBM Rational Technology Excellence Group (TEG) is a team of experts on Rational software products and technology. The team has several breakthrough projects and several successful assignments to their credit. TEG focuses mainly on solution development and research into industry best practices, in addition to training and mentoring the project teams and consultants. She can be contacted at

    Was this information helpful? Yes No 5 people rated this as helpful.