1 / 10

Influences on M&S COI Tasks

M&S Services at the Crossroads of Service Oriented Architecture and the DoD Architectural Framework. Bernard P. Zeigler, Ph.D., Arizona Center for Integrative Modeling and Simulation and Joint Interoperability Test Command Fort Huachuca, AZ 85613-7051 zeigler@ece.arizona.edu.

Download Presentation

Influences on M&S COI Tasks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. M&S Services at the Crossroads of Service Oriented Architecture and the DoD Architectural Framework Bernard P. Zeigler, Ph.D.,Arizona Center for Integrative Modeling and SimulationandJoint Interoperability Test CommandFort Huachuca, AZ 85613-7051zeigler@ece.arizona.edu

  2. Influences on M&S COI Tasks M&S Body of Knowledge MetaData M&S Theory and Framework Mediation DoD Architectural Framework Services

  3. DoD Architectural Framework (DoDAF) • DoD mandate requires that the DoD Architectural Framework (DoDAF) be adopted to express high level system and operational requirements and architectures. • DoDAF is the basis for the integrated architectures mandated in DOD Instruction 5000.2 and provides broad levels of specification related to operational, system, and technical views. • Operational views capture the requirements of the architecture being evaluated • System views provide its technical attributes

  4. Implications for GIG/SOA and M&S COI • The development of the Global Information Grid (GIG) and its service oriented architecture (SOA) • The concerns of the M&S COI must eventually be expressed within the appropriate DoDAF views. • The services offered by the M&S COI must be architected within the DoDAF operational views • Obstacles: • The DoDAF essential approach is that of systems orientation rather than service orientation • The DoDAF expresses interest in development of executable architectures but does not explicitly elucidate M&S support

  5. Correlating Development Life Cycle Phases with DODAF Views Planner Owner Designer Implementer Contractor Operator (not in DODAF) Actors (DODAF People/IO) Phases of life cycle DODAF view products Concept Analysis Design Develop Test Deploy Maintain For each phase in life cycle, associate the relevant actors and from there, the relevant DODAF View Products

  6. Community-wide Enterprise Services COI Enterprise Services CORE Enterprise Services Service Offering Life Cycle in SOA Environment • Services • at multiple levels • in multiple phases • under pressure to be delivered quickly

  7. OV-5 SVS-6 SVS-4 SVS-7 describes describes describes describes Service Definitions OV-6c describes Application Services Infrastructure Services describes describes describes describes SVS-5 SVS-1 SVS-2 SVS-3 Elaborating DoDAF with Services View Data Relationships define Service Performance Descriptions Operational Activities Services Hierarchy define structures Services Reference Model map to map to define define compose Operational Threads Service Compositions compose compose includes compose compose Operational Threads To Service Threads Mapping Application Service Threads Infrastructure Service Threads includes source: http://www.saug-usa.org/conferences/truman_parmele_pres_0405.ppt

  8. DEVS Model DEVS Model DEVS Model DEVS Simulator DEVS Distributed Executor DEVS Distributed Simulator DEVS-Based Life Cycle Development of Web Services Correlated with DoDAF Pre-test of Conceptual Model in non-distributed environment Packaging:XML SOA Messaging:SOAP Service Discovery: UDDI Communication: HTTP Sevice Description: WSDL Packaging:XML Messaging:SOAP Refine and Transfer model to distributed environment Communication: HTTP • Change engine • Provide meta-data for • Web presence as service

  9. Conclusions • Correlating DoDAF with SOA Life Cycle Development process and M&S is not straightforward • DoDAF needs elaboration with service oriented views • To support M&S needs • elaboration of downstream life cycle • integration of verification testing along cycle • integration of evaluation along cycle (connection with NR-KPP)

  10. Bernard P. Zeiglerzeigler@ece.arizona.eduACIMSwww.acims.arizona.edu Contact: More information:

More Related