Howard Cohen Hampton Roads Incose Chapter Meeting 2010

1,121 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,121
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Howard Cohen Hampton Roads Incose Chapter Meeting 2010

  1. 1. Joint Architecture Federation “SOA In Action - for Joint Warfighter Capabilities”<br />One warfighter<br />Multiple technical configurations <br />Incose Dinner 2010<br />Howard Cohen <br />Joint Architectures & <br />Capability Engineering Division<br />757-836-9334<br />howard.cohen@jfcom.mil<br />
  2. 2. Joint Forces J89 System Engineering and Architectures.<br />Enterprise consisting of people, process, Methods and Tools including applications providing a standard framework and repeatable process enabling the generation of reusable architecture depicting operational, system and technical perspectives. <br />
  3. 3. System Integration<br />
  4. 4. System Virtualization<br />The term virtualizationbroadly describes the separation of a resource or request for a service from the underlying physical delivery of that service.<br />
  5. 5. System Quality<br />and Assurance <br />Production<br />VM<br />Production<br />VM<br />DEV<br />VM<br />QA<br />VM<br />Production<br />VM<br />Development<br />Quality Assurance<br />Production<br />VM<br />Deploy<br />Test<br />Develop<br />System Testing <br />
  6. 6. 1<br />Database Server<br />App Server<br />App Server<br />Citrix Server<br />App Server<br /> Many to One <br />Server<br />Consolidation <br />App Server<br />ESX<br />Citrix Server<br />App Server<br />App Server<br />Database Server<br />
  7. 7. System Layers <br />
  8. 8. System Tuning <br />Apache Tomcat 6.0.18<br />Weblogic 9.2 <br />Versant<br />7.0.1.4 Patch11<br />Sun Solaris 9 <br />64 Bit Windows 2003 R2<br />32 Bit Windows 2003 R2<br />
  9. 9. System Deployment<br />Methodology<br />
  10. 10. Service Oriented <br />Warfighter<br />
  11. 11. **Architecture Context<br />Service Oriented Warfighter<br />Reduce Rework and Eliminate/Reduce Duplication of Effort <br />Share Data Between Various Organizations, Tools and Environments <br />Encourage a More Effective Collaboration Environment <br />Create More Efficient Architecture Development and Analysis Processes in Support of DoD Initiatives <br />Improved Speed of Development <br />
  12. 12. **Architecture Context<br />Service Oriented Warfighter<br />
  13. 13. 13<br />Joint Common<br />System Functions<br />List (JCSFL)<br />USN<br />USMC<br />USA<br />JCAs<br />JCAs<br />USAF<br />NCES/NECC<br />Other CPMs<br />Capability Mapping Baseline<br />“Periodic Table” for Operational DOTMLPF-P Analysis<br />Policy<br />Standards<br />Policy<br />Architectures<br />Systems Functions<br />Joint Capability Areas (JCAs)<br />CPM Areas<br />Standards<br />Tier I<br />Analysis<br />Policy<br />Technical<br />Standards<br />Accreditations<br />C2 Portfolio*<br /> - Programs of Record<br /> - Systems<br /> - Sub-systems<br /> - New Capabilities<br />Policy<br />Platforms/Weapons <br />Standards<br />ADS & Data Models<br />Policy<br />Joint Staff<br />J7 Mapping<br />Standards<br />Operational Activities<br />Applications/Services<br />Policy<br />JTF OperationalActivities / Tasks / Sub-tasks<br />Networks/Comms<br />UJTL<br />SN X.X<br />ST X.XX<br />OP X.X.X<br />TA X.X.X.X<br />Standards<br />Policy<br />Assessments<br />Joint Tasks<br />Operational<br />Standards<br />AUTLs, MCTL, NTTL, AFTL <br />Documentation<br />Policy<br />Service Tasks<br />Concepts/Plans<br />Operational Nodes & Billets <br />Standards<br /> Joint Warfighter<br /> Billets<br />Programmatic<br />JCAs- to- PECs<br />Op<br />Nodes<br />PA&E<br />Mapping<br />Joint Integration<br />& Interoperability<br />Recommendations via Detailed<br />DOTMLPF Analysis<br />Authoritative Sources:<br />
  14. 14. 14<br />
  15. 15. 15<br />Service Oriented Warfighter<br />
  16. 16. Any Questions?<br />The warfigher<br />is always on our mind <br />
  17. 17. BACKUP<br />
  18. 18. Policy & Guidance <br />DoD Directive 8000.1, “Management of DoD Info Resources”, November 21, 2003<br />DoD Manual 8020.1-M, “Functional Improvement Process”, August 1992<br />DoD Directive 8100.1, “GIG Overarching Policy”, September 19, 2002<br />DoD Directive 8100.2, “Wireless Technologies and the GIG”, April 14, 2004<br />DoDI 8110.1 “Multinational Information Sharing Networks Implementation”.<br />DoD Directive 8115.1, "I.T. Portfolio Management", October 10, 2005<br />DoD Manual 8320.1-M, “Data Administration Procedures”, March 1994.<br />DoD Manual 8320.1-M-1, “Standard Data Element Development”, May 1992.<br />DoD Directive 8320.2, “Data Sharing in DoD”, December 2, 2004.<br />DoD Directive 8320.03, “Identification Standards”, March 23, 2007.<br />DoD Directive 8500.1, “Information Assurance”, October 24, 2004.<br />DoD Net-Centric Data Management Strategy: Metadata Registration, April 3, 2003<br />DoD Net Centric Strategy, May 9, 2003<br />Department of Defense Discovery Metadata Specifications<br />DEPSECDEF Memorandum on “Information Technology Portfolio Management”,<br />March 22, 2004<br />Director of Central Intelligence, “Intelligence Information Sharing”, June 9, 2004<br />
  19. 19. DoD Directive 8320.02, Data Sharing in a Net-Centric Department of Defense, April 23, 2007<br />Department of Defense Chief Information Officer, Department of Defense Net-Centric Service Strategy, May 4, 2007<br />Global Information Grid (GIG) Architecture Federation Strategy, 01 August 2007<br />Policy Standards Guidance<br />
  20. 20. Architecture Federation Guidance<br />Business Transformation Agency (BTA), BMA – Federation Strategy and Roadmap, 26 September 2006<br />US Army Regulation (AR) – 71, Force Development Architecture (Draft) 10 September 2008.<br />DoD Instruction 8210.aa (Draft), Architecting the DoD Enterprise, 22 September 2008<br />DoD Manual 8210.11 (Draft), DoD Architecture Federation, 22 September 2008<br />DoD Metadata Registry and Clearinghouse Version 7.0 Federation Specification<br />DoD Architecture Framework (DoDAF) 2.0<br />
  21. 21. Policy & Guidance<br />DoD CIO Executive Board (CIO EB)<br /> Military Communications and Electronics Board (MCEB)<br /> GIG E2E Systems Engineering Advisory Board (SSEB)<br /> IT Standards Oversight Panel (ISOP)<br /> Information Assurance Senior Leadership Group (IASLG)<br /> Interoperability Senior Review Panel (ISRP)<br /> GIG Waiver Board and Panel<br />DISN Flag Panel<br />DISN Designated Approving Authority (DAA)<br /> DISN Security Accreditation Working Group (DSAWG)<br />DIAP (Defense-Wide Information Assurance Program.)<br /> Joint Battle Management Board (JBMC2 BoD)<br />Defense Business Systems Management Committee (DBSMC)<br />CCB (Configuration Control Board)<br />
  22. 22. Architecture Federation <br />Project Background<br />Architecture information, if properly developed, informs decision-making and assists in visualizing complex warfighter capability relationships and business processes <br />Some standards and guidance for architecture development exist, however:<br />Data is “stove-piped” in various proprietary tools and repositories<br />Information sharing is difficult <br />Use of proprietary architecture information has hampered the DoD’s capability to re-use and integrate previously developed architectures<br />
  23. 23. JACAE Goals<br /><ul><li>Establish standardized Joint Forces architectural definitions and product information to include baseline products and engineering developments
  24. 24. Provide and maintain a stable architecture data environment through the use of tools and configuration management processes
  25. 25. Enable performance and efficiency of architectural baseline and future developments, change control during development, and facilitate the accuracy and validation of joint data/information
  26. 26. Provide traceability of CPM operational, technical and programmatic elements to provide a standard context for the development, assessment, test, and exercise training of current and future warfighting capabilities
  27. 27. Facilitate architecture reusability across the C2 enterprise by normalizing business rules for web-service development and federation
  28. 28. Facilitate C2 capability engineering analysis for decision-making and capability improvement</li></li></ul><li>24<br />JACAE Objectives<br />Assist decision makers across the DoD by providing the ability to search, discover and visualize integrated, authoritative data and products from a secure, Joint/Service federated environment in support of Warfighter capability development.<br />Provide a secure, federated Joint/Service repository of reusable architecture products and reports to enable architecture developers to improve speed of development, reduce or eliminate duplication of effort, and create more efficient, collaborative architecture development and analysis processes in support of developing Joint, interoperable solutions for the Warfighter.<br />Provide a common infrastructure that is agile, scalable and reusable so that other architecture development efforts can easily integrate into the federation.<br />Reduce resource requirements through use/reuse of already existing technical expertise and previously developed architecture products and services.<br />

×