Jump to content

User:Faberwm/List of requirements engineering tools

From Wikipedia, the free encyclopedia

Requirements engineering tools (RE tools) are usually software products to ease the Requirements engineering processes. Due to the complex nature of Requirements engineering, involving multiple stakeholders taking part in documentation, elicitation, validation and managing the requirements of a system, there has been a need for creating and establishing RE tools.[1] Moreover, RE tools are changing rapidly.

According to the de Gea et al. [2] who performed a survey on Requirements engineering tool capabilities reported that the majority of participants stated that the tools they used had their first release in the last decade but these tools seems to be very updated. (Fig.1)

Fig. 1: Year of first and last release of Requirements Engineering Tools[2]

The way we manage requirements is changing as a result of willingness for adaptivity, learner and agile development, global collaboration and enhanced software and system ecosystems. [3] The main purposes of RE tools are: facilitating efficiency and consistency in requirements management. [4][3]

RE tools are unique, well maintained by their suppliers, and target specific environments, niche markets, development workflows, or usage scenarious. [3] However, according to 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.[5]

Capabilities classification

[edit]

According to ISO/IEC TR 24766:2009,[2] RE tools can be classified into eight district capabilities categories depending on their purpose:

  1. Requirements elicitation - contains capabilities centered on the tools' assistance for stakeholder identification, the capture and tracing of business/user requirements, functional requirements, and non-functional requirements during elicitation activities.
  2. Requirements analysis - contains tools for breaking down high-level needs into their component parts, assessing feasibility, negotiating priorities, spotting disputes, recognizing unclear, lacking, contradictory, or ambiguous requirements, and fixing all of these problems.
  3. Requirements specification - includes features that are intended at defining the requirements that a software or system must meet, in a consistent, easily available, and reviewable manner, in order to accomplish this goal.
  4. Requirements modelling - covers features that are centered on applying certain methodologies to create meaningful and verifiable requirements models.
  5. Requirements verification and validation (V&V) - contains tools for supporting the numerous testing and evaluation techniques needed to confirm and validate the requirements.
  6. Requirements management - investigates the tools' capacity to enable the maintenance of requirements and the monitoring of changes, thereby guaranteeing that the requirements appropriately reflect the product.
  7. Requirements traceability - comprises tools for tracking requirement changes, establishing linkages between related requirements, and documenting the life of a need.
  8. Other capabilities - features relating to the tool's integration into the system and software development environment fall under this section.

List capabilities

[edit]

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 eight tool capabilities (see above), the following categories are introduced for the list, which correlate closer with the product marketing or summarizes capabilities, such as RM including the elicitation, analysis and specification parts, and TM 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

[edit]
  • Agile: Agile helps teams deliver value to their clients more quickly and with fewer difficulties through an iterative approach to project management and software development. An agile team produces work in manageable, small-scale increments rather than staking all on a "big bang" launch. Teams have a built-in mechanism for fast adjusting to change since requirements, plans, and results are regularly evaluated. An example of agile tool is the one that supports methodologies, such as Scrum, Kanban or collaborative working.[10]
  • ALM: Application lifecycle management: supports the coordination of group of individuals, equipment, and procedures that manage the design, development, testing, maintenance, decommissioning, and retirement of a software program. ALM enhances product quality, maximizes productivity, and lessens the management and maintenance burden for associated goods and services by unifying and arranging the parts of an application's lifetime. The tool offers a complete set of capabilities that can be extended.[11]
  • CM: Configuration management (CM): The practice of keeping systems, such as computer hardware and software, in the desired condition. Also, a technique for making sure that systems perform consistently with expectations throughout time is part of the configuration management (CM). The configuration management includes both the software and the hardware of a device.[12]
  • ISM: Issue resolution management: The identification, management, and resolution of project challenges are necessary for the project's success. Throughout the project lifespan, issue management is crucial for preserving the stability and effectiveness of the project. It addresses issues that can prevent a project from succeeding or keep the project team from attaining its objectives. These challenges may include things like disagreements, circumstances that must be looked into, and newly discovered or unexpected duties. The goal of issue management is to recognize and record these problems, then address them by carefully evaluating all pertinent data.[13]
  • PDM: Product data management: A system called product data management (PDM) is used to consolidate procedures and data linked to products. PDM software is used by engineers to handle change requests, create Bills of Materials (BOMs), and more. PDM software reduces time spent on low-value tasks, increases product development agility, and fosters collaboration, all of which help businesses get products to market more quickly. PDM integrates with your design and business technologies to manage data, automate engineering processes, and capture the whole history of your designs.[14]
  • PLM: Product lifecycle management: The process of managing a product as it passes through its several lifetime stages, including development and introduction, growth, maturity/stability, and decline. The production of the good and its marketing are both a part of its handling. When making business decisions, from pricing and advertising to expansion or cost-cutting, the idea of product life cycle might be helpful.[15]
  • PJM: Project management: The utilization of particular information, skills, tools, and procedures in project management is done in order to provide people with something of value. Projects include things like building a building, providing relief following a natural disaster, expanding sales into a new geographic market, and developing software for better company processes.[16]
  • RM: Requirements management: To ensure that the objectives of product development are successfully attained, requirements management is used. To assure that engineering teams always have authorized and up-to-date requirements, a collection of procedures for recording, assessing, prioritizing, and agreeing on requirements has been developed. By monitoring changes to requirements and promoting communication with stakeholders from the beginning of a project through the entire lifecycle, requirements management offers a means of preventing errors. This criteria includes design, specification.[17]
  • TM: Test management: The process of managing testing activities in order to guarantee thorough and advanced testing of the software application is known as test management. To produce a high-quality software program, the method entails planning, managing, assuring traceability, and ensuring visibility of the testing process. It makes sure the software testing procedure goes as planned. This criteria also includes Quality Assurance (QA).[18]
  • VCS: Version control system: The process of monitoring and controlling software code changes. Software technologies called version control systems assist software development teams in tracking changes to source code over time. Version control solutions aid software teams in working more quickly and intelligently as development environments have advanced.[19]
  • VM_MBSE: Visual/UI/UX modeling or MBSE (Model-based systems engineering): A method that, as opposed to document-centric systems engineering, focuses on developing and utilizing digital system and engineering domain models as the key channel for the interchange of information, feedback, and needs. It entails the complete procedure of capturing, communicating, and ensuring that all digital representations of a system that we use are coordinated and maintained over the course of the system's full lifecycle.[20]

Excluded capabilities

[edit]

Other capabilities that are not part of the list of functionalities are:

  • CI/CD
  • Process management (Process design, etc.)
  • QM: Quality management
  • Risk management
  • Release/Patch management
  • Safety or Security
  • Variants management

Choosing the right tool

[edit]

It can be difficult for large software and systems engineering companies to select the right requirements engineering tool. This is because there is usually not one tool that is suitable for all the departments or projects [21]. Therefore, the process of selecting the right (set of) tools has become an intricate and time-consuming process. However, over the years several approaches have been developed to help companies or individuals select the right commercial off-the-shelf (COTS) RE tools [21][22]. Some of these tools are listed below.

  • VOLERE: The VOLERE method consists of pre-defined checklists that ask the right questions at the right time [21][23]. An example of such a question would be "how do you measure this requirement?". This is a low-level approach of finding the right tool. [21]
  • PORE (Procurement-Oriented Requirements Engineering): The PORE method is a high level method can help when someone is acquiring requirements while selecting the right tool [21][22][24]. It uses among other things feature analysis techniques, MCDM (Multi-Criteria Decision Making) techniques, argumentation techniques, requirements acquisition techniques, and requirements engineering methods. PORE consists of four steps [21]:
    1. Acquire information from the stakeholders;
    2. Analyze the acquired information;
    3. Make decisions on the compliance between the acquired requirements and the product.;
    4. Select one (or more) COTS software tool.
  • CAP (COTS Acquisition Process): The CAP consists of three components: the CAP Initialization Component (CAP-IC), the CAP Execution Component (CAP-EC), and the CAP Reuse Component (CAP-RC) [22]. The former, CAP-IC, can be used to select the right RE tool. This component consist of three steps [22]:
    1. Identify the criteria that will be used to compare the possible COTS tools;
    2. Estimate how much effort is needed to actually apply all evaluation criteria to all the possible COTS software candidates;
    3. Set up a measurement plan according to which all evaluation activities will be conducted.
  • OTSO (Off-The-Shelf-Option): The OTSO method consists of searching, evaluating, and selecting reusable software. It provides specific techniques that help define criteria, which are gradually defined throughout the selection process [22][25].

Requirements engineering tools examples

[edit]

Jira

[edit]

Main article: Jira (software)

Jira is a package of agile work management tools that enables collaboration amongst all teams from concept to customer, giving the freedom to work with others to produce your best work. Jira provides a variety of tools and deployment choices that are designed specifically for software, IT, business, operations teams, and other groups. It is developed and distributed by Atlassian. [26]The Jira family consists of: Jira Software (supports Scrum, Kanban, DevOps, and tracking bugs [27]), Jira Service Management (assisting in enabling high-dynamic teams [28]), Jira Workflow Management (a series of states and changes that an issue experiences during its existence[29]), Jira Align (formerly known as Atlassian AgileCraft, used for expanding agile to the enterprise[30]). However, Jira has some limitation when used in developing a large-scale software product. Firstly, the process of editing certain fields within a Jira issue cannot be managed by Jira automatically. Any user who has access to modify that JIRA issue may edit it, on the occasion that a field is present on the entry screen. Secondly, great tools are provided by JIRA for "current" status, but Jira does not support the visualization of historic data. Lastly, JIRA's present capabilities do not allow for navigating between numerous graphs to reach particular workload data.[31]

IBM DOORS Next

[edit]

Main article: IBM DOORS Next

IBM Engineering Requirements Management DOORS Next offers solutions for collaboration and communication between teams and stakeholders in order to boost productivity and quality. It gives the ability to keep track of, analyze, and manage requirements changes while adhering to rules and standards. Deployment can be done in different ways: on-premises and in the cloud. The tool manages traceability from requirements to testing, including engineering artifacts and software. Using Watson AI and the Requirements Quality Assistant add-on, it facilitates the writing of better requirements more quickly. The management of requirements across all engineering domains, including systems engineering, agile, lean, SAFe, continuous engineering, and DevOps, further propels software and systems engineering. [32] Employees using IBM DOORS Next at their workplace report for some limitations and missing functions. For example, a sorting feature is missing, and search capabilities should be improved. Additionally, bugs with user interface were reported, which creates problems with UI/UX. Also, use case modelling function integrated in the tool does not support automatic application of use case diagram rules. Moreover, some functionalities of exporting documents are missing. Finally, the tool does not support offline work process.[33]

Requirements engineering tools list

[edit]

The following table shows an extensive list of available Requirements Engineering Tools. The capabilities of the tools match with the description mentioned above.

Scope/Capabilities*
Name Vendor Agile ALM CM ISM PDM PLM PJM RM TM VCS VM_MBSE Other License type Last updated
acunote Pluron Inc. x Commercial November 2014
agosense.fidelia agosense GmbH x Commercial N/A
Aha! Aha! Labs x x Commercial Q4 2022
Aligned Elements Aligned AG x Commercial N/A
Quality Center Micro Focus x x x x x Commercial September 24th, 2021
ALM Octane Micro Focus x x x Commercial December 12th, 2022
Auros IQ Auros LLC x x x x x x x x CAD Commercial February 14th, 2022
Axosoft Axosoft x x Commercial September 24th, 2022
Azure DevOps Microsoft x x x x Commercial October 25th, 2022
Balsamiq Wireframes Balsamiq x x Commercial December 01th, 2022
Business Optix Business Optix x Commercial N/A
Cameo Systems Modeler No Magic Inc. (since 2018 part of Dessault Systemes) x x Commercial February 2021
Capella Eclipse Foundation x Eclipse Public License December 2022
CaseComplete Serlio Software x x Commercial June 2020
codeBeamer ALM Intland Software GmbH x x x x Commercial October 2022
Cognition Cockpit Cognition Corporation x x x x Commercial N/A
Cradle 3SL x x x Commercial June 27th, 2022
Dimensions RM Micro Focus x Commercial N/A
Eclipse (IDE) Papyrus Eclipse Foundation x Eclipse Public License December 2022
Enterprise Architect Sparx Systems x x x x x Commercial November 22th, 2022
Helix RM Perforce x x x x Commercial December 2022
Rational DOORS IBM x x x Commercial October 12th, 2022
Rational Rhapsody IBM x x x x Commercial May 27th, 2022
DOORS Next (Jazz) IBM x x x Commercial October 4th, 2022
innoslate SPEC Innovations x Commercial May 2022
Innovator for Business Analysts MID GmbH x x Commercial December 10th, 2022
in-STEP BLUE microTool GmbH x x x Commercial N/A
iRise iRise x x x Commercial September 1th, 2020
Jama Connect Jama Software x x x Commercial January 6th, 2023
Jira Atlassian x x x x Commercial December 06th, 2022
Kanban Flow CodeKick AB x Commercial N/A
Kanban Tool Shore Labs x Commercial N/A
kanbanize kanbanize x x Commercial November 2022
Kovair ALM Kovair Software, Inc. x x x x x x Commercial 2021
LeanKit Planview, Inc. x Commercial December 16th, 2022
MagicDraw No Magic Inc. (since 2018 part of Dessault Systemes) x Commercial March 24th, 2022
Matrix ALM/QMS Matrix Requirements GmbH x x x x x Commercial December 27th, 2022
Marvel App Marvel x x x Commercial N/A
Minerva PLM Minerva Group A/S x x x x Commercial Q2 2021
Swiftly Orca Intelligence x x x x x Commercial N/A
Modelio Analyst Modeliosoft x x Commercial March 23, 2022
Modern Requirements4DevOps eDev Technologies x x Commercial N/A
objectiF microTool GmbH x x Commercial N/A
objectiF RPM microTool GmbH x x x x Commercial November 2022
OneDesk Product Management OneDesk Inc. x x Commercial N/A
OpenPDM PROSTEP Inc. (see also ProSTEP iViP) x x Commercial N/A
OpenProject OpenProject GmbH x x GPL3 December 14th, 2022
OSRMT OSRMT x x GPL2 April 24th, 2020
PivotalTracker PivotalLabs x Commercial N/A
Polarion Siemens PLM Software x x x x x x x Commercial October 20th, 2022
PREEvision Vektor Informatik GmbH x x x Commercial December 14th, 2022
Psoda Psoda x x x x Commercial N/A
QVscribe QVscribe x Commercial July 6th, 2022
R4J ease solutions Pte Ltd x x Commercial November 17th, 2022
Rally Software Broadcom x x Commercial N/A
RaQuest SparxSystems Japan Co., Ltd x Commercial November 10th, 2022
ReqEdit REQTEAM GmbH x Commercial August 30th, 2022
ReqSuite RM OSSENO Software GmbH x Commercial October 16th,
ReQtest ReQtest AB x x x Commercial N/A
RequirementONE RequirementOne Inc. x Commercial January 9th, 2023
ReqView Eccam s.r.o. x x x Commercial December 13th, 2022
Retina Intland Software GmbH x x x Commercial October 9th, 2022
RMsis Optimizory Technologies Pvt. Ltd. x x x Commercial August 22th, 2022
rmToo flonatel GmbH & Co. KG x x GPL3 October 15th, 2022
RMTrak Prometeo Technologies x Commercial August 2016
Scrumwise Scrumwise Commercial N/A
ScrumWorks Pro CollabNet x Commercial N/A
SOX2 RM Engineers Consulting GmbH x Commercial N/A
Specification Wizard MeetAdd x Commercial N/A
SpiraTeam Inflectra x x x x Commercial December 2022
Storyteller Blueprint Software Systems, Inc. x x Commercial N/A
SwiftKanban Digité Inc. x Commercial January 08th, 2023
Targetprocess Targetprocess Inc. x Commercial December 2022
Tuleap Enterprise enalean x x Commercial January 2023
Valispace Valispace GmbH x x x x x x x Commercial January 02th, 2023
VersionOne CollabNet x x x Commercial N/A
Visual Paradigm Visual Paradigm International x x Commercial August 01th, 2022
Visure Requirements Visure Solutions, Inc. x x x Commercial N/A
Windchill RV&S PTC x x Commercial July 07th, 2022
Yodiz Yodiz x Commercial December 19th, 2017
Yonix Yonix Ltd. x Commercial December 22th, 2022

Future for requirements engineering tools

[edit]

Main article: NLP for Requirements Engineering

The world of RE tools is still developing. One promising development is the progress in the field of natural language processing for requirements engineering (NLP4RE)[34]. NLP4RE is an area of development that seeks to apply natural language processing (NLP) techniques and resources to the requirements engineering process. [34] With the help of NLP tools, requirements and user stories could be visualised, detected, or extracted from a text. NLP can also help human analysts to carry out various linguistic analysis tasks on textual requirements documents, such as detecting language issues and identifying key domain concepts.[34] Since the 1980s, researchers have tried to create such tools, but the sophistication of NLP had not reached a point yet where this was possible. [35][36] Since the end of the 2000s, this changed and since then the development of NLP tools increased rapidly. [37][38] The research into NLP for RE has also increased, with an annual workshop since 2018 called NLP4RE.[39] In the nearby future, NLP could improve RE tools significantly.

Useful reading materials

[edit]

See also

[edit]

References

[edit]
  1. ^ Matulevičius, Raimundas; Sindre, Guttorm (2006). Nilsson, Anders G.; Gustas, Remigijus; Wojtkowski, Wita; Wojtkowski, W. Gregory; Wrycza, Stanisław; Zupančič, Jože (eds.). "Requirements Engineering Tool Evaluation Approach". Advances in Information Systems Development. Boston, MA: Springer US: 695–706. doi:10.1007/978-0-387-36402-5_60. ISBN 978-0-387-36402-5.
  2. ^ a b c Carrillo de Gea, Juan M.; Nicolás, Joaquín; Fernández Alemána, José L.; Toval, Ambrosio; Ebert, Christof; Vizcaino, Aurora (2012-05-07). "Requirements engineering tools: Capabilities, survey and assessment". ISO. Retrieved 2023-01-08.{{cite web}}: CS1 maint: url-status (link)
  3. ^ a b c Carrillo de Gea, Juan M.; Nicolás, Joaquín; Alemán, José L. Fernández; Toval, Ambrosio; Ebert, Christof; Vizcaíno, Aurora (July 2011). "Requirements Engineering Tools". IEEE Software. 28 (4): 86–91. doi:10.1109/MS.2011.81. ISSN 0740-7459.
  4. ^ "What is Requirements Management". www.ibm.com. Retrieved 2021-03-23.
  5. ^ "Requirements Management: A Practice Guide". 2016-01-01. Retrieved 2021-04-05.{{cite web}}: CS1 maint: url-status (link)
  6. ^ "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.
  7. ^ "Home - Validas AG". validas.de. Retrieved 2021-03-22.
  8. ^ "Open Services for Lifecycle Collaboration integrations". www.ibm.com. 2019-04-12. Retrieved 2021-04-22.
  9. ^ "About". open-services.net. Retrieved 2021-04-22.
  10. ^ Atlassian. "What is Agile?". Atlassian. Retrieved 2023-01-09.
  11. ^ "What Is Application Lifecycle Management (ALM)?". Software Quality. Retrieved 2023-01-09.
  12. ^ "What is Configuration Management?". VMWare. Retrieved 2023-01-10.
  13. ^ Daniel Vitek MBA, PMP-Consultant to CDC NCPHI. "PMG | Issue Management - Description". www2a.cdc.gov. Retrieved 2023-01-09.
  14. ^ "Product Data Management". Autodesk. Retrieved 2023-01-10.
  15. ^ "Product Lifecycle Management (PLM): Definition, Benefits, History". Investopedia. Retrieved 2023-01-09.
  16. ^ "What is Project Management?". Project Management Institute. Retrieved 2023-01-10.
  17. ^ "What is Requirements Management? | IBM". www.ibm.com. Retrieved 2023-01-09.
  18. ^ Hamilton, Thomas (2020-01-03). "Test Management Process in Software Testing". www.guru99.com. Retrieved 2023-01-09.
  19. ^ Atlassian. "What is version control | Atlassian Git Tutorial". Atlassian. Retrieved 2023-01-10.
  20. ^ "What is Model-Based Systems Engineering (MBSE)?". www.ansys.com. Retrieved 2023-01-10.
  21. ^ a b c d e f Heindl, M.; Reinisch, F.; Biffl, S.; Egyed, A. "Value-Based Selection of Requirements Engineering Tool Support". 32nd EUROMICRO Conference on Software Engineering and Advanced Applications (EUROMICRO'06). IEEE. doi:10.1109/euromicro.2006.64.
  22. ^ a b c d e Cechich, Alejandra; Piattini, Mario (2002). "Methods for measurement-based COTS assessments and selection". IV Workshop de Investigadores en Ciencias de la Computación.
  23. ^ Robertson S. The VOLERE process model. Internal Document, Atlantic Systems Guild, London, 1996
  24. ^ Ncube, C.; Maiden, N.A.M. "Guiding parallel requirements acquisition and COTS software selection". Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188). IEEE Comput. Soc. doi:10.1109/isre.1999.777993.
  25. ^ Kontio, Jyrki; Caldiera, Gianluigi; Basili, Victor R. (1996). "Kontio, J., Caldiera, G., & Basili, V. R. (1996, November). Defining factors, goals and criteria for reusable component evaluation". CASCON. 96: 21.
  26. ^ Atlassian. "Jira Overview | Products, Projects and Hosting". Atlassian. Retrieved 2023-01-12.
  27. ^ Atlassian. "Jira Overview | Products, Projects and Hosting". Atlassian. Retrieved 2023-01-12.
  28. ^ Atlassian. "A brief overview of Jira Service Management". Atlassian. Retrieved 2023-01-12.
  29. ^ "Work with issue workflows". Atlassian Support. Retrieved 2023-01-12.
  30. ^ "What is Jira Align". Cprime. Retrieved 2023-01-12.
  31. ^ Fisher, J.; Koning, D.; Ludwigsen, A. P. (2013-09-16). "Utilizing Atlassian Jira For Large-Scale Software Development Management*". {{cite journal}}: Cite journal requires |journal= (help)
  32. ^ "Engineering Requirements Management DOORS Next - Overview". www.ibm.com. Retrieved 2023-01-12.
  33. ^ "IBM Rational DOORS Next Generation Reviews & Ratings 2023". TrustRadius. Retrieved 2023-01-23.
  34. ^ a b c Zhao, Liping; Alhoshan, Waad; Ferrari, Alessio; Letsholo, Keletso J.; Ajagbe, Muideen A.; Chioasca, Erol-Valeriu; Batista-Navarro, Riza T. (2021-04-17). "Natural Language Processing for Requirements Engineering: A Systematic Mapping Study". ACM Computing Surveys. 54 (3): 55:1–55:41. doi:10.1145/3444689. ISSN 0360-0300.
  35. ^ Ryan, K. (1993-01-06). "The role of natural language in requirements engineering". [1993] Proceedings of the IEEE International Symposium on Requirements Engineering: 240–242. doi:10.1109/ISRE.1993.324852.
  36. ^ Hirschberg, Julia; Manning, Christopher D. (2015-07-17). "Advances in natural language processing". Science. 349 (6245): 261–266. doi:10.1126/science.aaa8685. ISSN 0036-8075.
  37. ^ Goth, Gregory (2016-02-25). "Deep or shallow, NLP is breaking out". Communications of the ACM. 59 (3): 13–16. doi:10.1145/2874915. ISSN 0001-0782.
  38. ^ Ferrari, Alessio; Dell'Orletta, Felice; Esuli, Andrea; Gervasi, Vincenzo; Gnesi, Stefania (2017-11-13). "Natural Language Requirements Processing: A 4D Vision". IEEE Software. 34 (6): 28–35. doi:10.1109/MS.2017.4121207. ISSN 0740-7459.
  39. ^ "NLP4RE'22". nlp4re.github.io. Retrieved 2023-01-12.
  40. ^ 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: 364–365. doi:10.1109/RE.2013.6636753. ISBN 978-1-4673-5765-4.
  41. ^ Santana, Sonia R.; Perero, Lucrecia R.; Delduca, Amalia G.; Dapozo, Gladys N. (2020). Pesado, Patricia; Arroyo, Marcelo (eds.). "Evaluation of Open Source Tools for Requirements Management". Computer Science – CACIC 2019. Communications in Computer and Information Science. 1184. Cham: Springer International Publishing: 188–204. doi:10.1007/978-3-030-48325-8_13. ISBN 978-3-030-48325-8.
  42. ^ van der Heide, Johan. "09013 Amalthea". itea3.org. Retrieved 2021-03-22.
  43. ^ 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, ISBN 978-1-84996-404-3, retrieved 2021-03-22
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Faberwm/List_of_requirements_engineering_tools&oldid=1135420213"