Critical reading for software developers

One virtue of the SADT view of software development is its insistence on reading as well as writing the descriptions produced, which means that the business of reviewing what has been written is organized in the author/reader cycle.

Abstract

Reading is no less important in the earlier stages of development, in requirements, analysis, specification, and design, where the descriptions are-or should be-more varied both in form and in content than they are in programming. One virtue of the SADT view of software development is its insistence on reading as well as writing the descriptions produced. In SADT, the business of reviewing what has been written is organized in the author/reader cycle. New views of mature ideas on software quality and productivity are presented.>