1. Event Metamodel and Profile (EMP) Proposed RFP March 12,2008 Robert D Covington, CTO rcovington@rhysome.com 8425 woodfield crossing boulevard | suite 345 | indianapolis | in | 46240 | 317.252.2640 |

2. 2 Business Analyst CEP Evangelist I wonder where I can get an “Easy” Event Processor What you need is a Complex Event Processing solution with fully Immutable Event Objects and Distributed Tuple Management EDA/CEP is Hard Enough without Standards

3. OMG’s Mission Since 1989 1.Develop an architecture, using appropriate technology, for modeling & distributed application integration, guaranteeing: Specifications are freely available Implementations required for standardization Member-controlled not-for-profit open to all vendors and customers 2.Primary focus on modeling standards not wire protocols, data structure or domain specific languages – DDS, CORBA popular exceptions 3.Model Driven Architectures Enable business problems to be architected and described in a format that is independent of specific Domain Specific Languages, protocols, or message formats

4. Who Are the OMG? BEA Systems Borland Boeing Business RulesGroup CA Capgemini Credit Suisse CSC Daimler DND-Canada EDS Fujitsu GCHQ Harris Hewlett Packard Hitachi IBM IONA Kaiser-Permanente MetLife MITRE NASA Navy UWC & SWC NEC New York Life NIST Northrop Grumman Oracle Pega Systems Penn National PrismTech Raytheon Samsung Sandia SAP Satyam Savvion Siemens SoftwareAG Unisys Visa W3C

5. OMG is known for: All created and cared for by OMG’s Members!

6. Liaison Relationships

7. What is a Metamodel 1.Metadata modeling is a type of metamodeling used in software engineering and systems engineering for the analysis and construction of models applicable and useful some predefined class of problems.Metadata modelingsoftware engineeringsystems engineering 2.In data engineering and software engineering, the use of models is more and more recommended. This should be contrasted with the classical code-based development techniques. A model always conforms to a unique metamodel. One of the currently most active branch of Model Driven Engineering is the approach named model-driven architecture proposed by OMG[1]. This approach is based on the utilization of a language to write metamodels called the Meta Object Facility or MOF. Typical metamodels proposed by OMG are UML, SysML, SPEM or CWM. ISO has also published the standard metamodel ISO/IEC 24744.modelsmetamodelModel Driven Engineeringmodel-driven architectureOMG[1]Meta Object Facility or MOFOMGUMLSysML ISO Source Wikipedia Page 7

8. Page 8 Motivation for an improved Modeling Standard 1.Event Driven Architectures and correlated Stream and Complex Event Processing Systems are a critical component of Business Architectures. 2.Certain aspects of modern Event Driven Architectures have made them difficult to model using existing modeling standards (UML/BPMN) 3.No standard exists for modeling Complex Event Processing concepts such as composite events, causal event modeling, event patterns, partially ordered sets of events, and event constraints. 4.Having a modeling notation to describe Business Problems that require Complex Event Processing principals is important. 5.A common ontology, vocabulary and metamodel does not exist for EDA. 6.The diversity in the CEP industry makes development of common language, integration protocols, reference architectures, common event objects difficult. Development of a standard modeling notation and vocabulary for describing CEP Business problems is a good first step towards standardization in the industry.

9. Page 9 Applicable OMG EDA Standards BPMNBPMN provides a Business Process Diagram (BPD), which is a Diagram designed for use by the people who design and manage business processes. BPMN also provides a formal mapping to an execution language of BPM Systems (BPEL4WS). Adopted Standard Enterprise Collaboration Architecture (ECA) The Events profile, which describes a set of UML extensions that may be used on their own, or in combination with the other EDOC elements, to model event driven systems. Adopted Standard Event Service Specification Defines two roles for objects: the supplier role and the consumer role. produce event data and consumers process event data. Event data are communicated between suppliers and consumers by issuing standard CORBA requests Adopted Standard Event-driven architecture for SOA Developing modeling standards for the interaction of Event Driven Architectures and Service Oriented Architectures RFI Management of Event Domains Specifies an architecture and interfaces for managing event domainsAdopted Standard Notification / JMS Interworking The interworking involves several aspects such as: event message mapping; QoS mapping; event and message filtering; automatic federation between Notification Service channel concept and topic/queue concepts; and transaction support. Adopted Standard

10. Page 10 Applicable OMG EDA Standards (cont) Notification Service An extension to the existing OMG Event Service, adding to it: transmitting events in the form of a data structure; event subscription; discovery; QoS; and an optional event type repository. Adopted Standard Production Rules Representation (PRR) Production Rules Representation - Specification for Event - Condition - Action rule sets RFP SysMLThe OMG systems Modeling Language (OMG SysML™) is a general-purpose graphical modeling language for specifying, analyzing, designing, and verifying complex systems that may include hardware, software, information, personnel, procedures, and facilities Adopted Standard UML Profile and Metamodel for Services (UPMS) UML profile for modeling servicesRFP Unified Modeling Language (UML) A specification defining a graphical language for visualizing, specifying, constructing, and documenting the artifacts of distributed object systems. Adopted Standard

11. Page 11 Applicable OMG EDA Standards (cont) UML Profile for EDOC UML Profile for Enterprise Distributed Object Computing UML Profile for Schedulability, Performance and Time Specifies a UML profile that defines standard paradigms of use for modeling of time-, schedulability-, and performance-related aspects of real-time systems Ontology Definition Metamodel (ODM) ODM is applicable to knowledge representation, conceptual modeling, formal taxonomy development and ontology definition, and enables the use of a variety of enterprise models as starting points for ontology development through mappings to UML and MOF. Knowledge Discovery Metamodel (KDM) This specification defines a meta-model for representing information related to existing software assets and their operational environments Meta Object Facility 2 (MOF2) MOF is an extensible model driven integration framework for defining, manipulating and integrating metadata and data in a platform independent manner. MOF-based standards are in use for integrating tools, applications and data. MOF VersioningThe problem being addressed by this Specification is to manage the co-existence of multiple versions of metadata in a Meta Object Facility

12. Page 12 Applicable OASIS EDA Standards Common Alerting Protocol The Common Alerting Protocol (CAP), a data interchange standard for alerting and event notification applications, currently in version 1.1. CAP functions both as a standalone protocol and as a payload for EDXL messages. Approved Standard WS-BaseNotificationWS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. Approved Standard WS-BrokeredNotificationWS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. Approved Standard WSDM Management Of Web Services (MOWS) Defining a Web services architecture to manage distributed resourcesApproved Standard WSDM Management Using Web Services (MUWS) Defining a Web services architecture to manage distributed resourcesApproved Standard WS-TopicsWS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. Approved Standard

13. Page 13 Applicable W3C Standards Document Object Model Level 2 Events Specification Design of a generic event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event Recommendation Document Object Model Level 3 Events Specification Design of a generic event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event Draft Ubiquitous Web Applications Activity Proposal The Ubiquitous Web Applications Working Group seeks to simplify the creation of distributed Web applications involving a wide diversity of devices. Chartered Group WS-EventingThis specification defines a protocol for one Web service to register interest with another Web service (called an "event source") in receiving messages about events. Draft Xforms XForms is an XML application that represents the next generation of forms for the Web. Recommendation XHTML Events Module This specification defines the XHTML Event Module, a module that provides XML languages with the ability to represent in syntax the semantics of the Document Object Model (DOM) Level 2 event interfaces Draft XML Events 2An Events Syntax for XMLDraft XML State Chart XML (SCXML) State Machine Notation for Control AbstractionDraft

14. What do we mean by Event? The term “Event” is used to define both the definition of an event and an occurrences of the event A further breakdown of “Event” Event Generator – actor – The object that generates the event Event Detector – The method/object that detects events Event Specification – The definition of the event Event Occurrence/Instance – when the event occurs Event Notification – when the event notification is distributed Page 14

15. 15 UML v2.0 State Definitions State A state is a condition during the life of an object during which it satisfies some condition, performs some activity, or waits for some external event Event An event is the specification of a significant occurrence. For a state machine, an event is the occurrence of a stimulus that can trigger a state transition Transition A transition is a relationship between two states indicating that an object in the first state will, when a specified set of events and conditions are satisfied, perform certain actions and enter the second state. A transition has: Transition Components – A source state – An event trigger – An action – A target state Action An action is an executable, atomic (with reference to the state machine) computation. Actions may include – operations, the creation or destruction of other objects, or the sending of signals to other objects (events). Substates A substate is a state that is nested in another state. A state that has substates is called a composite state. A state that has no substates is called a simple state. Substates may be nested to any level.

16. Event Processing Glossary from EPTS Event: Something that happens. Event (also event object, event message, event tuple): An object that represents, encodes or records an event, generally for the purpose of computer processing. Notes: Events are processed by computer systems by processing their representations as event objects. The same activity may be represented by more than one event object; each event object might record different attributes of the activity. In many event processing systems, for example simulation systems, events are immutable. A modification or transformation of an event must be achieved by creating a new event object and not by altering the original event. Deletion would entail removing an event from further processing. Initial compilation by David Luckham and Roy Schulte Source: http://complexevents.com/?p=195 Page 16

17. Page 17 Objectives of RFP Develop a UML profile for representing and clarifying semantics concerned with modeling Events Driven Architectures in UML. Provide a UML metamodel to address the modeling needs for Complex Event Processing Tighter definitions of “Events” and triggers for continuous event processing CEP concepts such as Composite Events, causal relationships, Event patterns, Event broadcast, and Event constraints Support for all of BPMN/BPEL’s event handling capabilities Compiling a standard glossary of terms that is suitable for both CEP and other related domains. Supporting the interchange of event models between tools using XMI.

18. Page 18 Mandatory Requirements Required Metamodel and Profile Submissions to this RFP shall provide a MOF metamodel and equivalent Profile extending UML for Event Modeling. The metamodel shall extend UML for Event Modeling as specified in other mandatory requirements specified in this RFP. UML Compatibility These metamodel and profile extensions shall not conflict with existing UML semantics for extended metaclasses. However, if the metamodel and profile extensions can extend, but do conflict with existing UML semantics, the decision to do so shall be justified. UMPS, PRR, and RT Compatibility Notation Submissions shall specify icons for stereotype extensions to UML in order to extend the UML notation for Event modeling. Glossary of Event Terms Submissions shall provide a glossary of terms for Events that can be used to support interoperability among CEP applications.

19. New/Moved Mandatory Requirements Event Classification ODM “profile” for describing event ontology Taxonomy out of scope Event Aggregation and Correlation Submissions may specify how composite Events, causal relationships, Event patterns, Event Broadcast and Event constraints are modeled. Compatibility with Event Processing Styles Submissions shall address the issue of compatibility with different approaches to Event Processing, including Simple Event Processing, Stream Processing, and Complex Event Processing (CEP), permitting the analysis of Event stream networks and the control of event stream responses. UPMS Agents Submissions may provide specifications for modeling the use of Events by Agents, as defined in UPMS. Page 19

20. Page 20 Optional Requirements 1.BPMN/BPDM mappings 2.Alternative Notations Submissions may provide non-UML2 notations for consideration although every effort should be taken to avoid this. 3.Mappings to Existing Platforms and Languages Submissions may provide one or more mappings to existing platforms and languages as a proof-of-concept.

21. Page 21 Out of Scope/Future Scope 1.Event Calculus Mapping 2.QOS (Service Metrics, performance, etc.) 3.Event Source Discovery 4.Governance or Compliance 5.Security 6.Definition of data structures, wire protocols and messaging formats. 7.Implementation language 8.Event Taxonomy 9.Testing

22. Example Event (CEP) Model Source: TIBCO BusinessEvents Event Sources (technology, driver, etc) Event Sources/Destinations (IDL spec, pub-sub address, etc) Content Event lifecycle

23. Page 23 RFI and/or RFP Contributors Aptsoft Axway CA CellExchange Collaborative Consulting Cordys Data Blueprint EDS IBM MetLife NIST Oslo Software Rhysome Sandpiper Software Tibco WareLite Looking for more contributors!!

24. Page 24 Critical Path Items 1.Verify alignment with UPMS, PRR, UML-RT 2.CEP Vendor/End User Outreach Event Processing Technical Society OMG Complex Event Processing Session, March 13, 2008 Would like participation from more CEP vendors. 3.Resume weekly calls the week of March 24 4.RFP AB Vote planned for June 2008 meeting 5.Wiki: http://www.omgwiki.org/soaeda/doku.phpWiki: http://www.omgwiki.org/soaeda/doku.php