Email this Mix
Slide 1 - Sequence Diagrams
- Emerson Murphy-Hill
- Creative Commons Attribution 4.0 License.
- Material Produced by NCSU Software Engineering Faculty.
Slide 2 - UML Sequence Diagrams
- Used during requirements analysis
- To refine use case descriptions
- To find additional objects (“participating objects”)
- Used during system design
- to refine subsystem interfaces
- Classes are represented by columns (first column is actor that initiates use case)
- Messages are represented by arrows
- Activations of an operation are represented by narrow rectangles
- No significance to the horizontal orderings of the objects
- Return values are optionally indicated using a dashed arrow with a label indicating the return value
- Suggestion: not to indicate the return values when it is obvious what is being returned
- can be
Slide 3 - Scenario
- A player rolls the dice and gets a 6. The player moves 6 cells. The player lands on a cell that is an un-owned property. The player’s turn is over.
- Not all nouns become objects such as, perhaps, “turn”
Slide 4 - Conditional Logic
- If the player lands on a cell that is an un-owned property, the player’s turn is over.
- If the player lands on a cell that is owned, the player must pay rent to the owner of the property.
- Then, the player’s turn is over.