Legacy Issue Number: 11612
Source: oose Innovative Informatik eG ( Tim Weilkiens)
this about the interpretation of the the containment
relationship and its
implementation on the tool side.
We are using MagicDraw 14.0 and SysML 1.1sp2.
As soon as a containment relationship is created between two
contained requirement is automatically relocated to the package
of the container. This prevents distribution of requirements
packages, in particular if a contained requirement belongs to
I would like to properly distribute them.
We have a requirement A which contains requirement B and C.
A is a requirement on very high level of the system which is decomposed into
requirements B and C on a subsystem level.
To avoid to have all requirements together (because B and C
belong to the
subsystems) we want to put A, B and C in different packages
but still have
the containment relationship (as foreseen by the SysML spec.)
that's why I think it is different from a package containment. They
are not the same.
Reported: SysML 1.0 — Mon, 15 Oct 2007 04:00 GMT
Disposition: Resolved — SysML 1.1
No Data Available
Updated: Fri, 6 Mar 2015 20:58 GMT