Fundamental to the KROME schema is the division of the universe of possible combinations of policies and procedures in a computer-enabled business into four universal archetypes. The “Modular Model” shows the four archetypes in relation to each other. It is intended to address the design of BPM/BRE solutions by creating discrete, recognizable concerns each with its own appropriate mechanism for implementation and inclusion.
The role of the module is to encapsulate the complexity and detail in a way that maximizes reuse through simplified use. The separation of concerns increases the likelihood of reuse by encouraging the creation of larger recognizable units of behavior with well-defined boundaries. This separation also enables a division along lines of intimacy with either business or IT expertise.
The quadrants of the Modular Model lay out four component archetypes.
While “rule reuse” is an important element of the application design, there is little practicality in expecting reuse at the PRPC rule level of granularity. It simply takes less time to replicate a single rule, when and where you need it, than it does to locate a potentially “reusable” one. Specialized elements, typically single rules or tightly coupled data functions, are not worth the investment to build as reusable.
Reusability is best employed at the level of providing common business functions, and at the business policy decision level. By subdividing applications into key modules we simplify the answer to what can and should be reusable and the particular knowledge required to create and/or use these modules. The more common a function or a business policy is, the higher the opportunity for reuse.
The components of the Modular Model, their definitions, and the guiding principles of their design and development are explained on the following four pages:
