Create documentation on how to manage requirements

[kmohr-soprasteria]

Problem:
Requirements to use cases need to be properly captured.
These requirements will be translated into "capabilities" in the respective target application (i.e. services) or will have to be considered when capabilities are specified (e.g. non-functional requirements, restraints).
In the past there was no defined process for gathering and managing those requirements.

Solution:
Guidelines for requirement management are to be added to the documentation.
(And are to be applied for gathering future requirements.)