Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

User defined in RMsis

Default Role Description

Administrator

  • Installs the system and manages, licenses, database backup, system upgrades etc
  • Identifies the system users.
  • Defines the access rights against a role.
  • Assigns users to projects.

** Please note that from RMsis 1.5.1-r69 onwards

  • Administrator has all the rights (regarding a project in RMsis) by default.
  • However the Administrator should be assigned at least one role in JIRA configuration (ex. jira-users) for this project.
  • These rights have to be explicitly turned off, if the Project Manager / Senior Managers want to give only a limited access to the Administrators.

Product Manager / Project Manager / Project Lead **/ Requirement Manager (as referred to in this document)

  • Owns all the requirements and artifacts mapped to the requirements.
  • Schedules releases and assigns requirements to the same,
  • Maintains an oversight of the product / project.
  • Assigns the role to users.
  • Defines the Baselines.

Team Member

  • Can contribute requirement(s)
  • Reviews the requirement(s) and can comment on the same.
  • Refers to the requirements for other downstream activities.
  • Can view Tests and Test Runs
Analyst
  • Can create, update and delete requirements.
  • Map requirements to Baselines.
Test Manager
  • Owns all Validation artifacts, including Tests and Test runs.
  • Defines, composes and commits Test Runs.
  • Manages artifacts associated with tests.
  • Can manage references to requirements.
Testing Team Member
  • Can create, update and delete tests.
  • Assign tests to test runs
  • Can manage artifacts associated with tests.
  • Can manage references to requirements.
Tester
  • Executes the tests.
  • Can log issues against a Test Case in Test Run.

Customer

  • Has limited RW access, as defined by the administrator.
  • Can contribute requirement(s)

Note **: Also referred as Requirement Manager in document.


These users can map into various designations / roles for your specific context. Some examples of this mapping are enumerated below:

...

Default permissions and their assignment to roles is specified hereat Permissions, and their assignment to Roles.