Some of these articles are large and graphics-intensive. They can take time to download. Please, be patient.
Provides an introduction to the universal and dynamic models, illustrating how these are models of what it takes to be in business.
Review of the Business Rules Solution's RuleTrack product
Discusses how business states are important types of business rules.
Provides an overview of the Business Rules Groups two papers.
Using System Architect 2001
The third in a series on developing criteria and approaches for evaluating vendor provided business rules products. This article provides a technique for developing scenarios to be used in testing business rule products.
Second in a series that provides criteria and approaches for evaluating vendor-provided business rule products. This article provides criteria for evaluating business rule management and enforcement products.
First in a 3 part series that provides criteria and approaches for evaluating vendor products that claim to support business rules. This article describes the various categories of business rule products and provides an overview of the business rule classification scheme developed by the Business Rule Group.
Using "Country" as an example, illustrates how the same business term can have different meanings that are legitimate within specific contexts.
Discusses why addresses, email addresses and telephone numbers are separate from the Business Parties that use them.
Discusses the various definitions of "Household" that can exist within the organization and illustrates how the Business Party Relationship pattern can be used to support household structures.
Illustrates how the Business Party Relationship pattern can be used to represent organization structures.
Illustrates how the Business Party Relationship pattern can be used to represent the interpersonal relationships between business parties.
Presents a pattern (generic model) for the relationships that can occur between business parties (People and Organizations).
Provides an introduction to the dynamic business model and its applicability for managing information about customer relationships.
Provides an introduction to the dynamic business model as it can be applied to managing the customer relationship information.
Provides an overview of the types of functions that need to be supported if the business rule approach is to be successful
Challenges business rule advocates to listen to their business associates to ensure that the business rule classification scheme includes everything that the business includes when they use the term "business rules".
Continues to describe how scenarios can be used to capture and describe business rules.
Provides a scenario approach to process analysis as a methodology for capturing and documenting business rules
Describes how OO constructs such as the concept catalog and object class model ancan be effectively incorporated into the business rule approach
Review of The Fifth Discipline, Data Model Patterns and Data Reverse Engineering
Discusses many aspects of business rules, such as how the corporate values factor into the development of business rules. Also provides an architecture for behavior that is a function of the interaction between object states, business rules and events.
Describes situations where the only way you're going to find out what business rules are being enforced by your organization is by reverse engineering the code.
Examines four reverse engineering products against the evaluation criteria published in the 6/97 issue of Database Programming and Design.
Introduction discusses how business rules fit into the 3-layer architecture of Persistent data, Business Processes and Workflow. Persistent data and business process specifications are often common across industry or business. What is unique to an organization are its business rules and workflow. Using the Usoft suite of products to illustrate these concepts.
Using the knowledge management hierarchy of Data -> Information -> Knowledge -> Wisdom to illustrate that what an organization considers to be metadata changes depending on where the organization resides in the hierarchy.
Provides criteria which can be used to evaluate products that scan/parse source code to extract business rules. While these products are currently thought of as Year 2000 tools, they have a bright future in support of data warehouse mapping and application conversion efforts.
Provides an introduction to data reverse engineering and data mapping templates. Highlights the fact that data mapping is not just a data warehouse activity, but is required for any project that includes data interchange between applications.
Presents an overview of thr types of constraints an organization may encounter and how they effect business rule development
Uses a backyard landscaping project as an analogy to explore the feelings business users can encounter while trying to communicate their vision fof the information systems they want and the realities of what actually can be built.
Discusses some of the challenges we face in designing databases to support dynamic business models
Suggests that scenarios can be an effective approach, not only for identifying business rules, but in defining test data later in the development life cycle
Shows how common data modeling practices of generalization and aggregation, if not properly used, can obscure the business rules expressed by a business information model.
Warns against the urge to normalize business models too soon
Provides a business rule classification scheme to use in translating business ramblings into atomic business rule statements.
Proves evidence that the Business Rules Approach will be the next paradigm shift in business information analysis
Part of the Change Management Series. Uses a business rule classification scheme to determine whether an impact analysis is complete. Also discusses the need for multi-release impact analysis.
As part of the change management series, discusses the important role attributes play in a flexible application
As part of the change management series, describes the areas of the business from which change is most likely to be initiated. Also discusses how proper allocation of requirements across the three-level architecture can enable flexible applications.
Illustrates how the business party relationship business pattern can be used to represent most of the inter-relationships between business parties.
Last updated on: 12/17/01
Inastrol copyright 1995 - 2001 All rights reserved