EPIC: Metamodel Usability Adaptions

[aschemmel-tech]

What

This epic collects some topics around the usability of the implementation metamodel (needs elements of work products and their relations)

How

• The deployment of the work products to the score, modules and integration repositories shall be improved (e.g. by merging feature/module artefacts in the module repos)
  • This includes also metamodel changes if needed (e.g. new platform architecture views)?
• The integration with standards should be improved (e.g. SyML) docs: Align Relations in Metamodel to SysML #418

In reality more to come in other repos because of the dependencies ... The chain is:

1. adopt docs-as-code repo for future change with new optional links (PR432 done)
2. adopt process repo for examples (PR615 done)
3. adopt score repo -> PR 2703 done
4. adopt docs-as-code repo for real change with mandatory links (PR465 done) -> was blocked by tooling issues in PR and 3. (PR 2703)
5. adopt templates repo (PR58 done) -> template repo is currently empty, which means runs also without that change.
6. adopt also folder in score repo (PR2825 done and (PR2863 done)
7. adopt sw-modul repos (tbd -> blocked by PR 2703)
   • logging: (PR82 running) (blocked by infrastructure issues -> fix available -> but not tooling version) -> delayed to merge until next version on reference integration is done

Estimates for realization

2-3 month

Category

• Affects Detailed Design

Requirements / Architecture

• Requirements / Architecture are not affected by this change?