Artifact: Use-Case Model |  |
This artifact captures a model of the system's intended functions and its environment, and serves as a contract between the customer and the team.
Domains: Requirements
Purpose
This artifact presents an overview of the system's intended behavior. It is the basis for agreement between stakeholders and the project team regarding the intended functionality for the system. It also helps to guide the various tasks in the software development lifecycle.
Relationships
Fulfilled Slots | [Technical Specification]
Contained Artifacts | Use Case
Roles | Responsible: Analyst | Modified By: Analyst
Tasks | Input To: 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
Illustrations
Examples | Evolution of the Use-Case Model
Tailoring
Impact of not having | Without this artifact it can be difficult to determine all of the relationships between actors and use cases. It can also be difficult to gain an understanding of how different use cases relate to each other.
Reasons for not needing | If the overall set of use cases is fairly small with no complex relationships between them, then this artifact may not be required. If an alternative approach is being used to document functional requirements then this artifact is not needed.
Representation Options | Representation options include: reports and diagrams from UML modeling tools, graphical representations created using drawing tools, drawings on whiteboards. Most of the information in the use-case model is captured in the use-case specifications.
More Information
Checklists | Use-Case Model
Concepts | Actor Use Case Use-Case Model
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.