Model elements may change with the time,
how to address history of changes (suspicious state for the link) and other
attributes/properties of the traceability link?
Software Lead Expert / Driver Information
Electronics Division Europe
Tel.: +359 2 930 6412
Fax: +359 2 930 6462
Mobile: +359 888 122 609
Johnson Controls Electronics Bulgaria EOOD
40 Tsarigradsko shose Blvd - EUROPARK building
1784 Sofia, Bulgaria
Andreas Graf <andreas.graf@xxxxxxxxx>
Automotive Industry Working Group <auto-iwg@xxxxxxxxxxx>
07/27/2010 03:22 PM
as an action from our meeting, here is the description of "traceability"
as addressed by the Eclipse Modeling Platform Working Group. Note that
this basically fits
to a solution that we are currently developing as part of a research project
and will be releasing as open source:
5. Traceability to identify connection between model elements.
5.1 The MP must support the ability to create relationships between models
artifacts that are independent of the meta-model. Tools must be able to
relationships and provide a level a traceability between the model elements.
5.2 Artifact authors should be able to specify the relationships a high
level and then elaborate
in more detail and provide traceability a different levels of the model
5.3 The MP must support the traceability between non-modelled artifacts
and various types of
models and elements/parts of models.
For example, requirements might not be modelled but we still need to be
able to trace from
them to various types of models and elements/parts of models.
An example can be to trace from a requirement to models/model elements
requirement is designed and implemented and to models where it is verified.
And vice versa from design,