Top Qs
Timeline
Chat
Perspective
Requirements engineering tools
From Wikipedia, the free encyclopedia
Remove ads
Remove ads
Requirements engineering tools are usually software products to ease the requirements engineering (RE) processes and allow for more systematic and formalized handling of requirements, change management and traceability.[1][2]
The PMI guide Requirements Management: A Practical Guide recommends that a requirements tool should be identified at the beginning of the project, as [requirements] traceability can get complex and that switching tool mid-term could present a challenge.[3]
According to ISO/IEC TR 24766:2009,[4] six major tool capabilities exist:
- Requirements elicitation
- Requirements analysis
- Requirements specification
- Requirements verification and validation
- Requirements management
- Other capabilities
Note that INCOSE and Project Performance International (PPI) maintain an official database of tools, the Systems Engineering Tools Database (SETDB).[5]
Remove ads
RE tool list
Summarize
Perspective
As with most software, the vendor/owner, tool name or scope change over time.(https://www.Reqops.com)
Note that compliance with, for example, safety standards such as ISO 26262 is supported by few tools directly or indirectly via specialist consulting.[6][7]
Unlike the major six tool capabilities (see above), the following categories are introduced for the list, which correlate closer with the product marketing or summarizes capabilities, such as requirements management (including the elicitation, analysis and specification parts) and test management (meaning verification & validation capabilities).
Specialties, such as OSLC-support, are not presented in the current list, but exist for some tools.[8][9]
List capabilities
- Agile: The tool supports agile methodologies, such as Scrum, Kanban, collaborative working etc.
- ALM: Application lifecycle management (meaning, the tool offers a full set of capabilities or can be extended)
- CM: Configuration management (software or hardware)
- ISM: Issue resolution management (or problem resolution management)[10]
- PDM: Product data management
- PLM: Product lifecycle management
- PJM: Project management
- RM: Requirements management incl. design, specification, etc.
- TM: Test management (QA)
- VCS: Version control system
- VM_MBSE: Visual/UI/UX modeling or MBSE (Model-based systems engineering)
Excluded capabilities (limited list)
- CI/CD
- Process management (project management) (Process design, etc.)
- QM: Quality management
- Risk management
- Release/Patch management
- Safety or Security
- Variants management
List
 |
Remove ads
Other tools, developments, specialities
Further reading
- Winning the Hidden Battle: Requirements Tool Selection and Adoption[17]
- Evaluation of Open Source Tools for Requirements Management[18]
- A case study of requirements management: Toward transparency in requirements management tools[19]
- Modeling requirements with SysML (IREB, 2015)
- Is requirements engineering still needed in agile development approaches? (IREB, 2015)
- DOORS: A Tool to Manage Requirements[20]
- Risto Salo et al. Requirements management in GitHub with a lean approach (2015)
See also
- Application lifecycle management (ALM)
- ISO/IEC 12207
- List of SysML tools
- List of Unified Modeling Language tools
- Model-based systems engineering (MBSE)
- Open Services for Lifecycle Collaboration (OSLC)
- Product lifecycle management (PLM)
- Scope management
- Software development process
- Systems engineering tools
References
External links
Wikiwand - on
Seamless Wikipedia browsing. On steroids.
Remove ads