Technology Today 2006 Issue 3 - Raytheon

Feature
Continued from page 5
Reference Architectures, complimented
with flexible and responsive M&S
capabilities, are critical components to the
Raytheon Enterprise Architecture Process
(REAP). REAP was created to address both
the needs of our customer and of Raytheon
as a Mission System Integrator. The primary
industry and government standards unified
within REAP include the Department of
Defense Architecture Framework (DoDAF),
the Open Group Architecture Framework
(TOGAF), the Zachman Framework for
Enterprise Architecture, the Federal
Enterprise Architecture Framework (FEAF),
and the Software Engineering Institute’s
Architecture Tradeoff Analysis
Method (ATAM ® ).
REAP is a systems architecting process
extended with concepts and techniques to
support enterprise architecting. Enterprise
architecting is the interrelation and integration
of business architectures and technical
architectures. The business architecture
models the enterprise’s mission, needs,
strategies, goals, business rules, business
processes, information flows and supporting
organizational structure. The Technical
Architecture models the technically focused
architectural aspects of the system (e.g.
data, applications, enabling technologies).
Clearly, EMS is an integral need for both the
business and technical architecture 4 .
In addition, EMS is supporting commercial
efforts to develop model-driven architectures
(MDA) using Unified Modeling
Language (UML) and System Modeling
Language (SysML) through process/workflow
modeling and logical model
development support 5,6 .
Systems Engineering, System Architecture
Development, and Modeling and
Simulation are tightly intertwined, as illustrated
in Figure 2. The development of
“executable models” is a key enabler for
system design and implementation success
using the iterative process depicted in the
figure. EMS supports major contributions to:
Operational, process and workflow
modeling
Logical architecture modeling
Physical modeling
System prototyping
6 2006 ISSUE 3 RAYTHEON TECHNOLOGY TODAY
Raytheon
Enterprise
Architecture
Process (REAP)
Capabilities
Database
Integration
and Test
System
Build
Platform-
Specific
Model (PSM)
DODAF
Operational
View
Operational View
(Use Cases, Threads)
System
Prototype, MS&A,
Trades, CAIV
Physical
(Components, Integration
Platform)
DODAF
Technical
View
In fact, as the acquisition process progresses,
the system prototype evolves from high
level M&S system model abstractions to an
operationally representative prototype that
includes hardware and human in-the-loop
capabilities that significantly reduce program
risk. An additional benefit is that
components of the design prototype can
be reused as part of an operational engineering
testbed. The engineering testbed
becomes a key operational component for:
Operational performance/capacity analysis
Operational planning and scheduling
Support for operational anomaly resolution
Realistic hands-on operator training
New HW/SW verification and validation
Proof of concept technology insertion
Since this operational engineering testbed
is an evolutionary extension of the system
prototype, significant cost savings, schedule
compression and risk reduction benefits are
realized through the extensive reuse of verified,
validated and accredited components (VV&A).
EMS Process
EMS is not simply an integration of
Raytheon’s world-class M&S components.
More importantly, EMS encompasses a
process that ensures responsive, low-cost
solutions. This process is shown in Figure 3.
Platform-Independent
Model (PIM)
Objective Architecture
Logical View
(Class/Sequence/
Diagrams, SOA)
DODAF
System
View
One Architecture/EMS Strategy
Enterprise Modeling
and Simulation (EMS)
Operational, Process and
Workflow Modeling
Logical Architecture Modeling
Physical Modeling
Figure 2. EMS is an integral component of the systems engineering/architecture process.
The left-hand side of Figure 3 shows the
Systems of Elements TM where Raytheon possesses
full spectrum high-fidelity M&S components.
The gray box encompasses the
process for integrating and deploying those
capabilities in a responsive cost-efficient
fashion to solve customer problems.
The implementation of these broad-based
legacy and contemporary M&S capabilities
requires a simulation architecture that facilitates
the interoperability between legacy
infrastructures using distributed interactive
simulation and high-level architecture backbones
with commercial solutions, such as
Java TM messaging services and other web
service implementations, such as serviceoriented
architectures and high transaction
rate protocols. EMS has demonstrated this
full-scale integration capability through the
deployment of a number of modeling and
simulation experiments, referred to as
Raytheon Distributed Experiments (Ray DX ).
With a variety of components, or federates
composing a simulation or a simulation
federation, Simulation Control is a critical
component to successful execution. The
ability to add or delete components or federates
on the fly, display simulation status,
provide time management, and control
data acquisition with a single control con-