For
instance, a Block has one or more FMEA and a FMEA
references to only one block.
Remind,
the in the architectural model (system) there are only
architectural elements. When an user make an analysis of
system, the elements of this analysis exist on another model
(ESFArtefacts).
Consequently,
it’s import that the safety elements and architectural
elements are referenced amongst themselves.
Ummmm .....
After reflexion, I can't find any SafetyElement which need a
general association to an ArchitectureElement.
In fact, the safety artefacts are Events, Feared events,
Barrier, Failure Modes, etc. They will all have a ownership,
potentially with an ArchitecturalElement (like Block), but non
of them will 'reference' an ArchitecturalElement.
What is the purpose of this link ?
Initially it was :
Here, the aim of the 'reference' link is to ensure that the
abstract element can reference several analysis, using the
copied architectural element.
Do you want to make something similar, by having several
analysis per architectural element ?
Regards,
Jonathan
Le 22/04/2015 14:02, Jonathan DUMONT a
écrit :
This seems to be interesting !
It solves to problem to have an architectural element which
has the to properties 'reference' and 'is referenced by', in
the previous version.
This proposal is also a right way to separate the
architectural concepts and safety concepts.
Moreover the [0..1] is important on the 'reference' role, as
there are safety elements which doesn't reference an
architectural element, even if they are linked to some of
them by another way.
For example, the failure modes and feared events don't
reference any architectural element.
Regards,
Jonathan
Le 22/04/2015 11:24, MUNOZ JULHO
Yupanqui a écrit :
Hi everybody,
What do you think
about this new proposal ESFCore metamodel?
Thanks
Yupanqui
_______________________________________________
esf-dev mailing list
esf-dev@xxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://polarsys.org/mailman/listinfo/esf-dev
_______________________________________________
esf-dev mailing list
esf-dev@xxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://polarsys.org/mailman/listinfo/esf-dev
