Task: Develop Business Rule Application Architecture
Refine the architecture to an appropriate level of detail to support development.
Disciplines: Architecture & Design
Extends: Refine the Architecture
Purpose
Develop the piece of the software architecture related to the execution of the rules, and their management.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory: Optional:
  • None
Outputs
Main Description

In a BRMS deployment there are at least the following components to intergrate in the core business application and in the IT architecture:

  • The Rule Engine as an executable class, calleable using proprietary API or JSR94 API. Rule Engine can be embedded component or deployed in a pool. Java Connector Architecture can be a solution to manage a pool of Rule Engines. It offers a lot of services provided by the JEE container, that an architect can leverage.
  • The Rule Set(s) as script files which needs to be managed and deployed dynamically or at system startup to the rule engine.
  • An IDE, like a Rule Studio, to develop the core rule set.
  • A Web based Rule management platform, to let business users, analysts be able to maintain the rules.
  • A Rule testing framework to support functional testing of the rule set and non-regression tests.
Steps
Design the decision service interface
Key Considerations

The architect should perform this task through collaboration with the whole team to promote consensus and a common understanding of the overall solution. The architect should be working to coordinate and guide the technical activities of the team, rather than seeking to do all the work alone. The architect should place emphasis on involving the developer(s) throughout this task.

More Information