Requirements management is particularly important in situations where complex products and systems and work on them in a very collaborative manner. development is being worked on.
The aim of requirements management is to achieve a common understanding of the system to be developed between the contractor and the client. At the same time, the resulting documents often serve as a contractual basis for further implementation.
A common understanding can be achieved through the introduction and implementation of requirements management methods (including a. scoping, requirements analysis, requirements specification, requirements modeling, requirements reviews). The quality of requirements documentation can be increased by using these methods. Quality criteria for requirements documentation include comprehensibility, clarity, verifiability (including traceability), consistency, completeness and testability. [1] For the semi-automatic testing of some quality criteria, so-called requirements smells can be searched for in the requirements documentation, based on code smells, which reveal potential problems in the text. [2]
The management of requirements means that processes defined and implemented by the requirements documentation is updated during the entire course of the project and this is end can be used as a basis for the creation of test cases can.
