{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}


For each system events that each actor generates for

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: scenario SSD for Process Sale scenario (Larman, page 175) From Use Case to From Use Case to Sequence System Diagram How to construct an SSD from a use case: 1. 2. 3. 4. Draw System as black box on right side For each actor that directly operates on the System, draw a stick figure and a lifeline. For each System events that each actor generates For in use case, draw a message. in Optionally, include use case text to left of diagram. Example: use cases to SSD Example: use cases to SSD Identifying the right Actor Identifying the right Actor In the process Sale example, does the customer interact directly with the POS system? Who does? Cashier interacts with the system directly Cashier is the generator of the system events Why is this an important observation? Naming System events & operations Naming System events & operations System events and associated system operations should be expressed at the level of intent Rather than physical input medium or UI widget Start operation names with verb (from use case) Which is better, scanBarCode or enterItem? SSDs and the Glossary in parallel SSDs and the Glossary Why is updating the glossary important when developing the SSD? New terms used in SSDs may need explanation, especi...
View Full Document

{[ snackBarMessage ]}