Wrecked Requirements
Inaccurate requirements account for up to 60 percent of errors in software products. You would think this would be an incentive for a software development operation to develop a precise and effective requirements process, but the truth is that most of these organizations do not even have one in place.
Paying for expensive fixes and modifications after the fact is, unfortunately, a common practice--even when a corporation is forced to realize that it is considerably cheaper to invest in an infrastructure that helps get the requirements right the first time.
The greatest source of defects and quality problems, requirements errors and deficiencies in their assimilation and dissemination are one of the biggest causes of failure in software projects. The problem with these insufficiencies is that they are often there from the get-go of a product’s inception, thus impacting its success as well as the success of the software development team and the customer.
These bugs cost time, money, and patience on everybody’s part. It also means going back to the drawing board reworking the deliverable…and that means delays in implementation and impacts to staff and other resources that are needed for other scheduled projects.
What’s Right?
The process for gathering and verifying requirements is one that demands a precise
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"There's a Mr. Bartlett to see you, sir." - Graham Chapman, Monty Python's Flying Circus |




