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:
As with most software, the vendor/owner, tool name or scope change over time.
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.
↑"Check e.g. MBSE tools on PPI / INCOSE's tools example page". www.systemsengineeringtools.com. Retrieved 2023-03-24.
↑"Download now: "Automate Lifecycle Governance and Compliance for Automotive Software Systems" How To Accelerate Functional Safety in ISO 26262, SPICE, and CMMI". polarion.plm.automation.siemens.com. Retrieved 2021-03-22.
↑"SUP.9 – Problem Resolution Management - Kugler Maag Cie". www.kuglermaag.com. Archived from the original on 2024-09-08. Retrieved 2021-03-23.
12"No Magic Acquisition Completed: Dassault Systèmes Strengthens Foothold in Systems Engineering to Facilitate New Connected Experiences". www.3ds.com. 27 January 2020. Retrieved 2021-10-15.
↑"Requirements Management using Enterprise Architect's Specification Manager". sparxsystems.com. Retrieved 2021-04-22.
↑"Engineering Systems Design Rhapsody - Overview". www.ibm.com. Retrieved 2021-04-22.
↑Morais Ferreira, David (2018). Automated Creation of a Database for the Analysis of the Completeness of German Natural Language Requirements. Kaiserslautern. doi:10.24406/publica-fhg-282599.{{cite book}}: CS1 maint: location missing publisher (link)
↑"Use ReqIF to move data from DOORS to DOORS Next". www.ibm.com. Retrieved 2021-04-22.
↑Beatty, Joy (July 2013). "Winning the hidden battle: Requirements tool selection and adoption". 2013 21st IEEE International Requirements Engineering Conference (RE). Rio de Janeiro-RJ, Brazil: IEEE. pp.364–365. doi:10.1109/RE.2013.6636753. ISBN978-1-4673-5765-4. S2CID206524062.
↑Santana, Sonia R.; Perero, Lucrecia R.; Delduca, Amalia G.; Dapozo, Gladys N. (2020). "Evaluation of Open Source Tools for Requirements Management". In Pesado, Patricia; Arroyo, Marcelo (eds.). Computer Science – CACIC 2019. Communications in Computer and Information Science. Vol.1184. Cham: Springer International Publishing. pp.188–204. doi:10.1007/978-3-030-48325-8_13. ISBN978-3-030-48325-8. S2CID219428943.
↑van der Heide, Johan. "09013 Amalthea". itea3.org. Retrieved 2021-03-22.
↑Hull, Elizabeth; Jackson, Ken; Dick, Jeremy (2010), "DOORS: A Tool to Manage Requirements", Requirements Engineering, London: Springer London, pp.181–198, doi:10.1007/978-1-84996-405-0_9, ISBN978-1-84996-404-3, retrieved 2021-03-22