Help | Advanced Search
What's New?
What's Popular?


Avoiding Software Requirements Errors
sponsored by Ivar Jacobson Consulting
Posted:  18 Jun 2008
Published:  01 Jun 2008
Format:  PDF
Length:  15   Page(s)
Type:  White Paper
Language:  English


ABSTRACT:
While serious problems may arise from requirements being ambiguous, unclear or incomplete, they are not the sole source of requirements errors. Organizations often fail to realize that no single approach works in all cases for all kinds of requirements. Multiple techniques must be implemented to gain a more accurate picture of what needs to be built to achieve business efficiency.

This white paper presents a simple taxonomy for requirements and discusses the strengths and weaknesses of each of the major types of requirements approaches. Discover why no single approach can be used to develop requirements and explore how to implement a blended approach, based on the needs of your project or organization. Gain insight into the three major categories of requirements errors, including errors of conception, specification, and implementation.



Author

Kurt Bittner
CTO-Americas ,  Ivar Jacobson International
Kurt Bittner is CTO-Americas for Ivar Jacobson International. 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.



BROWSE RELATED RESOURCES
Functional Requirements | Prototyping | Software Development Tools | Software Project Management

View All Resources sponsored by Ivar Jacobson Consulting

Library Home | Advertise with Us | Product Library
A Service of Bitpipe