Event Metamodel and Profile (EMP) Proposed RFP Updated Sept, 2007

Transcription

1 Event Metamodel and Profile (EMP) Proposed RFP Updated Sept, 2007 Robert Covington, CTO 8425 woodfield crossing boulevard suite 345 indianapolis in

2 Motivation for this proposed RFP 1. Events are a critical component of Business Architectures. 2. Currently adopted standards, such as UML, are not sufficient for modeling events in business or IT systems, or the interactions between agents and services. 3. No standard exists for modeling Complex Event Processing concepts. 4. A common ontology defining EDA domain terminology and related conceptual knowledge is required to support interoperability among CEP systems. 2

3 Objectives of Proposed RFP One or more common ontology components representing common terminology and conceptual knowledge as well as a metamodel to unify the diverse notions of Events that exist in the industry. Clarify UML semantics concerned with Events and establish modeling best practices. Complement the existing UML metamodel by defining an extension to UML to ensure complete and consistent Event specifications and implementations. Integrate with and complement Event Driven Architecture (EDA) related standards developed by the OMG and other organizations such as W3C, ISO, IEEE and OASIS. Incorporate emerging industry consensus from University Research and the Event Processing Technical Society (EPTS). Enable modeling of Complex Event Processing concepts such as composite events, causal event modeling, event patterns, and event constraints. Facilitate the adoption of Event Driven Architectures (EDAs) through more abstract and platform independent models in order to (i) speed EDA development, (ii) decouple EDA design from evolving implementations, and (iii) enable generation of platform specific artifacts. Support for contracts and traceability between the Event Source and the Event Consumer. Enable interchange of event models between tools via XMI. 3

4 RFI and RFP Contributors Aptsoft BEA CellExchange Cordys Data Blueprint EDS IBM MetLife NIST Rhysome Sandpiper Software Tibco WareLite Your participation is welcome! 4

5 Applicable OMG s Unified Modeling Language (UML) Business Process Modelling Notation (BPMN) Enterprise Collaboration Architecture (ECA) Event Service Specification Event-driven architecture for SOA Management of Event Domains Notification / JMS Interworking A specification defining a graphical language for visualizing, specifying, constructing, and documenting the artifacts of distributed object systems. A process diagram specification 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). 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. 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 Developing modeling standards for the interaction of Event Driven Architectures and Service Oriented Architectures Specifies an architecture and interfaces for managing event domains 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. RFI 5

6 Applicable OMG s (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. Production Rules Representation (PRR) Semantics of Business Vocabulary and Rules (SBVR) SysML UML Profile and Metamodel for Services (UPMS) Business Process Definition Metamodel (BPDM) Production Rules Representation - Specification for Condition - Action rule sets extensible to ECA (Reaction) rules. Business language statements of terms, facts and business constraints, usually defined in relation to business events. The 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 UML profile for modeling services A metamodel for all different types of processes, primarily aimed at BPMN modeled processes but capable of extension to EDA processes. RFP (Finalization) RFP 6

7 Applicable OMG s (cont) UML Profile for EDOC UML Profile for Schedulability, Performance and Time Ontology Definition Metamodel (ODM) Knowledge Discovery Metamodel (KDM) Meta Object Facility 2 (MOF2) MOF Versioning UML Profile for Enterprise Distributed Object Computing Specifies a UML profile that defines standard paradigms of use for modeling of time-, schedulability-, and performance-related aspects of real-time systems 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. This specification defines a meta-model for representing information related to existing software assets and their operational environments 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. The problem being addressed by this Specification is to manage the co-existence of multiple versions of metadata in a Meta Object Facility 7

8 Applicable OASIS s 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 WS-BaseNotification WS-BrokeredNotification WSDM Management Of Web Services (MOWS) WS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. WS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. Defining a Web services architecture to manage distributed resources Approved Approved Approved WSDM Management Using Web Services (MUWS) WS-Topics Defining a Web services architecture to manage distributed resources WS-Notification is a family of related specifications that define a standard Web services approach to notification using a topic-based publish/subscribe pattern. Approved Approved 8

9 Applicable W3C s Document Object Model Level 2 Events Specification Document Object Model Level 3 Events Specification Ubiquitous Web Applications Activity Proposal WS-Eventing Xforms XHTML Events Module XML Events 2 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 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 The Ubiquitous Web Applications Working Group seeks to simplify the creation of distributed Web applications involving a wide diversity of devices. This specification defines a protocol for one Web service to register interest with another Web service (called an "event source") in receiving messages about events. XForms is an XML application that represents the next generation of forms for the Web. 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 An Events Syntax for XML Recommendation Draft Chartered Group Draft Recommendation Draft Draft XML State Chart XML (SCXML) State Machine Notation for Control Abstraction Draft 9

10 Mandatory Requirements 1. Provide a MOF metamodel and equivalent Profile extending UML for Event Modeling as specified in other mandatory requirements specified in this RFP. 2. Metamodel and profile extensions can extend, but not conflict with, existing UML semantics for extended metaclasses. 3. Specify icons for stereotype extensions to UML in order to extend the UML notation for Event modeling. 4. Notations must specify icons for stereotype extensions to UML 5. Specify one or more ontology components representing business and IT vocabulary for events, event types, and event-related processing to unify terminology usage across applications and vendor environments. Use cases and documentation describing coverage and providing examples are also required. 6. Describe how event sources and consumers maintain traceability of events during event processing. 7. The traceability specification must maintain consistency with the emerging UPMS and the BPDM standards. 8. Specify how Events convey information about publication and subscription to sources and consumers. 9. Specify how Events express their relationship to one another in terms of time. 10. Specify how totally ordered sets (TOSETs) and partially ordered sets (POSETs) are modeled for Events. 11. Specify how composite events, causal relationships, event patterns, and event constraints are modeled. 12. Specify how events communicate information about their retention and lifecycle. 13. Express the intent of Event models rather than any specific means by which that intent may be realized by some runtime platform. 14. Be compatible with existing event driven implementations from OMG, excluding CORBA Pull Consumer Interface 15. Be compatible 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. 10

11 Optional Requirements 1. Specifications for modeling the interaction with Agents 2. Modeling the interaction with Request/Reply Systems 3. Support for CORBA Pull consumer interface 4. Compatible with existing Event Implementations from OASIS, and W3C 5. Support for: 1. Changing metadata in the Event Source 2. Out of order Events 3. Event Persistence 11

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

13 Proposed Schedule Approx Day TC votes to issue RFP LOI to submit to RFP due Initial submissions due Voter registration closes Revised submissions due Event or Activity Issuance recommendation of RFP by TF Approval of RFP by Architecture Board Review by TC ( Four week rule ) Initial submission presentations Preliminary evaluation by TF Revised submission presentations Final evaluation and selection by TF Recommendation to AB and TC Approval by Architecture Board Review by TC ( Four week rule ) TC votes to recommend specifications BOD votes to adopt specifications June 2007 December 14, 2007 February 12, 2008 April 12, 2008 April 26, 2008 May 3, 2008 June 2008 Actual Date November 12, 2007 August 10, 2008 August 31, 2008 September 2008 October 2008 November 8, 2008 December 8,