＋设为首页 ＋添加到收藏夹
over the last two decades rules have become an increasingly important part of the information technology landscape. in fact, deductive rules have been applied to databases since the inception of sql and form the basis of policy management and decision making at most corporations. however, the rules are changing. a newer reactive rules solution based on events, conditions, and action (eca) has come to the foreground.
in addition, the rise of the java runtime and development environment from a niche solution to prime time is also changing the rules of the information technology landscape. with java as the core technology for embedded and enterprise applications, rules are an ideal means for businesses to harness the power of the language for a competitive advantage.
this article examines both types of rules, deductive and reactive, shows when and how to apply them, and explains how rules can work together to provide a more effective semantic integration solution. it also examines the different uses of rules and applies rule technology to j2me for desktop applications and j2ee for enterprise applications.
this article looks at the use of rules for managing personal workflow, business transactions, and web content in j2me, j2ee, and jsp environments, respectively. it also covers the application of rules to b2b, customer relationship management (crm), and supply chain management (scm) applications.
an overview of rules
according to the authoritative business report, guide business rule project (1995), a business rule is "a statement that defines or constrains some aspect of the business. it is intended to assert business structure or to control or influence the behavior of the business."as rules have become an increasingly important aspect of the management of the it landscape, this article examines the need for rules using a financial services example and looking at the different rules and how they can be applied to business-critical events in financial services. in the past, application builders have embedded the fundamental business-processing rules directly into application code. this led to an explosion of new applications when applications became too unwieldy and inflexible to meet business needs. it also led to an increase in maintenance as applications were modified to incorporate the necessary changes. this is more apparent in financial services where regulatory requirements and the personalization necessary to keep or gain market share are critical business factors.
many systems have been written and rewritten trying to keep up with the changes. business requirements are changing faster than applications can be created and/or modified. rules offer a way of encapsulating the business semantics and promoting them to the surface in the same way that databases enabled the separation of data from an application. the first attempts at doing this date back to e.f. codd, the founder of relational databases.
capturing the semantics, or gaining an understanding of what is really going on in terms business people can understand, is on... 下一页