RAYTHEON BRINGS EO TECHNOLOGY To Defend Our Nation

ARCHITECTURE & SYSTEMS INTEGRATION
onTechnology
Reference
Architectures
for Information-Intensive
Net-Centric Systems
Architecture has typically not been an
emphasis for Raytheon business in the past.
However, to become a Mission Systems
Integrator, architecture is necessary to integrate
all system components. The corporate
Architecture Review Board (ARB) has been
tasked to come up with a reference architecture
so we have a common understanding
of the respective architectures that are
being developed.
Axis of Instantiation
• Organizational hierarchy
• Modular open system
approach
• Customer policies,
reference architectures
(NR KPP, NCOW RM,
NCES, etc.)
Axis of Performance
• Shared system
attributes
• Categories may
include embedded
real-time, networked
decision
support, etc.
Enterprise
System
Subsystem
Functional
Area (Sub-
Subsystem)
Module
The ARB working group is coordinating the
development of an initial set of reference
architectures (RAs) as an element of a corporate
architecture methodology governed
by the Raytheon Enterprise Architecture
Process (REAP). An RA is an abstraction
of a class of architectures with common
characteristics and quality attributes. It is
instantiated to address a particular mission
solution by adding and selecting detail pertaining
to that mission. An RA can be
thought of as analogous to a class; a particular
mission solution architecture can then
be viewed as an object instantiated from
that class. The benefits RAs offers are
that they:
• establish a consistent, state-of-the-practice
architecture approach across multiple
programs and problem domains;
Axis of Abstraction
• Zachman matrix
• M&S/executable architecture levels
Component Enterprise Logical/ Process/ Operational
Functional Workflow
Figure 1. Our architecture taxonomy categorizes architecture in three dimensions.
Transformation from Abstraction
to Physical
• Architecture-centric, model-based,
object-oriented system
engineering
• Tools and methodologies – REAP,
reference models, frameworks
• establish an advanced point of departure
that reduces risk, cost and schedule in
implementing specific mission solutions;
• embed best practices and lessons learned
in the architectural foundation of a system
or enterprise;
• provide a framework for maximizing the
reuse of existing components, ensuring
consistency in interfaces and information
exchanges, and ensuring conformity to
customer policies, RAs and reference
models (RMs);
• facilitate the application of REAP;
• support customer dialogue to refine
requirements, communicate Raytheon
capabilities, and establish the foundation
for proposals and program plans; and
• serve as a foundation for coherent product
line development.
These RAs are instantiated through an
object-oriented system engineering (OOSE)
methodology to create mission solutions to
meet specific customer needs. An RA is
used in activities 3 and 4 of REAP (business
architecting and technical architecting) and
is therefore organized into a business reference
model and technical reference model.
These, in turn, form the basis for the operational
and logical views of an architecture.
The GIG Integrated Architecture, the
NCOW RM and the principles of service-oriented
architecture as embodied in GIG Net-
Centric Enterprise Services, are also taken
into account, and the methodology generates
the products of the DoD Architecture
Framework. This approach provides an
advanced point of departure in implementing
a system or enterprise, and thereby
reduces risk, cost and schedule. It incorporates
best practices of the Information
Technology community, promotes the use
of REAP, addresses customer needs in the
warfighter’s domain and promises significant
advantages to a wide range of programs
across the company. State-of-thepractice
architecture methodology gives
Raytheon a significant advantage over
competing strategies that are rooted
in older architecture and system engineering
paradigms.
An important aspect of the RA strategy is
the taxonomy summarized in Figure 1. The
axes represent three basic dimensions of
architecture and allow any given mission
solution or architecture issue to be consistently
and unambiguously placed in an
overall context. We are developing an initial
set of RAs at the top (enterprise) level for
two basic system categories: embedded
16 2005 ISSUE 1 YESTERDAY…TODAY…TOMORROW