IT Employment

General discussion


Five phases of requirements management

By MaryWeilage Editor ·
Tell us what you think about the five phases of requirements management, as featured in this week's Application Developer Management newsletter. Please rate this column from 1 to 5, with 5 being the highest.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Great Advice!

by trmweb In reply to Five phases of requiremen ...

If these "Five phases" are done right, you will have a firm grasp on the project scope and have a solid basis for time estimates. You made these steps generic enough to apply to any type of project and platform. Great Article!

Collapse -

question about CAB

by jg In reply to Five phases of requiremen ...

Enjoyed the article very much. Practical information that can apply to many different types of projects. A question: In "phase 1: initiation," Scott identifies one of the components as "CAB." I am not familiar with that acronym. Can someone explain?

Collapse -


by sdw5177 In reply to question about CAB

The CAB should really be CBA for Cost Benefit Analysis.

Darn fingers!

Thanks for the feedback.


Collapse -

Needs more content

by esb_us In reply to Five phases of requiremen ...

Requirements Process needs more content -

a. Emphasis on Business Goals & Objectives. Business objectives must be enumerated and all functional and non-functional requirements should be cross-referenced to the enumerated business objectives. Business objectives should be stated by stakeholders.

b. Scope document should tally with business objectives. Any changes in scope should be done with a change management process and tallied with enumerated business objectives. Therefore, any change in requirements would be reflected as a change in business objectives.

c. 'Phase 5 - Managment' should also include an 'Alignment' chapter. This would describe alignment of the system being built with the business objectives - this can be done viakey metrics (scorecard-type mapping).

Over 70% of failed systems (developed, overbudget, overdue, cancelled, etc) are attributed to a failure in Requirements process.
The Requirements Process is a human communication & collaboration process and has very little to do with the system's technology. It is a reflectance of the management process, good or bad.

S.B. Chatterjee
Manager, Business Tech Services
KeyTech, LLC
Hartford, CT

Collapse -

Unrealistic Expectations

I think a really big point to make is that a purpose of requirements management is to avoid unrealistic expectations.

In web development, I frequently (more like *always*) find that the customer is shocked at how much designing has to go on before even one line of production code gets written, much less dealing with the tiered data management that every app needs.

Collapse -

Oh, do I agree!

by sdw5177 In reply to Unrealistic Expectations

Definitely. Hopefully if we do our Requirments process correctly we can delivery this message as well.

Great insight.


Collapse -

Samples of Requirements Doc's

by tdean2000 In reply to Five phases of requiremen ...

My company is just delving into PM concepts and processes. I'm trying to devise a simple style for a Requirements Document - many of our projects are small and short term in nature (30-120 days). While we want to follow a reasonable path here, we have to be realistic about how much time is spent on the PM process as well. Anyone have some examples they can send me or point me to? Looking for style and type of content that is outlined in the document.

Collapse -

Disciplined Requirements Management

by kevinh In reply to Five phases of requiremen ...

Requirements Management that has been employed successfully in aerospace systems (including software)involves generally four phases: Identification, Analysis, Implementation and Verification. Analysis considers the clarity, accuracy, achievability,ownership and verifiability of each requirement, and very well may result in splitting a single (or several) requirements into many, consolidating several into into less, or spawning the creation or of completely new requirements or deletion of requirements. Requirements Analysis incorporates the elements of mapping (to system entities, owners, etc.), allocation, and negotiation. Requirements Verification is the process of determining the compliance of the system to the set of requirements thathas been levied on it. It involves identifying and mapping verification methods (similarity, inspection, analysis, demonstration, test, etc.) to each requirement, and determining compliance by executing those methods.

Those interested can find information on disciplined requirements management processes at the International Council on System Engineering at, the Software Engineering Institute at, and the Software Productivity Consortium at

Collapse -


by kfp36 In reply to Five phases of requiremen ...

Quality steps to adhere too when implementing a project. It has an added benefit of set quidelines. No sudden changes from outside sources.It also prevents people from the floor demanding additional changes.

Related Discussions

Related Forums