Requirement Management

REQUIREMENT MANAGEMENT

Presented by :

Mubashar Mehmood (1632)

BS SE 5th Evening

WHAT IS REQUIREMENT ?

A capability that must be met or possessed by a system to satisfy a contract, standard, specification, regulation, or other formally imposed documents.

A requirement is something that the product must do or a quality that the product must have

The voice of your customer, The building blocks of your products, Verification that you are building what you mean to build.

REQUIREMENT MANAGEMENT

REQUIREMENT MANAGEMENT Requirements management is the process of

documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome.

Requirements management is the sum of all activities in connection with requirements that take place after the requirements have been developed or engineered.

OVERVIEW

The purpose of requirements management is to assure the organization documents, verifies and meets the needs and expectations of its customers and internal or external stakeholders.

Requirements management begins with the analysis and elicitation of the objectives and constraints of the organization.

Requirements management involves communication between the project team members and stakeholders, and adjustment to requirements changes throughout the course of the project

WHY REQUIREMENT MANAGEMENT

The principal concerns are

Managing the relationships between requirements Managing priorities between requirements Managing the dependencies between different

documents Requirements document Specification And other documents produced in the systems engineering process

Managing changes to agreed requirements

WHY REQUIREMENT MANAGEMENT

Between 40% and 60% of software failures and defects are the result of poor software requirements management.

Cost of rework: 70% to 85% of rework cost come from requirements errors.

Failures attributed to poor requirements management Incorrect definition of requirements Poor management throughout development

lifecycle

HOW REQUIREMENT MANAGEMENT ?

Requirements Planning Requirements Elicitation Requirements Analysis Requirements Development Requirements Validation Requirements Acceptance Requirements Administration

HOW REQUIREMENT MANAGEMENT ?

SUMMARY

Manage versions of requirements documents. Adopt and enforce a change control process. Perform requirements change impact analysis. Store requirement attributes. Track the status of each requirement. Trace requirements into designs, code, and tests

REFRENCES

http://www.jiludwig.com/Requirements_Management.html

http://www.akamonitor.cz/2007/08/sprva-poadavk-v-studijnm-plnu-manaersk.htm

http://www.rational.com/products/whitepapers.

http://www.rational.com/products/reqpro.

http://en.wikipedia.org/wiki/Requirements_management#Requirements_activities

QUESTIONS