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

Use Case Modeling Guidelines (from Environment)GlossaryBusiness Rules (from Business Strategy)
Subject Matter Expert
Information Architect
Requirements AnalystDetail a Use CaseStructure the Use Case ModelManage Dependencies
Requirements Analyst
Subject Matter Expert
Stakeholder
Actor CatalogWireframesUse CaseUse Case ModelRequirements Attributes
Requirements ReviewerReview Requirements Site Map
Review Record

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.