Design Records: A Way to Organize Domain Knowledge

Will Tracz – Steve Shafer – Lou Coglianese
IBM Federal Systems Company
MD 0210, Owego, NY 13827
Tel: (607) 751-2169, fax: (607) 751-6025
Email: tracz@vnet.ibm.com

This document describes the Design Records being developed as part of the Domain-Specific Software Architecture Avionics Domain Application Generation Environment (DSSA-ADAGE) Project¹. A design record aids in the generation of new avionics applications as well as the maintenance of existing systems built using ADAGE. The purpose of a design record is to serve as a vehicle for software understanding by functioning as a collection point for domain-specific knowledge about the components that make up a Domain-Specific Software Architecture (DSSA),

There are three kinds of design records used by ADAGE to describe the avionics software architecture and components [#!ADAGEIBM9307!#,#!ADAGEUT9303!#].

1. Domain Model Design Record defines a collection of realms²,
2. Realm Design Record defines the interface for a collection of components, and
3. Component Design Record represents an (alternative) implementation or design choice.

Keywords:Domain Analysis, Knowledge Representation, Software Reuse.

Workshop Goals: Facilitate the technical interchange of ideas and experience related to the development and use of software components.

Working Groups: Knowledge Representation, Design for Reuse.