IEEE 1016-2009 pdf download IEEE Standard for Information Technology—Systems Design— Software Design Descriptions
1. Overview
1.1 Scope
This standard describes software designs and establishes the information content and organization of asoftware design description (SDD). An SDD is a representation of a software design to be used forrecording design information and communicating that design information to key design stakeholders. Thisstandard is intended for use in design situations in which an explicit SDD is to be prepared. Thesesituations include traditional software construction activities, when design leads to code, and “reverseengineering” situations when a design description is recovered from an existing implementation.
This standard can be applied to commercial, scientific, or military software that runs on digital computersApplicability is not restricted by the size, complexity, or criticality of the software. This standard can beapplied to the description of high-level and detailed designs.
This standard does not prescribe specific methodologies for design, configuration management, or qualityassurance. This standard does not require the use of any particular design languages, but establishesrequirements on the selection of design languages for use in an SDD, This standard can be applied to thepreparation of SDDs captured as paper documents, automated databases, software development tools, orother media.
1.2 Purpose
This standard specifies requirements on the information content and organization of SDDs. The standardspecifies requirements for the selection of design languages to be used for SDD, and requirements fordocumenting design viewpoints to be used in organizing an SDD
1.3 Intended audience
This standard is intended for technical and managerial stakeholders who prepare and use SDDs. It guides adesigner in the selection, organization, and presentation of design information. For an organizationdeveloping its own SDD practices, the use of this standard can help to ensure that design descriptions arecomplete, concise, consistent,interchangeable, appropriate for recording design experiences and lessonslearned, well organized,and easy to communicate.
1.4 Conformance
An SDD conforms to this standard if it satisfies all of the requirements in Clause 4 and Clause 5 of thisstandard. Requirements are denoted by the verb shall.
2. Definitions
For the purposes of this standard, the following terms and definitions apply. The Authoritative Dictionaryof IEEE Standards Terms (B137′ and EEE Std 12207TM-2008 B21] should be referenced for terms notdefined in this clause.
3.1 design attribute: An element of a design view that names a characteristic or property of a designentity, design relationship. or design constraint See also: design constraint, design entity, designrelationship.
3.2 design concern: An area of interest with respect to a software design.
3.3 design constraint: An element of a design view that names and specifies a rule or restriction on adesign entity, design attribute, or design relationship. See also: design attribute, design entity, designrelationship.
3.4 design element: An item occuring in a design view that may be any of the following: design entity,design relationship,design attribute,or design constraint.
3.5 design entity: An element of a design view that is structurally, functionally, or otherwise distinct fromother elements, or plays a different role relative to other design entities. See also: design view.
3.6 design overlay: A representation of additional, detailed, or derived design information organized withreference to an existing design view.