When Requirements Go Bad
The notion that errors in requirements are a contributing cause to the failure of many projects is nothing new. It is easy to attribute the problem to lack of clarity in the requirements - that if only the ambiguities could be eliminated all would be well. Ambiguous, unclear or incomplete requirements are serious problems, to be sure, but they are not the sole source of requirements errors. Requirements errors have many sources, however, and ambiguous or unclear requirements are only part of the problem. In order to reduce requirements errors, it's worth exploring a nuerrors to find their source and strategies for dealing with them.
| DOWNLOAD NOW | |||||
| Publisher: | Ivar Jacobson International | Published: | 08/22/2008 | Type: Length: Format: |  Whitepaper 14 pages |
| Rating: | Share: | Send to a friend | |||
| Topics: | Project Mgmt. Agile | ||||
Related Library Resources
02/18/2009 High Performance Rules Engine for Outsourced Data Center
09/16/2008 3PAR Thin Provisioning
01/25/2009
Essential EMF
10/13/2009 The Next Generation of Source Code Analysis
09/24/2008 Equifax Case Study
08/07/2008 Managing Small/Medium Business Tool Synchronization
09/26/2008 Six Steps to Signing your Java Code
07/12/2009 NetBeans IDE 6.7 Update
08/11/2008 Agile Development and Model Driven Design Solve the Broken Software Delivery Process
08/06/2008 Service-Oriented Virtualization
Spotlight Resources
Core Mule
Mule is one of the most mature open source enterprise service busses (ESBs) out there. It provides an easy to use, lightweight ESB that can easily...
Getting Started with Equinox and OSGi
Equinox is a highly modular, dynamic Java runtime environment based on the OSGi framework specifications. This reference card gives you a quick...
Essential EMF
The Eclipse Modeling Framework (EMF) is a powerful framework and code generation facility for building Java applications based on simple model...
Want your resource here? Contact our team today.
