use case tutorial - introduction (1/7)

epts event processing technical society

eptsevent processing technical society

Pedro Bizarro on behalf of the group

Use Case TutorialIntroduction


2

Motivation of EPTS Use Case Workgroup

• Purpose

– Creation of a use case questionnaire

– Collection of use cases

– Classification of use cases

• Taxonomy and classification


3

Members• Dieter Gawlick <[email protected]> (co-chair)

• Pedro Bizarro <[email protected]> (co-chair)

• Alexander Widder <[email protected]>

• Arkady A. Godin <[email protected]>

• Bala Maniymaran <[email protected]>

• Beth Plale <[email protected]>

• Christoph Emmersberger <[email protected]>

• David Tucker <[email protected]>

• Florian Springer <[email protected]>

• Hans-Arno Jacobsen <[email protected]>

• Harvey G. Reed <[email protected]>

• Matthew Cooper <[email protected]>

• Rainer von Ammon <[email protected]>

• Steve Holbrook <[email protected]>

• Thomas Ertlmaier <[email protected]>

• Thomas Paulus <[email protected]>

• Serge Mankovskii ([email protected])

13 meetings since Feb

average participation: 7-8


4

Use Cases

• Retail Fraud • Thomas Paulus (CITT)

• Health Care • Pedro Bizarro, Diogo Guerra (U Coimbra), Dieter Gawlick (Oracle)

• Fleet Management • Matthew Cooper (EventZero)

• Very Large EPN – Bio-defense• Harvey G. Reed (MITRE) – Dieter on behalf of Harvey

• BPM/BAM • Hans-Arno Jacobsen (University of Toronto)

http://members.ep-ts.com/index.php?title=EPTS_UC_RF_Lessons

http://members.ep-ts.com/index.php?title=EPTS_UC_HC_Lessons

http://members.ep-ts.com/index.php?title=EPTS_UC_RF_Lessons

http://members.ep-ts.com/index.php?title=EPTS_UC_BD_Lessons

http://members.ep-ts.com/index.php?title=EPTS_UC_BB_Lessons


5

Information per Use Case

• Questionnaire

• Textual description

• PowerPoint overview

• Wiki-page with lessons learned and extra-info

http://members.ep-ts.org


6

The Questionnaire – Earlier versions

• 2007: Kick-off by Opher Etzion (IBM)

• 2008: Dieter Gawlick, Tao Lin (SAP), and Pedro andF2F meeting @ DEBS’2008 with Alex Kozlenkov (Betfair), Brian Connell (WestGlobal),Opher Etzion, and Richard Tibbetts (Streambase)

• 2008: 1st version @ 4th EPTS in September

• 2009: 2nd version today


7

The Questionnaire – Sections

• Short Description

• Functionality

– System Inputs and Outputs

– System users

– Event Processing

– Pattern Detection

– Reactions

– Specific Functional Aspects

• Operational

• Implementation Constraints

• Terminology in use


8

The Questionnaire – Short Description

• What problem are you trying to solve?

• Why do you use or want to use event processing systems? (e.g., better scalability, latency, detection, ROI, increased automation, or adaptability to changing requirements).

• What industry or organizations are involved?

• If end users are involved, briefly describe are their department, roles and responsibilities?

• What are the success metrics, if any?

• Status of your system? (in use, development, design)

• Diagrams (architecture, data-flows, GUIs)


9

The Questionnaire – FunctionalitySystem Inputs and Outputs

• Sources: Where do data come from?

• Input: What are the types of incoming data

• Acquisition: How is the data obtained?

• Sinks: Where is data delivered to?

• Output: What are the types of outgoing data

• Delivery: How is data delivered?

• Channels: How is data transmitted?


10

The Questionnaire – FunctionalityEvent Processing

• Filter: Describe any filters applied to events

• Enrichment: Are additional properties added into events

• Aggregation: Is the incoming event data aggregated?

• Concatenating/Merging: Are different event types being concatenated or combined?

• Translate: Is any encoding/decoding, enumerating, mediation, mapping, etc. required at the semantic and data levels?

• Transform: Is any schema transformation of the representation of a data model required?


11

The Questionnaire – FunctionalityPattern Detection for…

• Discover associations/relationships between events?

• Correlate events using event properties?

• Discover specific sequences of events?

• Discover trends over sequences of events?

• Discover trends over groups of events?

• Is there a need for an external program or user to query the state stored in a rule, e.g., to determine eventual pending alarms?

• Is there a need to express rules over a state instead/in addition to over individual events?

• Is there a need to store and/or query past patterns/states?


12

The Questionnaire – FunctionalitySpecific Functional Aspects

• Are events/messages time stamped and/or geo-tagged?

• Is there a need for other support associated with events such as classifications, security, clearance, or sensitivity markings?

• How should the system deal with out-of-order/missing events?

• Do you require the system to automatically learn new queries/patterns/models?

• Is there a requirement for a dynamic system with respect to new sources/sinks/channels?


13

The Questionnaire – FunctionalityOperational

• Number of components (sources, sinks, transformers, channels)?

• Events per second and with how much delay? Specify examples

• How many concurrent patterns/thresholds/triggers?

• How many “detections” per time unit do you anticipate having?

• Are there detection time requirements?

• How long do pattern instances need to be retained?

• Is scalability/growth a fundamental characteristic of your system?

• Recovery?, Fault Tolerance?, Disaster Tolerance?

• High Availability?, Load Balancing?, Transactionality?


14

Build and Review Process

• Build questionnaire incrementally, section-by-section

• Review, review, review

– Reviewers per document section

– Cross-review each other’s work

• Prevent stalemates by taking things offline

(Thank you Dieter!)


Outline

• Introduction Pedro

• Fraud in Retail Thomas

• Health Care Dieter

• Very Large EPN (Bio-D) Dieter on behalf of Harvey

• ---- 15-minute break ----

• Transport Management Matthew

• BAM/BPM Arno

• Lessons Learned Pedro

• Q&A All

15

use case tutorial - introduction (1/7)

Technology