![]() ![]() Return value := MessageName(Arguments) * Sequence Number. An instance can be: An object, not a class An actor Types of objects in a diagram interface object entity object control object Messages ( ) can be Simple like: One object sends a message to a passive object The sender does not care what happens to the message Messages can be Return messages ( ) Results of procedure callsĥ Sequence Diagrams Activation: thick box over object's life line drawn when object's method is on the stack either that object is running its code, or it is on the stack waiting for another object's method to finish nest activations to indicate recursionĦ Sequence Diagrams Messages have a specific format * Create a sequence diagram for each use case scenarioĤ Sequence Diagrams Sequence diagrams show how instance exchange messages. Detail how operations are carried out Dynamic Diagrams Organized according to time The time progresses as you go down the page The objects involved in the operation are listed from left to right according to when they take part in the message sequence. Interactions between objects are indicated by annotated arrows. ![]() ![]() The objects and actors involved are listed along the top of the diagram, with a dotted line drawn vertically from these. Used to model the interactions between the actors and the objects within a system. 1 Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering BookĢ Sequence diagrams: An Interaction Model ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |