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 developers.
Domain: Requirements Work Product Kinds: Model
Purpose
The Use-Case model is useful when you consider it along with its related artifacts: Artifact: Use Case and Artifact: Actor. In general, a Use-Case model presents an overview of the system; therefore, it provides a basis for an agreement between customers 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
Contained Artifacts | Actor Use Case
Roles | Responsible: Analyst | Modified By: Analyst
Tasks | Input To: Analyze Architectural Requirements Detail Requirements Demonstrate the Architecture | Output From: Detail Requirements Find and Outline Requirements
Tailoring
Representation Options | Tailor this artifact to support the project team's needs. Projects may not include the Use-Case model as one of the work products being created. Identifying actors and use cases, then describing the use-cases and scenarios are recommended tasks though.
More Information
Checklists | Use-Case Model
Concepts | Use-Case Model
Guidelines | Use-Case Model
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright