2008 Issue 2 - Raytheon

onTechnology
ARCHITECTURE & SYSTEMS INTEGRATION
Systems and Software Architecture Summit 2008
Emphasizes Interoperability
On March 11 and 12, more than 80 system
and software architects from across the
company met in Dallas, Texas, for the Fifth
Annual Systems and Software Architecture
Summit. The summit’s purpose was to gather
the community, share lessons learned,
summarize activities in the businesses, and
develop connections across the company.
The summit’s theme — Architecting
Interoperability — emphasizes that what we
produce must also work well within a larger
system. This is important not only to ensure
NoDoubt product performance, but to
improve Raytheon’s Mission Systems
Integration (MSI) know-how.
Plenary Sessions
The summit began with four plenary
presentations describing architecting efforts
of interest to all Raytheon businesses.
Raytheon people presented three of these
sessions, and a senior technical staff
member of Carnegie Mellon University’s
Software Engineering Institute (SEI)
presented the fourth.
Rolf Siegers of Intelligence and Information
Systems (IIS) led off by discussing Raytheon’s
architecture initiatives, principally the
Raytheon Mission Architecture Program
26 2008 ISSUE 2 RAYTHEON TECHNOLOGY TODAY
(RayMAP). Rolf described and provided
the status of:
The Raytheon Enterprise Architecture
Process (REAP), which provides a common
process for developing architecture
across the company
The Raytheon Certified Architect Program
(RCAP), which is generating a cadre of
well-trained and highly experienced architects
to enhance our MSI capabilities
The Reference Architectures, which
improve reuse and standardization across
the company
The Raytheon Architecture Review Board,
which oversees corporate architecture
products and processes
The Architecture Collaboration Tool,
which enables all employees to share
lessons learned, get access to tools, and
use the architecture repository
Architecture Standards Collaboration,
which includes activities that Raytheon
undertakes to influence current and
future architecture standards
Louise Bator from Raytheon Missile Systems
(RMS) then discussed the RMS Modularity
Project, which will increase product reusability,
reliability and interoperability. One key
aspect of this effort is the use of a Technical
Reference Model (TRM) that identifies modularity
at three hierarchical layers: mission
management, resource management and
resources. This TRM framework is being
used at RMS, and other Raytheon businesses
and enterprise initiatives are beginning to
apply it to their products as well.
Julie DeMeester of Integrated Defense
Systems (IDS) spoke next on using serviceoriented
architecture and enterprise service
buses as MSI enablers. She identified four
objectives to achieving net-centric operations:
Get connected by using Internet protocol
as the common protocol
Share information by leveraging XML
[extensible markup language] and COI
[community of interest] constructs
Implement a service-oriented architecture
Protect the network by implementing
information assurance solutions
One of DeMeester’s intriguing discussion
points was the implementation of the
Consolidated Afloat Network and Enterprise
Services (CANES) program. CANES will
establish a SOA with enhanced capabilities
but a reduced infrastructure to create the
future total ship computing environment
infrastructure (TSCEI).
The last plenary discussion, presented by
Dr. Paul C. Clements of Carnegie Mellon
University, was on the importance of architecture.
Clements discussed the latest SEI
architecture-related tools, methods, courses
and certificate programs. He then presented
very thorough data showing the traits that
industry requires of architects. Interestingly
enough, solid project management skills
are among the most important of these.
Dr. Clement also spoke on SEI’s Architecture
YESTERDAY…TODAY…TOMORROW