IEEE 1016.1-1993 [ Withdrawn ]

IEEE 1016.1-1993 [ Withdrawn ] IEEE Guide to Software Design Descriptions
standard by IEEE, 05/25/1993

More info

Full Description

Scope

This guide describes the application of design methods and design documentation recommended in IEEE Std 1016-1987. Since most design methods specify media and information, organization of the material is left up to the user of the design method. This guide shows how the information requirements of IEEE Std 1016-1987 are met by several common design methods. IEEE Std 1016-1987 is not limited to the specific methods described in this guide. Rather, these examples were selected to illustrate the application of IEEE Std 1016-1987. The methods selected as examples are widely used and are familiar, thus making the concepts of IEEE Std 1016-1987 more concrete. This information in this guide may be applied to commercial, scientific, or military software that runs on any computer. Applicability is not restricted by the size, complexity, or criticality of the software.

Purpose

The purpose of this guide is to show how to apply IEEE Std 1016-1987, IEEE Recommended Practice for Software Design Descriptions. The approach used to do this is as follows:The relationship between IEEE Std 1016-1987 and design methods that are familiar and widely used is shown. This includes identifying what design entities each method recognizes and what entity attributes it emphasizes. The set of models (or views) that each design method requires are also identified.

Abstract

New IEEE Standard - Inactive-Withdrawn.Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. The application of design methods and design documentation recommended in IEEE Std 1016-1987 is described. Several common design methods are used to illustrate the application of IEEE Std 1016-1987, thus making the concepts of that standard more concrete. The information in this guide may be applied to commercial, scientific, or military software that runs on any computer. Applicability is not restricted by the size, complexity, or criticality of the software.