Creating and Using Business Rules
"Creating and Using Business Rules
Business rules (or business policies) define and control the structure, operation, and strategy of an organization. Business rules may be formally defined in procedure manuals, contracts, or agreements, or may exist as knowledge or expertise embodied in employees. Business rules are dynamic and subject to change over time, and can be found in all types of applications. Finance and insurance, e-business, transportation, telecommunications, Web-based services, and personalization are just a few of the many business domains that are governed by business rules. Each of these business domains shares the need to convey business strategies, policies, and regulations to information technology (IT) personnel for inclusion into software applications.
Traditional procedural and object-oriented programming languages, such as C, C++, and Microsoft® Visual Basic®, are oriented towards programmers. Even advanced object-oriented languages, such as Java and C#, are still primarily programmers' languages. The traditional software development cycle of design, develop, compile, and test requires substantial time and coordination, and does not enable nonprogrammers to participate in the maintenance of automated business policies. The Business Rules Framework addresses this problem by providing a development environment that allows rapid application creation without the lengthy cycle of traditional application programming. For example, business policies constructed by using this framework can be updated without recompiling and redeploying the associated orchestrations.
The Business Rules Framework is tightly integrated with Microsoft® BizTalk Server 2006, and developers can use the following features to build and manage business rules:
A high-performance rule engine that implements an inference mechanism to evaluate the business rules.
A rich set of application programming interfaces (APIs) for developing rule-based applications.
A graphical user interface, the Business Rule Composer, which developers, business analysts, and administrators can use in various ways to efficiently develop and apply rules and policies.
A seamless integration with BizTalk orchestrations, which enables you to invoke a business policy or a set of business rules from a BizTalk orchestration.
The Rule Engine Deployment Wizard, which enables you to rapidly import or export business rules or the vocabularies used by the rules, as well as to deploy or undeploy these rules.
The business rules (policy) you create by using the Business Rules Framework can be used in an orchestrated business process, as shown in the following figure.
Business Policy
This section provides conceptual information about how you can leverage the Business Rules Framework and use the tools that BizTalk Server 2006 provides to develop business rules.
In This Section
Creating Business Rules
Business Rules Framework Security
Programming with Business Rules Framework
Rule Engine Configuration and Tuning Parameters "
Mostrando postagens com marcador BRE. Mostrar todas as postagens
Mostrando postagens com marcador BRE. Mostrar todas as postagens
sábado, 5 de abril de 2008
Business Rules Engine
Business Rules Engine
"Business Rules Engine
The Business Rules Framework is a Microsoft .NET-compliant class library. It provides an efficient inference engine that can link highly readable, declarative, semantically rich rules to any business objects (.NET components), XML documents, or database tables. Application developers can build business rules by constructing rules from small building blocks of business logic (small rule sets) that operate on information (facts) contained in .NET objects, database tables, and XML documents. This design pattern promotes code reuse, design simplicity, and modularity of business logic. In addition, the rule engine does not impose on the architecture or design of business applications. In fact, you can add rule technology to a business application by directly invoking the rule engine, or you can have external logic that invokes your business objects without modifying them. In short, the technology enables developers to create and maintain applications with minimal effort.
In planning development of a rule-based application, you first need to determine how rules will fit into your business processes. Your application will create an instance of a policy and supply it with data, or facts, on which to operate. The policy object encapsulates the rule engine and provides a single point of entry through which to run it.
You also will need to plan for the development and testing of your rules design. You must consider how you are going to deploy and update your policies. You will likely want to track the progress of your rule engine's execution and monitor its current state.
Account for the following steps as you plan your rules development:
Plan how to incorporate your rules into your application.
Identify the business logic that you want to represent with rules in your application. The term "business logic" can refer to many things; an example of business logic is "Purchase orders for more than five hundred dollars must be approved by a manager."
Identify data sources for your rule elements. You can optionally define and publish vocabularies (domain-specific nomenclature that represents underlying bindings).
Define rules from vocabulary definitions or directly from data bindings, and from them compose a policy that represents your business logic.
Note
Vocabularies must be published before they can be applied in rules.
Test and debug the policy with sample facts. You can either use the Test Policy functionality in the Business Rule Composer or use Policy or PolicyTester classes to execute from an application, command-line program, or orchestration.
Publish the policy version to the rule store.
Deploy the policy version.
Instantiate and build the short-term fact list in the hosting application. Use the Call Rules shape in an orchestration to execute your business policy or programmatically instantiate a policy version in your hosting application.
Monitor and track rule execution as needed.
Note
The default tracking interceptor works with orchestrations. If your hosting application is not an orchestration, you must write your own tracking interceptor to do this.
In This Section
Rules
Policies
Vocabularies
Business Rules Framework Architecture
Facts
Rule Engine"
"Business Rules Engine
The Business Rules Framework is a Microsoft .NET-compliant class library. It provides an efficient inference engine that can link highly readable, declarative, semantically rich rules to any business objects (.NET components), XML documents, or database tables. Application developers can build business rules by constructing rules from small building blocks of business logic (small rule sets) that operate on information (facts) contained in .NET objects, database tables, and XML documents. This design pattern promotes code reuse, design simplicity, and modularity of business logic. In addition, the rule engine does not impose on the architecture or design of business applications. In fact, you can add rule technology to a business application by directly invoking the rule engine, or you can have external logic that invokes your business objects without modifying them. In short, the technology enables developers to create and maintain applications with minimal effort.
In planning development of a rule-based application, you first need to determine how rules will fit into your business processes. Your application will create an instance of a policy and supply it with data, or facts, on which to operate. The policy object encapsulates the rule engine and provides a single point of entry through which to run it.
You also will need to plan for the development and testing of your rules design. You must consider how you are going to deploy and update your policies. You will likely want to track the progress of your rule engine's execution and monitor its current state.
Account for the following steps as you plan your rules development:
Plan how to incorporate your rules into your application.
Identify the business logic that you want to represent with rules in your application. The term "business logic" can refer to many things; an example of business logic is "Purchase orders for more than five hundred dollars must be approved by a manager."
Identify data sources for your rule elements. You can optionally define and publish vocabularies (domain-specific nomenclature that represents underlying bindings).
Define rules from vocabulary definitions or directly from data bindings, and from them compose a policy that represents your business logic.
Note
Vocabularies must be published before they can be applied in rules.
Test and debug the policy with sample facts. You can either use the Test Policy functionality in the Business Rule Composer or use Policy or PolicyTester classes to execute from an application, command-line program, or orchestration.
Publish the policy version to the rule store.
Deploy the policy version.
Instantiate and build the short-term fact list in the hosting application. Use the Call Rules shape in an orchestration to execute your business policy or programmatically instantiate a policy version in your hosting application.
Monitor and track rule execution as needed.
Note
The default tracking interceptor works with orchestrations. If your hosting application is not an orchestration, you must write your own tracking interceptor to do this.
In This Section
Rules
Policies
Vocabularies
Business Rules Framework Architecture
Facts
Rule Engine"
domingo, 30 de março de 2008
Assinar:
Postagens (Atom)
