Experiences in preparing a DOD-STD-2167A software design document for an Ada project

Authors:
C. Meyer;S. Lindholm;J. Jensen
Affiliations:
Betac Corporation, Southwest Engineering Division, San Antonio, Texas;Betac Corporation, Southwest Engineering Division, San Antonio, Texas;Betac Corporation, Southwest Engineering Division, San Antonio, Texas
Venue:
TRI-Ada '89 Proceedings of the conference on Tri-Ada '89: Ada technology in context: application, development, and deployment
Year:
1989

Citing 3
Cited 0

Using a multi-level design method under DOD-STD-2167A

WADAS '89 Proceedings of the sixth Washington Ada symposium on Ada
Layered virtual machine/object-oriented design

WADAS '88 Proceedings of the fifth Washington Ada symposium on Ada
Structured Analysis and System Specification

Structured Analysis and System Specification

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper describes our experiences in using OOD and Ada in developing a Software Design Document (SDD) in accordance with DoD-STD-2167A. The paper first provides an overview of the SDD requirements stated in 2167A. It next describes the initial objectives and assumptions under which we began the project, then discusses the problems we encountered while trying to achieve our objectives and satisfy 2167A requirements. Three different categories of problems are described: those dealing with precise definitions of terms used in 2167A; those dealing with 2167A document format requirements; and, those dealing with satisfying customer expectations. The paper then describes the specific lessons we learned during this project, and finishes with some overall conclusions.