|
ABSTRACT:
Getting software requirements right is the most critical aspect of the software development lifecycle. Ambiguous, unclear or incomplete requirements can cause serious problems during software development. These problems typically result in costly rework, compromised product quality, delayed delivery on current projects and start of new ones and the potential for project failure.
This white paper discusses methods for reducing requirements errors during the software development lifecycle. Survey a number of common requirements errors and learn how to identify their source and the strategies best suited for eliminating them. Explore the critical role testing plays in determining whether or not requirements were actually satisfied. Discover the three major categories of requirements errors, including:
- errors of conception
- errors of specification
- errors of implementation
|
| |
 |
| |
AUTHOR:
Kurt Bittner
CTO-Americas, Ivar Jacobson Consulting
Kurt Bittner is CTO-Americas for Ivar Jacobson Consulting. He is the author of numerous articles on software engineering, and is the co-author with Ian Spence of "Use Case Modeling", published by Addison-Wesley in 2002, and "Managing Iterative Software Development Projects", published by Addison-Wesley in 2006. His industry experience spans more than twenty-four years of successfully applied iterative approaches to delivering software solutions in a number of industries and problem domains, and he is a past contributor to the Rational Unified Process.
|
My Research History
Free Newsletters
