A second key feature supported by every DMN tool is the decision table. In DMN, decision tables are one form of expression used to determine the value of a decision or BKM. Decision tables have been around for 40 years, but DMN defines specific formats and rules for their construction. In one common format, the columns of the table represent inputs and outputs, and the rows represent decision …
If DMN just wanted to be a requirements-gathering notation along the lines of BPMN 1.x, DRDs and decision tables would be enough. (And unfortunately, to many decision management vendors and consultants, those are enough!) But DMN has higher aspirations. Like BPMN 2.0, it seeks to unify modeling and execution in a single language, accessible to business people but powerful enough to handle …
Last time I mentioned that FEEL is just an expression language not a programming language. It does not have statements. It cannot create variables. But, of course, you need those to define executable decision logic! So where do they come from? What makes DMN business-friendly is that variables and their value expressions are created graphically, in diagrams and tables. We've already seen how each …
All of the conceptual elements of DMN - their names, attributes, relationships to each other, whether they are required or optional, and so forth - are formally defined in the specification by a metamodel, a set of UML class diagrams. Here, for example, is the metamodel for a Decision: Closely related to the metamodel is the XML Schema, or XSD, defining the standard XML interchange format for DMN …
While unifying decision modeling and execution is a laudable goal, OMG realizes not all DMN vendors and practitioners want to do that. So DMN defines three levels of conformance to the standard. A tool vendor can implement just a sliver of DMN and still proudly slap that "standards-based" label on their software. Conformance Level 1 (CL1) applies to tools that support DRDs and non-executable …
DMN 1.1 is the first implementable version of the standard. The spec is done, but won't be released to the public until mid-2016. A lot of work went into it, so people are surprised at all the things that are not in it: Business glossary. Howls of anguish went out online when it was revealed that DMN would not specify a Business glossary, a business-maintained data dictionary for decision models. …
I am happy to announce a brand new class, DMN Method and Style Basics, based on the Trisotech DMN Modeler, tailored for business users. The training includes 60-day use of the Trisotech Digital Enterprise Suite and post-class certification. Click here to register. Until October 31, we are offering it for the special price of $295, after which the price will revert to the standard price of $695. By …
If you're like most people trying to find out about DMN by reading the spec, you focus on the diagrams and examples. And you probably come away thinking, Yikes, what a mess! The thing that elicits this response from most people is the proliferation of business knowledge models (BKMs), those rectangles with clipped corners that seem to be stuffed in every nook and cranny of the DRD.
I've been heads-down for a while working on a new book and training: DMN Method and Style. The Decision Modeling and Notation standard now promises to transform the world of proprietary decision management software in the same way that BPMN upended the world of workflow, EAI, and business process analysis software a decade ago. Do we even use those terms any more?? DMN is a business-oriented …
bpmNEXT 2016 just concluded its fourth event this week in Santa Barbara, and it was even better than ever! One highlight for me was the rapid pace of progress in DMN implementation. Before this event I was beginning to despair that tool vendors would implement only the barest outlines of DMN, nothing that could fulfill the promise of a business-friendly, model-based, executable, tool-independent …