It Is Still The Requirements

Getting Software Requirements Right
  • examine requirements readiness


  • discuss proposed requirements in detail
  • discuss operational scenarios
  • identify issues and errors
  • correct, resolve, rewrite


  • evaluate risks and benefits
  • decide on resource expenditures
  • establish a requirements baseline

Figure 1: The Requirements Definition Process

Deliver Systems That Meet Requirements
Given the difficulty of requirements definition, expend the time and effort needed to ensure that the systems you implement do, in fact, meet the true customer requirements. Employing the six step method that I have described in this article, your efforts can yield complete, consistent requirements for systems that meet or exceed the expectations of your customers--the first time and every time.

Further Reading

  • Carnegie Mellon University, Software Engineering Institute (1995), The Capability Maturity Model , Addison Wesley, Reading, MA.
  • Davis, Alan M., Achieving Quality In Software Requirements , Software Quality Professional, June 1999, ASQ, Milwaukee.
  • Gause, Donald C. and Weinberg, Gerald M. (1989), Exploring Requirements, Quality Before Design , Dorset House, New York.
  • Robertson, Suzanne and Robertson, James (1999), Mastering the Requirements Process , Addison Wesley, Harlow, England.
  • Weinberg, Gerald M. (1982). Rethinking Systems Analysis and Design , Little, Brown and Company, Boston.
  • Yourdon, Ed, "Write Stuff For Users," Computerworld, November 20, 2000.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.