636-530-7776
Legend: RUP Notation
Workflow > Detail > Activity

Activity: Prioritize Use Cases

The team sets priorities for Artifact: Use Cases to determine the contents and focus for each iteration within the project. This activity describes the contributing factors to consider when setting priorities.

More detail: Purpose - Frequency - Steps

Click the icons for definition

Business Strategist
Software Architect
Information Architect
Subject Matter Expert
Project Manager
Requirements Analyst
Stakeholder
Business Concept (from Business Strategy)Business Use Case Model (from Business Strategy)User Research ReportBusiness Operations Plan (from Business Strategy)
Find Actors and Use Cases
Manage Dependencies		 Glossary (from Environment)
Use Case Modeling Guidelines
Supplementary SpecificationUse Case (sketch)Requirements AttributesUse Case ModelActor Catalog
Software ArchitectPrioritize Use CasesSoftware Architecture Document (updated)
Requirements Analyst Define System Wide Attributes

Purpose

To determine the priority and extent of specific Use Cases to be worked on during a given iteration. Once the project's scope is known, the Role: Software Architect analyzes the Use Cases to determine which ones are architecturally significant. These Use Cases, in whole or in part, have high priority and should be developed during the Elaboration phase. Other use cases are completed during the Construction phase.

Other factors contributing to Use Case priority and the contents of iterations include: risks, effort, dependencies, business priorities, and available resources. Role: Stakeholder, Role: Project Manager, Role: Requirements Analyst, and others participate in priority setting discussions.