The values of the 'Uses', 'Results' and 'State' columns are added as Tagged Values of the Message.If you have not selected the 'Show Sequence Numbering' checkbox on the 'Diagram Sequence' page of the 'Preferences' dialog, the Message name on the Sequence diagram is prefixed by the step number, as shown in the example diagram in this topic if you have selected the checkbox, the message sequence number is shown instead of the step number.Because the diagram generator acts on element names in the step, you must not use the element names as normal text for example, in step 1 in the example dialog, the term ATM-Card is interpreted as a reference to the ATM element, and two 'Customer inserts ATM-Card into ATM' messages are generated for the step (to avoid confusion, in the diagram the first Message has been deleted).The subsequent Context Reference element(s) become the destination(s).The first Context Reference element in a step is treated as the originator.The step itself becomes the Message between an originator and its destination(s).So, each Context Reference element named in a scenario step is modeled as a Lifeline.All the elements involved in the scenario must be identified in the 'Context Reference' tab that is, relationships must already exist between the scenario parent element and the other elements named in the scenario (t he Scenario is a Process, and the Sequence diagram is showing the flow of messaging between different Lifelines for that to happen the lifeline/object has to be defined, which is achieved using a Context Reference).There are a number of points to note in this process: When you create a scenario on an element and then generate a Sequence diagram, an Interaction is created as a child of the selected element to act as a container for the diagrams - the Basic, Alternate and Exception paths are each modeled as a separate Sequence diagram under the Interaction.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |