Administering lifecycle projects
In the Lifecycle Project Administration (LPA) user interface, you can create and manage project areas, from multiple applications, and establish associations between those project areas. For example, you can use the LPA user interface to create and manage a change and configuration management project area, a quality management project area, a requirements management project area, and an architecture management project area, and establish associations between each of those project areas.
Creating project areas within a lifecycle project
LPA implements a lifecycle project to manage your project areas. A lifecycle project groups multiple project areas that collaborate with each other. Rather than managing each project area separately, you can manage all of the project areas from this central lifecycle project.
After associations are established between project areas, you can link their artifacts to establish traceability across the requirements, development, and testing phases of the application development lifecycle. For example, you can link requirements to work items that describe the development work being done to implement the requirements. You can also link work items to test cases that verify whether the implementation is successful.
Using templates to create lifecycle projects
When you create a lifecycle project, you select a lifecycle project template, which specifies which project areas to create and which associations to establish between those project areas. The Lifecycle Project Administration user interface includes a set of predefined lifecycle project templates. You can also import customized lifecycle project templates.
Managing users across project areas
Project administrators can add users as members of their project areas. Likewise, team leaders can add users as members of their team areas. These members can be assigned different roles. Each role has a set of permissions that determine which actions the role can perform. In a cross-application environment, each project area has its own roles and permissions. For a user to work on linked artifacts in each project area, the user must have sufficient roles and permissions in each project area.
In the Lifecycle Project Administration user interface, you can view and modify the roles assigned to users across a set of project areas. You can also configure rules that specify which combination of process roles members should have across the project areas. The Lifecycle Project Administration user interface then flags users who do not have those process roles. In this way, the Lifecycle Project Administration user interface helps you to avoid problems where members do not have the permissions needed to do their work.
For example, your lifecycle project might have a change and configuration management project area and a quality management project area. To associate change and configuration management work items with quality manager test cases, a user might need the Team Member role in the change and configuration management project area and the Test Team Member role in the quality management project area. You can configure a rule that specifies this requirement.
Additionally, you can search for a user and then add that user to the lifecycle project. When you add a user to the lifecycle project, the user is added to each of the project areas that belong to the lifecycle project.
Adding existing project areas to a lifecycle project
In addition to using the Lifecycle Project Administration user interface to create project areas, you can also use it to add existing project areas to a lifecycle project so that you can manage them from that central location. For example, your organization might have change and configuration management and quality management project areas that have associations established between them. Over time, you might add users to both project areas, and you should ensure that they have the necessary roles and permissions to work on artifacts across those project areas. You could add those project areas to a lifecycle project and more easily manage those users.