Requirements Management Process
The requirements management process for a specific project is defined by:
The requirements management process should integrate the usability engineering process as needed (IEC 62366).
Traceability should be established based on a document layer structure e.g. according to a V-
Comprehensive templates should be used in all cases/ on all levels to avoid requirements gaps. Quality of requirements should be verified.
All requirements documents should be part of the traceability concept according to a V-
Product risks and their mitigation should be integrated within the requirements management process, especially when using a tool, then risks become individual database entries with linked risk mitigation (safety requirements).
The use of a requirements management tool is recommended from a certain complexity level on. This enables the team to create real-
Snapshots can be created for certain development stages, product configurations, product versions or country specific design histories.
Traceability can be established for international teams e.g. also having their owned requirements artifacts in databases on-
Requirements artifacts are available as document deliverables and also stored with their individual requirements/ attributes as part of a database.