Insights with RMsis Custom Reports
Users desire flexibility in reporting, which meets their own Project and Organizational needs. RMsis provides custom reporting feature from version 1.5.0 onwards and this simple yet powerful feature can cover almost 90% of the reporting needs for most users. In this article, we present few possibilities, which represent some of the most common use cases.
Release Management
Requirements and Issues included in a Release
This report can be used to generate raw data for Release Notes OR identifying the Requirements and Artifacts (newly) included in the latest Release. To create this report, choose the following options:
Entity | Attribute/Column | Value |
---|---|---|
Release | Name | DESIRED_RELEASE_NAME |
Requirement | ID | - |
Requirement | Type | REQUIREMENT |
Requirement | Summary | - |
Requirement | Status | CLOSED |
Artifact | ID | - |
Artifact | Summary | - |
Artifact | Status | CLOSED |
A view of the report is shown below:
Incomplete Requirements and Issues
This report can be used to generate a view of Pending Requirements and Issues in the Target Release. To create this report, choose the following options:
Entity | Attribute/Column | Value |
---|---|---|
Release | Name | DESIRED_RELEASE_NAME |
Requirement | ID | - |
Requirement | Type | REQUIREMENT |
Requirement | Summary | - |
Requirement | Status | OPEN |
Artifact | ID | - |
Artifact | Summary | - |
Artifact | Status | OPEN | REOPENED | IN_PROGRESS |
A view of the report is shown below:
Requirements Management
Filtering High Priority Requirements
To keep track of High Priority Requirements, which should be taken up next for implementation, choose the following options for your report.
Entity | Attribute/Column | Value | Sort |
---|---|---|---|
Requirement | ID | - | - |
Requirement | Type | REQUIREMENT | - |
Requirement | Summary | - | - |
Requirement | Effort | - | Ascending |
Requirement | Priority | BLOCKER | CRITICAL | - |
Requirement | Criticality | HIGH | - |
Requirement | Feasibility | YES | - |
Requirement | Status | OPEN | - |
Including all the Linked Requirements in a Release
Many a times, a Product Manager is faced with a situation, where he /she wants to ensure that all the low level requirements (in a requirement hierarchy) are included in a release. This ensures that a high level functionality is completely build into the product. The following dependency report can help the Product Manager, identify all the requirements which must be included:
Entity | Attribute/Column | Value |
---|---|---|
Requirement | ID | - |
Requirement | Type | REQUIREMENT |
Requirement | Summary | - |
Requirement | Depends on | - |
Requirement | Dependents | - |
Release | Name | DESIRED_RELEASE_NAME |
Note : Please note that Depends on / Dependent definition should be uniformly understood and implemented inside the organization.
Test Management
Requirements covered by Test Cases
This report can be used to list down the Requirements covered by Test Cases and hence determine which Requirements are not covered ! testers can use this information to determine additional Test Cases for the identified requirements.
Entity | Attribute/Column | Value |
---|---|---|
Requirement | ID | - |
Requirement | Type | REQUIREMENT |
Requirement | Summary | - |
Release | Name | DESIRED_RELEASE_NAME |
Test Case | ID | - |
Test Case | Summary | - |
Completeness of Testing for a Release
Before making a release, Product Manager needs to be sure that all relevant tests have been executed and passed. This report can be used to view the list of TC's which were either not executed OR which failed in one of the Test Runs corresponding to a release.
Entity | Attribute/Column | Value |
---|---|---|
Test Run | Name | DESIRED_TR1 | DESIRED_TR2 |
Test Run | Release | - |
Test Case | ID | - |
Test Case | Summary | - |
Test Case | Status | ??? | FAIL |