AUTOSAR / S-CORE artifact mapping

[aschemmel-tech]

Meeting with AUTOSAR colleagues. Apr-16, 15-16 o'clock
Preparation see list https://eclipse-score.github.io/score/main/process/workproducts/index.html#s-core-work-product-list

• restricted the artefacts mapping to the ones needing exchange: (feature) requirements and (feature) architecture.

• Had a look at Feature requirements defined in .rst files (https://eclipse-score.github.io/score/main/_sources/features/communication/ipc/requirements/index.rst.txt) - AUTOSAR should be able to export from their RS specifications (via arxml) into this text format (description, attributes). Safety and security attributes need to be resolved as currently not available in RS specs.

• The same applies for the static architecture and interface definitions but with some more effort due to the amount of different attributes (traceability,...)

• S-CORE Dynamic architecture is documented in plantuml pictures (sequence diagrams) - these may also be exported pictures from Enterprise Architect. AUTOSAR to decide if component architecture is documented in EA or in sphinx-needs/plantuml

• conclusion: exchange of main artefacts seems feasible from AUTOSAR -> S-CORE. No follow-up needed

• separate topic of "use-cases" as in Kick-Off will need folllow-up

---

Previous & parallel work

• Kick-Off
• Tooling Comparison with AUTOSAR
• Mapping requirements levels to AUTOSAR