EventMetamodelandProfile(EMP)ProposedRFP(ad07-11.pptVIP

Confidential and Intellectual Property of Rhysome, Inc. RHYSOME and ZOMA TM are trademarks of Rhysome Copyright 2005. All rights reserved. Event Metamodel and Profile (EMP) Proposed RFP (ad/07-11-01)Updated December 11, 2007P.J. Hinton, Software Engineer8425 woodfield crossing boulevard | suite 345 | indianapolis | in | 46240 | 317.252.2640 |  Talk Organization Changes made to the RFP since September meeting (ad/07-08-01) RFP Objectives Motivation RFP Scope Response requirements (mandatory, optional, for discussion) Reasons for postponing issuance Proposed Schedule Acknowledgements What’s Changed Since September Meeting? Several major revisions made based on detailed review by Pete Rivett. Narrowed and refined RFP scope. Removed citations of standards that were of limited relevance to event modeling. Moved several requirements from mandatory to optional. Increased items to be discussed. Streamlined evaluation criteria. Objectives for this proposed RFP Clarify semantics concerned with modeling Events using a UML Profile Establish Event modeling best practices for UML by incorporating constraints from the UML Profile and Metamodel for Services (UPMS). Provide a UML metamodel to address the modeling needs of the Event Processing community. Enable Event model interchange between tools via XMI. Events in Complex Event Processing In CEP, an Event is an observation of state. An Event has three aspects: Form: What does the event report about the occurrence? Significance: What does the event represent? Relativity: How are events related to one another? Types of relationships between events Time: “receiver lifted” precedes “number dialed” Causality: “window shatters” event happened because “projectile strikes window” Aggregation: “account overdrawn” event consists of “check received”, “withdrawal attempt”, “subzero balance computed” and “fee assessed” events. Source: David Luckham, The Power of Events, Addison-Wesley, 2002. Events in UML Existing Modeling Sta