Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Tags and keywords UML keywords Sequence Diagram Lifeline Message MessageSort MessageSort::synchCall Message::messageSort MessageSort::reply reply-message-label Operation Message::signature SysML keywords Block Slide kind SysML Sequence Diagram UML Sequence Diagram Click on the image to view it full size Q: What is 'Ready' on the reply Message ? A: In this case, because there is no signature, anything you like! UML-2.5.1: 'If the Message has a signature, this will be the name of the Operation referenced by the signature (which should be the Operation for whose call this is a reply). Otherwise the name is unconstrained.' Up next Figure D.11 - Establishing HSUV Requirements Hierarchy (containment) Notes Snippets (quotes/extracts) [SysML-1.6] The lifelines on Figure D.10 (“whitebox” sequence diagram) need to come from the Power System decomposition. This now begins to consider parts contained in the HybridSUV block. [SysML-1.6] A synchronous Message (messageSort equals synchCall) has a filled arrow head. [SysML-1.6] A reply Message (messageSort equals reply) has a dashed line with either an open or filled arrow head. [UML-2.5.1] A reply-message-label is used for reply Messages. It has the following form ... [UML-2.5.1] The message-name appearing in a reply-message-label is the name property of the Message. [UML-2.5.1] If the Message has a signature, this will be the name of the Operation referenced by the signature (which should be the Operation for whose call this is a reply). Otherwise the name is unconstrained. Visit also Visit also (backlinks) Related slides (includes other tutorials) Related slides (backlinks, includes other tutorials) Flags Book traversal links for Figure D.10 - White Box Interaction for “StartVehicle” Previous Up Next
