Synthesis Opportunistic Domain Engineering
PRODUCT DESCRIPTION
PROCESS DESCRIPTION
INTERACTIONS WITH OTHER ACTIVITIES
The Component Design Activity is an activity of the Product Design Activity for creating a Component Design. The Product Architecture identifies a set of Adaptable Components that may be used to implement a work product family. A Component Design is a design specification for one of these Adaptable Components. Application engineers, using the Generation Procedure, may adapt and compose a set of these components to implement certain work products, or portions thereof. Each component must be designed to satisfy relevant aspects of the Product Requirements and all design structures of the Product Architecture.
The objective of the Component Design Activity is to produce a design for an Adaptable Component that satisfies applicable Product Requirements in accordance with its role in the Product Architecture.
The Component Design Activity requires the following information:
The Component Design Activity requires domain and software knowledge and experience in:
The interface part of Adaptable Components is different for software and documentation. The content of the software interface is specific to the design method(s) used to create the members of the family. The following types of information are examples: definitions of interface programs (names, parameters, parameter types, returned values), definitions of exported types, descriptions of the effects of interface programs, assumptions about the environment in which the software is to be used.
The interface for a documentation component does not require the same type of detailed information. It consists of a brief statement of the content of the component. It should provide enough information to determine the importance of selecting this component as part of a Generation Procedure.
Component Design - Pedestrian Lanes with Push Buttons (TLC0PL0PB01)Adaptation Specification
Instantiation Parameters COMP_interface one of (TL0A, TL0B) {type of interface to the "walk/don't walk" light indicators}
COMP_blinking_rate one of (yes, no) {A yes value means the pedestrian lane indicators have a variable blinking rate capability. A no value means they do not.}
....
Instantiation Constraints None
Interface Specification This component contains the functional requirements for the pedestrian lanes present at the intersection. All the pedestrian lanes with push buttons at an intersection must satisfy these requirements. The indicators and the push button associated with the pedestrian lanes of this intersection conform to the < COMP_interface > standard.
< if COMP_blinking_rate is yes then > The variable blinking rate for the pedestrian lane indicators must be set by the system. < endif >
....
Example DE.2.2.4.2-1 illustrates a fragment of a Component Design for a DOD-STD-2167A System/Segment Specification work product family of the TLC domain. This design corresponds to one of the adaptable components identified in the Product Architecture shown in Example DE.2.2.4.1-1. The Adaptation Specification defines the adaptation parameters for this adaptable component. The Interface Specification is parameterized, where appropriate, in terms of these adaptation parameters.
The Component Design Activity consists of two steps shown in Figure DE.2.2.4.2-1 Component Design Process.
Follow these steps for the Component Design Activity. Domain engineers perform these steps for each Adaptable Component defined in the internal organization of the Product Architecture.
Step: Define Component Adaptation Specification
Step: Specify Component Interface
None
