Repository navigation
Incorporation of external SEooCs #840
Description
What
Currently the S-CORE process already expects to use external SEooCs like the OS and defined requirements towards these in the "Stakeholder" level. Also the incorporation of external SEooCs AoUs is covered in the metamodel already. But there is no process how to map the S-CORE requirements to the "Assumed (System) Requirements" which are usually supplied by SEooCs and which are the basis for their development. This mapping needs to confirm that the two requirements sets match.
Acceptance Criteria (DoD)
- process described
- docs_as-code metamodel changes
- pilot usage
How
see discussion https://github.com/orgs/eclipse-score/discussions/407#discussioncomment-18945400:
... have an additional needs element like for AoU ... which can link to any S-CORE requirements levels, because we also do not know on which level the "Assumed Requirements" of the external module would be. Which links to S-CORE requirements by a link which may be called "matches" or "maps_to".
Activity