DevEX - reference for building teams, processes, and platforms
RMsis Overview
1. RMsis – v 1.8.0
Simplify Requirement Management for JIRA
2. RMsis for JIRA is
an enterprise class application
designed specially to complement JIRA
capable of handling 10’s of thousands of
Requirements per project.
built to simplify Requirement Management
at a price point which makes it accessible to
thousands of users
3. Managing moderate to large number of
Requirements emerging from different sources.
Establishing and managing baselines to enforce
agreements between multiple stakeholders.
Managing evolution of Requirements
Establishing, documenting and publishing
forward and reverse traceability between
Requirements as well as other artifacts.
Ensuring contract compliance in large and
complex contracts.
4. Define a flexible information model, as per your own needs.
Create, elaborate, analyze and manage all requirements on a single page.
Create requirement baselines, versions and branches.
Establish cross project dependencies between Requirements.
Manage real time requirement traceability with JIRA artifacts and test
cases
Maintain oversight from requirement perspective for a Product Release.
Create test cases and link with requirements.
Create Test Runs for repeated validation and determine regression
status.
Plan your key milestones and product releases.
Ensure effective collaboration between users by sharing the current state
of Requirements, which can be referenced, reviewed or commented upon.
8. 1. Right click on the requirement
2. Select add requirement above/below
3. Enter requirement ID to move
Movement of Requirement within Planned
Requirement
9. • Add requirement dependencies
• RMsis automatically takes care of cyclic dependencies
Requirement Dependencies
12. RMsis maintains a list of sources
A requirement can be mapped to a source
Specify source of a Requirement
13. View Requirement Links and Dependencies.
View traceability of issues/bugs/tasks against requirements.
Any custom type of JIRA issue can be traced.
Requirement Traceability
14. Already linked issues can be viewed and new issues can be added.
Traceability: Linking Issues
15. Traceability view can be extended with Requirement Attributes
User can set filters for each of these attributes
Filters on Extended Traceability view
16. View status of all the issues associated with a Release
View Requirements and Test cases associated with any given JIRA issue
This view effectively points to the health of a Release
Reverse Traceability
19. Manager can create baseline and provide a name to it.
Baseline: Create Baseline
20. Create new releases within RMsis or sync with JIRA versions
Planned and Actual effort is automatically updated from associated Requirements and Artifacts
Release Management
21. Map Test Cases to Requirements
Map Artifacts (Issues) to Test cases
Specify Test Cases
22. Also define rules to compute the Test Case status from Test Steps.
Specify Steps within Test Cases
23. Create, Edit, Status Update, Copy, Commit a Test Run
Map Issues to Test Runs
Automatically generate Issues for failed Test Cases
Create and Manage Test Runs
30. Default Roles
◦ Administrator
Acts like a Tool Admin.
◦ Product Manager
Owner of Requirements in the Project
Also referred as Project | Requirement Manager
◦ Analyst
◦ Team Member
◦ Customer
◦ Test Manager
◦ Testing Team Member
◦ Tester
Permissions given to Default Roles can be changed by
Administrator.
Custom Roles can be defined by Administrator.
38. RMsis Home
http://products.optimizory.com/rmsis
RMsis Documents
Latest Release :
http://docs.optimizory.com/display/rmsis/RMsis+
Documentation+-+Latest+Release
Functions included in Releases :
http://docs.optimizory.com/display/rmsis/Summar
y+of+RMsis+Releases
RMsis at Atlassian Marketplace
https://marketplace.atlassian.com/plugins/com.opt
imizory.rmsis.plugin.jira-rmsis
Hinweis der Redaktion
Thanks for your time and interest !
Finally, we want to ensure that we build products, which really solve your problems.
So, if you have any open issues, please feel free to contact our support team.