Artifact: Use Case |
This artifact captures the system behavior to yield an observable result of value to those who interact 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 Design Performance Test Design the Solution Detail Component Model Develop Test Cases Envision the Architecture Establish Performance Test Goals Organize Requirements Outline Component Model Plan Project Analyze Target Define Test Strategy Detail the Design Develop Security Test Policy Document Architectural Decisions Identify and Outline Requirements Identify Test Ideas Plan Iteration | Output From: Detail Use-Case Scenarios Identify and Outline Requirements
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). Write the description so that the customer can understand it. 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 of the requirements of the use case that are not considered in the use-case model, but that must be taken care of during design or implementation (for example, non-functional requirements) Preconditions: A textual description that defines a constraint on the system when the use case starts Post-conditions: A textual description that defines a constraint on the system when the use case ends Extension points: A list of locations within the flow of events of the use case at which additional behavior can be inserted by using the extend-relationship
Illustrations
Templates | Use-Case Specification Use-Case Specification (formal)
Examples | Use-Case Specification
Tailoring
Impact of not having | Without this artifact, it might be unclear which functionality the solution needs to support.
Reasons for not needing | You might not need to use a use case if your project uses alternative requirements practices (for example, "The system shall..." statements).
Representation Options | You can document the use case as a use-case specification document or you can incorporate the use case in a use-case model. You can also use a requirements management tool to capture use cases and parts of use cases.
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 © Copyright IBM Corp. 1987, 2009. All Rights Reserved. © Copyright ABC Corp. 2009. All Rights Reserved. Includes materials licensed from IBM and Eclipse. See IBM copyright and Eclipse copyright .