1confidential & proprietary copyright © 2002-2008 bizrules is a registered trademark of...
TRANSCRIPT
1CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Why Systems Work
2CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
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
Enterprise architecture Knowledge engineering
Shared values and principles that state what we should and should not do
Clear and simple rules that statewhat you can and cannot do, must and must not do
5CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
A general framework for designing rules
WHO(people/organization)
WHY(goal/motivation)
HOW
(pro
cess
/func
tion)
WHAT
(thing/data)
WHEN
(eve
nt/tim
ing)
WHERE
(network/location)RULEcondition/decision
permission/constraint
6CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Prevent “World’s Dumbest Bank” transfer
WHO(people/org)
WHY(goal/motivation)
HO
W(p
roce
ss/fu
nctio
n)WH
AT
(thing/data)W
HE
N(e
vent
/tim
ing)
WH
ER
E
(network/locn)
Dur
ing
a gl
obal
finan
cial
sys
tem
mel
tdow
n or
a
bank
ing
cris
is
Cancel all
automated
transfersLoss Prevention
i.e. $426 million transfer to Lehman Brothers the
day it declared insolvency
Aut
omat
ed
curr
ency
sw
aps
Globally
with banks that are declaring
bankruptcy
7CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Prevent United Airlines $25 fare US to Paris
WHO(people/org)
WHY(goal/motivation)
HO
W(p
roce
ss/fu
nctio
n)WH
AT
(thing/data)W
HE
N(e
vent
/tim
ing)
WH
ER
E
(network/locn)
Effe
ctiv
e 10
/22/
08
Minim
um one-w
ay
fare is $100Prevent
“fantasy fares” glitch
i.e. $25 faresUS to Paris
Onl
ine
book
ing
or c
all c
ente
r
All
International flights
(i.e. US
to France)Unless authorized
by senior mgmt
8CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Prevent parents boarding flight, forgetting children
WHO(people/org)
WHY(goal/motivation)
HO
W(p
roce
ss/fu
nctio
n)WH
AT
(thing/data)W
HE
N(e
vent
/tim
ing)
WH
ER
E
(network/locn)
Effe
ctiv
e 10
/22/
08
Whe
n bo
ardi
ng
pass
enge
rs
With tickets that
say they are
travelling with lap-
children without a
boarding pass Ensure no child is left behind
i.e. forget toddler at the airport
Mus
t ver
ify th
at a
ll
child
ren,
esp
ecia
lly
thos
e w
ithou
t a
boar
ding
pas
s, a
re
pres
ent
At the gate
The check-in agent
9CONFIDENTIAL & 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
10CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Architecture
Strategy Rules• Mission• Values• Principles• Vision• Strategy
Business Rules• Policy• Rules
• Rulebase• Rulesets
• RulesTo see a Flash video of the “Rules EA Framework RuleMap”, visit www.RuleMap.com
11CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Architecture
Strategy Rules• Mission• Values• Principles• Vision• Strategy
Business Rules• Policy• Rules
• Rulebase• Rulesets
• RulesTo see a Flash video of the “Rules EA Framework RuleMap”, visit www.RuleMap.com
12CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Architecture
Strategy Rules• Mission• Values• Principles• Vision• Strategy
Business Rules• Policy• Rules
• Rulebase• Rulesets
• RulesTo see a Flash video of the “Rules EA Framework RuleMap”, visit www.RuleMap.com
13CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Architecture
Strategy Rules• Mission• Values• Principles• Vision• Strategy
Business Rules• Policy• Rules
• Rulebase• Rulesets
• RulesTo see a Flash video of the “Rules EA Framework RuleMap”, visit www.RuleMap.com
14CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
The bridge between business and IT
15CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Business and IT are in different worlds
Dollars
BusinessTechnology
Data
16CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Rules and knowledge are the bridge between Business and IT
Dollars
BusinessTechnology
RulesKnowledge
Data
17CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Architecture is how to design systemsEngineering is how to build systems
Dollars
BusinessTechnology
RulesKnowledge
Data
18CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Enterprise Architecture – A FrameworkTM
19CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Enterprise Architecture – A Framework TMComplete “Business Model” Architecture
20CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Enterprise Architecture – A Framework TMComplete “System Model” Architecture
21CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Enterprise Architecture – A Framework TMComplete “Technology Model” Architecture
22CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Object Oriented Modeling (UML; Use Cases)
23CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Structured Methods Modeling
24CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Enterprise Architecture – A Framework TMComplete “Data Model” Architecture
25CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Enterprise Architecture – A Framework TMComplete “Business Process Model” Architecture
26CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Complete “Business Rule Model” Architecture
28CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Traditional Procedural Language
R1: IF a is true THEN b is true
R10: IF y is true THEN z is true
R100: IF x is true THEN y is true
R1000: IF z is true THEN “APPROVE”
R10,000: IF d is true THEN “DENY”
Traditional Procedural language is sequential, forward only
Once you get an answer, the rest of the rules fire anyway
You have to loop a few times to get around sequence problem
Suppose your rules are out of order? Problems arise if sequence is incorrect
What if you have to add a new rule? Developer has to figure out what order
to put it in Adding a new rule could break existing
rules
Loop #1 Ran 10,000 rules1 rule fired(R100)
Loop #2 Ran 10,000 rules2 rules fired(R10, R1000)
CONCLUSION: Approve
ResultsRan 20,000 rulesOnly 3 rules fired
DATA: X is TRUE
29CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Declarative (Rule-based) Language
R1: IF a is true THEN b is true
R10: IF y is true THEN z
is true
R100: IF x is true THEN
y is true
R1000: IF z is true THEN
“APPROVE”
R10,000: IF d is true THEN
“DENY”
Rules are in no particular orderCycle #1Ran 2 rulesFired 1 rule(R100)
Cycle #2Ran 1 ruleFired 1 rule (R10)
Cycle #3Ran 1 ruleFired 1 rule (R1000)
ResultsSearch found 4 matching rulesOnly 3 rules fired
CONCLUSION: APPROVE
Search for rules that match the data R1000: IF z is true THEN “APPROVE”Execute those rules R1000 fires because z is true
DATA: X is TRUE Y is TRUE Z is true
Search for rules that match the data R10: IF y is true THEN z is TrueExecute those rules R10 fires because y is true
DATA: X is TRUE Y is TRUE
Search for rules that match the data R50: IF x is false THEN “Deny” R100: IF x is true THEN y is TrueExecute those rules R50 does not fire R100 fires because x is true
DATA: X is TRUE
R50: IF x is false THEN
“DENY”
30CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Traditional approach using hard-coded rules
Client Applications 1st
Tier
Database 2nd Tier
Code Business Rules Data
Rule Engine 3rd TierClient
Applications 1st Tier
Modern approach using business rules
31CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
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…
32CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Gramm-Leach-
Bliley Act
HIPAAEnron WorldCom Collapse
Sarbanes-Oxley
1st Internet Stock Trade
Google IPO
Subprime Mortgage Collapse
Global Credit Crisis$700b Bank Bailout
Who uses rules technology? A.I. Expert Systems, Rulebase, and Knowledgebase Case Studies
dot.com BurstS&L Crisis
$150b S&L Bailout
AMEX Authorizer’s
Assistant
DuPont
DECXSEL
XCON
US DOLOSHA Expert
Advisors
Mobil OilLube Knowledge
Base
Orbitz Launched June 2001
AmazonFounded 1994
Dell
AIG
VISA
dot.com Bubble
Y2K
GoogleFounded
1998
Canada HRDCIncome Security
Program Redesign
US IRS PRIMEInternal Revenue
Service Modernization
Sabre Aug 2001
eBayFounded 1995 9/11
CountrywideCLUES
FICO Credit Score
Freddie MacLP Loan Prospector®
Fannie MaeDU Desktop Underwriter®DO Desktop Originator®
Fortune 10 Compliance
& Tax
Sun
Genworth
Harrah’s
CitiStreetDelta
ES
ESRBESKBESBREBRMSEDMTERBMS
Expert SystemRule-Based Expert SystemKnowledge-Based Expert SystemBusiness Rule EngineBusiness Rules Management SystemEnterprise Decision ManagementTrust EngineRulebase Management System
RBES KBES BRE BRMS EDM TE RBMS
The Future of IT is… Aligning IT Systems with Business Strategy
DATA
DP - Data Processing
BATCH DATA PROCESSING
Accounting Automating
Magnetic Tape/Flat FileHierarchical Database
COBOLInternet e-Mail
DATA-BASED SYSTEMS Rules hard-wired in code, stored procedures, or triggers
Mainframe Era1970’s
INFORMATIONMIS - Management Information Systems
ONLINE TRANSACTION
PROCESSING (OLTP)TransactingReporting
NetworkingRelational DatabaseClient/Server LAN
Object-Oriented Systems
Expert System (ES)
Rulebase
RULE-BASED SYSTEMS Simplistic, Externalized, Declarative Rules; Shallow/broad scope of reasoning
PC Revolution1980’s
KNOWLEDGE
IT - Information Technology
ONLINE ANALYTICAL
PROCESSING (OLAP)Analyzing
Warehousing Decision Support
MiningDecision Support
Multidimensional Database
CRM & SCM
Knowledge Management (KM)Business Rule Engine (BRE)
Knowledge Base
Windows (Microsoft) WWW URL HTTP
KNOWLEDGE-BASED SYSTEMSComplex rules; Deep/narrow scope of reasoning
World Wide Web1990’s
INTELLIGENCE
IT - Intelligent Technology
ONLINE DECISION PROCESSING (OLDP)
DecisioningAdvising
ComplyingRecommending
SchedulingOptimizingDiagnosing
Troubleshooting
Business IntelligenceA.I. Artificial Intelligence
Real-Time Decisioning System
BPM & BRMBusiness Rule Mgmt System
Web BrowserSearch Engine (Google)
ARTIFICIAL INTELLIGENCE SYSTEMS
2000’sWireless WebSmart Phone
WISDOM
ReasoningAnswering
…
QA Technology…
Answer Engine…
SMART SYSTEMS
Semantic Web2010’s
The Future of IT All
34CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
What is the difference between data-based, rule-based, and knowledge-based systems?
Data-Based System
Rule-Based System
Knowledge-Based System
Can process Data Data Rules
DataRules
Knowledge
Can output InformationInformation
Decisions Real-Time Decisions
InformationDecisionsAnswers
Expert AdviceRecommendations
Commonly implemented
using
“Hard-coded rules”Procedural languages
“Rule-based” Declarative languages
Deterministic
Fuzzy Logic, CBR,Probabilistic reasoning,other AI/ES techniques
Ideal for IT/System rulesApplication rules
Simplistic business rules Complex business rules
Best for these types of
applications
TransactingReporting
(Traditional information systems)
Decisioning Compliance
AdvisingProduct selectionRecommendingTroubleshooting
Intelligence Capability Not intelligent Shallow logic
Broad domainsDeep Logic
Narrow domain
35CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Number of US Patents
36CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Framework for building and designing systems
that work, change, and last
37CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
The result of architectureDesign & Build
ImplementationPhysical
Instantiation
ArchitectureEngineering
IdeaLogical
Representation
38CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Nameit
Defineit
Represent it
Specifyit
Configure it
Instantiate 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…
A general framework for building any system
Architecture Engineering Design Build
39CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
A general framework for building any system
Architecture Engineering Design Build
Nameit
Defineit
Represent it
Specifyit
Configure it
Instantiate 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
40CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Nameit
Defineit
Represent it
Specifyit
Configure it
Instantiate it
Architecture
Engineering
Designing
Building
A general framework for building any system
41CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
TM
Nameit
Defineit
Represent it
Specifyit
Configure it
Instantiate it
Architecture
Engineering
Designing
Building
Enterprise Architecture – A FrameworkTM
42CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
A general framework for designing any system
WHO(people/organization)
WHY(goal/motivation)
HOW
(pro
cess
/func
tion)
WHAT
(thing/data)
WHEN
(eve
nt/tim
ing)
WHERE
(network/location)
43CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Data / What
Things Inventory sets
44CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Process / How
Process transformations
45CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Place / Where
Transportations Locations Network nodes
46CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
People / Who
Organization Groups
47CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Event / When
Timing periods Master schedules Deadlines Due dates
48CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Reasons / Why
Motivation reasons Reasoning Strategy Mission Goals Objectives
49CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise architectureensures that all the parts of the
business system connect, fit, and work
50CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Data
Process
Ruleset
Terms Facts
Rulebase Hierarchy
Rules
BIZRULES® RULEMAP™ EXAMPLE GLOBAL ENTITY MANAGEMENT: U.S. EMPLOYER COMPLIANCE RULES
ENTITY MANAGEMENT RULEBOOK1 LEGAL ENTITY MASTERFILE 10/06/08 FINAL
Source: This is from a BIZRULES presentation archived on the Web at http://bizrules.info/files/bizrules-brf2005orl.pdf.
Bureau of Citizenship and Immigration
Services
Immigration and Naturalization Service
Authorization to Work
Lawful Permanent
Resident
Individual
Illegal Alien Citizen Resident
United States
Location
Work Authorization
Status
Employment Eligibility
Verification Form
Form I-9Compliant Misdemeanor
Violate the LawPenalty and
Fine
U.S. Employers
Verify Identity
Verify Employment
Eligibility
Employees
hired
The Immigration Reform and Control Act
Effective Date
November 6, 1986
Comply with the Law
after
is
To work in
that are
of all
of all
is an
has an
responsible to
makes all
whoimposes
is a
are guilty of aare
required to complete a
used to verify
has
is an
is given to an
Is evidence ofis given by the
aka
formerly
of the
in the
BUSINESS UNIT (BU)START
PROCESS
Business Unit Decides to Hire
Employee
HR Initiates Employment
Eligibility Verification
Process
Evaluate Business
Rules
Record Reason and Decision
Inferences
Prepare Electronic Form I-
9
Wait for Government Notification
Receive & Process Form
I-9
Determine Work
Authorization Status
Record Reason and Decision
Inferences
BU continues here…
Is Candidate Authorized to Work in
U.S. ?
Verify Candidate’s
Employment Eligibility or
Identify?
notifiesHR
ENTERPRISE COMPLIANCE SYSTEM
BUREAU OF CITIZENSHIP AND IMMIGRATION SERVICES (BCIS) FEDERAL AGENCY
OUTPUT:Work Authorization Status is either
Illegal Alien, Citizen, Lawful Permanent Resident, or Resident
No
Yes
Submit eForm Send Notification
No
Notify BU
Candidate Must Not Be Hired as
an Employee
Candidate Can Be Hired as an
Employee
END
DIGITIZED PROCESS (BUSINESS PROCESS MODEL)
Employment Eligibility Verification BUSINESS MAP (FACT MODEL) TERMS
Authorization To WorkIllegal AlienIndividualU.S. CitizenLawful Permanent ResidentBureau of Citizenship and Immigration ServicesU.S. EmployersEmployingEmployment EligibilityIdentifyEmployeesHired to WorkEmployment Eligibility Verification Form (Form I-9)Work Authorization StatusGuiltyMisdemeanor
FACTS
An Illegal Alien is an individual, who is not a Citizen or a Lawful Permanent Resident and who has not been given Authorization To Work by the Bureau of Citizenship and Immigration Services (formerly, the Immigration and Naturalization Service).
GOVERNING RULES
U.S. Employers must verify the Employment Eligibility and Identify of all Employees Hired to Work in the United States after November 6, 1986.
Employers are required to complete Employment Eligibility Verification Forms (Form I-9) for all Employees, including U.S. Citizens.
Anyone Employing an Illegal Alien without Verifying his or her Work Authorization Status is Guilty of a Misdemeanor.
BUSINESS RULES
Corporate / External / Compliance RulesBusiness Rules for Employment Eligibility
RULE NO.1 2 3 4 5
NOTES IF
THEN
Company is _______
Company wants to hire an______
Candidate Work Locationis ______
Candidate Hire Date is______ Nov. 6, 1986
Company must verifyCandidate’s Employment Eligibility
Company must verifyCandidate’s Identity
Submit I-9form
Work Authorization Rules
Candidate WorkAuthorization
Status?
Candidate is Authorized to
Work in US
Candidate is not Authorized to
Work in US
Illegal Alien Other
Yes
a US Employer
Employee
In the US
After
Yes
Yes
not a US Employer
-
-
-
No
No
-
Con-tractor
-
-
No
No
-
-
Outside the US
-
No
No
-
-
-
On or before
No
No
52CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Enterprise Architecture – A Framework TMTerms and Facts
Terms
Facts & Fact Models
53CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
Goals, Rules and Decisions
Mission & Goals/Objectives
Strategy & Policy (Governing Rules)
Rulebase/Rulesets(Textual/Decision Trees/Decision Tables)
Formal/Detailed Rules(Textual/If…Then)
Source Code (Automated Rules)
Management Intention
Informal or Detailed Description
Detailed Logical Definition
Detailed Technical Specification
Implementation
Enterprise Decision
54CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. Application Architecture
I/O = User ViewsProc .= Application Function
e.g. System Design
I/O = Data Elements/SetsProc.= Computer Function
e.g. Program
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Business Logistics System
Node = Business LocationLink = Business Linkage
e.g. Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. Technology Architecture
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. Network Architecture
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYMODEL
(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-condition
Means = Step
e.g. Rule Design
End = ConditionMeans = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component CycleTime = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = Job
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
John A. Zachman, Zachman International (810) 231-0531
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGYENTERPRISE
e.g. Business Plan
TM
Reprinted by permission – www.zifa.comEnterprise Architecture – A Framework™ ©John A. Zachman, Zachman International (810) 231-0531
How do business rules fit into the Enterprise Architecture?
TERMS
BUSINESS PROCESS MODELS
FACT MODELS
FACT TABLES
WORK FLOW MODELS
MISSION & GOALS
USER INTERFACE ARCHITECTURE
GOVERNING RULES
BUSINESS RULE MODELS
RULE DESIGNS
RULE SPECIFICATIONS
If [Conditions] Then [Actions] [Goals]
55CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
A general framework for designing rules
WHO(people/organization)
WHY(goal/motivation)
HOW
(pro
cess
/func
tion)
WHAT
(thing/data)
WHEN
(eve
nt/tim
ing)
WHERE
(network/location)RULEcondition/decision
permission/constraint
56CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
General Rule Pattern
WHO(people/org)
WHY(goal/motivation)
HO
W(p
roce
ss/fu
nctio
n)WH
AT
(thing/data)W
HE
N(e
vent
/tim
ing)
WH
ER
E
(network/locn)
Con
ditio
n
Condition
Principle or Rule
Con
ditio
n
Condition
Condition
57CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Security Rule Pattern
WHO(people/org)
WHY(goal/motivation)
HO
W(p
roce
ss/fu
nctio
n)WH
AT
(thing/data)W
HE
N(e
vent
/tim
ing)
WH
ER
E
(network/locn)
Whe
n w
ill I
allo
w
you
to d
o it?
What w
ill I allow
you to do?Security
Management
How
will
I al
low
you
to d
o it?
Where w
ill I allow
you to go?Are you who you
say you are?
58CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Technology Integration and Architecture™
WHO(people)
WHAT(data)
HO
W(fu
nctio
n)
WH
Y
(reason)W
HE
N(ti
me)
WH
ER
E
(network)
CE
PB
AM
ESBR
E
BR
MS
ED
M
KMCRMSRM
BP
RB
PM
SO
AS
aaS
DBMSMDM
SC
MER
P
EC
M
Cloud com
puting
WM
S
59CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Rules Integration™
WHO(people)
WHAT(data)
HO
W(fu
nctio
n)
WH
Y
(reason)W
HE
N(ti
me)
WH
ER
E
(network)
CE
P
ESBR
E
BR
MS
ED
M
KMCRMSRM
BP
RB
PM
SO
AS
aaS
DBMSMDM
SC
MER
P
EC
M
Cloud com
puting
WM
S
60CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Rules Integration™
WHO(people)
WHAT(data)
HO
W(fu
nctio
n)
WH
Y
(reason)W
HE
N(ti
me)
WH
ER
E
(network)
CE
P
ESBR
E
BR
MS
ED
M
KMCRMSRM
BP
RB
PM
SO
AS
aaS
DBMSMDM
SC
MER
P
EC
M
Cloud com
puting
WM
S
61CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Rules Integration™
WHO(people)
WHAT(data)
HO
W(fu
nctio
n)
WH
Y
(reason)W
HE
N(ti
me)
WH
ER
E
(network)
CE
P
ESBR
E
BR
MS
ED
M
KMCRMSRM
BP
RB
PM
SO
AS
aaS
DBMSMDM
SC
MER
P
EC
M
Cloud com
puting
WM
S
62CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Rules Integration™
WHO(people)
WHAT(data)
HO
W(fu
nctio
n)
WH
Y
(reason)W
HE
N(ti
me)
WH
ER
E
(network)
CE
P
ESBR
E
BR
MS
ED
M
KMCRMSRM
BP
RB
PM
SO
AS
aaS
DBMSMDM
SC
MER
P
EC
M
Cloud com
puting
WM
S
63CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Rules Integration™
WHO(people)
WHAT(data)
HO
W(fu
nctio
n)
WH
Y
(reason)W
HE
N(ti
me)
WH
ER
E
(network)
CE
P
ESBR
E
BR
MS
ED
M
KMCRMSRM
BP
RB
PM
SO
AS
aaS
DBMSMDM
SC
MER
P
EC
M
Cloud com
puting
WM
S
64CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Enterprise Rules Integration™
WHO(people)
WHAT(data)
HO
W(fu
nctio
n)
WH
Y
(reason)W
HE
N(ti
me)
WH
ER
E
(network)
CE
P
ESBR
E
BR
MS
ED
M
KMCRMSRM
BP
RB
PM
SO
AS
aaS
DBMSMDM
SC
MER
P
EC
M
Cloud com
puting
WM
S
65CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com
Thank youRolando Hernandez
Chief Rules Architect, [email protected]
972-987-1685