-
Key: SYSML17-21
-
Legacy Issue Number: 12147
-
Status: closed
-
Source: No Magic ( Darren Kelly)
-
Summary:
Figure B.27: <<view>> Package "steals ownership" of MOEs, Actor, UseCase and Requirement Severity Critical since there is currently no sensible way to implement <<view>> in tools ! In Figure B.27 - Establishing a Performance View of the User Model It is not at all clear how the MOEs, Actor, UseCase and requirement should be shown as directly within the view without the view package "stealing ownership". Appears to break constraint: '7.3.2.4 View [1] A view can only own element import, package import, comment, and constraint elements.' See also example images in Magicdraw UML SysML Plugin at: http://school.nomagicasia.com/node/127 http://school.nomagicasia.com/files/images/Figure%20B.27%20-%20Establishing%20a%20Performance%20View%20of%20the%20User%20Model.png Note that this relates to:: Issue 11500: <<view>> as Package extension is very bad idea (sysml-rtf), No Magic, Inc. (Mr. Nerijus Jankevicius, nerijus@magicdraw.com nerijus@nomagic.com) '<<view>> as Package extension is very bad idea. Package is used for ownership, so it is not possible to show the same elements in different packages (as different point of view)'
-
Reported: SysML 1.0 — Wed, 2 Jan 2008 05:00 GMT
-
Disposition: Duplicate or Merged — SysML 1.7
-
Disposition Summary:
Merge with
SYSML17-185This issue is tracked and resolved in the integrated Annex D model that is required by
SYSML17-185. -
Updated: Thu, 22 Dec 2022 13:45 GMT