Let’s start by recapping decisions services. Decision services are services, generally stateless ones, that answer business questions for other services. Decision Services typically have no side effects so they can be called whenever they are needed without the caller worrying that something will change in the system. This means that database updates, event generation or other actions taken as a result of the decision are taken by the caller not by the Decision Service. This is not 100% true but works as a general rule. To work, Decision Services need to contain all the logic and algorithms necessary to make the decision correctly.
Continuing some posts on next generation warranty systems in the build up to speaking at the Warranty Chain management conference I thought I would contrast how current generation warranty systems handle critical decisions with how next generation systems do so.
- leave anything related to transport, communication to other layers- use this revised CEP to express and execute event-relevant logic, the purpose of which is to translate the ambient events into relevant business events- have these business events trigger business processes (however lightweight you want to make them)- have these business processes invoke decision services implemented through decision management to decide what they should be doing at every step- have the business processes invoke action services to execute the actions decided by the decision services- all the while generating business events or ambient events- etc.
- First, event management is primarily about the identification and generation of business events from the ambient events. Similar to what Carole-Ann and I had written in previous posts.- Second, IBM wants to introduce high level EPLs to express the logic for that processing that are business-centric, something very similar to what Business Rules Languages and approaches are in the business rules management area.
Substitute a standard web services interface for a speaking tube, a business rules management system for his encyclopedic knowledge of policies and regulations, data mining or predictive analytics for his customer knowledge and adaptive control for his experimentation and you have Decision Management. The Answerer but on an industrial scale.
business processes and business rules capturing the operational logic and decisioning logic respectively.
To study this analysis, we first need to understand theory which is the basis of their analysis i.e. BWW. Representational analysis is basically comparing constructs of representation theory with the constructs of the modeling grammar. The two evaluation criteria used are ontological completeness which determines the extent of lack of constructs in modeling grammar and ontological clarity. Now BWW is the representational theory to represent real world and has been earlier used to benchmark many languages. SRML and SBVR are compared to BWW to benchmark their representational power.
A business analyst should get the right rules and get them right, to answer compliance questions, to avoid unedning re-work, and to retain your business ‘smarts’ in a single-source. RuleArts develops the new work environment that proactively addresses the costs of business-level miscommunications, stovepipe vocabularies, and misinterpretation of policy.
RuleXpress can help you today with business-oriented support for measuring and improving quality in: capturing, assessing and changing business rules; retaining core business-worker knowledge; and ensuring compliance with regulation.
RuleXpress is a repository-based tool that can be used offline or in a multi-user environment. Models are stored in a central repository and can be checked out to a local copy and then merged back. Within the tool the key organizing principle is that of a community - a group of people who share the same understanding about their vocabulary and rules. Within this you can have projects but the focus of the tool is on the activity of vocabulary/rule management as an ongoing task. The key activities are to manage vocabulary and rules or, more specifically terms, fact model, rules, decision tables and rule groups.
Rule-processing is just a style of computation. Of course it is used in BRMS, but it is also used in CEP. CEP systems typically employ rules-based processing to infer higher-order events by matching patterns across many event streams within the event ‘cloud’. BRMS’s use rule processing to match patterns within data tuples representing business-orientated data. CEP systems may support the use of advanced analytics to manage predictive analysis, reasoning under uncertainty and other requirements in relation to the event cloud. Some of the better BRMS’s offer similar analytics in regard to processing business data.
The MS Rules Framework was a spirited attempt by MS to create a wide-ranging environment that could integrate rules held in different forms in different repositories, mange the deployment of rule sets out across an enterprise environment and even target a range of different rules engines.
What is a business rule? What is the business rule approach?
In this Second Edition of his popular handbook, first published in 1998, Mr. Ross brings you up-to-date on these and related questions.
Compliance. Requirements. Adaptability. Knowledge.
Find out about practical solutions for these and other urgent business challenges. In readable,get-to-the-point style, this book gives you a fast-paced, up-to-the-minute inspection tour of the breakthrough ideas and innovations that have the industry abuzz.
Semantics in Business Systems begins with a description of what semantics are and how they affect business systems. It examines four main aspects of the application of semantics to systems, specifically: How do we infer meaning from unstructured information, how do application systems make meaning as they operate, how do practitioners uncover meaning in business settings, and how do we understand and communicate what we have deduced? This book illustrates how this applies to the future of application system development, especially how it informs and affects Web services and business rule- based approaches, and how semantics will play out with XML and the semantic Web. The book also contains a quick reference guide to related terms and technologies. It is part of Morgan Kaufmann's series of Savvy Manager's Guides.
M. zur Muehlen, M. Indulska, and K. Kittel. 19th Australasian Conference on Information Systems (ACIS 2008), Christchurch, New Zealand, Australasian Computer Society, (2008)
J. Schiefer, S. Rozsnyai, C. Rauscher, and G. Saurer. DEBS '07: Proceedings of the 2007 inaugural international conference on Distributed event-based systems, page 198--205. New York, NY, USA, ACM, (2007)
M. zur Muehlen, M. Indulska, and G. Kamp. EDOCW '07: Proceedings of the 2007 Eleventh International IEEE EDOC Conference Workshop, page 189--196. Washington, DC, USA, IEEE Computer Society, (2007)