James Taylor wrote: “Frankly I have seen so many failed code generators at this point that I no longer believe that a business-friendly model can be enriched to the point of execution without either making gross assumptions about the deployment OR making the model too different from the original business intent. I prefer to keep the model clean and focused on the business problem and then link to the implementation.” What is your experience with code generators for decision model execution?
- Follow on WordPress.com
Sponsors
-
Recent Posts
- Miss Manners is back – Challenge June-2023
- An active repository of all human knowledge?
- OptaPlanner continues as Timefold
- Red Hat and IBM: Business Automation Update
- Consistency Checks of Large Language Models
- wAIting for Godot
- How do we define intelligence?
- Don Knuth takes ChatGPT for a ride
- MiniCP: A lightweight Java Constraint Programming Solver
- AI Decisioning Platforms
- Human-Machine Conversations: Dynamic Planning and Composition
- AI: Yann LeCun vs Yuval Noah Harari
- Decisions as Code
- Programmers of the future will be artists
Recent Comments
Categories
- Algortithms
- API
- Architecture
- Art
- Artificial Intelligence
- Authentication and Access Control
- AWS
- Blockchain
- Books
- BPM
- Business Analytics
- Business Processes
- Business Rules
- Case Management
- Case Studies
- CEP
- Challenges
- ChatGPT
- Cloud Platforms
- Constraint Programming
- Containers
- Coronavirus
- Customer Experience
- Customer service
- Data Science
- Database
- Decision Intelligence
- Decision Making
- Decision Modeling
- Decision Models
- Decision Monitoring
- Decision Optimization
- DecisionCAMP
- DevOps
- Digital Decisioning
- Digital Transformation
- Discoveries
- DMN
- Education
- Ethics
- Event-driven
- Events
- Excel
- Explanations
- Fraud Prevention
- Games
- GPT-4
- HR
- Human Intelligence
- Human-Machine Interaction
- Humor
- Innovation
- Insurance Industry
- Java
- Knowledge Representation
- Languages
- LLM
- Logic and AI
- Machine Learning
- Manufacturing
- Microservices
- Misc
- MISMO
- Most Influential
- Natural Language Processing
- Open Source
- Optimization
- PMML
- Process Mining
- Products
- Prolog
- QA
- Reactive Rules
- Reasoning
- Retail
- RPA
- Rule Engines and BRMS
- Rule Violations
- RuleML
- Scheduling and Resource Allocation
- Security
- Semantic Web
- Serverless
- Software Development
- Sponsors
- Spreadsheets
- Standards
- State Machines
- Testing
- Trends
- Uncategorized
- Vendors
Archives
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- June 2014
- May 2014
Meta
+1 Even worse: the errors and explanations are reported in terms of the target system (generated code) and not in original business terms – the reason CASE systems failed long time ago and even the very term is forgotten today.
Code Generators only translate decision models in a language which cannot be read nor understood anymore by most of the business stakeholders, i.e. a blackbox. And reverting blackboxes back into something manageable by the business is exactly one of the main purposes of decision modeling. So, let’s not make the same mistake again.
Well – I am not sure if it is that black and white.
Jacob – correct me if I am wrong but OpenRules provides a hook from Decision Models via Decision Tables to automation of decision logic. Is that not code generation out of a model?
And many others are out there do exactly the same using DMN as a starting point to generate automated decisions.
I am not sure if that is a good idea to do so but I think – James – it is to late!
Humans are lazy and they like automation of dull repeatable tasks. Why would we not generate repeatable decisions and expose them as a consumable services?
Hi Olaf,
I need to correct you – OpenRules does NOT generate code “out of a model”. OpenRules directly executes all decision tables and other decision modeling constructs presented in Excel by instantiating the predefined Java classes in run-time. Our customers may even define snippets of Java inside Excel cells (which look very similar to DMN FEEL) and they will be executed when they run an instance of OpenRulesEngine without any code generation. OpenRules-based decision models are always executable by design. As Bruce Silver pointed in his recent book, “whatever execution algorithm is employed, the DRD (and I’d add, the entire the decision model) should be executable”.
When OpenRules is used together with DecisionsFirst Modeler, then James’ high-level decision model is simply linked to executable implementations using decision tables represented in OpenRules or other vendor’s format. Again no code generation occurs here.
Actually, the real problem is not with code generation, but rather with which decision model representation will be maintained: the original one in DMN or the generated one in a target format. I suspect that in many code generation cases, “the target representation” is the one that is actually being supported by users using the target BRMS. And this is the problem! However, if the code is generated on the fly every time when you run the decision model and there is no performance overhead, then it is not a problem.
As an example, I may point to success of the JSR-331 standard (http://jsr331.org). The same decision model (in this case a constraint satisfaction problem) can be executed by different constraint or linear solvers without changing a single character in the original model. For example, we may generate the proper code for a linear model in the MPS format on the fly (!), then execute this code with one of 7 linear solvers, and then present the results back in the original terms. Nobody ever looks at the generated code and everything works just fine.
Jacob