Configuring the environment
This topic describes how to set up the server environment, create project areas, create users, and assign process roles to those users. You assign roles to users so that they have the required permissions to work on artifacts in the project areas.
Typically, the server administrator runs the server setup wizard and creates user accounts. The project administrator creates projects, assigns members to the projects, and assigns roles to members.
Before you begin
Before you can configure your environment, you must install the Jazz® Team Server and the Change and Configuration Management (CCM), Quality Management (QM), and Requirements Management (RM) applications. Then set up the database and deploy and start the Jazz Team Server.
Step 1: Run the server setup wizard
For the Jazz Team Server and each of the applications, the server setup wizard guides you through the process of configuring the database connection, the data warehouse connection, email notification, and the user registry. The wizard detects the applications that you have installed (CCM, QM, and RM) and registers them with the Jazz Team Server.
Step 2: Create users
For each of the users who will work in the applications that you installed, create user accounts. Because user records are synchronized between the Jazz Team Server and the applications registered with it, you can create users through the administrative user interface of the Jazz Team Server or the administrative user interface of any of the applications.
When you create a user, you assign one or more client access licenses (CALs) and a repository group. The repository group assignment controls the level of access that the user has to the repository. The CAL assignments control the level of access that the user has to the capabilities provided by the applications.
Step 3: Create projects
For each application, you must create a project area. A project area is an area in the repository where information about one or more software projects is stored. A project area defines deliverables, team structure, process, and schedule. You can create project areas through the project administration user interface in each application. However, a more efficient way to create and manage project areas is to use the Lifecycle Project Administration user interface.
The Lifecycle Project Administration user interface uses the notion of 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 one central location, the lifecycle project. When you create a lifecycle project, you can select a template that is used to create project areas in the change and configuration management, quality management, and requirements management applications. When these project areas are created, associations are created between them so that you can link artifacts, such as requirements collections, development plans, and test plans to each other.
After you create the lifecycle project, you can use the user interface to add users as members to each of the project areas that belong to the lifecycle project.
Step 4: Assign roles
After you add users as members to the change and configuration management, quality management, and requirements management project areas, you must assign roles to the members within the project areas. Each role has a set of permissions, which determine which actions, such as creating and modifying artifacts, the member can do within the project area.
From within the Lifecycle Project Administration user interface, you can assign roles to users in each of the project areas that belong to the lifecycle project.
By completing this task, you have configured the server and applications; created user records; created change and configuration management, quality management, and requirements management project areas and a lifecycle project through which you can manage them; added members to the project areas; and assigned roles to the members.
What to do next
Now you are ready to plan the project, which includes defining requirements, creating a release plan, and creating a test plan.