REQUIREMENTS REVISITED In generally accepted software development practice, requirements analysis is supposed to happen before design, and design is supposed to happen before coding and testing. Some kind of document is supposed to come out of requirements analysis. The IEEE 830-1993 Recommended Practice for Software Requirements Specifications includes a list of quality attributes for requirements: correct, complete, unambiguous, consistent, ranked for importance, verifiable, modifiable, and traceable. The specification is supposed to guide the engineering activities that follow. The so-called generally accepted practice, however, isn’t generally practiced.
Reframing Requirements Analysis
In this article I apply systems thinking to the process of requirements analysis. Article for 1999, IEEE Computer Society by James Bach
