Why Systems Work

Why systems work, change, and last Shared values and principles Clear and simple rules Business IT alignment A framework for designing and building any system E t Enterprise architecture i hit t Knowledge engineering 2 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Shared values and principles that state what we should and should not do

Clear and simple rules that state what you can and cannot do, must and must not do

A general framework for designing rules WHO (people/organization) RULE condition/decision permission/constraint WHY (goal/motivation) 5 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Prevent “World’s Dumbest Bank” transfer with banks that are declaring bankruptcy WHO (people/org) WHY (goal/motivation) Loss Prevention i.e. $426 million transfer to Lehman Brothers the day it declared insolvency 6 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Prevent United Airlines $25 fare US to Paris Unless authorized by senior mgmt WHO (people/org) WHY (goal/motivation) Prevent “fantasy fares” glitch i.e. $25 fares US to Paris 7 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Prevent parents boarding flight, forgetting children The check-in agent WHO (people/org) WHY (goal/motivation) Ensure no child is left behind i.e. forget toddler at the airport 8 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Business IT Alignment Strategy Rules • Mission • Values • Principles • Vision • Strategy Business Rules • Policy • Rules • Rulebase • Rulesets • Rules To see a Flash video of the “Rules EA Framework RuleMap”, visit www.RuleMap.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 9

Enterprise Architecture Strategy Rules • Mission • Values • Principles • Vision • St t Strategy Business Rules • Policy • Rules • Rulebase • Rulesets • Rules To see a Flash video of the “Rules EA Framework RuleMap”, visit www.RuleMap.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 10

Rules and knowledge are the bridge between Business and IT Business Technology Dollars Rules Data Knowledge CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 16

Architecture is how to design systems Engineering is how to build systems Business Technology Dollars Rules Data Knowledge CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 17

TM ENTERPRISE ARCHITECTUREA FrameworkTM Enterprise Architecture – - A FRAMEWORK DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 18

TM ENTERPRISE ARCHITECTUREA Framework TM Enterprise Architecture – - A FRAMEWORK Complete “Business Model” Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 19

TM ENTERPRISE ARCHITECTUREA Framework TM Enterprise Architecture – - A FRAMEWORK Complete “System Model” Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 20

TM ENTERPRISE ARCHITECTUREA Framework TM Enterprise Architecture – - A FRAMEWORK Complete “Technology Model” Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 21

TM ENTERPRISE ARCHITECTURE - A FRAMEWORK Object Oriented Modeling (UML; Use Cases) DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 22

TM ENTERPRISE ARCHITECTURE - A FRAMEWORK Structured Methods Modeling DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 23

TM ENTERPRISE ARCHITECTUREA Framework TM Enterprise Architecture – - A FRAMEWORK Complete “Data Model” Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 24

TM ENTERPRISE ARCHITECTUREA Framework Enterprise Architecture – - A FRAMEWORK Complete “Business Process Model” Architecture TM DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 25

TM ENTERPRISE ARCHITECTURE - A FRAMEWORK Complete “Business Rule Model” Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 26

Traditional Procedural Language DATA: X is TRUE Traditional Procedural language is R1: IF a is true THEN b is true sequential, forward only Loop #1 Ran 10,000 rules Suppose your rules are out of order? 1 rule fired R10: IF y is true THEN z is true Problems arise if sequence is incorrect (R100) What if you have to add a new rule? Loop #2 Developer has to figure out what order , Ran 10,000 rules R100: IF x is true THEN 00 i p to put it in 2 rules fired y is true Adding a new rule could break existing (R10, R1000) rules CONCLUSION: Once you get an answer, the rest of Approve R1000: IF z is true THEN “APPROVE” the rules fire anyway Results Ran 20,000 rules Only 3 rules fired R10,000: IF d is true THEN “DENY” You have to loop a few times to get around sequence problem 28 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Declarative (Rule‐based) Language DATA: X is TRUE Search for rules that match the data Rules are in no particular order R50: IF x is false THEN “Deny” Cycle #1 R100: IF x is true THEN y is True Ran 2 rules Execute those rules R50 does not fire Fired 1 rule R100 fires because x is true (R100) R10: IF y is true THEN z is true DATA: X is TRUE Cycle #2 Y is TRUE Ran 1 rule R10,000: IF d is true Fired 1 rule R1: IF a is THEN “DENY” Search for rules that match the data (R10) true THEN R10: IF y is true THEN z is True b is true Execute those rules R10 fires because y is true Cycle #3 R50: IF x is Ran 1 rule false THEN DATA: X is TRUE “DENY” Fired 1 rule Y is TRUE (R1000) Z is true R1000: IF z is true THEN Results “APPROVE” Search for rules that match the data R1000: IF z is true THEN “APPROVE” Search found Execute those rules 4 matching rules R100: IF x is true THEN R1000 fires because z is true Only 3 rules fired y is true CONCLUSION: APPROVE 29 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Traditional approach Modern approach using hard‐coded rules using business rules Database 2nd Tier Rule Engine Client Client 3rd Tier Applications Applications 1st Tier 1st Tier Code Business Rules Data CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 30

Benefits of centralizing rules in one rulebase Can take a broader view of the customer If you just cancelled my policy… If you just raised my premium… If you just lost my luggage… …stop sending me email or text messages with special offers for a while I’m not happy with you right now Less code Easier maintenance ($6/$1) Faster time to market … etc… 31 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Who uses rules technology? A.I. Expert Systems, Rulebase, and Knowledgebase Case Studies US IRS PRIME Sabre Internal Revenue Aug 2001 AMEX Service Modernization Authorizer’s Fortune 10 Assistant Canada HRDC Compliance Income Security & Tax Mobil Oil Program Redesign US DOL OSHA Expert Lube Knowledge Advisors Base Sun VISA Dell DuPont Freddie Mac Genworth LP Loan Prospector® AIG Fannie Mae Delta CitiStreet FICO DU Desktop Underwriter® DEC Credit Score DO Desktop Originator® XSEL Orbitz Harrah’s XCON Launched Countrywide Google June 2001 CLUES Founded 1998 Amazon Founded 1994 eBay Founded 1995 9/11 ES RBES KBES BRE BRMS EDM TE RBMS Gramm‐ dot.com ES Expert System Leach‐ Burst Google IPO Global Credit Crisis RBES Rule‐Based Expert System KBES Knowledge‐Based Expert System S&L Crisis 1stInternet Bliley Act Y2K $700b Bank Bailout BRE Business Rule Engine $150b S&L Bailout Stock Trade BRMS Business Rules Management System Sarbanes‐Oxley EDM Enterprise Decision Management HIPAA dot.com Subprime Mortgage TE Trust Engine RBMS Rulebase Management System Bubble Enron WorldCom Collapse Collapse CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 32

WISDOM The Future of IT All INTELLIGENCE IT ‐ Intelligent Technology KNOWLEDGE ONLINE DECISION IT ‐ Information Technology PROCESSING INFORMATION (OLDP) ONLINE MIS ‐ Management ANALYTICAL Decisioning Reasoning DATA Information Systems PROCESSING (OLAP) Advising Answering Complying … ONLINE Analyzing Recommending DP ‐ Data Processing Warehousing Scheduling TRANSACTION Decision Support PROCESSING (OLTP) Optimizing BATCH DATA Mining Diagnosing PROCESSING Transacting Decision Support Troubleshooting The Future of IT is… Aligning IT Systems with Business Strategy The Future of IT is Aligning IT Systems with Business Strategy Reporting Multidimensional Database Multidimensional Database Accounting Business Intelligence Networking CRM & SCM A.I. Artificial Intelligence QA Technology Automating Real‐Time Decisioning System … Relational Database Knowledge Management (KM) Client/Server LAN Business Rule Engine (BRE) BPM & BRM Magnetic Tape/Flat File Object‐Oriented Systems Business Rule Mgmt System Hierarchical Database Knowledge Base Expert System (ES) Answer Engine COBOL Web Browser Windows (Microsoft) Search Engine (Google) … Internet e‐Mail Rulebase WWW URL HTTP Semantic Web 2000’s 2010’s Wireless Web World Wide Web Smart Phone SMART SYSTEMS PC Revolution 1990’s Mainframe Era 1980’s ARTIFICIAL INTELLIGENCE SYSTEMS 1970’s KNOWLEDGE‐BASED SYSTEMS Complex rules; Deep/narrow scope of reasoning RULE‐BASED SYSTEMS Simplistic, Externalized, Declarative Rules; Shallow/broad scope of reasoning DATA‐BASED SYSTEMS Rules hard‐wired in code, stored procedures, or triggers

What is the difference between data‐based, rule‐based, and knowledge‐based systems? Data‐Based Rule‐Based Knowledge‐Based System System System Data Data Can process Data Rules Rules Knowledge Information Information Decisions Can output Information Decisions Answers Real‐Time Decisions Expert Advice Recommendations Commonly “Rule‐based” Fuzzy Logic, CBR, “Hard‐coded rules” implemented Declarative languages Probabilistic reasoning, Procedural languages using Deterministic other AI/ES techniques IT/System rules Simplistic business Ideal for Complex business rules Application rules rules Transacting Advising Best for these Reporting Decisioning Product selection types of (Traditional Compliance Recommending applications information systems) Troubleshooting Intelligence Shallow logic Deep Logic Not intelligent Capability Broad domains Narrow domain 34 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Architecture The result of architecture Engineering Design & Build Idea Implementation Logical Physical Representation Instantiation CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 37

A general framework for building any system Architecture Engineering Design Build Name Define Represent Specify Configure Instantiate it it it it it it Lack of specificity in one step leads to ambiguity in the next steps… Lack of quality in one step leads to mistakes in the next steps… Lack of completeness in one step leads to gaps in the next steps… CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 38

A general framework for building any system Architecture Engineering Design Build Name Define Represent Specify Configure Instantiate it it it it it it Lack of specificity in one step leads to ambiguity in the next steps… Lack of quality in one step leads to mistakes in the next steps… Lack of completeness in one step leads to gaps in the next steps… and thus the need for reiteration & rework in the process CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 39

A general framework for building any system Name it Define Architecture it Represent Engineering it Specify Designing it Configure Building it Instantiate it CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 40

TM ENTERPRISE ARCHITECTURE A FrameworkTM Enterprise Architecture – - A FRAMEWORK TM DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Name it Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) Define (CONCEPTUAL) Architecture it Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Represent Engineering it Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Specify Designing it Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS Configure TATIONS (OUT-OF (OUT-OF- CONTEXT) Building CONTEXT) it Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING Instantiate e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY FUNCTIONING ENTERPRISE ENTERPRISE it John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 41

BIZRULES® RULEMAP™ EXAMPLE GLOBAL ENTITY MANAGEMENT: U.S. EMPLOYER COMPLIANCE RULES Employment Eligibility Verification BUSINESS MAP (FACT MODEL) TERMS Authorization To Work Compliant Misdemeanor is a Illegal Alien Form I‐9 Individual Work U.S. Citizen Authorization aka are are guilty of a Lawful Permanent Resident Status Penalty and Bureau of Citizenship and Immigration Services Bureau of Citizenship Comply with Violate the Law Fine Is evidence of used to verify the Law U.S. Employers and Immigration is given by the Employment Employing Services Eligibility imposes Employment Eligibility formerly Authorization Verification who Identify required to to Work Form complete a Employees Immigration and U.S. The makes all Immigration Hired to Work Naturalization Service has Employers Employment Eligibility Verification Form (Form I‐9) is given to an Reform and Control Act Work Authorization Status Guilty responsible to Individual Misdemeanor has an Verify is an Identity November FACTS 6, 1986 Illegal Alien Citizen Lawful Resident Verify An Illegal Alien is an individual, who is not a Citizen or a Lawful Permanent Permanent Employment Resident and who has not been given Authorization To Work by the Bureau of Resident is an Eligibility Effective Citizenship and Immigration Services (formerly, the Immigration and of all Date is Naturalization Service). of the of all GOVERNING RULES U.S. Employers must verify the Employment Eligibility and Identify of all United Employees Hired to Work in the United States after November 6, 1986. States Employees Employers are required to complete Employment Eligibility Verification Forms in the (Form I‐9) for all Employees, including U.S. Citizens. Location that are Anyone Employing an Illegal Alien without Verifying his or her Work To work in hired after Authorization Status is Guilty of a Misdemeanor. DIGITIZED PROCESS (BUSINESS PROCESS MODEL) BUSINESS RULES Corporate / External / Compliance Rules RULE NO. HR Initiates Business Rules for Employment Eligibility 1 2 3 4 5 Business Unit notifies Employment START Decides to Hire HR Eligibility BU continues BUSINESS UNIT END PROCESS Employee Verification here… NOTES IF (BU) Process Company is _______ a US not a US ‐ ‐ ‐ Employer Employer Company wants to hire an Employee ‐ Con‐ ‐ ‐ ______ tractor Notify BU Candidate Work Location In the US ‐ ‐ Outside ‐ is ______ the US Record Reason Candidate Can Candidate Hire Date is After ‐ ‐ ‐ On or and Decision Be Hired as an ______ Nov. 6, 1986 before Verify No Inferences Employee Evaluate Candidate’s Yes Record Reason ENTERPRISE COMPLIANCE SYSTEM Business Employment and Decision THEN Rules Eligibility or Inferences Identify? Yes Prepare Wait for Is Candidate Submit I‐9 Company must verify Yes No No No No Authorized Candidate Must Electronic Form Government No form Candidate’s Employment to Work in Not Be Hired as Eligibility I‐9 Notification an Employee U.S. ? No No No Company must verify Yes No Candidate’s Identity Submit eForm Send Notification Work Authorization Rules Determine Candidate Work BUREAU OF CITIZENSHIP AND Receive & Work Authorization IMMIGRATION SERVICES (BCIS) Process Authorization Status? FEDERAL AGENCY Form I‐9 Status OUTPUT: Work Authorization Status is either Illegal Alien, Citizen, Lawful Candidate is Candidate is not Permanent Resident, or Resident Authorized to Authorized to Work in US Work in US ENTITY MANAGEMENT RULEBOOK Source: This is from a BIZRULES presentation archived on the Web at http://bizrules.info/files/bizrules‐brf2005orl.pdf. 1 LEGAL ENTITY MASTERFILE 10/06/08 FINAL

TM ENTERPRISE ARCHITECTUREA Framework TM Enterprise Architecture – - A FRAMEWORK Terms and Facts DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Terms Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Facts & Fact Models Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 52

TM ENTERPRISE ARCHITECTURE - A FRAMEWORK Goals, Rules and Decisions DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs (CONTEXTUAL) the Business Operates Mission & to the Business Important to the Business (CONTEXTUAL) Goals/Objectives Management Intention Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE MODEL System Strategy & Policy MODEL (CONCEPTUAL) (CONCEPTUAL) (Governing Rules) Informal or Detailed Description Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM MODEL Architecture Rulebase/Rulesets Architecture MODEL (Textual/Decision Trees/Decision Tables) (LOGICAL) (LOGICAL) Detailed Logical Definition Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) Formal/Detailed Rules (PHYSICAL) (Textual/If…Then) Node = Hardware/System Detailed Technical Specification Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Builder Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- TATIONS Source Code REPRESEN- TATIONS (OUT-OF- (Automated Rules) (OUT-OF CONTEXT) CONTEXT) Sub- Implementation Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING ENTERPRISE e.g. DATA e.g. FUNCTION e.g. NETWORK Enterprise e.g. ORGANIZATION Decision e.g. SCHEDULE e.g. STRATEGY ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 53

TM How do business rules fit into the Enterprise Architecture? ENTERPRISE ARCHITECTURE - A FRAMEWORK DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat TERMS MISSION & GOALS SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model BUSINESS PROCESS e.g. Business Process Model e.g. Business Logistics WORK FLOW MODELS e.g. Work Flow Model e.g. Master Schedule GOVERNING RULES e.g. Business Plan ENTERPRISE ENTERPRISE MODELS System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) FACT MODELS Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. USER INTERFACE Human Interface e.g. Processing Structure BUSINESS RULE MODELS e.g., Business Rule Model ARCHITECTURE SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) FACT TABLES Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design RULE DESIGNS TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action DETAILED e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Security Architecture e.g. Timing Definition RULE SPECIFICATIONS e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- If [Conditions] Then [Actions] [Goals] Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Sub- Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) Enterprise Architecture – A Framework™ 231-0531 ©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com 54

A general framework for designing rules WHO (people/organization) RULE condition/decision permission/constraint WHY (goal/motivation) 55 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Security Rule Pattern Are you who you say you are? WHO (people/org) WHY (goal/motivation) Security Management 57 CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008 BizRules is a registered trademark of BizRules.com

Why Systems Work

0 comments

Notes on slide 1

2 Favorites & 1 Event

Why Systems Work - Presentation Transcript

More by user

More info about this document

Categories

Tags

Tags

Groups / Events

Why Systems Work

0 comments

Notes on slide 1

2 Favorites & 1 Event

Why Systems Work - Presentation Transcript

Related Presentations

More by user

More info about this document

Categories

Tags

Tags

Groups / Events