Mission Critical
Enterprise Systems
Symposium
Architecting the Extended
Enterprise
Architectural Patterns for the
Extend Enterprise
Janet E. Wedgwood, Jeffrey Stavash, John
Sausman, Dr. Bipin Chadha, Harris Zebrowitz
Lockheed Martin
Advanced Technology Laboratories
April 17, 2002
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 1
What is a Virtual Prototyping
Environment?
G An architecture to dynamically integrate systems that
represent the product data and behavior of a complex
system in an extended enterprise
G The software that implements the enterprise
G The standards used for interoperability
G A collaborative environment in which a multi-
organizational team can:
N Develop, manage, analyze, and optimize product definition and
behavior throughout its lifecycle
AAVirtual
VirtualPrototype
Prototypeis
isan
aninstantiation
instantiationof
ofaadesign
designin
inthe
the
Virtual
VirtualPrototyping
PrototypingEnvironment
Environment
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 2
Why Build a Virtual Prototype?
G Increased complexity increases lifecycle costs
G Key to addressing lifecycle costs early in the
design cycle
N Perturbations in the design are more practical in the
early design stages
G All aspects of product definition and behavior
can be represented by the virtual prototype to
support complex analysis
N Trade studies that drive decisions that affect cost in
all lifecycle phases can be performed
N VPE makes multi-domain optimization practical
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 3
Properties of the VPE
Architecture
G Accessible
G Available
G Scalable
G Deployable
G Extensible
G Affordable
G Interoperable
G Reliable
G Reusable
G Maintainable
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 4
How Will the Architecture
Evolve?
G Architecture must support the product over
a long life-cycle (many decades)
G Must adapt to changes in:
N Requirements
N Technologies
N Business practices
N Organizations
N Roles
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 5
Architectural Approach
G Managed and controlled evolution of a stable
architecture
N Decouple fast changing things from slow changing things
N Decouple Information Architecture from
from System
System Architecture
Architecture
N Decouple Logical Architecture
Architecture from
from Physical
Physical Architecture
Architecture
N Use pervasive standards in the development of information
architecture to enable interoperability
N Use Component Based Architectures with Explicit
Explicit Interfaces
Interfaces
for easier replacement
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 6
VPE Logical Architecture
Web
Browser
Users
HTML, XML, HLA,
JAVA, CORBA
CORBA
Domain
Tools
Visualization
Tools
Models
VPE
Simulations
Databases
Components
Componentscan
canbe
beimplemented
implementedincrementally;
incrementally;
supports
supportsmany
manystandard
standardprotocols
protocols
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 7
VPE Functional Architecture
Virtual Prototyping Environment (VPE)
Cost
Analysis
Analysis
Systems
Engineering
Performance
Analysis
Analysis
Task
Analysis
Analysis
…
MDO
MP
IDE
Collaborative Environment
Component
Componentbased
basedwith
withexplicit
explicitinterfaces
interfacesfor
foreasier
easier
replacement;
spread
responsibility
to
replacement;layers
layersisolate
isolatechanges,
changes,spread
spreadresponsibility
responsibilityto
to
accommodate
accommodatechange,
change,and
andpromote
promotereuse
reuse
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 8
VPE Design Patterns
G Catalog/occurrence
G Design specific attributes
G MVC
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 9
Catalog/Occurrence
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 10
Design Specific Attributes Pattern
The
snap on
” functionality
Thepattern
patternis
isused
usedto
to““snap
on”
functionalityto
tothe
themodel
model
without
withoutaffecting
affectingexisting
existingdata
dataor
orrequiring
requiringdatabase
databaseschema
schema
modifications
modifications
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 11
MVC Pattern
Uses
Sees
Controller
Modify
Model
User
User
Update
Load and
refresh
View
The
TheProduct
ProductManager
ManagerMVC
MVCarchitecture
architecturemirrors
mirrorsthe
the
application
snap-on” architecture
applicationthread
thread““snap-on”
architecture
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 12
The Product Manager
User
The
TheProduct
ProductManager
ManagerMVC
MVCarchitecture
architecturemirrors
mirrorsthe
the
application
snap-on” architecture
applicationthread
thread““snap-on”
architecture
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 13
Views
Program
Program
System
1
Subsystem
11
System
2
Subsystem
12
...
...
System
m
Subsystem
1p
Compartment
1
Component
21
Compartment
2
Component
22
...
...
Compartment
n
Component
2q
Traceability
Traceability
P1
P2
P3
...
Pn
Pn+1
Pn+1
Enable
Enabledifferent
differentdisciplines
disciplinesto
toview
viewthe
theproduct
productstructure
structurefrom
from
their
theirown
ownperspectives;
perspectives;maintain
maintainoverall
overallintegrity
integritybetween
between
different
. perspective
differentdisciplines;
disciplines;and
anddesign
designphase
phaseview
viewvs
vs.
perspective
(adopted
(adoptedfrom
fromOMG
OMGdata
dataarchitecture)
architecture)
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 14
Templates
Product
Product
Data
Data
IMP/IMS
IMP/IMS
Design
Design
Requirements
Requirements
Performance
Performance
Assessment
Assessment
Risk
Risk
Assessment
Assessment
Integrated
Integrated
Test
Test Plan
Plan
Design
Design
Requirements
Requirements
Schedule
Schedule
Data
Data Item
Item
Deliverables
Deliverables
Functional
Functional
Model
Model
(HW)
(HW)
Physical
Physical
Model
Model
Cost
Cost
Change
Change
Requirements
Requirements
Data
Data
Training
Training
** Design
Design
Document
Document
(WORD)
(WORD)
Subsystems
Subsystems
Use
Use Case
Case
Object
Object
Model
Model
(SW)
(SW)
Evolution
Evolution
Functional
Functional Flow
Flow
Diagram
Diagram (RDD-100)
(RDD-100)
Functional
Functional Hierarchy
Hierarchy
(RDD-100)
(RDD-100)
Block
Block Diagram/
Diagram/
Deactivation
Deactivation Diag
Diag
(VISIO)
(VISIO)
Functional
Functional Diagram
Diagram
(Simsmart,
(Simsmart, EDSA,
EDSA,
Maestro)
Maestro)
Sequence
Sequence Diagram
Diagram
(ROSE)
(ROSE)
Class
Class Diagram
Diagram
(ROSE)
(ROSE)
Object
Object Diagram
Diagram
(ROSE)
(ROSE)
Deployment
Deployment Diagram
Diagram
(ROSE)
(ROSE)
** Design
Design Document
Document
(ROSE)
(ROSE)
3D
3D Model/Dwg
Model/Dwg
(CATIA)
(CATIA)
Product
Productdefinition
definitionincludes
includesall
alldesign
designinformation
informationincluding
includingaa
consolidated
consolidatedrepresentation
representationof
ofhardware,
hardware,software
softwareand
andpeople
people
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 15
Multidisciplinary Design
Optimization
Configuration Controlled Environment
REQUIREMENTS
DESIGN
DOORS
ROSE
Current
EXPERIMENTS
WIP OBJECTS
Requirement
(Proxies)
PS
Design
Justification
(Demos)
Assessment
Areas
Experiments
Future
Sandbox Environment
MDOM
MDOMenables
enablessophisticated
sophisticatedanalysis
analysisand
andoptimization
optimizationcapabilities
capabilities
by
sandbox” environment
byleveraging
leveragingMPS
MPSand
andenabling
enablingaa““sandbox”
environment
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 16
Lessons Learned
G Special skills required to translate user requirements
into a useable, multidisciplinary tool environment
N Design-a-little, Build-a-little definitely needed for VPE
designers to understand domain requirements (i.e. VPE
designers are not propulsion engineers …)
N Use design experiences to prevent documenting bad business
processes
G Application threads must be independent of
deployment environment
N Service Architecture is critical
critical
G Design Build plan must mirror thread-oriented design
environment
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 17
Future
G Application thread tools will be offered as services
N Jini-like application architecture
N Users can request services
N Services can be access controlled
G Design/build environment improvements are being
studied
N Multiple sites, threads, versions, projects
G Integration of tools based on complexity science show
promise of increased ability to explore the design
space
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 18
Examples of Complex Systems
End Users
Transport
Warehouse
Manufacturer
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 19
Mission Effectiveness
Transition Point
ROBUST
FRAGILE
ROBUST
No. of Ships
It is desirable to understand the properties of
transition points and tools to position and maintain
systems at the transition point
MCES 2002 April 14 – 19, 2002
Janet E. Wedgwood
Wedgwood
Page 20