Currently an SSP container shall contain at least one .ssd-file with an hard-coded SystemStructure name.
In the context of SSP as system design language where system models are represented with level 2-4 representations, it could be relevant to assign a level an .ssd-file with a comprehensible name.
To be clarified:
- What do we want to achieve at the end?
- How to handle dependencies and
inheritance (i.e., define and re-use interfaces between levels)
- SSP as system design language: How to handle additional blocks e.g.,
delay block between two fmu-me?
Currently an SSP container shall contain at least one
.ssd-file with an hard-codedSystemStructurename.In the context of SSP as system design language where system models are represented with level 2-4 representations, it could be relevant to assign a level an .ssd-file with a comprehensible name.
To be clarified:
inheritance(i.e., define and re-use interfaces between levels)delay blockbetween two fmu-me?