Project areas and lifecycle projects

In Design Management and in the Rational® solution for Collaborative Lifecycle Management (CLM) applications, teams work within the context of a project area. A lifecycle project groups multiple project areas whose members collaborate with each other so that you can manage the project areas and their members from one central location.

A project area defines the deliverables, team structure, process, and schedule for a project. You access all project artifacts, such as designs, plans, work items, requirements, test cases, and files under source control within the context of a project area.

A project area is stored as a top-level or root item in a repository. A project area references project artifacts and stores the relationships between these artifacts. Access to a project area and its artifacts is controlled by access settings and permissions. A project area cannot be deleted from the repository; however, it can be archived, which places it in an inactive state.

Each project area has a process, which governs how members work. For example, the project area process defines these items:
  • User roles
  • Permissions assigned to roles
  • Timelines and iterations
  • Operation preconditions and follow-up actions
  • Work item types and their state transition models

You can create and manage project areas in Design Management, as well as the CLM applications, by using the project area editor. However, a more efficient method is to use the Lifecycle Project Administration application to create a lifecycle project. When you create a lifecycle project, you select a template that defines the project areas to create, the process to use for each project area, and the associations to establish between the project areas.

After you create a lifecycle project, you can use the Lifecycle Project Administration application to add users as members to one or more of the project areas that belong to the lifecycle project. You can also assign roles to those members for each project area.