Develop a component that allows to manage traceability between models and (externally-defined) system requirements:

Import and synchronize sets of requirements from an external source (database, file) into a Gitlab repository (using Issues or the Requirements Management feature, to be agreed with ESA). The input format for the requirements shall be the ReqIF (Requirement Interchange Format). A requirement shall have an identifier, a description (the requirement itself), a verification method, and possibly additional information – in accordance with the ECSS standards. (read requirements, and fill gitlab repository – setting in “project” for the gitlab URL,authentication/login, ...)

Let Space Creator connect to the gitlab server to load requirements via the gitlab API

Distribute/Attach requirements to model elements (functions, interfaces, MSC scenarios) (attribute for IV/DV, extend comment block in MSC)

Export traceability information to allow the monitoring of the implementation of the requirements in the model (View to list the “usages” of each requirement. And a list of requirements per entity (function, interface, ...))

Connect the verification methods with actual data (“verification method” is in the requirement . Could point to a msc scenario. Maybe only pointing to generic text input. Stored in the gitlab issue?)

Propagate requirements to other tools (e.g. OpenGEODE). (done by the #3 (closed) probably)

Support basic model versioning and change logs (similar to git tags) to allow the freezing of a model version together with the list of requirements it implements. (use git)

Provide basic impact analysis for new versions: compare the list of requirements attached to a version of the model with a new version of the requirement inputs: if some requirements were deleted of modified, summarize the impacts on the model. (detect and react on new, edited, deleted requirements)