IEEE Std 1016-1998 IEEE Recommended Practice for Software Design Descriptions -Description
Abstract: The necessary information content and recommendations
for an organization for Software Design Descriptions (SDDs) are
described. An SDD is a representation of a software system that
is used as a medium for communicating software design information.
This recommended practice is applicable to paper documents, automated
databases, design description languages, or other means of description.
Keywords: software design, software design
description, software life cycle process
Content
1. Scope
2. References
3. Definitions
4. Considerations for producing
an SDD
4.1 Software life cycle
4.2 SDD within the life cycle
4.3 Purpose of an SDD
5. Design description information
content
5.1 Introduction
5.2 Design entities
5.3 Design entity attributes
5.3.1 Identification
5.3.2 Type
5.3.3 Purpose
5.3.4 Function
5.3.5 Subordinates
5.3.6 Dependencies
5.3.7 Interface
5.3.8 Resources
5.3.9 Processing
5.3.10 Data
6. Design description organization
6.1 Introduction
6.2 Design views
6.2.1 Decomposition description
6.2.2 Dependency description
6.2.3 Interface description
6.2.4 Detailed design description
Annex A Sample table of contents for an
SDD
Annex B Guidelines for compliance with IEEE/EIA
12207.1-1997
B.1 Overview
B.1.1 Scope and purpose
B.2 Correlation
B.2.1 Terminology correlation
B.2.2 Process correlation
B.2.3 Life cycle data correlation for SDDs
B.2.4 Life cycle data correlation between other data
in IEEE/EIA 12207.1-1997 and IEEE Std
1016-1998
B.3 Document compliance
B.4.1 Compliance with information
requirements of IEEE/EIA 12207.0-1996
B.4.2 Compliance with generic content
guidelines of IEEE/EIA 12207.1-1997
B.4.3 Compliance with specific content
requirements of IEEE/EIA 12207.1-1997
