ReqSuite® RM 3.1 offers the following new features and functions
Improved review support
In ReqSuite® RM 3.1, the existing workflow was optimized with regard to review support.
In a project template, it is now possible to define under “States” that a state explicitly serves a review. If an element is set to this state, all persons assigned as “reviewers” in a project are automatically invited to submit a review. This review can then be done using the comment function in the editing window of each element.
ReqSuite® RM now offers a new field type “Richtext”. Fields of this type can now be used to enter text formatting, enumerations and tables.
To activate this function, the corresponding attributes of a category must be set to the data type “RICHTEXT”.
Starting with ReqSuite® RM 3.1, elements of a category for which a workflow has been defined can be visualized not only in tabular form but also in the form of a (Kanban) board. For this purpose, ReqSuite® creates a column in the board for each status.
To use this function, the user can switch the tabular display to the board display in the tab of a category.
For each element in ReqSuite® RM you can now set a deadline. If the element has not been completely processed by this date, the user responsible for the element will automatically receive a notification.
Extended dependency graph
The graph for displaying the dependencies of an element has been extended in ReqSuite® RM 3.1. It is now possible to filter the dependent elements or set the dependency depth. Furthermore, implicit dependencies to elements of the same category can be revealed.
Under the menu item “Views”, users can now view the last ten items they have opened. This makes it easier to follow their own work steps.
Similar to TFS or Azure DevOps and JIRA, ReqSuite® RM 3.1 now also offers an interface to GitLab. This interface can be configured like the two interfaces mentioned above.
Display of Git Commits
If an interface to TFS or Azure DevOps or GitLab has been configured and the underlying Git repository is used, it is possible to display the git commits associated with an element in the editing window. To do so, enter the ID of the addressed element with a hash sign in front of it in the change description of a git commit, e.g. #FR25
Improved Enterprise Architect add-in
The Addin for Enterprise Architect, which has been implemented as a prototype for some time, was completely revised in ReqSuite® RM 3.1 and now allows a more flexible mapping of elements from ReqSuite® to modeling constructs in Enterprise Architect.
To do this, the respective model or diagram type must be set in the respective project template for categories, relationships and the diagrams to be used. For example, a category “Usage Scenarios” can be declared as model type “UML_UseCase” in ReqSuite®, whereby the addin can automatically create use cases from this in Enterprise Architect.
In addition to the main changes mentioned above, there are a number of other minor changes in ReqSuite® RM 3.1. of which the most important are listed below.
By default, ReqSuite® RM no longer displays all columns for clarity reasons. However, the user can show additional columns and save the individually desired display as his own view.
Save without closing
In the editing window of a single element it is now possible to save changes without closing the window. For this purpose the “Save” button has been divided.
Rows per table page
In the tabular display of elements of a category, you can now individually set how many elements should be displayed on a page. In the kanban board, the user can alternatively choose between the first 20 of each column and “all”.
Check for Excel export
The direct export to Excel via the button above the table view can now be filtered to the selected elements. However, this does not affect the Excel export, which can be accessed via the main menu “Export / Imports -> Excel”.
New specification markers
The markers for the Word export have been extended by “SORT BY” and “DOCUMENT_VERSION”.
With “SORT BY” tables can now be sorted by attributes, e.g. “###USE CASE:TABLE WITH ID, NAME, DESCRIPTION, ACTOR SORT BY ACTOR###. The marker “DOCUMENT_VERSION” can be used to assign specific version numbers to individual documents when generating baselines. These numbers may differ from the actual baseline number and are instead based on the changes compared to the previous document version.
Quality check directly in the editing window
The results of ReqSuite® RM’s unique quality checker are now immediately displayed in the editing window of each element. A project-wide overview is still available under the menu item “Assistance -> Quality Inspection”.
Floating users who explicitly forget to log out will be automatically logged out 12 hours after their login. This ensures that no licenses will be blocked in the long term in the event of the loss of one person.
The visual customizing of ReqSuite® RM has been enhanced to allow client administrators to customize not only the colors but also the product title in the ReqSuite® RM header to give the solution a company-specific name as needed.
The dashboard was slightly optimized in ReqSuite® RM and provided with additional explanations.
Active Directory groups
Until now, when connecting to Active Directory, users had to be assigned to several groups to determine their general usage rights of ReqSuite® as well as their specific role in the tool. Starting with ReqSuite® 3.1, it is sufficient to assign users only to the role-specific group.