Project

General

Profile

Feature #2883

[Requirement] Find a nice solution to model traces

Added by Anonymous over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
03/20/2017
Due date:
% Done:

0%

Estimated time:

Description

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.


Related issues

Related to Feature #2950: Generic Allocation Meta-ModelClosed11/23/2017

History

#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.

#2 Updated by Simon Barner over 3 years ago

#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).

#4 Updated by Anonymous almost 3 years ago

  • Assignee changed from Anonymous to Anonymous

@Hernan: you are now more aware than me on the latest status for that. What's the status? Is there a need for this "issue"?

#5 Updated by Anonymous almost 3 years ago

  • Target version changed from AF3 2.12 RC1 (Feature Freeze) to AF3 2.12 Post-release

#6 Updated by Anonymous almost 3 years ago

  • Status changed from New to Resolved
  • Assignee changed from Anonymous to Anonymous

Traces are now added either from the component view with drag&drop or from the requirement view from the traces tab.

#7 Updated by Anonymous almost 3 years ago

  • Assignee changed from Anonymous to Anonymous

And is it "clean" both at the GUI and at the modelling level?

i.e., only your traces are visible through the GUI, and the old traces are/can be removed from the metamodel?

#8 Updated by Anonymous almost 3 years ago

  • Assignee changed from Anonymous to Anonymous

Answer: yes, both views call the same method to create the trace.
I don't remember if we keep the model implementation of your solution or the previous one, but at least is the same for both views.

#9 Updated by Anonymous almost 3 years ago

  • Status changed from Resolved to Closed

Testing is the same as in the issue #3123

Also available in: Atom PDF