Use requirements management tools to improve the efficiency of requirements management and traceability


It is not easy to manage requirements changes and traceability between requirements without using any requirements tools. Generally speaking, users will first execute requirements and files at different levels to get out the hierarchy and framework of requirements files. Then, create multiple word and EXCEL documents to write requirements at different levels, and then write requirements one by one. If you need to view the complete traceability information, you also need to open multiple files to read the traceability relationship between each layer of requirements layer by layer. Finally, the change records of these files are managed through a version control tool similar to subversion. Although this method can really enable users to manage requirements and traceability, it is very inefficient.

If you pass one at the beginningdemand management Tools for management, such asVisure Requirement ALM, users can easily incorporate all current requirements into the requirements management tool for unified management, and can see all the data they need to see on one screen without opening multiple word and

1) The directory structure of requirement files and the traceability relationship between files

The requirements management tool comes with several different compliance group templates. If the user is to meet a compliance specification, such as ISO 26262, the tool provides built-in templates and template documents to tell users what files are needed and what the traceability relationship between files is, so that users can get started quickly. At the same time, these built-in templates can also allow users to customize settings. After the user-defined settings are completed, they can also be saved and become an optional template for creating projects in the tool.

remarks: template is a built-in template. The saved custom template can be used by selecting customize to specify the template location.

2) Establish traceability between requirements

Survival allows users to easily establish traceability between requirements in a variety of ways. As shown below, one of these tools can provide a

3) Displays the complete traceability information of a requirement. At the same time, when the content of a requirement changes, it provides impact analysis information and displays the requirements that may be affected.

The survival tool can provide different styles to display the complete traceability chain. Users can view all upstream complete traceability chains or downstream complete traceability chains from a selected file. From this picture, users can easily distinguish which requirements have not been set retroactively.

If the above presentation method cannot be met, the user can also customize the number of fields, and then select the traceability file to display for each field. Visit can completely present the traceability relationship of these selected files in a way similar to excel table. At the same time, it can also allow users to summarize the information of the complete traceability chain presented into an excel file and provide complete traceability evidence to a third-party company.

4) The version change information of each file or requirement is displayed

When using the tool, users can easily manage the architecture of all requirements and documents and the traceability information between each requirement in a unified way, and present it in the tool. At the same time, the tool can also record the change records of each file and requirement, so that all users can see the version change information of each file and requirement at any time.

After using the functions provided by the tool, users can quickly implement the architecture of the requirements document and the traceability relationship between the requirements in the document. At the same time, users can easily manage and trace the requirements and documents in the visit tool, and present the information users need to see in each requirement document at any time, or a complete traceability chain from a high-level requirement to a low-level requirement. Finally, like any version management tool, visit also carries out version control for each requirement and document, so that users can see the content and records of each change.

These contents are stored in a central database. Each user can use his own account login tool to view the information that his account can see or modify. If the company needs to manage multiple copies and versions of requirements documents when employees leave or have new employees, the use of requirements management tools can greatly improve the efficiency of management; It can also make it easier for new employees to understand the relationship and process between the company’s requirements and testing and other documents.

“Original content, please indicate the source for reprint”