-
Key: SYSMLR-130
-
Legacy Issue Number: 18737
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
In Appendix A there is a list that says:
The following are some of the designated model elements associated with the different diagram kinds.
? activity diagram - activity
? block definition diagram - block, package, or constraint block
? internal block diagram - block or constraint block
? package diagram - package or model
? parametric diagram - block or constraint block
? requirement diagram - package or requirement
? sequence diagram - interaction
? state machine diagram - state machine
? use case diagram - packageBased on my readings, which seems to indicate that the type of element whose namespace contains the elements in the diagram, I would say it should be
? activity diagram - activity
? block definition diagram - block, package, or constraint block, activity, profile
? internal block diagram - block or constraint block
? package diagram - package or model, view, modelLibrary, profile
? parametric diagram - block or constraint block
? requirement diagram - package or requirement, model, view, modelLibrary,
? sequence diagram - interaction
? state machine diagram - state machine, block, operation, use case
? use case diagram ? package, block, view, model, modelLibrary( I left out some cases of profile, when I couldn?t think of what it would show, but profile could be added to any list that covers package)
-
Reported: SysML 1.4 — Wed, 29 May 2013 04:00 GMT
-
Disposition: Resolved — SysML 1.5
-
Disposition Summary:
List of "some of the designated model elements" that can represent a diagram frame has been clarified.
The text reads 'some of the designated model elements' and not 'all of the designated model elements' in the following introductory sentence. The list does not show all possible elements that can designate a frame in the same way that the diagram elements tables do not identify all possible elements that can be shown in a SysML diagram. In general, this is a broader issue with SysML that we have not rigorously mapped the concrete syntax to the abstract syntax. However, this may be done in the future, at which time we can include the complete list of elements that can designate each frame. In the interim, including or excluding the element in this list does not imply any change to the underlying abstract syntax and semantics, but merely impacts the ability to present this model element as a diagram frame.
The resolution incorporates some of the proposed changes but not all. A compelling use case should be provided to designate other diagram elements as frames.
The following should be noted in response to the proposed changes:
• As of SysML v1.4, view extends class and not package
• A state machine diagram always designates a state machine -
Updated: Thu, 6 Apr 2017 13:49 GMT
-
Attachments:
- R-130 SF Response 20151010.rtf 2 kB (application/rtf)
- R-130 SF Response 20151029.rtf 2 kB (application/rtf)
- R-130_resolved-draft-designating diagram frames.docx 25 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)