Discipline: Requirements |
This discipline defines the minimal tasks required to elicit, analyze, specify, validate and manage the requirements for the system to be developed.
Relationships
Tasks | Define Vision Detail Requirements Find and Outline Requirements
Main Description
The purpose of this discipline is to: Understand the problem to be solved (what the users want) Define the requirements for the solution (what the system must do) Define the boundaries (scope) of the system Identify external interfaces for the system Identify technical constraints on the solution Provide the basis for planning iterations Provide the initial basis for estimating cost and schedule To achieve these goals, it is important to understand the definition and scope of the problem that we are trying to solve. Stakeholders are identified and the problem to be solved is defined. Having agreed on the problem to be solved, the Requirements for the system are elicited, organized, analyzed, validated and specified. Throughout the lifecycle, changes to the requirements are managed. The Requirements discipline is related to the other disciplines in the following ways: The Analysis & Design discipline gets its primary input from the Requirements discipline The Test discipline validates the system against the requirements The Configuration & Change Management discipline provides the mechanisms to manage changes to the requirements The Project Management discipline plans the project and each iteration by analyzing the prioritized requirements and assigning work
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