With the latest May 2015 update of our list of requirements management (RM) tools we newly included two requirements solutions that are add-on products to Atlassian JIRA: RMsis by Optimizory Technologies Pvt. Ltd. and Requirements for JIRA by ease solutions Pte Ltd. This blog article introduces RMsis. Requirements for JIRA will follow in a separate article.
RMsis Availability and Vendor
RMsis is an add-on product to Atlassian JIRA on-premise installations. It plugs into JIRA as a separate sub-product coming with its own user interface, data structures, user roles, and access rights. JIRA issues can be linked from RMsis items (e.g., requirements), and RMsis items can be exported into JIRA issues. Besides RM functionality, RMsis provides support for testing.
The initial release 0.2 of RMsis was made available in October 2010. The current major release 1.8.0 dates from March 2015 with two additional updates since. RMsis vendor Optimizory is located in New Delhi, with consulting partners in Singapore, India, Germany, the Benelux countries, and Turkey.
RMsis Features, Information Model, and User Interface
Important features of RMsis according to the product page at Atlassian Marketplace are:
- Flexible information model
- Requirement versions, baselines, and branches
- Cross project dependencies between requirements
- Traceability between RMsis artifacts with JIRA artifacts and RMsis test cases
Information model: RMsis’s information model is based on a general type of requirement, which comes with a set of default attributes. Attribute values of these default attributes can be customized, and additional attribute types can be added. Requirements hierarchy can be expressed using parent/child relationships and via assignment of hierarchical tags. Child requirements are the actual items that contain detailed requirements information.
User interface: The main requirements view of the user interface is a tabular presentation similar to a spreadsheet table. There is one view for each of the two predefined requirements categories of unplanned and planned requirements. Within these table views, table columns correspond with requirements attribute types.
I could not run a trial-use of RMsis, yet. So the information provided in this article is based on the vendor’s sources available in the public domain, which are relatively rich and detailed.
While the list of RMsis product features is long, I am not always convinced of their implementation: Overall, RMsis makes some strong assumptions on requirements structure and process that cannot be changed. So, interested customers should carefully check whether the tool meets their way of working. One should also be aware that RMsis is a separate system running within JIRA, adding its own configuration needs and usage concepts. On the plus side are that RMsis has quite a long track record and a relatively large user base, and that it includes basic support for testing and test management.
Product homepage at Atlassian Marketplace: https://marketplace.atlassian.com/plugins/com.optimizory.rmsis.plugin.jira-rmsis
Product homepage at vendor site: http://products.optimizory.com/rmsis
Product documentation of latest release: http://docs.optimizory.com/display/rmsis/RMsis+Documentation+-+Latest+Release