Creating Repository & Project area and exploring the project area in Rational Team Concert.

Create project areainRational Team Concert.
Project area: A systemrepresentationof asoftware project.The projectareadefinesthe project
deliverables,teamstructure,process,andschedule.
We can create the ProjectAreafrom jazzwebclientandwe can alsocreate the projectareafrom the
RTC eclipse clientwhichisshownbelow.If we tryto create the projectarea withsame name isalready
createdinthe projectareathenwe can't create the projectarea inthe RTC withthe same name inRTC.
In eachof the Collaborative Lifecycle Management(CLM) applications,teamsperformtheir work within
the contextof a projectarea.A projectareais an area inthe repositorywhere 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 itemtypesandtheirstate 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
artifactsand storesthe relationshipsbetweentheseartifacts.Accessto 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 projectareain the local Jazz repositorywe needtoaddthe repositoryinthe Repository
connectionof the RTC the snapshotsare shownbelow whilecreatingthe local jazzrepositoryin the RTC
client.
Repository Connection:
A repositoryworkspace on ourmachine isthe replicaof the repositoryworkspace thatis
available onthe server. We cancreate a repositoryworkspace,andloadthe componentsthatcontain
projectartifacts.Afterworkingwiththe projectartifacts, we candeliverthemsothatthe artifactsin wer
sandbox andinthe repositoryworkspace onthe serverare insync.
We can create a repositoryworkspace eitherfromastreamor from My RepositoryWorkspaces.

We will create the newjazzrepositoryconnectionasshownbelow.
In the Team Artifacts tool window, right-click My Repository Work paces and click New Repository
Workspace.
We can add newcomponentstothe emptyrepositoryworkspace.

We will create the Jazzrepositorywithfollowingmethods,byupdatingthe URL,Name of repositoryand
User ID and Password forthe local jazz repository.

To create newrepositoryconditionswe have toselectthe Crate a new repositoryconnection.

Nowrepositoryconnectionissuccessfullycreatedinthe TeamArtifacttabas showninthe below,
To create the newproject areawe have to rightclick onrepositoryconnectionsandselectNew>Project
Areaas showninbelow,
We createdthe newprojectareaunderthe Practice Projectname as showninbelow,

Process templates
Process templates provide a starting point and guide for a project area process configuration and
iterationstructure.Theycaninclude process documentationthatisin 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 templatesfromscratchor from existingprojectareas. 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
ProjectManagement.These templateshave beenexternalizedtosupporttranslationof text strings into
numerouslanguages.When we create aprojectarea 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.Inaformal projectmanagementprocess,insteadof developingin 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
nextphase.Each phase hasspecifictargetdatesthat the team observes to complete the project by the
release date.
The Formal Project Management Process template provides the Milestone work item type, which
identifiessignificantpointsoreventsinaprojector projectphase. We can use milestones to control the
transitions between phases and to monitor the project progress.
The Formal ProjectManagementprocessisalsoready 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:Identifiesanddescribesapotential 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 processtemplate forScrum.Scrumis a popularapproachto manage projectsinan agile way.
Unconfigured Process

Description:
Thisprocessshouldbe usedforprojectareas thatconsume a sharedprocessor that are usedto manage
workitemaccesscontrol.It doesnot provide anyconfiguration.
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 createdthe Practice Projectinthe Formal ProjectManagementprocesstemplate
Afterthis processwe will foundthe newprojectareascreatedinthe repositoryconnection.

But onlythe Jazz adminisallowtocreate the new projectareaany JazzUser, JazzGuest isnot allowto
create the newprojectarea because onlyjazzadminhasrepositorypermissionstocreate the Project
area.
In the belowscreenshotthe userisonlya Jazz Guestand JazzUser so userwill notable tocreate a new
projectarea.

If user triestocreate the projectareauser will getthe below errormessage whilecreatingthe project
area.

So inthisway the withthe repositorypermissiontojazzadminwe successfullycreatedthe Projectarea
as showninthe screenshot below.

We can see the differenttabsinthe Projectarea
Permissions:

Exploring the Project Area:
Startingwiththe MembersTab,
We can add the Memberwiththe add optioninthe membersTab

We can add the membersasperbelowwindow andwe candeselectthe members.

We can assign the Rolestothe membersasperbelow screenshot

We can see inthe belowscreenshotthe membersare createdasperprojectrequirement.

Andwe can assignthe ProcessRolesinthe Memberstab,
There are 8 predefinedrolesinthe RTC as perprocessrequirementswhichare explainedasbelow:
Each projectarea and eachteam areacan define asetof roles. The defined roles are visible in the area
where theyare declaredandinall childareas.Rolesdefinedinthe projectareacan 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
similarlybe assignedinthatteamor in anychildteam.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 personinthis role representscustomerandend-userconcernsbygatheringinputfrom
stakeholderstounderstandthe problemtobe solvedandbycapturingandsettingprioritiesfor
requirements.
Architect:
Description:Thisrole isresponsiblefordefiningthe softwarearchitecture,whichincludesmakingthe
keytechnical decisionsthatconstrainthe overall designandimplementationof the project.
Developer:
Description:Thisrole isresponsiblefordevelopingapart of the system, includingdesigningittofitinto
the architecture,possiblyprototypingthe user-interface,andthenimplementing,unit-testing,and
integratingthe componentsthatare partof the solution.
Release Engineer:
Stakeholder:
Team Lead:
Description:Thisrole technicallyleadsacomponentandisresponsibleforplanningandarchitectural
integrityof the component.
Tester:
Description:Thisrole isresponsibleforthe core activitiesof the testeffort.Those activitiesinclude
identifying,defining,implementing,andconductingthe necessarytests,aswell asloggingthe outcomes
of the testingandanalyzingthe results.
ProjectManager :

Description:Thisrole leadsthe planningof the project,coordinatesinteractionswiththe stakeholders,
and keepsthe projectteamfocusedonmeetingthe projectobjectives.
Administrators :
We can add the administratorwiththe administerasshowninbelow
Here we addedtwo useras administratorsandwe canadd multiple asperprocessrequirements.

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 differentdeliveryschedules,teams,andprocesses.Withinatimeline, we can create a hierarchy of
iterationswhere top-level iterationsrepresentreleasesandchilditerationsrepresentmilestones within
those releases.

We can alsocreate the Timelineasperour requirement,
In the above screenshotwe createdthe timelineas ProcessRequirement Timelineasthe new timeline.
Timeline :
The projecttimeline definesastartand enddate along withan iterationbreakdown.Additional
timelinescanbe definedtotracksecondaryactivities.
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 differentdeliveryschedules,teams,andprocesses.Withinatimeline, we can create a hierarchy of
iterationswhere top-level iterationsrepresentreleasesandchilditerationsrepresentmilestones within
those releases.
We can designate one of ourtimelinesasthe projecttimeline. All of the predefined process templates
exceptforthe 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 projecttimeline iterationsapply tothe projectarea. 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 teamareas 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 alsocreate the Iterationsunderthe timeline asshowninabove screenShot.
Iteration and iterationtypes
Projectsare organizedintoa seriesof developmentperiodscallediterations.Eachtimeline containsa
hierarchyof iterations,whichcandefinestartandenddates.

An iterationhierarchytypicallyrepresentsbroadphasesof aproject,eachof whichisdividedintoa
seriesof shorteriterations.
We can create iterationtypesandassociate aniterationwithaniterationtype.Foreachiterationtype,
we can configure specificpermissionsand,forChange andConfigurationManagementandQuality
Managementprojectareasand teamareas,operationbehavior.Those permissionsandbehavior
settingsapplytoall iterationsof the iterationtype.Forexample, werorganizationmightwantto
establishstrictercontrol ondeliveriestowardsthe endof arelease.Todothis,we mightcreate an
iterationtype withaname such as End Game,and configure the behaviorforthatiterationtype to
require teammemberstogetapprovalsbefore deliveringchange sets.Alliterationsof the EndGame
iterationtype wouldenforce thatbehavior.
- Bharat P Malge

Creating Repository & Project area and exploring the project area in Rational Team Concert.

Recommended

More Related Content

Viewers also liked (7)

Similar to Creating Repository & Project area and exploring the project area in Rational Team Concert. (20)

Recently uploaded (20)

Creating Repository & Project area and exploring the project area in Rational Team Concert.