By default, rmCloud starts out with two requirement types:
That works for many teams, but often you’ll need to make some changes. By navigating to Settings → Apps → rmCloud → General Configuration, you’ll be able to
Rename requirement types and/or their prefixes
Add additional requirement types
Tweak the hierarchy of the requirement types as shown in the Traceability Matrix
Renaming Requirement Types
On the rmCloud General Configuration page (Settings → Apps → rmCloud → General Configuration), simply click “Edit” next to the requirement type you’d like to make changes to.
When you’ve edited the name to your liking, hit “Submit” to save it:
Add Additional Requirement Types
To add more than the default requirement types, go to the rmCloud General Configuration page (Settings → Apps → rmCloud → General Configuration) and click “New requirement type”
Select a name and prefix, and “Submit”. Done!
Editing Requirement Type Hierarchy
By default, there’s a very simple hierarchy of Business Requirement (higher level) → Software requirement (lower level).
If you add additional requirement types (see above) and you need to make changes to the way the hierarchy is displayed in the Traceability Matrix, you can do that. Go to the rmCloud General Configuration page (Settings → Apps → rmCloud → General Configuration) and click “Edit” next to the requirement type you’d like to update the hierarchy for.
Note: A requirement of a given type can only be linked to adjacent types. For example. if there are three requirement types with levels 1, 2, and 3, the requirements with the level 3 type can only be linked to requirements of the level 2 type.
By default, each additional requirement type added will be added to a new level of the hierarchy.
If your requirement types look like this:
Your matrix will look like this:
If you’re ever trying to do something that doesn’t seem to be supported by the app, contact us (Get Help in the app) and we’ll try to help.