G
Gertjan Hendriks
Guest
Hi akisoto, An interesting point of view. Thank you for sharing this. In my experience, a BRMS is *the* place where Business meets IT. And in the Corticon case, the EDC-part is the exact meetingpoint: IT guards the datamodel, and the business defends their business entities. Business and IT need to find a consensus, in order to get optimal integration. Indeed, from a pure Business Rules point, extending Rulesheets to a database, preparing data as decision input, or writing output data to a database with the use of a rulesheet, is not Business Rules Management. Business Rules Management is about making Business Decisions, not about what attributes should be mapped to what database-column. To make a difference in Business Rules and more I/O like functionality, I use colourcoding of RuleFlows: Business and IT have their own code, meaning they will not interfere in Rulesheets (or Flows) created by the other department. Does this mean that Business and IT work parallel? The contrary: They work together as they are able to read and understand (and even improve) each others work (BRM vs data management), leading to more synergy and shorter lead times in projects. Is that an advantage? To my opinion it is! -Gertjan
Continue reading...
Continue reading...