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

Activity: Manage Dependencies

Each requirement affects other requirements. The relationships between requirements need to be managed effectively to make informed decisions about project scope, iteration size and contents, and cost.

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 effectively manage the requirement relationships, the team must choose the relevant attributes to track (such as risk, effort, dependency, traceability, and stability) and then update those attributes during the project. Collectively, this information is referred to as Artifact: Requirements Attributes. This activity uses Requirements Attributes to manage dependencies and other factors affecting project plans.