[Requirement] Find a nice solution to model traces
Traces are a little bit messy right now: modelled partly as constrained (me guilty on this), but also as explicit traces for transitions (me guilty again), and originally a little bit dirtyly in MIRA.
#1 Updated by Anonymous over 3 years ago
A recurring question is the one of "where shall we put these traces?"
Gonna generalize the solution used for transitions: a trace is just a class containing a set of "target" requirements.
This can be then very naturally put in MIRA: handler and everything is there. Just not the compositors.
Compositors have to be placed where it is relevant to trace.
#3 Updated by Simon Barner over 3 years ago
We have been discussing the issue of representing traces in the context of planning a generic allocation metamodel that is to replace the deployment metamodel in the long run. It will provide generic mechanisms to describe 1:1, n:1 and 1:n relationships, and that are to be customized to specific mappings (e.g,. component-to-task, task-to-partition, or requirement-to-(system model artifact).