Business Rules and Information Systems

Information systems often fail because their requirements are poorly defined. This book shows IT professionals how to specify more precisely and more effectively what their systems need to do. The key lies in the discovery and application of what are called business rules. A business rule is a compact and simple statement that represents some important aspect of a business. By capturing the rules for your business--the logic that governs its operation--you will gain the ability to create systems fully aligned with your business needs.

In this book, Tony Morgan provides a thorough introduction to business rules, as well as a practical framework for integrating them into information systems. He shows you how to identify and express business rules, offers practical strategies for their use, and explains the key elements of logic that underpin their application.

Topics covered include:

Understanding the role of business rules and models in information systems development
Using models to structure and manage business activities, including e-commerce
Defining and discovering business rules
Controlling business rule quality
Fitting business rules into varied technical architectures
Implementing business rules using available technology
Whether you are an analyst, designer, developer, or technical manager, the in-depth information and practical perspective in this valuable resource will guide you in your efforts to build rule-centered information systems that fully support the goals of your organization.

0201743914B03042002

Autorentext
Tony Morgan is a Senior Solution Specialist at Unisys Corporation. He has a broad range of IT experience gained at companies such as EDS and Unisys, including more than fifteen years of rule-based system development. His main interest is in IT systems that deliver real business value. Tony holds a Ph.D. in Computer Science from the University of Cambridge and is a Visiting Research Fellow at Brunel University in London, England.

0201743914AB03112002

Zusammenfassung
Shows IT professionals how to specify what their systems need to do. This book provides an introduction to business rules, as well as a framework for integrating them into information systems. It shows you how to identify and express business rules, offers strategies for their use, explains the elements of logic that underpin their application.

Inhalt


List of Figures.


Preface.


Acknowledgments.
I. A NEW APPROACH TO BUSINESS SYSTEMS. 1. The Problem.
What This Book is about.Why Should You Care?What is a Business Rule?The Way We Build Software.The Vision.How Could It Be?Some Implications.Is This Really Practical?Moving Forward.Where We Stand.2. Frameworks, Architectures, and Models.
Needful Abstractions.Frameworks.Architectures.Models.Case Study: A Sample Business Architecture.Overview.Business Objects.Business Process Elements.Narratives.Business Events.Actors and Roles.Business Intentions.Organizational Units.Business Rules.What Does a Complete Model Look Like?Model Summary.II. CAPTURING BUSINESS RULES. 3. Defining Business Rules.
Rule Statements.Business Rule Characteristics.Business Aspects.What Should a Rule Say?Levels of Expression.OCL.Forming Rule Statements.Pattern Conventions.Rule Patterns.Rule Sets.Static Models Versus Rule Statements.References to Facts.Terms and Rules.Individual Items.References to Multiple Items.Business Parameters.Tips on Rule Construction.Using Facts.Simple Constraints.Quantifications and Qualifications.States and Events.Actors.Dangerous Verbs.Computation.Structure and Consistency.Case Study: Microsoft Outlook.Outlook Rule Structure.Conditions, Exceptions, and Actions.Internals.Logic.Outlook Rule Features.Rule Description Summary.4. Discovering Business Rules.
That Which We Call a Rule.Where Rules Come Rrom.Information Sources.Common Indicators.Finding Rules.Static Analysis.Interactive Sessions.Automated Rule Discovery.Case Study: Loan Approval.The Early Stages.Fishbones.Input Data.Loan-assessment Rules.Rule-discovery Summary.5. Controlling Rule Quality.
Developing Quality Rules.Reviewing Rules.What to Look for in Reviewing Rules.Roles.Rule Context.Tone.Review Outcomes.Review Records and Approvals.Walkthroughs.Planning and Preparation.Conducting a Walkthrough.Inspections.Planning and Preparation.Managing an Inspection.Testing.The Use of Testing.Test Implementation.The Process of Testing.Case Study: Testing the VBB Loan-application Rules.Setting up the ABC Testing.Assessing the Rules.Choosing Test Cases.Implementing the Rule Tests.VBB Test Results.Metrics.Guidelines.Minimum Metrics.Quality Summary.III. IMPLEMENTING BUSINESS RULES. 6. The Technology Environment.
More about Architecture.A Typical Reference Architecture.Business Flexibility.Shared Resources.Component Architecture.Interfaces.Component Interaction.Transactions.Server Pages and Ccripting.State Management.Implications for Business Rules.Where Rules Live.Client.Channel Tier.Middle Tier(s).Data Services Tier.Legacy Systems.Summarizing the Technology Environment.7. Realizing Business Rules.
Taking Stock.Distributing Rules.Realizing Rules.Program Statements.Scripts.Rule Components.Rules Engines.Database Mechanisms.Workflow Systems.Look-up Tables.Flags and Magic Codes.System Rules.Implementation Summary.8. Managing Business Rules and Models.
Life-cycle Costs.Managing Evolution.Coping with Changes.Automating Housekeeping.Deploying Rules.Testing a New System.Rollout.Supporting a Live System.Tools to Support Rule Management.Rule Repository.Why a Repository?Repositories and Rules Engines.An Example Repository Design.Rule Management Summary.IV. THE ROLE OF B…