1	Business Rules to the Rescue in the 21^st Century! Special 20-minute overview Bonnie O’Neil Westridge Consulting/Apex Solutions
2	Agenda How Business Rules have Evolved Summary of Tool Classes The Future? The Goal
3	5 Parts to BR Approach Analysis/Requirements Gathering Metadata Coding Paradigm AI/Engine Grammar/English Language
4	How BR have Evolved Started out as an Analysis Approach A Better Way to do Analysis Major Players Ron Ross Barbara von Halle Emphasis on Requirements Gathering Not code-oriented
5	Analysis Phase II Zachman Framework Debate Where are BRs? BRs as Metadata Powerful Business Knowledge Major Players David Hay Alan Kolber Keri Anderson-Healy Terry Moriarty
6	Code Gets Involved Write applications as BR components Just a Better Way to Program No concern with linking with natural language Problem seen as too complex Easier maintenance Major Players Paul Dorsey David Wendelken
7	AI Involvement Rule Engines Conflict resolution a hard problem AI can help
8	Language Issue Grammars introduced Work out of the Netherlands Bonnie O’Neil: basic grammar, 1997 Usoft Terry Halpin eFuturia:TMBR Goal: to hook English language to code BR maintained by business people
9	Summary of Tool Classes Capture and Classification tools (BR Repository) Example: BRS RuleTrack Engine-oriented Rules engine Some app help, mostly 3GL Provide conflict resolution Example: Brokat (formerly Blaze Software, Neuron Data)
10	Tools Classes, Cont’d Visual Development Environment Rules as business logic GUI development Example: Versata
11	Conclusion: The Future Information Systems should be maintained by business people Business rules should be located centrally, available ubiquitously Business rules should be expressed in English language but must also be executable Business rules should be able to be changed and instantly reflected in systems