Traces of Observations
In AF1 Extended Event Traces (EETs) were used to describe single paths
of executions of components, i.e., traces of observations (TrObs).
The graphical representation of EETs were similar to the Message
Sequence Charts (MSCs) of AF3.
However, in the current AF3 implementation TrObs have not been deeply
integrated, although they relate to many features of AF3:
- Requirements: scenarios describe exemplary system executions (graphically described by MSCs)
- Simulator: each simulation run produces a TrObs (inputs, outputs, states)
- Verification: model-checkers produce counter-examples, i.e., TrObs with a loop indication.
- Test Case Generation: a generated test case is a TrObs (inputs, outputs, [states])
- Debugging / On-target Simulation: executions of the deployed system produce TrObs, which may be translated back to the model level.
The purpose of this sub-project of AF3 is to define and implement an EMF
meta-model for TrObs and additional support services.
The first step of this project is to elicit the requirements of the
TrObs support.
(from redmine: issue id 227, created on 2011-10-16, closed on 2018-01-19)
- Relations:
- child #668 (closed)