Upload
aamir97
View
557
Download
1
Embed Size (px)
DESCRIPTION
Citation preview
1
Joint Integrated Joint Integrated Open Open
Architectures: Architectures:
Progressing Progressing Toward Net-Toward Net-
Centric Centric Operations and Operations and
WarfareWarfare
March 30, 2004
2
OverviewOverview
• DoD Enterprise Architecture DevelopmentDoD Enterprise Architecture Development
• Joint Integrated Architecture DevelopmentJoint Integrated Architecture Development
• Reference Architecture ConvergenceReference Architecture Convergence
• Program Architecture ConvergenceProgram Architecture Convergence
• Architecture-Driven DevelopmentArchitecture-Driven Development
• Way AheadWay Ahead
3
DoD Enterprise ArchitectureDoD Enterprise Architecture• DoD Enterprise ArchitectureDoD Enterprise Architecture• Strategic, Operational, Tactical Strategic, Operational, Tactical
Use CasesUse Cases
• Mapping to FEAFMapping to FEAF• Acquisition GuidanceAcquisition Guidance• Definition of ‘Network Centric’Definition of ‘Network Centric’
• Enterprise Services DefinitionEnterprise Services Definition• Platform (COE) to NetworkPlatform (COE) to Network
• DoD Information Management DoD Information Management and Interoperabilityand Interoperability
Defining the Environment in Which We Delivery Capability
GIG Architecture V2
NCOW RM V1
NCES ICD/CDD
DoD Data
Strategy
4
Joint Integrated ArchitecturesJoint Integrated Architectures
Navy FORCEnet
Air Force C2 Constellation
Army LandWarNet
Partnering to Evolve Joint Architectures that Guide Program Development
JTF C2Architecture
Joint IntegratedArchitecture (JIA)OSD
JFCOM
Service
5
Reference Architecture ConvergenceReference Architecture Convergence
Focus on Standards Without Constraining Innovation and Diversity
Multi-Service
NESICommercialBestPractice
Army
PASS
Navy
RAPIDS
AF C2ERA
6
Program Architecture ConvergenceProgram Architecture Convergence
Leverage the DoD Program Portfolio
Converged Program Platform
AOC LSI BMC2 ISPANJC2 NCES
7
Architecture-Driven DevelopmentArchitecture-Driven Development
Capabilities/Requirements
Operational Analysis:• CONOPS/Scenarios• Stressing Vignettes• System Behaviors• External Interactions
Operational View:• Use Cases• Threads• Actors• Context
SOA Mapping:• Mission Svcs• Application Svcs• Platform Svcs
Logical View:• Structural• Behavioral• Reference Arch
• SSS• ICDs
Product Mapping:• New Development• Reuse
Physical View:• Hardware• Software
• Architecture Validation• TPMs
System Prototype
M&S:• Operational• Process/Workflow• Architecture• Physical
CAIV/MEP
Architecture Drives Net-Centricity and Delivered Capability!
8
Way aheadWay ahead• Continue to Evolve Joint Architectures and Continue to Evolve Joint Architectures and
Mechanisms to Foster ConvergenceMechanisms to Foster Convergence– Master Capabilities List, Common Activities/Functions Master Capabilities List, Common Activities/Functions – Common Repository (DARS Lite) and toolsCommon Repository (DARS Lite) and tools
• Manage the Information in Information SuperiorityManage the Information in Information Superiority– DoD Data Strategy, XML Repository, C2EIDM DoD Data Strategy, XML Repository, C2EIDM
• Converge SORs on Reference Architecture (NESI) Converge SORs on Reference Architecture (NESI) – SOA, Enterprise Services, Publish and SubscribeSOA, Enterprise Services, Publish and Subscribe– GCSS-AF, AOC LSI, DCGS, CCICC2, FIOP, ISPANGCSS-AF, AOC LSI, DCGS, CCICC2, FIOP, ISPAN
• More Joint/Coalition Demonstration/ExperimentationMore Joint/Coalition Demonstration/Experimentation– Prove it, in Operational TermsProve it, in Operational Terms
Industry Competition in Services not Architecture