Database Generated Software Requirements Specification

Abstract

Listen

Translate article

AbstractThe goal of software requirements management at Grumman is to provide Systems Engineering's internal and external customers with the right information to produce and evaluate a computer program that meets the system's needs. A valuable approach to requirements management is to model one or more aspects of a system and communicate and control the system and software requirements via a database of the model elements.Engineering models can range from abstract models such as a series of partial differential equations for the solution of harmonic vibrations to isomorphic models such as a data flow diagrams or perspective drawings. The modeling method chosen uses a graphical notation and an Entity‐Relationship‐Attribute (ERA) database to create four isomorphic models to define a system and is currently implemented using RDD‐100® from Ascent Logic Corporation.The models used to specify the system are:1) Design Knowledge Capture (DKC) model‐an ERA model of the requirements flowdown from the perceived need to the requirements specification. 2) Behavior model – built using entities that represent functions and items, along with temporal notations of the functional flow. 3) Physical model –sometimes called the system architecture, includes the hierarchical structure of the components that build the system, the interfaces between the components, and the physical links that comprise the interfaces. 4) Resource model‐allows the engineer to evaluate the amount of resources needed when specified behavior is exhibited by a system architecture and to determine the behavior of the system when resources are depleted.The customization of the RDD language and the augmentation of RDD with other tools to add the required capability is described. The elements of the model are mapped from the RDD database to the an expansive interpretation of the Data Item Description for a Software Requirements Specification (DI‐MCCR‐80025A). The interpretation is based on interchanges between the requirements provider and the requirements implementor.The paper describes the aspects of systems specified using the database of models method. The method is heavily driven by the need to meet the MIL‐STD 2167A requirements for a Software Requirements Specification. However; the main value of this paper may be in the identification of the information produced while engineering the system that is not in the Systems Requirements Specification (SRS).