Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
There are two levels of requirements: end user needs concerning requirement engineering activities and tool requirements that precisely define what ReqCycle will do to support end user needs.
operational use cases
Concerning user/operational needs we find following expectations gathered from industry (Airbus, Thales, Safran for now) and AMALTHEA european project (). They will be refined into ReqCycle requirements in future months.
configuration support use cases
There are also configuration/setup end user requirements to define the way requirement engineering will be driven.
Collaborative work use cases
Concerning collaborative work support, we find the following use cases, with two main possible situations:
- either access by copy to a shared repository (push/pull, update/commit)
- else direct access to the shared remote repository and modifications done directly on it
There are UC to share requirements:
And UC to share traceability:
1. it can occur that traceability links retrieved are broken, because source or destination objects of the link are missing (especially in the case of a local repository/copy of the shared repository). So it is important to be able to detect those "broken" links.
2. It can also occur that source or destination of a link changes and link is not guaranteed to remain valid. There shall be a way to detect "suspicious" links.
standard process activities concerning requirement engineering
During stakeholder needs and requirements definition (see ISO 15288:2015) we find the following activities that concern requirements:
During system requirements definition (see ISO 15288:2015) we find the following activities that concern requirements: