Administering projects

Project administrators are responsible for creating and maintaining project areas. A project area is an area in the repository where information about one or more software projects is stored. A project area defines the project deliverables, team structure, process, and schedule.

Each CLM application (Change and Configuration Management, Requirements Management, and Quality Management) uses project areas to organize teams' work. You access all project artifacts, such as plans, work items, requirements, test cases, and files under source control within the context of a project area. Typical project administrator tasks include:
  • Adding users as members of project areas.
  • Assigning roles to members.
  • Creating team areas.
Each project area has a process, which governs how members work. As project administrator, you customize the process to meet your team's needs. For example, the project area process defines:
  • 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 project areas in each application by using the project area editor. However, a more efficient method is to use the Lifecycle Project Administration user interface 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 those project areas. Associations enable linking of artifacts, such as requirements, development work items, and test cases, across project areas. From within a lifecycle project, you can manage membership and role assignments for each of the constituent project areas.