busness rules

Published on December 2016 | Categories: Documents | Downloads: 47 | Comments: 0 | Views: 527
of 1
Download PDF   Embed   Report

Business rules are gathered in these situations: When dictated by law During the business analysis As an ephemeral aid to engineers.This lack of consistent approach is mostly due to the cost and effort required to maintain the list of rules. The cost of maintaining the list increases in situations where the rules are rapidly changing, such as in a start-up company. Another common obstacle to the adoption of formal business rule management is resistance from employees who understand that their knowledge of business rules is key to their employment.Because technologies require and enforce consistency in their use, technology is often used to address these issues. As a result, there has been substantial investment in tools to perform business rules management and rules execution. Software tools such as Wolf Frameworks are an example of this trend.[2]Note that many tools make a distinction between Business Rules Engines and Business Rules Management, and require a translation between the two. Commercially available tools now also offer the possibility to combine both management and execution of rules. Combined with an easy to use interface and a proper notation which can be maintained by business users, customers of these tools hope to reduce or eliminate the obstacles mentioned above.While newer software tools are able to combine business rule management and execution, it is important to realize that these two ideas are distinct, and each provides value that is different from the other. Software packages automate business rules using business logic. The term business rule is sometimes used interchangeably with business logic; however the latter connotes an engineering practice and the former an intrinsic business practice. There is value in outlining an organization's business rules regardless of whether this information is used to automate its operations.One of the pitfalls in trying to fill the gap between rules management and execution is trying to give business rules the syntax of logic, and merely describing logical constructs in a natural language. Translation for engines is easier, but business users will no longer be able to write down the rules

Comments

Content

Business rules are gathered in these situations: When dictated by law During the business analysis As an ephemeral aid to engineers. This lack of consistent approach is mostly due to the cost and effort required t o maintain the list of rules. The cost of maintaining the list increases in situ ations where the rules are rapidly changing, such as in a start-up company. Anot her common obstacle to the adoption of formal business rule management is resist ance from employees who understand that their knowledge of business rules is key to their employment. Because technologies require and enforce consistency in their use, technology is often used to address these issues. As a result, there has been substantial inv estment in tools to perform business rules management and rules execution. Softw are tools such as Wolf Frameworks are an example of this trend.[2] Note that many tools make a distinction between Business Rules Engines and Busin ess Rules Management, and require a translation between the two. Commercially av ailable tools now also offer the possibility to combine both management and exec ution of rules. Combined with an easy to use interface and a proper notation whi ch can be maintained by business users, customers of these tools hope to reduce or eliminate the obstacles mentioned above. While newer software tools are able to combine business rule management and exec ution, it is important to realize that these two ideas are distinct, and each pr ovides value that is different from the other. Software packages automate busine ss rules using business logic. The term business rule is sometimes used intercha ngeably with business logic; however the latter connotes an engineering practice and the former an intrinsic business practice. There is value in outlining an o rganization's business rules regardless of whether this information is used to a utomate its operations. One of the pitfalls in trying to fill the gap between rules management and execu tion is trying to give business rules the syntax of logic, and merely describing logical constructs in a natural language. Translation for engines is easier, bu t business users will no longer be able to write down the rules

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close