[FEATURE] Updated OpenSUT SysML model

[podhrmic]

Summary

We currently have two Cameo models: OpenSUT_architecture.mdzip and RTS.

Update the model such that:

• [x] We have either only one project, or the top level OpenSUT is linked with the RTS project
• [x] Import ReqIF requirements, as exported from Strict Docs (see #50)
  • what works well, and what does not get imported properly?
  • what format can the SysML requirements be exported to? (Markdown? HTML? ReqIF?)
• [x] Update RTS project to Mission Protection System (see #43)
  • remove the saturation channel
  • change code/wording accordingly

Acceptance Criteria

Updated SysML project is uploaded as a Git LFS file, old projects (OpenSUT/RTS) are removed.

[hshackleton]

Notes on Requirements:

1. Import from StrictDocs generated reqIF into MagicDraw/Cameo

   • All data was correctly imported including extra fields such as RATIONALE, and all relationships.
   • The numerical ordering (Hierarchy Id) is not consistent due to a blank/header requirement being added at the start of the MD/C import. So the first MD/C requirement is 2.1 not 1.1.
   • The imported requirement groupings lost there names in translation, this was easy to add after the fact.

2. Output from MagicDraw/Cameo

   • There are several report templates including a Requirements Report and a Coverage Analysis Report. These can be modified to include any images and tables that are created within the model and also give good textual representations of all the requirements and their relationships. These reports are designed to be output as doc files or html.
   • It is trivial to create a requirements table that has columns for all the data (including extra fields like RATIONALE) and relationships. These tables can be exported to xlsx, csv or html formats.
   • There is also an reqIF output format with multiple flavors (MagicDraw, IBM, Polarion, Reqtify, Teamcenter). The export includes all the extra fields such as RATIONALE and all relationships in the model.

3. Import of reqIF from MagicDraw/Cameo into StrictDocs

   • None of the outputted MD/C formats worked. All resulted in a "422 Unprocessable Entity" error.
   • I could read back the StricDocs generated reqIF, and modifying the header information did not resolve the issues. More digging into the expected format specifics or looking at the open source parser would be necessary to determine if a complete round trip is possible.