Information Technology Reference
In-Depth Information
Chapter 1
Introduction to Requirements
Engineering and Management
Requirements are the precursor to all other software development phases, namely,
software design, software construction and testing. When the end result of the
software development activity is a COTS (Commercial Off The Shelf) product, we
term requirements as ''product specifications''. When the end result of the software
development activity is to deliver the product to a single client in a project scenario,
we use the term requirements. In either case, the activity of managing the require-
ments is the same.
The importance of properly managing requirements cannot be overemphasized
as any omission of a vital requirement or error committed during requirements
analysis results in increased cost of the product and in some cases, may result in
project / product failure. Another important aspect of requirements management is
the change management. If changes to requirements are not properly controlled,
it may result in uncontrollable scope creep and increased costs.
A proper understanding of requirements and careful management thereof can
prevent project failures and contribute to the delivery of quality software products
to intended clients.
1.1 What is a ''Requirement''
Consider these five statements:
1. I ''hope'' to have a car (The capability to posses a car is absent but hope exists
that someday it might be possible)
2. I ''wish'' to have a car (The capability to posses a car is distinctly possible but
not feasible yet)
3. I ''desire'' to have a car (The capability to posses a car exists. But there are
other competing demands to cater to.)
Search WWH ::
Custom Search