The property at each successive position following the first position must be contained in the classier that types the property at the immediate preceding position. The path must start from a property owned by either a classifier, which is the target of the simulation configuration or a classifier of an instance specification, which is the target of the simulation configuration. It is used to specify a property path to an object that will be recorded by a sequence diagram generator. They are elements (objects) that will be ignored (will not be recorded as lifelines) during a simulation recording. They are signals that will be ignored (will not be recorded) during a simulation recording. You need to select only the element that can own an Interaction element, otherwise a model inconsistency will occur. A generated Sequence diagram will be created under that particular Interaction element. It is an element that owns a generated Interaction element. It contains the following six tag definitions: You can customize recorded messages (signals) and lifelines using a SequenceDiagramGeneratorConfig.įigure 3: A SequenceDiagramGeneratorConfig element showing its parameters.Ī SequenceDiagramGeneratorConfig is a stereotype that is inherited from an ExecutionListener stereotype. Select Arguments in the tree on the left-hand side of the specification dialog to see the value of each argument.Either double-click a message or right-click it and select Specification to open the specification window.How to see the values of arguments sent with a signal or an operation call Double-click the message or right-click it and select Specification to open the specification window.How to see what connector a signal or an operation call is sent through See the following figure for examples.įigure 2: A sequence diagram depicting call messages running between lifelines. StateInvariants are designated by yellow rounded rectangle symbols. Changes in value are enclosed in constraint brackets, for example. (vi) record each change in the feature value of a lifeline object as a StateInvariant on the Lifeline. (v) record each change in the state of a lifeline object as a StateInvariant on the Lifeline, with the changed state symbol. (iv) record an object that receives a signal and(or) an operation call as a Lifeline, unless it exists in the diagram, the object will be called 'lifeline object'. (iii) record each operation call caused by a call message, a CallOperationAction, or a ALH.callOperation with argument and return value as messages in the sequence diagram. (ii) record each signal sent from the selected runtime object as a Message in the sequence diagram. (i) create the first Lifeline, which represents the selected runtime object. Whenever you simulate a model (for example, Stereo System as shown in the figure above, Cameo Simulation Toolkit will An empty sequence diagram will be created.įigure 1: Shortcut menu that can be accessed from the simulation console. Click Create Sequence Diagram on the context menu (see the following figure).In the Variables pane, select and right-click a runtime object.How to record signals sent from and to a runtime object and subsequent state/value changes of the related objects as a sequence diagram The sample StereoSystem.mdzip, located in the /samples/simulation/ directory, will be used throughout this section. This section demonstrates how to record signal, state change, operation call, and value change as a sequence diagram during a model simulation. (iv) record changes of states and primitive values as StateInvariants on Lifelines that represent features of objects that own the states or the values. ![]() Connectors will be assigned to messages if operations are called via ports. (iii) record operation calls as CallMessages connected between Lifelines that represent operation caller and operation owners respectively. Connectors will be assigned to the messages if signals are sent via ports or connectors. (ii) record signals as SendMessages connected between Lifelines that represent signal senders and signal receivers respectively. (i) record created objects as CreateMessages connected between Lifelines that represent the object creator and features of the created object respectively. The recording capability of Cameo Simulation Toolkit allows you to:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |