A recommended practice for describing software designs: IEEE standards project 1016
H. Jack Barnard, Robert F. Metz, Arthur L. Price · IEEE Transactions on Software Engineering · 1986
The method outlined presumes that a design is completely described when the information needs of each design user are satisfied. The minimum set of design users and their specific information requirements are discussed. An information model is used to describe the needed design information through a set of 15 standard design entity attributes. To simplify the access and assimilation of design information, an organization of the entity attributes into four distinct design views is proposed.