Create project area in Rational Team Concert.

Project area: A system representation of a software project. The project area defines the project deliverables, team structure, process, and schedule.

We can create the Project Area from jazz web client and we can also create the project area from the RTC eclipse client which is shown below. If we try to create the project area with same name is already created in the project area then we can't create the project area in the RTC with the same name in RTC.

In each of the Collaborative Lifecycle Management (CLM) applications, teams perform their work within the context of 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 the project deliverables, team structure, process, and schedule. We can access all project artifacts, such as iteration plans, work items, requirements, test cases, and files under source control within the context of a project area. Each project area has a process, which governs how members work. For example, the project area process defines:

User roles Permissions assigned to roles Timelines and iterations Operation behavior (preconditions and follow-up actions) for Change and Configuration

Management and Quality Management Work item types and their state transition models (for Change and Configuration Management

and Quality Management)

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 control settings and permissions. A project area cannot be deleted from the repository; however, it can be archived, which places it in an inactive state.

Project : Practice Project

To create the project area in the local Jazz repository we need to add the repository in the Repository connection of the RTC the snapshots are shown below while creating the local jazz repository in the RTC client.

Repository Connection:

A repository workspace on our machine is the replica of the repository workspace that is available on the server. We can create a repository workspace, and load the components that contain project artifacts. After working with the project artifacts, we can deliver them so that the artifacts in wer sandbox and in the repository workspace on the server are in sync.

We can create a repository workspace either from a stream or from My Repository Workspaces.

We will create the new jazz repository connection as shown below.

In the Team Artifacts tool window, right-click My Repository Work paces and click New Repository Workspace.

We can add new components to the empty repository workspace.

We will create the Jazz repository with following methods, by updating the URL, Name of repository and User ID and Password for the local jazz repository.

To create new repository conditions we have to select the Crate a new repository connection.

Now repository connection is successfully created in the Team Artifact tab as shown in the below,

To create the new project area we have to right click on repository connections and select New>Project Area as shown in below,

We created the new project area under the Practice Project name as shown in below,

Process templatesProcess templates provide a starting point and guide for a project area process configuration and iteration structure. They can include process documentation that is in HTML format. We apply a process template when we create a project area; the process can then be modified in the project area or its team areas, independent of the template.

We can create templates from scratch or from existing project areas. Templates are specified in XML by using a schema that can be extended by configuration point declarations. We can edit templates by using source and high-level editors.

Rational Team Concert™ includes a set of templates for common processes, such as Scrum and Formal Project Management. These templates have been externalized to support translation of text strings into numerous languages. When we create a project area and choose to deploy one of these templates, we can select the language. We can also externalize a process template that we create to support translated versions. Templates for additional processes can be downloaded from jazz.net.

Process

Right-click a repository connection in the Team Artifacts view and select New > Project Area. In the Create Project Area window, enter a name and optional summary for the project area

and click Next. If wer team does not have custom process templates in the repository, click the Deploy

Templates button to deploy the predefined templates to the repository as shown in below,

Select the template for the process that should govern the project area.

Formal Project Management Process.

Description:A traditional project management process where development progresses in sequential phases: Requirements, Design, Implementation, and Testing.

Use the Formal Project Management Process template to create a project area for traditional project management. In a formal project management process, instead of developing in iterations as we would in an Agile process, we track change management in sequential phases: Requirements, Design, Implementation, and Testing.

Team members complete each phase of a formal project management process before beginning the next phase. Each phase has specific target dates that the team observes to complete the project by the release date.

The Formal Project Management Process template provides the Milestone work item type, which identifies significant points or events in a project or project phase. We can use milestones to control the transitions between phases and to monitor the project progress.

The Formal Project Management process is also ready to use. This process provides the following work item types:

Defect: Identifies a bug Task: Describes a specific piece of work Project Change Request: Provides a formal mechanism to renegotiate key project parameters,

such as scope, timeline, or resources Business Need: Records commitments that the development team makes to the business

organization Risk: Describes project risks, and provides a matrix to calculate the risk probability and impact Risk Action: Describes specific actions to counter or mitigate a risk Issue: Identifies and describes a potential problem for which no concrete solution is proposed.

Issues can be created from risks that do not have a proposed solution. Milestone: Identifies a significant event in the project plan or a phase plan

Scrum

Description:A process template for Scrum. Scrum is a popular approach to manage projects in an agile way.

Unconfigured Process

Description:This process should be used for project areas that consume a shared process or that are used to manage work item access control. It does not provide any configuration.

Use the Unconfigured Process template if our project area will consume the process of another project area.

A project area can share its process so that other project areas can use that process rather than maintain their own process. This sharing feature allows us to centralize process in one project area. When we update the process in the sharing project area, all project areas that consume that process use the updated process.

When we create a project area, we must specify a process template. However, if wer new project area will consume the process of another project area, we can specify the Unconfigured Process template, which contains no timelines, iterations, roles, configured permissions, configured operation behavior, and work item types.

We created the Practice Project in the Formal Project Management process template

After this process we will found the new project area s created in the repository connection.

But only the Jazz admin is allow to create the new project area any Jazz User, Jazz Guest is not allow to create the new project area because only jazz admin has repository permissions to create the Project area.

In the below screen shot the user is only a Jazz Guest and Jazz User so user will not able to create a new project area.

If user tries to create the project area user will get the below error message while creating the project area.

So in this way the with the repository permission to jazz admin we successfully created the Project area as shown in the screen shot below.

We can see the different tabs in the Project area

Permissions :

Exploring the Project Area:

Starting with the Members Tab,

We can add the Member with the add option in the members Tab

We can add the members as per below window and we can deselect the members.

We can assign the Roles to the members as per below screenshot

We can see in the below screenshot the members are created as per project requirement.

And we can assign the Process Roles in the Members tab,

There are 8 predefined roles in the RTC as per process requirements which are explained as below:

Each project area and each team area can define a set of roles. The defined roles are visible in the area where they are declared and in all child areas. Roles defined in the project area can be assigned to users for the whole project area or they can be assigned in any team area. Roles defined in a team area can similarly be assigned in that team or in any child team. The ordering of roles in this section determines how they will be ordered in other sections of the editor, but it does not affect the process runtime.

Analyst:

Description : The person in this role represents customer and end-user concerns by gathering input from stakeholders to understand the problem to be solved and by capturing and setting priorities for requirements.

Architect :

Description : This role is responsible for defining the software architecture, which includes making the key technical decisions that constrain the overall design and implementation of the project.

Developer :

Description : This role is responsible for developing a part of the system, including designing it to fit into the architecture, possibly prototyping the user-interface, and then implementing, unit-testing, and integrating the components that are part of the solution.

Release Engineer :

Description : This role is responsible for developing a part of the system, including designing it to fit into the architecture, possibly prototyping the user-interface, and then implementing, unit-testing, and integrating the components that are part of the solution.

Stakeholder :

Description : This role is responsible for developing a part of the system, including designing it to fit into the architecture, possibly prototyping the user-interface, and then implementing, unit-testing, and integrating the components that are part of the solution.

Team Lead :

Description : This role technically leads a component and is responsible for planning and architectural integrity of the component.

Tester :

Description : This role is responsible for the core activities of the test effort. Those activities include identifying, defining, implementing, and conducting the necessary tests, as well as logging the outcomes of the testing and analyzing the results.

Project Manager :

Description : This role leads the planning of the project, coordinates interactions with the stakeholders, and keeps the project team focused on meeting the project objectives.

Administrators :

We can add the administrator with the administer as shown in below

Here we added two user as administrators and we can add multiple as per process requirements.

Timelines :

A timeline represents an area of activity within a project that typically has its own schedule, deliverables, teams, and process. For example, a project with both new product release development and current product maintenance might define these two efforts in separate timelines because they have different delivery schedules, teams, and processes. Within a timeline, we can create a hierarchy of iterations where top-level iterations represent releases and child iterations represent milestones within those releases.

We can also create the Timeline as per our requirement,

In the above screen shot we created the timeline as Process Requirement Timeline as the new timeline.

Timeline :

The project timeline defines a start and end date along with an iteration breakdown. Additional timelines can be defined to track secondary activities.

A timeline represents an area of activity within a project that typically has its own schedule, deliverables, teams, and process. For example, a project with both new product release development and current product maintenance might define these two efforts in separate timelines because they have different delivery schedules, teams, and processes. Within a timeline, we can create a hierarchy of iterations where top-level iterations represent releases and child iterations represent milestones within those releases.

We can designate one of our timelines as the project timeline. All of the predefined process templates except for the Unconfigured Process template specify a project timeline. The project timeline defines

the project area start and end dates along with the iteration breakdown of those dates. The project timeline differs from our other timelines in the following ways:

The project timeline iterations apply to the project area. This means that if the project timeline process is customized for the current iteration, that customized process affects any artifacts associated with the project area.

All team areas that do not have an explicit custom timeline set are governed by the process of the project timeline.

Below Screenshots shows the new timeline created under the Process Requirement.

We can also create the Iterations under the timeline as shown in above screen Shot.

Iteration and iteration types

Projects are organized into a series of development periods called iterations. Each timeline contains a hierarchy of iterations, which can define start and end dates.

An iteration hierarchy typically represents broad phases of a project, each of which is divided into a series of shorter iterations.

We can create iteration types and associate an iteration with an iteration type. For each iteration type, we can configure specific permissions and, for Change and Configuration Management and Quality Management project areas and team areas, operation behavior. Those permissions and behavior settings apply to all iterations of the iteration type. For example, wer organization might want to establish stricter control on deliveries towards the end of a release. To do this, we might create an iteration type with a name such as End Game, and configure the behavior for that iteration type to require team members to get approvals before delivering change sets. All iterations of the End Game iteration type would enforce that behavior.

- Bharat P Malge