Business rules management system
A business rule management system ( GRMS ) or English Business Rule Management System ( BRMS ) enables the development and deployment of an on business rules (business rule) based computer program, services or a specialized application or a business process.
Goal setting
With a BRMS bring business users their competence and responsibility in their businesses with increased responsiveness to the game by using business rules to define their business logic quickly and accurately for the completion of a task in the Group and in greater independence from the computer science department ( IT ) your company can act. The syntax used can usually be defined in multiple languages, colloquial, technical or legally compliant.
IT managers are equipped with a BRMS with sophisticated development tools for automated applications and the creation of uniform IT organizational processes. In interaction with process management systems ( business process management ), processes are designed, managed and changed more easily. In a service-oriented architecture (SOA), business rules can be provided as a service or services can be called up themselves. Control information and organizational knowledge can be made usable within a BRMS.
Specialist users and developers should be able to carry out analyzes of what-if scenarios as well as simple comparisons of calculations with varying business rules or data sets.
The centralization of the logic in a business rule repository simplifies the company-wide administration of technical applications and makes business processes transparent and easier to audit. The direct, centralized administration of rules makes analyzes of business transactions easier to understand.
A BRMS should be based on IT standards such as Java or .NET , offer open data interfaces such as XML , be easy to integrate into IT architecture models such as service-oriented architecture (SOA) and also be able to use existing interfaces from legacy systems.
The Object Management Group (OMG) and the World Wide Web Consortium (W3C) strive to create standards for the formulation and exchange of (business) rules. The first standard in this area is the OMG specification Semantics of Business Vocabulary and Business Rules (SBVR) . The W3C was working on a Rule Interchange Format (RIF) planned for 2007 , while the EU research project REWERSE I1 Rule Modeling and Markup developed an R2ML rule exchange format and offered it on its website along with demo translation programs.
Why Business Rule Management?
The dynamics of the markets require ever shorter cycles in the procurement, production, marketing and billing of products and services. However, there are still high demands on service quality and the traceability of decisions. This requires rapid changes in the computer program, the service, the technical application or the business process.
There are business rules in all of these programs, applications, services or business processes - in the company manual, in legal texts, implementation provisions, detailed specifications of the IT departments, work instructions, tax tables, tariffs, sales guidelines and of course in the minds of the employees.
There are rules for procurement , marketing, sales , marketing , application processes, credit decisions , data validation, balance sheet analysis , billing, working hours , invoice verification and customer relationships.
Externally managed business rules are suitable for automating decisions within a process. Business process automation is done in two ways:
- When it comes to simple decisions that are subject to frequent changes and need to be applied to a high volume of transactions.
- In complex decision-making contexts that are less likely to be changed by the specialist side.
The rules for this are managed, maintained and revision-proof saved in a repository by specialist users .
Centrally managed business rules are useful when a company is looking for flexibility. An essential paradigm in business rule management is the externalization and central administration of business rules from applications and business processes. This allows rules to be flexibly changed, simulated, checked and made available at runtime.
For this purpose, a BRMS provides a simulation environment in order to run through data-related and / or logic-related scenarios. Rules can be changed as part of a quality assurance process because they can be managed centrally (in a business rule repository ); However, they should be auditable up to and including audit security. This approach enables consistency with constantly changing requirements during operation.
Business Rule Management is suitable to guarantee or increase the influence of the specialist users on the business application, the service or the business process. By using such a system, the user from the specialist area can flexibly create, change, manage, logically check, quality-assure and execute their business rules in a familiar technical language and - if desired also daily updated - without the need for additional IT Expenses (programming) for software adaptations are necessary. The IT department, however, has to put such a process into operation just like any other software project. However, the department can change business transactions during operation.
See also
literature
- Barbara von Halle: Business Rules Applied Building Better Systems Using the Business Rules Approach . John Wiley & Sons 2001, ISBN 0-471-41293-7
- Markus Schacher, Patrick Grässle: Agile companies through business rules - the business rules approach . Springer Verlag 2006, ISBN 3-540-25676-8
- Ronald G. Ross: Principles of the Business Rule Approach . Addison-Wesley 2003, ISBN 0-201-78893-4
Individual evidence
- ^ Semantics of Business Vocabulary and Business RulesTM. OMG, May 5, 2017, accessed July 31, 2019 .
- ↑ Rule Interchange Format (RIF)
- ↑ REWERSE I1 Rule Modeling and Markup ( Memento of the original from January 6, 2007 in the Internet Archive ) Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.
