300 likes | 316 Views
J89 Mission: Support rapid architecture development, analysis, capability assessments, and portfolio management for well-informed decision-making. Explore JAFE service-oriented strategy and collaboration model. Implement system virtualization for enhanced resource allocation. Enhance architecture development processes for defense initiatives.
E N D
Service Oriented ApproachJAFE: a Joint architecture federation environmentHoward cohen(Booz Allen Hamilton)howard.cohen@jfcom.milMatthew Sutton (Booz Allen Hamilton) matthew.sutton.ctr@jfcom.mil
J89 Mission MISSION • The Joint Integrated Architectures and Systems Engineering Division (J89) mission is to support architecture development, analysis, capability assessments and portfolio management to enable speed, agility and well-informed decision making through rapid availability and re-use of architectures. (Gen. Kennedy, USJFCOM J8, April 2010) VISION • "An operations officer is in the field and has been assigned a new battalion to their forces. The officer calls up the appropriate federated data, modifies the view dynamically with the new resources and dynamically re-builds the view, re-tasks the resources, simulates it and generates all the appropriate operations orders on the fly." "That is my vision." (SES Martin Westphal, USJFCOM J8F, March 2010)
VISION Enablers • Federation of Architecture Data (Data Sharing) • Way to Expose Data(Visibility) • Access to Validated Architecture Products (Discoverability) • Connection and Traceability (common lexicons) • Operational Context (Understandability) • Joint Mission Threads • Virtual Development Environment • Teaming
JAFE The Joint Architecture Federation Environment Project 2008 - Present
Why Federate? Purpose is to support decision makers by enabling the speed and agility of well-informed decision making through rapid availability and re-use of architectures
JAIWG- Joint Architecture Federation and Integration Project • Goals: • Establish the capability to discover authoritative data in federated Joint and/or Service repositories • Leverage partnerships with mature DoD architecture development efforts in order to maximize use of existing resources and re-use of architecture data • Provide the framework, standardsand governance for a federated, joint, architecture information sharing and development environment
Project Strategy • Top Down Systems Engineering Approach • Virtual Teaming • Geographically and organizationally dispersed members • Three Part Integration • Application Enterprise Construction • Developing Requirements, DoDAF Views, Business Process and System Models • Scope of Work – WBS and task breakdown governance • Integration Consideration – exchange and interoperate with many sources
Pattern JAFE: The Joint Architecture Federation Environment
JAFE Service model • Enterprise Stack • Joint Context • Joint Service Model • Joint Application Stack DoD DoD Enterprise *DISA* Logical Unintended / Intended User Joint Forces J89 Next Level
JAFE service model • Joint Forces J89 Stack J8 Applications J89 / SADIE Business Process J892
Virtual Teaming This approach brings people together across the DoD and beyond!
Three Part Integration Use Case: The normalization of data from J89 data providers.
Enterprise Application ConstRuction Certification Labor Acquisition Engineering Standards
Integration Considerations Governance
Summary • This is work in progress and it’s real
System Virtualization The term virtualizationbroadly describes the separation of a resource or request for a service from the underlying physical delivery of that service.
System Quality and Assurance Production VM Production VM DEV VM QA VM Production VM Development Quality Assurance Production VM Develop Test Deploy System Testing
Server Consolidation 1 Database Server App Server App Server Citrix Server App Server Many to One App Server ESX Citrix Server App Server App Server Database Server
System Tuning Apache Tomcat 6.0.18 Weblogic 9.2 Versant 7.0.1.4 Patch11 Sun Solaris 9 64 Bit Windows 2003 R2 32 Bit Windows 2003 R2
Service Oriented Warfighter
**Architecture Context Service Oriented Approach • Reduce Rework and Eliminate/Reduce Duplication of Effort • Share Data Between Various Organizations, Tools and Environments • Encourage a More Effective Collaboration Environment • Create More Efficient Architecture Development and Analysis Processes in Support of DoD Initiatives • Improved Speed of Development
**Architecture Context Service Oriented Warfighter
Capability Mapping Baseline Joint Common System Functions List (JCSFL) USN JCAs USMC USA JCAs USAF NCES/NECC Other CPMs Policy Standards Policy Architectures Systems Functions Joint Capability Areas (JCAs) CPM Areas Standards Tier I Analysis Policy Technical Standards Accreditations C2 Portfolio* - Programs of Record - Systems - Sub-systems - New Capabilities Policy Platforms/Weapons Standards ADS & Data Models Policy Joint Staff J7 Mapping Standards Operational Activities Applications/Services Policy JTF OperationalActivities / Tasks / Sub-tasks Networks/Comms UJTL SN X.X ST X.XX OP X.X.X TA X.X.X.X Standards Policy Assessments Joint Tasks Operational Standards AUTLs, MCTL, NTTL, AFTL Documentation Policy Service Tasks Operational Nodes & Billets Concepts/Plans Standards Joint Warfighter Billets Programmatic JCAs- to- PECs Op Nodes PA&E Mapping Joint Integration & Interoperability Recommendations via Detailed DOTMLPF Analysis Authoritative Sources: