This topic contains examples of a scenario where you have
two projects, each corresponding to a different system.
Projects: SystemA and SystemB.
Roles: Contributor, Tester, Developer, ProjectManager, CCB
Privileges: submitter, verifier, reviewer, assigner, resolver,
concluder.
Groups:
- SystemA_Tester, SystemA_Developer, SystemA_CCB
- SystemB_Tester, SystemB_Developer
Role definitions (role: privilege…)
Contributor:
submitter
Tester: submitter, verifier, concluder
Developer:
submitter, verifier, resolver
ProjectManager: submitter, assigner
CCB:
reviewer
Project definition for SystemA
Contents
(CRs Included in this Project): product_name=”SystemA”
Members
and Privileges:
- Group SystemA_Tester has the role Tester
- Group SystemA_Developer has the role Developer
- Group SystemA_CCB has the role CCB
- User Frank has the role ProjectManager
Project definition for SystemB
Contents
(CRs Included in this Project): product_name=”SystemB”
Members
and Privileges:
- Group SystemB_Tester has the role Tester
- Group SystemB_Developer has the role Developer
- User Lisa has the role ProjectManager
Global assignments
The pseudo-group Everyone
has the role Contributor
Observations about this example:
- Anyone in the system can submit CRs for either project, which
is achieved through a global assignment.
- Since each project has only a single project manager, those roles
are assigned directly in the project to the individual.
- Project-specific groups were created. The same roles are bound
to different (but related) groups.
- To bring a new developer on to the project SystemA, create the
user in Rational® Directory
Server and assign the user to the group SystemA_Developer.