


|
When Requirements Go Bad - Understanding the causes for Requirements errors can help prevent them
sponsored by Ivar Jacobson Consulting
|
|
|
Posted:
|
17 Jun 2008
|
|
Published:
|
01 Jan 2008
|
|
Format:
|
PDF
|
|
Length:
|
13
Page(s)
|
|
Type:
|
White Paper
|
|
Language:
|
English
|
|
|
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
testing and analysis
change and configuration management
requirements management
business intelligence solutions
business process management
application lifecycle management
|
|
|
|
 |
BROWSE RELATED
RESOURCES
Functional Requirements | Software Development Life-Cycles | Software Development Methodologies | Software Development Tools | Software Project Management
|
View All Resources
sponsored by Ivar Jacobson Consulting
|
|
Research Library Copyright © 1998-2008 Bitpipe, Inc. All Rights Reserved. Designated trademarks and brands are the property of their respective owners. TechTarget · 117 Kendrick St · Needham, MA · 02494
Use of this web site constitutes acceptance of the Bitpipe Terms and Conditions and Privacy Policy. webmaster@bitpipe.com
|