Joint Integrated Open Architectures:  Progressing Toward Net-Centric Operations and Warfare March 30, 2004
Overview <ul><li>DoD Enterprise Architecture Development </li></ul><ul><li>Joint Integrated Architecture Development </li>...
DoD Enterprise Architecture <ul><li>DoD Enterprise Architecture </li></ul><ul><li>Strategic, Operational, Tactical Use Cas...
Joint Integrated Architectures Navy  FORCEnet Air Force  C2 Constellation Army  LandWarNet Partnering to Evolve Joint Arch...
Reference Architecture Convergence Focus on Standards Without Constraining Innovation and Diversity Multi-Service NESI Com...
Program Architecture Convergence Leverage the DoD Program Portfolio Converged Program Platform AOC LSI BMC2 ISPAN JC2 NCES
Architecture-Driven Development Capabilities/ Requirements <ul><li>Operational Analysis: </li></ul><ul><li>CONOPS/Scenario...
Way ahead <ul><li>Continue to Evolve Joint Architectures and Mechanisms to Foster Convergence </li></ul><ul><ul><li>Master...
Upcoming SlideShare
Loading in …5
×

Joint Integrated Open Architectures: Progressing Toward Net ...

543 views
409 views

Published on

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
543
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
25
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Joint Integrated Open Architectures: Progressing Toward Net ...

  1. 1. Joint Integrated Open Architectures: Progressing Toward Net-Centric Operations and Warfare March 30, 2004
  2. 2. Overview <ul><li>DoD Enterprise Architecture Development </li></ul><ul><li>Joint Integrated Architecture Development </li></ul><ul><li>Reference Architecture Convergence </li></ul><ul><li>Program Architecture Convergence </li></ul><ul><li>Architecture-Driven Development </li></ul><ul><li>Way Ahead </li></ul>
  3. 3. DoD Enterprise Architecture <ul><li>DoD Enterprise Architecture </li></ul><ul><li>Strategic, Operational, Tactical Use Cases </li></ul><ul><li>Mapping to FEAF </li></ul><ul><li>Acquisition Guidance </li></ul><ul><li>Definition of ‘Network Centric’ </li></ul><ul><li>Enterprise Services Definition </li></ul><ul><li>Platform (COE) to Network </li></ul><ul><li>DoD Information Management and Interoperability </li></ul>Defining the Environment in Which We Delivery Capability GIG Architecture V2 NCOW RM V1 NCES ICD/CDD DoD Data Strategy
  4. 4. Joint Integrated Architectures Navy FORCEnet Air Force C2 Constellation Army LandWarNet Partnering to Evolve Joint Architectures that Guide Program Development JTF C2 Architecture Joint Integrated Architecture (JIA) OSD JFCOM Service
  5. 5. Reference Architecture Convergence Focus on Standards Without Constraining Innovation and Diversity Multi-Service NESI Commercial Best Practice Army PASS Navy RAPIDS AF C2ERA
  6. 6. Program Architecture Convergence Leverage the DoD Program Portfolio Converged Program Platform AOC LSI BMC2 ISPAN JC2 NCES
  7. 7. Architecture-Driven Development Capabilities/ Requirements <ul><li>Operational Analysis: </li></ul><ul><li>CONOPS/Scenarios </li></ul><ul><li>Stressing Vignettes </li></ul><ul><li>System Behaviors </li></ul><ul><li>External Interactions </li></ul><ul><li>Operational View: </li></ul><ul><li>Use Cases </li></ul><ul><li>Threads </li></ul><ul><li>Actors </li></ul><ul><li>Context </li></ul><ul><li>SOA Mapping: </li></ul><ul><li>Mission Svcs </li></ul><ul><li>Application Svcs </li></ul><ul><li>Platform Svcs </li></ul><ul><li>Logical View: </li></ul><ul><li>Structural </li></ul><ul><li>Behavioral </li></ul><ul><li>Reference Arch </li></ul><ul><li>SSS </li></ul><ul><li>ICDs </li></ul><ul><li>Product Mapping: </li></ul><ul><li>New Development </li></ul><ul><li>Reuse </li></ul><ul><li>Physical View: </li></ul><ul><li>Hardware </li></ul><ul><li>Software </li></ul><ul><li>Architecture Validation </li></ul><ul><li>TPMs </li></ul>Architecture Drives Net-Centricity and Delivered Capability! System Prototype <ul><li>M&S: </li></ul><ul><li>Operational </li></ul><ul><li>Process/Workflow </li></ul><ul><li>Architecture </li></ul><ul><li>Physical </li></ul>CAIV/MEP
  8. 8. Way ahead <ul><li>Continue to Evolve Joint Architectures and Mechanisms to Foster Convergence </li></ul><ul><ul><li>Master Capabilities List, Common Activities/Functions </li></ul></ul><ul><ul><li>Common Repository (DARS Lite) and tools </li></ul></ul><ul><li>Manage the Information in Information Superiority </li></ul><ul><ul><li>DoD Data Strategy, XML Repository, C2EIDM </li></ul></ul><ul><li>Converge SORs on Reference Architecture (NESI) </li></ul><ul><ul><li>SOA, Enterprise Services, Publish and Subscribe </li></ul></ul><ul><ul><li>GCSS-AF, AOC LSI, DCGS, CCICC2, FIOP, ISPAN </li></ul></ul><ul><li>More Joint/Coalition Demonstration/Experimentation </li></ul><ul><ul><li>Prove it, in Operational Terms </li></ul></ul>Industry Competition in Services not Architecture

×