Achieving software quality through requirements analysis

Abstract

A thorough requirements analysis prior to developing software can significantly improve the quality of the end product. The key benefit of this analysis is a better understanding of the end users' actual and underlying needs. Often the initial description of requirements does not accurately portray what the end users want. The outlined methodology including interviews with a cross section of users identifies three types of key information: what tasks are to be accomplished; the information flow; and future requirements. Armed with this knowledge, the system design and coding can be accomplished more quickly and accurately, user needs met effectively, and costs due to rework reduced substantially.<>