Artifact: Use Case |  |
This artifact captures system behavior that yields an observable result of value to those interacting with the system.
Domains: Requirements
Purpose
Use cases are used for the following purposes: to reach a common understanding of system behavior. to design elements that support the required behavior. to identify test cases. to plan and assess work. to write user documentation.
Relationships
Fulfilled Slots | [Technical Specification]
Container Artifact | Use-Case Model
Roles | Responsible: Analyst | Modified By: Analyst
Tasks | Input To: Detail Use-Case Scenarios Detail System-Wide Requirements Create Test Cases Design the Solution Implement Solution Outline the Architecture Plan Project Refine the Architecture Assess Results Identify and Outline Requirements Plan Iteration | Output From: Detail Use-Case Scenarios Identify and Outline Requirements Implement Solution
Description
Brief Outline | A use case typically includes the following information: Name: The name of the use case. Brief Description: A brief description of the role and purpose of the use case. Flow of Events: A textual description of what the system does in regard to a use case scenario (not how specific problems are solved by the system). The description is understandable by the customer. The flows can include a basic flow, alternative flows, and subflows. Key scenarios: A textual description of the most important or frequently discussed scenarios. Special Requirements: A textual description that collects all requirements, such as non-functional requirements, on the use case, that are not considered in the use-case model, but that need to be taken care of during design or implementation. Preconditions: A textual description that defines a constraint on the system when the use case may start. Post conditions: A textual description that defines a constraint on the system when the use cases have terminated. Extension points: A list of locations within the flow of events of the use case at which additional behavior can be inserted using the extend-relationship.
Illustrations
Templates | Use-Case Specification
Examples | Use-Case Specification
Tailoring
Impact of not having | Without this artifact it may be unclear what functionality the solution needs to support.
Reasons for not needing | A project may use alternative requirements practices (e.g. “The system shall…” statements) which could replace use cases.
Representation Options | The use case can be documented as just a use-case specification document, or can be incorporated in a use-case model. Use cases, and parts of use cases, can also be captured in a requirements management tool.
More Information
Checklists | Use Case
Concepts | Use Case
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.