DMN and the TCK at #bpmNEXT
- May 18, 2017
- 0 Comments
Over the last year, Keith Swenson has been pushing the process and decision management community to provide a reference implementation of DMN, or a reference test-bed for it.
This subset of the community is more focused on DMN from an execution point of view than from a definition, collaboration, and trace-ability view (which was my initial impression of the “purpose” of DMN as presented by folks like none other than James Taylor).
At this year’s bpmNEXT, Keith presented the results – good work, really. He’s also blogged about it here. The biggest question asked and answered is, why have a reference testing kit anyway?
“The problem with a specification that does not have running code is that the English language text is subject to interpretation. Until implemented, the precise meaning of phrases of the spec can not be known. I say: the code is 10 times more detailed than the spec can ever be; until you have the code you can not be sure of the intent of the spec. Once code is written and running, you can compare implementations and sort out the differences.”
The whole kit and test cases and runner are available in GitHub, so there’s really no friction to get started and participate. What I appreciate about Keith’s approach is that he put forward a proposal, and then adapted to what the community was willing to do – and pointed it in a useful direction. He didn’t get all of what he wanted but he managed to instigate quite a bit of progress.
Watch the video from bpmNEXT here: