Interoperability, Automation, Built-in Evolution: the DEVS Framework for Coping with Emerging Complexity Bernard P. Zeigler Arizona Center for Integrative.

Slides:



Advertisements
Similar presentations
REST Introduction 吴海生 博克软件(杭州)有限公司.
Advertisements

Siebel Web Services Siebel Web Services March, From
Crucial Patterns in Service- Oriented Architecture Jaroslav Král, Michal Žemlička Charles University, Prague.
Web Service Ahmed Gamal Ahmed Nile University Bioinformatics Group
Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
Snejina Lazarova Senior QA Engineer, Team Lead CRMTeam Dimo Mitev Senior QA Engineer, Team Lead SystemIntegrationTeam Telerik QA Academy SOAP-based Web.
Reliability on Web Services Presented by Pat Chan 17/10/2005.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Workflow utilization in composition of complex applications based.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
DEVS-Based Simulation Web Services for Net-Centric T&E Saurabh Mittal, Ph.D. Jose L. Risco-Martin*, Ph.D. Bernard P. Zeigler, Ph.D. Arizona Center for.
Distributed Heterogeneous Data Warehouse For Grid Analysis
Presentation 7 part 2: SOAP & WSDL. Ingeniørhøjskolen i Århus Slide 2 Outline Building blocks in Web Services SOA SOAP WSDL (UDDI)
Latest techniques and Applications in Interprocess Communication and Coordination Xiaoou Zhang.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Community Manager A Dynamic Collaboration Solution on Heterogeneous Environment Hyeonsook Kim  2006 CUS. All rights reserved.
Web Service What exactly are Web Services? To put it quite simply, they are yet another distributed computing technology (like CORBA, RMI, EJB, etc.).
Web Services Michael Smith Alex Feldman. What is a Web Service? A Web service is a message-oriented software system designed to support inter-operable.
Processing of structured documents Spring 2003, Part 6 Helena Ahonen-Myka.
February Semantion Privately owned, founded in 2000 First commercial implementation of OASIS ebXML Registry and Repository.
Enterprise Systems & Architectures. Enterprise systems are mainly composed of information systems. Business process management mainly deals with information.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
THE NEXT STEP IN WEB SERVICES By Francisco Curbera,… Memtimin MAHMUT 2012.
Web Services Mohamed Fahmy Dr. Sherif Aly Hussein.
Adapting Legacy Computational Software for XMSF 1 © 2003 White & Pullen, GMU03F-SIW-112 Adapting Legacy Computational Software for XMSF Elizabeth L. White.
DMSO Technical Exchange 3 Oct 03 1 Web Services Supporting Simulation to Global Information Grid Mark Pullen George Mason University with support from.
Web services: Why and How OOPSLA 2001 F. Curbera, W.Nagy, S.Weerawarana Nclab, Jungsook Kim.
 Applied Architectures and Styles Chapter 11, Part 2 Service-Oriented Architectures and Web Services Architectures from Specific Domains Robotics Wireless.
Outline  Enterprise System Integration: Key for Business Success  Key Challenges to Enterprise System Integration  Service-Oriented Architecture (SOA)
What is Service Oriented Architecture ? CS409 Application Services Even Semester 2007.
DEVS Namespace for Interoperable DEVS/SOA
International Telecommunication Union Geneva, 9(pm)-10 February 2009 ITU-T Security Standardization on Mobile Web Services Lee, Jae Seung Special Fellow,
Architecting Web Services Unit – II – PART - III.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Interfacing Registry Systems December 2000.
Crystal-25 April The Rising Power of the Web Browser: Douglas du Boulay, Clinton Chee, Romain Quilici, Peter Turner, Mathew Wyatt. Part of a.
Web Services Based on SOA: Concepts, Technology, Design by Thomas Erl MIS 181.9: Service Oriented Architecture 2 nd Semester,
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Modeling and Simulation Methodology: The Challenge of Complex Endeavors Bernard Zeigler Arizona Center for Integrative Modeling and Simulation, University.
Introduction to Server-Side Web Development Introduction to Server-Side Web Development using JSP and Web Services JSP and Web Services 18 th March 2005.
1 UNIT –II Architecting Web Service. 2 Why SOA? – business point of view  Information Technology (IT) workers face many challenges, including: Limited.
The Need for a Theory of Modeling and Simulation to Support the M&S COI Mission Bernard P. Zeigler, Ph.D., Arizona Center for Integrative Modeling and.
XML and Web Services (II/2546)
Unifying Discrete and Continuous Simulation with Discrete Events: DEVS as the Next Modeling Standard Bernard P. Zeigler Arizona Center for Integrative.
SOAP-based Web Services Telerik Software Academy Software Quality Assurance.
M&S Services at the Crossroads of Service Oriented Architecture and the DoD Architectural Framework Bernard P. Zeigler, Ph.D., Arizona Center for Integrative.
DEVS and SES as a Framework for Modeling and Simulation Tool Development Bernard P. Zeigler Arizona Center for Integrative Modeling and Simulation University.
Slide 1 Service-centric Software Engineering. Slide 2 Objectives To explain the notion of a reusable service, based on web service standards, that provides.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
INFSO-RI Enabling Grids for E-sciencE Web Services Mike Mineter National e-Science Centre, Edinburgh.
EGEE is a project funded by the European Union under contract IST Introduction to Web Services 3 – 4 June
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
Introduction to Service Orientation MIS 181.9: Service Oriented Architecture 2 nd Semester,
Software Architecture Patterns (3) Service Oriented & Web Oriented Architecture source: microsoft.
XML and Distributed Applications By Quddus Chong Presentation for CS551 – Fall 2001.
By Jeremy Burdette & Daniel Gottlieb. It is an architecture It is not a technology May not fit all businesses “Service” doesn’t mean Web Service It is.
A service Oriented Architecture & Web Service Technology.
Service Oriented Architecture (SOA) Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
WEB SERVICES.
Unit – 5 JAVA Web Services
SOA (Service Oriented Architecture)
Software Connectors.
Inventory of Distributed Computing Concepts and Web services
Service-centric Software Engineering
Service-centric Software Engineering 1
Tools for Composing and Deploying Grid Middleware Web Services
Service Oriented Architecture (SOA)
The Anatomy and The Physiology of the Grid
Presentation transcript:

Interoperability, Automation, Built-in Evolution: the DEVS Framework for Coping with Emerging Complexity Bernard P. Zeigler Arizona Center for Integrative Modeling and Simulation University of Arizona, Tucson and RTSync Corporation 1

IT Systems Developmental Complexity? IT Systems Developmental Complexity = degrees of developmental freedom × interdependence of design decisions × special requirements of environments IT Complexity explosion – is driven by faster, cheaper computers, networking, web middleware, …, – Emergence: each stage enables the next stage with accelerating options for further growth – Wherever choices in platform, language,…, line of code, are possible, different developers will make different choices – Underlying structure/behavior dependencies force local decisions to have global impact breaking neat design patterns – Environments impose a plethora of special situations and an exponentially growing number of parameter combinations. 2

Consequences of complexity explosion: – Proliferation of incompatible variations on same themes – Ubiquitous heterogeneity – Vertical integration - “Stove piping” 3 Response: Model-Driven Development Methodology is increasingly being adopted for software-intensive system development In this context, model is an abstract representation of software code, that – is technology independent – can survive technology changes – can be implemented in multiple code instantiations – enables reuse and automation

UML (Unified Modeling Language) Is the most widely used framework to support model driven development Promoted by Object Management Group as a standard within its Model Driven Architecture (MDA) Supported by increasingly powerful commercial tools Enhanced by SysML supporting requirements front end Incorporated in architectural frameworks: DoDAF, MoDAF, … 4

Issues In Developmental Complexity of IT Systems Often development does not start from scratch Conditioned by idiosyncratic requirements Powered, but unconstrained, by applicable standards Requires legacy subsystem integration Rigorous testing is needed to cope with complexity Methodology must scale with growth and evolution of system UML/MDA offers only limited support to address these concerns 5

Formulate the Issues within a Formal System of System Models (SoSM) Concept SoSM = collection of disparate system models to be federated to satisfy new simulation requirements Each participating system model may itself be large and complex Participant models usually have become efficient at achieving their own specialized requirements Participant models often adhere to idiosyncratic formalisms and development approaches Distinguish between interoperation and integration to set appropriate objectives 6

Interoperation vs Integration* Interoperation of system components participants remain autonomous and independent loosely coupled interaction rules are soft coded local data vocabularies persist share information via mediation Integration of system components participants are assimilated into whole, losing autonomy and independence tightly coupled interaction rules are hard coded global data vocabulary adopted share information conforming to strict standards * adapted from: J.T. Pollock, R. Hodgson, “Adaptive Information”, Wiley-Interscience, 2004 NOT Polar Opposites! reusability composability efficiency 7

DEVS Framework Discrete Event Systems Specification (DEVS) is the basis for a formal framework for modeling and simulation DEVS contributes to scalability by: – Offering a standard for distributed simulation to support interoperability, composability, and reuse – Exploiting the separation between model, experimental frame and simulator – Fostering model continuity and progressive development – Automating and integrating complex systems implementation and testing – Emulating the biological brain for its "built-in" correlation of activity and behavior to drive efficient evolution via component re-us 8 DEVS is not a technique, method or technology… But it can leverage technology to add implement its contributions … in particular Web Service Technology

Web Service Oriented Architecture Basis for M&S 9 Language and platform independent => separation of specification and implementation Loosely coupled => message based, synchronous and asynchronous interactions. Net-Centric => No centralized control, use of established protocols, security considerations. Inter-operable => Standards based Observable => agents can inspect service requests/responses Transport protocol HTTP/HTTPS request/response Data Encoding SOAP (Simple Object Access Protocol), XML Schema Interface Description WSDL (Web Services Description Language) Service Description and Discovery UDDI (Universal Description, Discovery and Integration) Security WS-Security, XML-Signature, XML-Encryption,... Emerging infrastructure => Net-Centric Enterprise Services on the Global Information Grid Basis for Model Registration and Discovery => Meta-Data Registry Basis for Simulation => Web server and service development frameworks (.Net, AXIS) Emerging advances => Mediation services, Semantic Web Data Type Schema and Instances SOAP XML Network Layers Services Registries Data

Approach to Current Issues in SoSM Adopt Web-enabled M&S Concepts for composing SoSM Exploit SOA infrastructure for Model Repository and Component Reuse Develop Formal Dynamic SoSM Distributed Simulation Standard Build on this foundation to support Higher Levels of Interoperability Develop automated and integrated development and testing methodology 10

SOA-enabled Model Repository Composability and Reuse * * adapted from: ZEIGLER, B. P A framework for modeling & simulation. Applied Modeling & Simulation: An Integrated Approach to Development & Operation, McGraw-Hill, New York. RequirementIn relation toSupports Components and Coupling Creating new compositionscomposability reusability building block components for application areas defining a small number of “primitives” for synthesizing a wide variety of models for specific domain expressability reusability hierarchical modular model construction input/output ports for both building block components and coupled models composability complexity management experimental frame base indexing supports discovery of frames instantiated in the model base that are related to a desired frame for given objectives meta data characterization discovery accommodate multiple formalisms enable using different types of models with specific semantics, advantages, and limitations expressabilty interoperability 11

Success Story: DEVS-based Joint MEASURE – Model Repository Reuse* Note presence of discrete and continuous dynamic model types “… the Lockheed-Martin activities may well represent the state of the art in complex model composability …”, Improving the Composability of Department of Defense Models and Simulations, P.Davis and R.Anderson RAND, 2004 GPS III *Advanced Simulation Center, Lockheed Martin Corp., Sunnyvale, CA Use of infrared model in JCTS project 12

Linguistic Levels of Information Exchange and Interoperability syntactic semantic pragmatic syntactic semantic pragmatic Linguistic Level A System of Systems or services interoperates at this level if : Pragmatic – how information in messages is used The receiver re-acts to the message in a manner that the sender intends (assuming non-hostility in the collaboration). Semantic – shared understanding of meaning of messages The receiver assigns the same meaning as the sender did to the message. Syntactic –common rules governing composition and transmitting of messages The consumer is able to receive and parse the sender’s message System Participant 13

DEVS Model Specification SOAP XML DEVS Simulation Protocol Network Layers Services DEVS Standardization Supports Higher Level Web-Centric Interoperability DEVS Protocol specifies the abstract simulation engine that correctly simulates DEVS atomic and coupled models Gives rise to a general protocol that has specific mechanisms for: declaring who takes part in the simulation declaring how federates exchange information executing an iterative cycle that controls how time advances determines when federates exchange messages determines when federates do internal state updating DEVS Simulation Concept DEVS Protocol DEVS Simulator DEVS Model Note: If the federates are DEVS compliant then the simulation is provably correct in the sense that the DEVS closure under coupling theorem guarantees a well-defined resulting structure and behavior. syntactic semantic pragmatic 14 Schemata Registry

Web-enabled interoperability of DEVS components IP Network DEVS coordinator DEVS coordinator DEVS coupled Model DEVS coupled Model DEVSJAVA client JRE DEVS Simulator Services In C++ DEVS Simulator Services In C++ DEVS Model DEVS Model aDEVS Federate Microsoft web server.Net DEVS Simulator Services In JAVA DEVS Simulator Services In JAVA DEVS Model DEVS Model DEVSJAVA Federate Apache tomcat server AXIS2 Proxies DEVS Messages DEVS Namespace DEVS Namespace SOAP messages DEVS Message Class is defined in the formalism Schemata for entity classes in Message are stored in namespace DEVS Federates can register and discover schemata for information exchange DEVS Message Class is defined in the formalism Schemata for entity classes in Message are stored in namespace DEVS Federates can register and discover schemata for information exchange Supports re-use, composability, and interoperability Supports re-use, composability, and interoperability Can be automated for JAVA using Dynamic Invocation

Simulator Services Non-DEVS Federate web server Biologically Inspired Assessment for Component Re-use DEVS Simulator Services DEVS Model DEVS Model DEVS Federate Web server DEVS coordinator DEVS coordinator DEVS coupled Model DEVS coupled Model DEVS Coordinator JRE IP Network DEVS Agent DEVS Agent DEVS Agent DEVS Agent Mission Thread Evaluation Mission Thread Evaluation Activity Tracking Component Credit Assignment Component Credit Assignment Information for Future Component Re-use Http Requests/ responses Correlations of activity with Mission Thread Success Component benefit and resource cost in context collector

DEVS-Based Net-Centric Systems Test Agent Capability 17 Mission Thread Information Exchange Network Monitoring Middleware Mission Effectiveness System Performance Pragmatic Agents Semantic Agents Syntactic Agents T&E Instrumentation sites servers users clients networks workstations

Summary Model-driven methodology employs technology-independent software abstractions, e.g., in UML, to support diverse implementation platforms and enable reuse and automation Existing interoperability standards do not provide needed separation between models and simulations and do not effectively constrain object models System of System Modeling (SoSM) concepts go beyond UML/MDA to address issues in interoperability, composability, and reuse DEVS system theory –based framework operationalizes SoSM concepts and supports automated, rigorous testing in realistic GIG/SOA environments 18

devsworld.org Books and Web Links 19

More Demos and Links Integrated Development and Testing Methodology: AutoDEVS (ppt) & DEMO – Natural language-based Automated DEVS model generation – BPMN/BPEL-based Automated DEVS model generation – Net-centric SOA Execution of DEVS models – DEVS Unified Process for Integrated Development and Testing of SOA Intrusion Detection System on DEVS/SOA 20

DEVS/SOA Infrastructure: Supports Deployment and Execution of DEVS Models on the Web WEB SERVICE CLIENT Middleware (SOAP, RMI etc) Net-centric infrastructure DEVS Simulator Services DEVS Modeling Language (DEVML) DEVSJAVA DEVS Agent ( Virtual User) DEVS Agent (Observer) WEB SERVICE CLIENT Run ExampleExample Service Oriented Architecture (SOA) consists of various W3C standards Machine-to-machine interoperable interaction over the network based on WSDL interface descriptions Client server framework Message encapsulated in SOAP wrapper which is in XML

1.MAJ Smith tasks Intel to reconnoiter objective area and provide threat estimate 2. Posts taskings using Discovery and Storage 5. Intel Cell issues alert via messaging 6.MAJ Smith pulls estimate from Storage 3. Intel Cell initiates high priority collection against objective, and collectors post raw output 4. Intel posts products via Discovery and Storage Observing Agent for Major Smith Observing Agent for Intel Cell NCES GIG/SOA Test agents are DEVS models and Experimental Frames They are deployed to observe selected participant via their service invocations notes time of posting Observing Agent alerts other Agent Computes Time for Task, Measure Performance sends time to other Agent Example of GIG/SOA Mission Thread Testing 22