Showing posts with label conceptual model. Show all posts
Showing posts with label conceptual model. Show all posts

Saturday, November 16, 2013

On ER 2013


This week I have spent several days in Hong Kong attending the ER 2013 conference.  I have attended this conference several times before, but not recently, and came back due to the fact that I have renewed interest in conceptual modeling due to my work on event modeling.    It was interesting to observe what are the key topics today in conceptual modeling research.    The keynote speakers by  David Embley. Surajit Chauduri and Marie-Aude Aufaure have all dealt with conceptual modeling in big data, enterprise analytics and business intelligence, so this seems to be the key interesting topics. Other topics were the classic topics like: business process modeling, data semantics, and ontology based modeling.     Conceptual modeling has contributed as means of providing abstractions over computing and data, where modeling play a vital role in the current IT industry, moreover, we see standards emerging in various areas such as BPMN and recently DMN.   You can look at the conference program to get a feeling on the various presentation.   This was my 5th visit in Hong Kong over the last 9 years and this place has its own charm.   

Tuesday, August 16, 2011

Book review: Managing event information by Gupta and Jain



I am reading the book "Managing event information" by Gupta and Gain,  which is part of the series of short books by Morgan&Claypool synthesis lectures series.   The authors, professors from U.C. San Diego, and U.C. Irvine, have concentrated in the modeling of events, the illustration below was copied from the book to demonstrate the flavor.   The book starts with an introduction and running example about news agency, it also defines the setting of various types of events: spatio-temporal database events, sensor events, multi-media events (video, audio).    Chapter 2 deals with "Event Data Models" starting with temporal database as a tool for event modeling,  such that the temporal database represents the collection of states, while event is any transition in any state (value change), then it moves to discuss conceptual temporal models and discusses E* - a graph based event model using RDF and ontologies.  formalizing E* and showing some example of modeling using E*.  It discusses several modeling constructs such as disjointness (causal or temporal) of events; coverage; ordering' lifespan and spacespan of events, and constraints on graph relationships, such as follows, sub-class etc..  In chapter 3 the book discusses the implementation of the event data model; the illustration below is a UML diagram showing one of the supported patterns - events that participate within a situation, there are other patterns supported such as causality.  Later it discusses storage model of various types of events.  Chapter 4 is entitled "querying events" and discusses the possibility to query a collection of events. Example of queries are: spatiotemporal queries such as: "which meetings are scheduled in this hotel today after a certain talk", which looks like a regular query in spatiotemporal database, the queries can also support aggregates (looking for frequent meetings with a certain characteristics), and hierarchy, expanding to sub-events.   It can also query continuous events, graph relationships etc -- these queries seem to be the same as queries on spatiotemporal and graph databases, except he fact that the database represents events.  Chapter 5 brings a major application of the event model - the creation of a story based on the event model.  The storytelling is of multimedia type, a thread of research that follows Brooks' paper. 
Kevin M. Brooks: Do Story Agents Use Rocking Chairs? The Theory and Implementation of One Model for Computational Narrative. ACM Multimedia 1996: 317-328
The  book is summarized with some applications, conclusion and references.


The E* model is interesting in the sense that it shows various relationships among events,  and enable to get observation on the events and their relations to states.   Since there are no standards in this area, the terminology used in this book is sometimes inconsistent with other publications in this area, but it is generally clear.   The book proposes a holistic approach of event modeling, claiming that current event modeling systems are looking isolated aspects of events and cited the famous metaphor on the blind men that touch an elephant from different points, I have used this metaphor talking about misconceptions about event processing.
It still remains to be seen whether such models will penetrate the real-world systems.  
I'll give as a project topic in my event processing course more investigation of E*.

Sunday, February 28, 2010

Book review: The Decision Model


The last package from Amazon brought me the book entitled: "The Decision Model: A Business Logic Framework Linking Business and Technology" by Barbara von Halle and Larry Goldberg.

I have read a draft of the book before, at Barb's request, and wrote a review, from which one line was quoted on the back cover; I believe that the trend of modeling decisions and look at them in perspective of higher level abstractions will become more pervasive, and I view technologies like business rules, event processing and various analytics as building blocks in decision platforms that are going to be notable part of enterprise computing and managing much of the operational decisions. The book has three sections:

Section I puts the decision model in context, explains what is decision model, providing a background comparing decision models with data models, and positioning decision model in the SOA and BPM universe, it also explains the business value. This section is intended mostly for business users and managers that want to get an overview.

Section II explains the decision model in detail, discussing the structural, declarative and integrity principles, and comparing the decision model to the relational model, a motive repeating in previous books by Von Halle. There is even a chapter that is called "The decision model formally defined", but the formalization is in terms of explanations and tables, and not by formal writing, which I guess fits the target audience.

Section III is called "Commentaries" and is actually a collection of articles by the authors as well as by various people active in this space (John Zachman, James Taylor, Bruce Silver and more) discussing specific related issues such as: relations to enterprise decision management, standards, business decision maturity model.

Event based decisions and event processing are mentioned several times within the book, but are not thoroughly discussed. The focus is on facts and rules kind of terminology; a combined model that combines both rules and events is a natural extension, from the point of view of this decision model as well as from the point of view of event processing modeling. I have written before about decision agents, and since that time advanced on the thinking about such a decision agents framework. I'll revisit this issue in one of the following postings.

Bottom line -- the decision model book is a very good book to explain the book to various types of readers (the introduction maps the chapters of the book to the various types of users) and possible basis for both pragmatic foundations of rules technology, as well as a possible basis for a more formal basis for extended decision agents framework. More on this topic -- later.

Tuesday, May 20, 2008

On Event Processing Research Challenges




This picture has been taken a year ago on the stairs to the old church in Schloss Dagstuhl, in that meeting we had people both from academia and from industry discussing the state of the art and future of event processing. I have returned to the conclusion of the Dagstuhl Seminar done by my colleague Peter Niblett from IBM recently, after my return to the IBM Research Division from spending several years in the product organization, I was asked about challenges to the research community, as seen by the product development community (or the industry in general), since we had a session about it in Dagstuhl, in which people from the industry expressed their opinions about the same questions, I just had to take it as a basis of a presentation in this area.
In Dagstuhl four major areas has been put as challenge to the Research community (adding my own interpretation and comments)
1. Event Processing Algebra and Meta-Language: Like the database area in the pre-relational era, the first (and probably second) generations of event processing are "engineering based", various vendors are building implementations based on the use cases they see and their innovative ideas, bringing to the table, not only a variety of languages, but also a variety of (typically - implicit) conceptual models behind this implementation. One of the indication for a maturity of an area is the existence of an agreed upon conceptual model. The relational model has done it for databases, the browser concept has done it for the internet, now we need the same for event processing. David Luckham's concept of EPN/EPA is a possible starting point, but more work is needed on this - the challenge is still there; after constructing the "relational model" for event processing we also need the "SQL" (not necessarily SQL extension - but this is a possibility) for it - in term of meta-language that describes the model and can be mapped to various implementation.
2. Software Engineering issues: This is a challenge from a different perspective. Event processing and Event Driven Architectures impose different thinking about computing. We are programmed to think in a certain way in all programming language, and the event based programming is somewhat different paradigm. Even the basic principle of decoupled asynchronous processing is something that is not easy to digest f0r people. We need software engineering tools, methodologies and best practices.
3. Implementation optimization: If we have done the analog of SQL, another analog come to mind - database tuning and query optimization. There are many optimization issues especially when the event processing applications are distributed and may have various QOS requirements - parallel processing, acceleration of hardware, inter-operability, support in illites in general - all are challenges. The goal function in this optimization is not unique, while in some systems it is maximal throughput, in other it may be scalability in number of rules/queries/patterns (there are applications in which the throughput is measured in millions, and others in which the number of rules, the number of producers, or the number of consumers is measured in millions...), the goal function can be a combination of multiple criteria.
4. Variety of "small issues" - examples: uncertain events, out-of-order events, retention and vacuuming of events etc....
It will be interested to look at recent research project to see how much progress has been done on these, and if the list should be modified after a year that has passed. The major research event of the EP community this year is DEBS 2008 , the program has not been published yet, and it will be interesting to compare the accepted papers with this list (I'll do it when surveying the conference itself in July). We also intend to do in the EPTS event processing symposium in September a session with academic people about it - stay tuned for further notice. I am also thinking about a follow-up Dagstuhl Seminar, may be in 2009 or 2010 - to re-discuss event processing in perspective. More - later.