Page 188 -

DOMAIN-SPECIFIC & IMPLEMENTATION-INDEPENDENT SOFTWARE ARCHITECTURES 173
Figure 10.3 Domain Reference Architecture Derivation Positioned Among System
Development Activities

Requirements Acquisition, Modeling,
Refinements, and Synthesis

Domain
Model (DM)
Plan

RARE DRA Derivation

Domain
Reference
Architecture
(DRA) Plan

System Design

should be offered by an instance of the DRAC specification; the Behavioral Model (DRAC B-M)
describes the behavior expected from an instance of the DRAC through a high-level state chart;
and the Integration Model (DRAC I-M) defines the constraints and dependencies between DRAC
instances resulting from the distribution of dependent domain functions across DRACs. These
dependencies are based on the input and output of data and events as well as the clustering of
classes into subsystems to represent domain functionality typically colocated.
The next section provides a detailed explanation of the DRA derivation process, followed by a
discussion of related work and the benefits and limitations of RARE and the DRA in the context
of a standard software engineering process. The chapter then concludes with summary remarks
and future work.

DERIVING THE DOMAIN REFERENCE ARCHITECTURE USING THE
REFERENCE ARCHITECTURE REPRESENTATION ENVIRONMENT

The RARE DRA derivation process is positioned among phases associated with typical software
engineering methodologies as shown in Figure 10.3 (Barber, 2004; Barber and Graser, 2000a,
2000b; Barber, Graser, and Jernigan, 1999; Barber et al., 1999; Graser, 2001). DRA derivation
follows requirements acquisition, modeling, refinement, and synthesis activities that yield a DM,