On enterprise rules integration. enterprise rules architecture, and the Zachman enterprise architecture framework. (NOTE: Download the file and start Powerpoint to see high quality graphics; the slideshare viewer messes up some of the graphics)

1. Rulebase Architecture
Rolando Hernandez
Enterprise Rules Architect
Enterprise Rules Architect
CEO, BIZRULES
RH.2008@BizRules.com
www.BizRules.com
www.VisibleKnowledge.com
Copyright © 2008 BIZRULES 1

2. Enterprise Rules Integration
Data Rules Terms Facts
Process/Code
Ruleset Rulebase Hierarchy
Rulebase Hierarchy
Copyright © 2008 BIZRULES 2

3. Enterprise Rules Architecture
Copyright © 2008 BIZRULES 3

4. Enterprise Architecture – A Framework TM TM
ENTERPRISE ARCHITECTURE - A FRAMEWORK
MOTIVATION
PEOPLE TIME
DATA FUNCTION NETWORK
What How Where Who When Why
y
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 SCOPE
to the Business Business Performs to the Business
the Business Operates Important to the Business
(CONTEXTUAL) (CONTEXTUAL)
Function = Class of Ends/Means=Major Bus. Goal/
Planner Node = Major Business
ENTITY = Class of Planner
People = Major Organizations Time = Major Business Event
Business Process Critical Success Factor
Business Thing Location
e.g. Master Schedule
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Business Plan
e.g. Work Flow Model ENTERPRISE
ENTERPRISE System
MODEL
MODEL
(CONCEPTUAL)
(CONCEPTUAL)
Owner Owner
Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective
People = Organization Unit Time = Business Event
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 A hit t
Architecture
MODEL
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function
Ent = Data Entity Proc .= Application Function Time = System Event
People = Role End = Structural Assertion
(Processor, Storage, etc) Designer
Designer Cycle = Processing Cycle
Reln = Data Relationship 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. Control Structure e.g. Rule Design
e.g. Presentation Architecture TECHNOLOGY
TECHNOLOGY
MODEL
MODEL
(PHYSICAL)
(PHYSICAL)
Node = Hardware/System Builder
Ent = Segment/Table/etc. Proc.= Computer Function End = Condition
Builder People = User Time = Execute
Software
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action
Link = Line Specifications Work = Screen Format
e.g. Security Architecture DETAILED
e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification
e.g. Data Definition
DETAILED
REPRESEN-
REPRESEN-
TATIONS
TATIONS
(OUT OF
(OUT-OF
(OUT-OF-
(OUT OF
CONTEXT)
CONTEXT)
Sub-
Sub-
End = Sub-condition
Proc.= Language Stmt
Contractor Ent = Field Node = Addresses Time = Interrupt
People = Identity
Contractor
Cycle = Machine Cycle
Reln = Address I/O = Control Block Link = Protocols Work = Job Means = Step
FUNCTIONING
FUNCTIONING
e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY
ENTERPRISE ENTERPRISE
Enterprise Architecture – A Framework™
John A Zachman Zachman International (810) 231 0531
A. Zachman, 231-0531
©John A. Zachman, Zachman International (810) 231‐0531 Reprinted by permission – www.zifa.com
4
Copyright © 2008 BIZRULES

5. ENTERPRISE ARCHITECTUREA Framework TM
Enterprise Architecture – - A FRAMEWORK
TM
Complete “Data Model” Architecture
MOTIVATION
PEOPLE TIME
DATA FUNCTION NETWORK
What How Where Who When Why
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 SCOPE
to the Business Business Performs to the Business
the Business Operates Important to the Business
(CONTEXTUAL) (CONTEXTUAL)
Function = Class of Ends/Means=Major Bus. Goal/
Planner Node = Major Business
ENTITY = Class of Planner
People = Major Organizations Time = Major Business Event
Business Process Critical Success Factor
Business Thing Location
e.g. Master Schedule
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Business Plan
e.g. Work Flow Model ENTERPRISE
ENTERPRISE System
MODEL
MODEL
(CONCEPTUAL)
(CONCEPTUAL)
Owner Owner
Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective
People = Organization Unit Time = Business Event
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
O
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function
Ent = Data Entity Time = System Event
Proc .= Application Function People = Role End = Structural Assertion
(Processor, Storage, etc) Designer
Designer Cycle = Processing Cycle
Reln = Data Relationship 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. Control Structure e.g. Rule Design
e.g. Presentation Architecture TECHNOLOGY
TECHNOLOGY
MODEL
MODEL
(PHYSICAL)
(PHYSICAL)
Node = Hardware/System Builder
Ent = Segment/Table/etc. Proc.= Computer Function End = Condition
Builder People = User Time = Execute
Software
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action
Link = Line Specifications Work = Screen Format
e.g. Security Architecture DETAILED
e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification
DETAILED
REPRESEN-
REPRESEN-
TATIONS
TATIONS
(OUT-OF
(OUT-OF-
CONTEXT)
CONTEXT)
Sub-
Sub-
End = Sub-condition
Proc.= Language Stmt
Contractor Ent = Field Node = Addresses Time = Interrupt
People = Identity
Contractor
Cycle = Machine Cycle
Work = Job
Reln = Address I/O = Control Block Link = Protocols Means = Step
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) 231-0531
Enterprise Architecture – A Framework™
Reprinted by permission – www.zifa.com
©John A. Zachman, Zachman International (810) 231‐0531
Copyright © 2008 BIZRULES 5

6. ENTERPRISE ARCHITECTUREA Framework TM
Enterprise Architecture – - A FRAMEWORK
TM
Complete “Business Process Model” Architecture
MOTIVATION
PEOPLE TIME
DATA FUNCTION NETWORK
What How Where Who When Why
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 SCOPE
to the Business Business Performs to the Business
the Business Operates Important to the Business
(CONTEXTUAL) (CONTEXTUAL)
Function = Class of Ends/Means=Major Bus. Goal/
Planner Node = Major Business
ENTITY = Class of Planner
People = Major Organizations Time = Major Business Event
Business Process Critical Success Factor
Business Thing Location
e.g. Master Schedule
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Business Plan
e.g. Work Flow Model ENTERPRISE
ENTERPRISE System
MODEL
MODEL
(CONCEPTUAL)
(CONCEPTUAL)
Owner Owner
Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective
People = Organization Unit Time = Business Event
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
O
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function
Ent = Data Entity Time = System Event
Proc .= Application Function People = Role End = Structural Assertion
(Processor, Storage, etc) Designer
Designer Cycle = Processing Cycle
Reln = Data Relationship 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. Control Structure e.g. Rule Design
e.g. Presentation Architecture TECHNOLOGY
TECHNOLOGY
MODEL
MODEL
(PHYSICAL)
(PHYSICAL)
Node = Hardware/System Builder
Ent = Segment/Table/etc. Proc.= Computer Function End = Condition
Builder People = User Time = Execute
Software
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action
Link = Line Specifications Work = Screen Format
e.g. Security Architecture DETAILED
e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification
DETAILED
REPRESEN-
REPRESEN-
TATIONS
TATIONS
(OUT-OF
(OUT-OF-
CONTEXT)
CONTEXT)
Sub-
Sub-
End = Sub-condition
Proc.= Language Stmt
Contractor Ent = Field Node = Addresses Time = Interrupt
People = Identity
Contractor
Cycle = Machine Cycle
Work = Job
Reln = Address I/O = Control Block Link = Protocols Means = Step
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) 231-0531
Enterprise Architecture – A Framework™
Reprinted by permission – www.zifa.com
©John A. Zachman, Zachman International (810) 231‐0531
Copyright © 2008 BIZRULES 6

7. Complete “Business Rule Model” Architecture
TM
ENTERPRISE ARCHITECTURE - A FRAMEWORK
MOTIVATION
PEOPLE TIME
DATA FUNCTION NETWORK
What How Where Who When Why
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 SCOPE
to the Business Business Performs to the Business
the Business Operates Important to the Business
(CONTEXTUAL) (CONTEXTUAL)
Function = Class of Ends/Means=Major Bus. Goal/
Planner Node = Major Business
ENTITY = Class of Planner
People = Major Organizations Time = Major Business Event
Business Process Critical Success Factor
Business Thing Location
e.g. Master Schedule
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Business Plan
e.g. Work Flow Model ENTERPRISE
ENTERPRISE System
MODEL
MODEL
(CONCEPTUAL)
(CONCEPTUAL)
Owner Owner
Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective
People = Organization Unit Time = Business Event
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
O
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function
Ent = Data Entity Time = System Event
Proc .= Application Function People = Role End = Structural Assertion
(Processor, Storage, etc) Designer
Designer Cycle = Processing Cycle
Reln = Data Relationship 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. Control Structure e.g. Rule Design
e.g. Presentation Architecture TECHNOLOGY
TECHNOLOGY
MODEL
MODEL
(PHYSICAL)
(PHYSICAL)
Node = Hardware/System Builder
Ent = Segment/Table/etc. Proc.= Computer Function End = Condition
Builder People = User Time = Execute
Software
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action
Link = Line Specifications Work = Screen Format
e.g. Security Architecture DETAILED
e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification
DETAILED
REPRESEN-
REPRESEN-
TATIONS
TATIONS
(OUT-OF
(OUT-OF-
CONTEXT)
CONTEXT)
Sub-
Sub-
End = Sub-condition
Proc.= Language Stmt
Contractor Ent = Field Node = Addresses Time = Interrupt
People = Identity
Contractor
Cycle = Machine Cycle
Work = Job
Reln = Address I/O = Control Block Link = Protocols Means = Step
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) 231-0531
Enterprise Architecture – A Framework™
Reprinted by permission – www.zifa.com
©John A. Zachman, Zachman International (810) 231‐0531
Copyright © 2008 BIZRULES 7

8. Object Oriented Modeling (UML; Use Cases)
TM
ENTERPRISE ARCHITECTURE - A FRAMEWORK
MOTIVATION
PEOPLE TIME
DATA FUNCTION NETWORK
What How Where Who When Why
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 SCOPE
to the Business Business Performs to the Business
the Business Operates Important to the Business
(CONTEXTUAL) (CONTEXTUAL)
Function = Class of Ends/Means=Major Bus. Goal/
Planner Node = Major Business
ENTITY = Class of Planner
People = Major Organizations Time = Major Business Event
Business Process Critical Success Factor
Business Thing Location
e.g. Master Schedule
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Business Plan
e.g. Work Flow Model ENTERPRISE
ENTERPRISE System
MODEL
MODEL
(CONCEPTUAL)
(CONCEPTUAL)
Owner Owner
Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective
People = Organization Unit Time = Business Event
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
O
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function
Ent = Data Entity Time = System Event
Proc .= Application Function People = Role End = Structural Assertion
(Processor, Storage, etc) Designer
Designer Cycle = Processing Cycle
Reln = Data Relationship 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. Control Structure e.g. Rule Design
e.g. Presentation Architecture TECHNOLOGY
TECHNOLOGY
MODEL
MODEL
(PHYSICAL)
(PHYSICAL)
Node = Hardware/System Builder
Ent = Segment/Table/etc. Proc.= Computer Function End = Condition
Builder People = User Time = Execute
Software
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action
Link = Line Specifications Work = Screen Format
e.g. Security Architecture DETAILED
e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification
DETAILED
REPRESEN-
REPRESEN-
TATIONS
TATIONS
(OUT-OF
(OUT-OF-
CONTEXT)
CONTEXT)
Sub-
Sub-
End = Sub-condition
Proc.= Language Stmt
Contractor Ent = Field Node = Addresses Time = Interrupt
People = Identity
Contractor
Cycle = Machine Cycle
Work = Job
Reln = Address I/O = Control Block Link = Protocols Means = Step
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) 231-0531
Enterprise Architecture – A Framework™
Reprinted by permission – www.zifa.com
©John A. Zachman, Zachman International (810) 231‐0531
Copyright © 2008 BIZRULES 8

9. Structured Methods Modeling
TM
ENTERPRISE ARCHITECTURE - A FRAMEWORK
MOTIVATION
PEOPLE TIME
DATA FUNCTION NETWORK
What How Where Who When Why
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 SCOPE
to the Business Business Performs to the Business
the Business Operates Important to the Business
(CONTEXTUAL) (CONTEXTUAL)
Function = Class of Ends/Means=Major Bus. Goal/
Planner Node = Major Business
ENTITY = Class of Planner
People = Major Organizations Time = Major Business Event
Business Process Critical Success Factor
Business Thing Location
e.g. Master Schedule
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Business Plan
e.g. Work Flow Model ENTERPRISE
ENTERPRISE System
MODEL
MODEL
(CONCEPTUAL)
(CONCEPTUAL)
Owner Owner
Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective
People = Organization Unit Time = Business Event
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
O
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function
Ent = Data Entity Time = System Event
Proc .= Application Function People = Role End = Structural Assertion
(Processor, Storage, etc) Designer
Designer Cycle = Processing Cycle
Reln = Data Relationship 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. Control Structure e.g. Rule Design
e.g. Presentation Architecture TECHNOLOGY
TECHNOLOGY
MODEL
MODEL
(PHYSICAL)
(PHYSICAL)
Node = Hardware/System Builder
Ent = Segment/Table/etc. Proc.= Computer Function End = Condition
Builder People = User Time = Execute
Software
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action
Link = Line Specifications Work = Screen Format
e.g. Security Architecture DETAILED
e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification
DETAILED
REPRESEN-
REPRESEN-
TATIONS
TATIONS
(OUT-OF
(OUT-OF-
CONTEXT)
CONTEXT)
Sub-
Sub-
End = Sub-condition
Proc.= Language Stmt
Contractor Ent = Field Node = Addresses Time = Interrupt
People = Identity
Contractor
Cycle = Machine Cycle
Work = Job
Reln = Address I/O = Control Block Link = Protocols Means = Step
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) 231-0531
Enterprise Architecture – A Framework™
Reprinted by permission – www.zifa.com
©John A. Zachman, Zachman International (810) 231‐0531
Copyright © 2008 BIZRULES 9

10. ENTERPRISE ARCHITECTUREA Framework TM
Enterprise Architecture – - A FRAMEWORK
TM
Complete “Business Model” Architecture
MOTIVATION
PEOPLE TIME
DATA FUNCTION NETWORK
What How Where Who When Why
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 SCOPE
to the Business Business Performs to the Business
the Business Operates Important to the Business
(CONTEXTUAL) (CONTEXTUAL)
Function = Class of Ends/Means=Major Bus. Goal/
Planner Node = Major Business
ENTITY = Class of Planner
People = Major Organizations Time = Major Business Event
Business Process Critical Success Factor
Business Thing Location
e.g. Master Schedule
e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Business Plan
e.g. Work Flow Model ENTERPRISE
ENTERPRISE System
MODEL
MODEL
(CONCEPTUAL)
(CONCEPTUAL)
Owner Owner
Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective
People = Organization Unit Time = Business Event
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
O
MODEL (LOGICAL)
(LOGICAL)
Node = I/S Function
Ent = Data Entity Time = System Event
Proc .= Application Function People = Role End = Structural Assertion
(Processor, Storage, etc) Designer
Designer Cycle = Processing Cycle
Reln = Data Relationship 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. Control Structure e.g. Rule Design
e.g. Presentation Architecture TECHNOLOGY
TECHNOLOGY
MODEL
MODEL
(PHYSICAL)
(PHYSICAL)
Node = Hardware/System Builder
Ent = Segment/Table/etc. Proc.= Computer Function End = Condition
Builder People = User Time = Execute
Software
Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action
Link = Line Specifications Work = Screen Format
e.g. Security Architecture DETAILED
e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification
DETAILED
REPRESEN-
REPRESEN-
TATIONS
TATIONS
(OUT-OF
(OUT-OF-
CONTEXT)
CONTEXT)
Sub-
Sub-
End = Sub-condition
Proc.= Language Stmt
Contractor Ent = Field Node = Addresses Time = Interrupt
People = Identity
Contractor
Cycle = Machine Cycle
Work = Job
Reln = Address I/O = Control Block Link = Protocols Means = Step
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) 231-0531
Enterprise Architecture – A Framework™
Reprinted by permission – www.zifa.com
©John A. Zachman, Zachman International (810) 231‐0531
Copyright © 2008 BIZRULES 10