Use Cases
Other One Sheeters
What are they?
A Use Case represents a single interaction between a primary actor (who initiates the interaction) and other (secondary) actors, and the system itself. The interaction is presented as a sequence of simple steps.
A Use Case provides one or more scenarios that convey how an Actor interacts with the system to achieve a specific goal or function. Use Case actors may be end users or other systems.
Who uses them?
Business Analysts use them to direct writing of Functional Specifications.
Project Managers use them to manage scope throughout the project lifecycle.
Information Architects can use them to build storyboards for clients.
Use cases helps us make intelligent decisions about implementation priorities and effects of requested changes and enhancements on the overall level of effort can be assessed objectively.
How It Works
- Create the Diagram. Create a use case diagram (using UML or simple graphical elements) describing the actors and their interaction with the system.
- Write a Use Case Specification. Based on the diagram, document the business functionality into clear-cut and detailed use case specifications.
- Write Related Scenarios. Elaborate the Use Case into a precisely defined statement of system behaviour, if desired.
Getting More Information
This post is an edited extract from Leah Buley’s site IA One Sheeters with contributions from Tom Dell’Aringa. I am using the One Sheeter concepts here to showcase what I do as an IA and show examples of my work.
