1 / 19

Additional Visio Diagrams

Additional Visio Diagrams. State Machine & System Sequence Diagramming. The State Machine Diagram. Used to document states of an object Is based on the object and not the class Only needed when a class of objects goes through varied distinct state with key preconditions for transition

inara
Télécharger la présentation

Additional Visio Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Additional Visio Diagrams State Machine & System Sequence Diagramming

  2. The State Machine Diagram • Used to document states of an object • Is based on the object and not the class • Only needed when a class of objects goes through varied distinct state with key preconditions for transition • Usually documents the lifecycle of an object • Focus is on • States • Transitions between states & • Guards (conditions that must be met to move to the next state

  3. Creating a state simply requires dragging icon to desired spot • Double clicking to open dialog box and enter a descriptive name for the state and perhaps a Documentation entry • State appears as an object under the main model and can be used in other diagrams

  4. Transitions are used to link 2 states & are drug and dropped like all VISIO flows • Arrow points to the state we are moving into • After double clicking specify a name and • If there is a condition that must be met before transitioning to the receiving state • Check the Guard checkbox & enter a description of the condition in the Guard Body

  5. Then pick the Action Category on the Transitions dialog box and • Pick new • specify an appropriate Action type • Under the Action column enter a descriptive name for the action that transitions the object to the new state

  6. Other State Machine Elements • Initial & final state • Decision, and Note • Have the same meaning/ specification as in Activity diagrams • Fork & join transitions similar to Activity diagram synchronization bars • Horse shoe shaped transition can be used to link back to same state

  7. System Sequence Diagram • A variant of the Design level Sequence diagram • Focus is on the messages between objects and their timing (sequence) • Creation of a message with parameters • Creates an Operation (method) in the class receiving the message, • Receiving entity must be a class • Message specs. Are added to the receiving class

  8. System Metaclass • Since the system Sequence diagram focus on the boundary of the system and messages between the system and an Actor, • We create a metaclass called System in VISIO so that we can send it messages with parameters.

  9. 1st Create an object lifeline for the Actor – Drag &Drop object lifeline • Double click, on the dialog box for the Classifier Role Category • enter a descriptive name • Find the appropriate actor element from the classifier dropdown (all actors you have created in other diagrams will be available)

  10. Adding the System Metaclass • Pick object lifeline & Drag & drop • Double click & in the classifier role Category Dialog box: • Click on the New icon to the left of the classifier dropdown. • This displays a Class properties dialog box. • Under the Class category • Name your class System and • Select MetaClass as its Stereotype

  11. Features of your MetaClass • System is now an element available across diagrams • It is a class capable of having attributes and operations • This allows us to send it messages with parameters • They are stored as Operations (Methods) of our System MetaClass

  12. Message to a Class • Now we can send a message to our System MetaClass & that message can have parameters • Pick the Message Element - Drag&Drop • Double Click. From the Message Category Dialog box • Provide a descriptive name • Click on New icon left of the Operation DropDown • On the Next Dialog box in the Operation Category • Provide an operation name and • If needed select a return type (in our example we are returning course objects)

  13. Next select the Parameters category, click new and • Enter names of parameters that will be sent by the user to the system (inputs). The kind will be in and you can specify the datatype of the parameters as desired

  14. Note that a different element is used for a return message (a dotted line) The arrow for the return message will point to our actor • Since the actor is outside the system and not a class it cannot have Operations and can’t be sent parameters • We simply provide a name descriptive of what the system sends to the user

  15. Noting Repeated Messages • Best way to denote a repetition of sets of messages in the VISIO Sequence Diagram seems to be to use the 2 element constraint component. • This component provides a vertical line that can be extended to intersect the messages we wish to designate as being repeated • Drag & Drop, Double-Click and • Enter a description of the looping in he name field of the dialog box • You will need to modify the Display properties for this element to have the name display NOT Elegeant, but it works

  16. Activity Diagrams: Documenting Details of a use Case • Swim lanes defined for the Actor(s) and the Use Case • Action State used to indicate • Actions (events) initiated by the user • System actions to respond • Flows from 1 system action to the next to the next if multiple steps involved in system response to the user • Flows across the swim lanes represent the message flow from actor to system and back

More Related