February 28, 2014
Rational Requirements Composer
Definition · Management · Analysis
Rational Requirements Composer 4.0 M7 Milestone
Rational Requirements Composer 4.0 M7 "New and Noteworthy"
Rational Requirements Composer is an integral part of the CLM 2012 solution, which provides seamless integrations for application lifecycle management, with reduced cost of ownership and administration, improved cross-product visibility and reporting, and lifecycle integrations.
Rational Team Concert, Rational Quality Manager, and Rational Requirements Composer share a common set of server applications with each product offering role-based licenses that permit access to different capabilities provided by the applications. Therefore you should also read the New & Noteworthy page for Jazz Foundation 4.0 M7 and unless you elect to not install the Change & Configuration Management and the Quality Management applications, you should also read the pages for Rational Team Concert 4.0 M7 and Rational Quality Manager 4.0 M7.
- Write Access
- All Projects Page
- Requirements Parsing
- Multiple File Upload
You can now set the permissions for a project role for the members of a project or a team area:
Context menu for folders are now enabled or disabled based on the associated process area assignments:
- New Folder: This item is enabled if the process area of the folder has "Save Folder/Create a folder" enabled.
- Delete: This item is enabled if the process area of the folder has "Save Folder/Delete a folder" enabled.
- Move: This item is enabled if the process area of the folder has "Save Folder/Delete a folder" enabled and the destination folder's process area has "Save Folder/Create a folder" enabled.
- Rename: This item is enabled if the process area of the folder has "Save Folder/Modify a folder" enabled.
You can find these process area permissions on the Jazz admin UI Permissions tag page of a team area or project.
When you move an artifact, the following checks are now performed:
- The "move artifact" action is enabled only if the user has permission to delete an artifact that is of the artifact type of the artifact from the containing folder. This permission is based on the process area of the containing folder.
- The "destination folder" is restricted to only those folders whose process areas support creating the artifact type of the artifact.
When you copy an artifact, the destination folder that you select is now restricted to a folder whose process area states that the artifact type of the source can be created. For example, if you are attempting to copy an Actor artifact, the process area of the target folder must have "Create an artifact / Create an artifact of a specific type / Create Actor artifact" enabled.
When you create an artifact, you are now restricted to only creating an artifact of one of the artifact types that are enabled for creation according to the process area of the target folder. For example, if you are attempting to create an Actor artifact, the process area of the target folder must have "Create an artifact / Create an artifact of a specific type / Create Actor artifact" enabled.
Users using the "Contributor" license no longer inappropriately see create/delete/modify operations as enabled. This was an issue in the previous M5 build, where these checks were not enabled. In this milestone, these "Contributor" checks have been added back.
You can search for string values in a module by using the Find/Replace dialog. To open that dialog, on the Module toolbar, click the Find button. Because the Find/Replace window is modeless, it can be left open while you edit the module. The Find operation starts from the row that has focus and moves forward or backward across rows, depending on the dialog setting. Content and String attribute columns are searched. You can replace single values within a row. When the focus moves off of a row, replaced values are saved. The Find and Replace list cache the last 10 search values.
To use the Go To feature for modules, on the Module toolbar, click the Find button. In the window that opens, click the Go To tab, and enter an object ID or a section number. If a section number might also be an object ID, such as 5, append a period to the number to indicate that you are entering a section number.
If the item is found, the item is displayed and selected.
If a section is not found and the module is in book order, the nearest parent is shown.
When you add an artifact to a module, you can now select artifacts that contain content that was created by other tools and uploaded to the RM system. If those resources are images, the image is displayed in the grid and in the scroll preview. You can also add graphical artifacts, such as sketches, to modules and display graphical artifacts in modules.
You can add uploaded artifacts to modules.
If the resource is a PDF file, you can open the embedded PDF viewer in the module grid. You can manually resize the cell that the viewer is in by grabbing the lower border.
Based on feedback about the first iteration of the scroll preview (fisheye), the scroll preview was improved to more clearly show what the contents of the visible section will be when you stop or pause scrolling.
The Collections and Reviews sidebar has been renamed to "Where Used." The sidebar now includes a section named "In Module."
From the module editor, you can access a list of modules in which an artifact is being reused. To access the list, add the Used in Modules column to the display.
The Content Folder property was added under the Overview section in the module viewer. You can use this property to set the default location to store module artifacts. Content Folder is the default folder, but you can override this attribute and specify a different folder each time you create an artifact in the module. The Content Folder contains the base artifacts, which can be reused in other modules.
Modules can now participate in Collaborative Lifecycle Management (CLM) scenarios, which are like requirements collections. You can use the RM pickers to create or select modules alongside collection artifacts. You can also select artifacts inside of modules as requirements in the requirements pickers.
You can generate report documents from within modules. You can generate reports from both the current view and from saved filters. This capability uses the embedded Rational Reporting for Document Generation component.
In a module, the main content column, called "Content (ReqPro)", now shows both the name of each artifact and its content, such as primary text and images. If either field is empty, the empty field is not displayed, but can be added if necessary. You can work with requirements in modules by using either title, or primary text, or both, depending on your process and preference.
If only one of the values is displayed in the content column, you can hover your cursor on the grid cell to display a button that adds the missing field. To edit a field that is already displayed, double-click the field. In earlier versions, one click opened the field for editing.
If the name of an artifact is removed, or set to blank, the artifact is automatically given a name that is generated from the first words in the primary text of the artifact. The generated name is shown everywhere that the name of the artifact is shown, with the exception of the content column in a module. In the content column, a name generated in this way is not displayed because the name is a duplicate of all or part of the primary text that is displayed in the same column.
When the primary text is used for heading text, you can now format it and extend it over multiple lines, although the text maintains the general appearance of a heading.
An alternative content column is available called "Content (DOORS)". In that column, artifacts that are not headings display the primary text only.
The column names "Content (ReqPro)" and "Content (DOORS)" are temporary.
The entry URL to the web client, https://yourhost.com/rm/web, opens an RM-specific user dashboard. This dashboard was replaced with an All Projects page that the user can use to select a project to navigate.
Users are encouraged to use the user dashboard from Jazz Foundation, which can be accessed from the Personal Dashboards section of the
The Requirements Dashboard link that was available in the banner area was replaced with a Project Dashboard link, which opens the project dashboard that is associated with the currently opened project.
New project dashboards can now include the new My Requirements Projects viewlet.
You can now use the ReqIF import to specify which folder to place newly created resources in. Also, in cases where incoming resources do not have a module context, you can specify the module to import the resources into.
You can now use the ReqIF Export Wizard to export requirements to a ReqIF file. Then, you can use that ReqIF file to import the requirements into another project. In the wizard, you can export and download content that is specified by a ReqIF Definition. You can also specify at export time which requirements to include. In addition, you can use the wizard to download a package that was already exported.
The ReqIF Definition Editor is a new tab on the project properties page that you can use to create and modify ReqIF definitions. These definitions can be used in the export of a ReqIF file.
You can now use text delimiters when you identify requirements in a document to make into separate artifacts. Users can mark up a document with text delimiters and then define those delimiters by using the Requirements Parsing wizard. Requirements are created from the text found in the delimiters.
Individual artifact types can be defined for each unique keyword or set of text delimiters. Any requirements that are identified based on those keywords or delimiters will be of that defined artifact type.
When you parse Rational Requirements Composer text artifacts, you can now create a link from the source artifact to any requirements that are parsed from that artifact.
You can perform a few module edit operations by using keyboard commands instead of using the pull-down menu on an artifact. The operation is performed on the artifact that has keyboard focus. The artifact that has focus is usually highlighted by a black dotted border. These commands are available:
F2: Create artifact after
Shift+F2: Create artifact before
Ctrl+F2: Create artifact below
Ctrl+F3: Convert to heading/Convert to non-heading
Spacebar: Select artifact
Delete: Remove Artifact
Up and Down Arrows: Move the focus through the module
Ctrl+A: Add existing artifact after
Ctrl+Alt+Right Arrow: Demote
Ctrl-Alt-Right Arrow : Promote
The keys that are used for these operations might be changed in future milestones. Additional keyboard operations are planned for future milestones.
While you edit a storyboard artifact, you can use keyboard actions to expand or collapse the thumbnail view of the frame list. To select the expand/collapse button, press the Tab key. To activate the expand/collapse button, press the Enter key.
In Rational Requirements Composer V3.0.1, when an artifact was deleted, its links were left in the repository and displayed as broken links. Now when an artifact is deleted, any links to other artifacts are also deleted. For example, artifact A is linked to artifact B. If artifact A is deleted, when you view artifact B, a broken link is not shown to the deleted artifact A.
This functionality applies only to links between RM artifacts that are on one RM server. For example, if a requirement is linked to a test case and you delete the requirement, the reverse link that can be seen on the test case is not deleted. The Rational Quality Manager reconciliation wizard already addresses this case.
The file upload feature is enhanced so that you can upload multiple files at the same time. In Firefox, you can drag files to upload them, while in Internet Explorer, you use an upload window.
|Products||Downloads Community||Our Story|