2009 use cases

2009 use cases - Use Cases Used to capture functional...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Fall 2009 ACS-3913 Ron McFadyen 1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability, performance, supportability, interface, … A use case represents a goal an actor wants to accomplish. An actor is anything with behaviour – roles played by people, organizations, other systems
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ACS-3913 Ron McFadyen 2 Process Sale Use Case – fully dressed Primary Actor : the actor that executes the use case Preconditions : describes a state the system must be in prior to the execution of the use case Postconditions : describes a state the system must be in after execution of the use case Main Success Scenario : Step by step description of the interaction between the actor and the executing use case Extensions or Alternate Flows Alternate ways steps could terminate At this point in time (Inception), processing a sale is described in one use case that contains a main success scenario and all possible alternative scenarios. Some components of the written use case:
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 7

2009 use cases - Use Cases Used to capture functional...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online