decision dominoes

1 Copyright © 2011 BizRules® (brand) is a registered trademark of BIZRULES (company)

What is the biggest challenge facing CIOs ?

Alignment of systems to strategy

2 CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com

What is the biggest challenge facing CIOs? Alignment of IT systems to business strategy.

Busin

ess

Technolo

gy

Busin

ess

Technolo

gy

Why do systems fail? No alignment.


Models are the bridge that enables you to connect and align Business and IT

Dollars

Sense

Business Technology

Knowledge

Rules Decisions

Process Events

Terms Facts Concepts

Knowing Understanding Meaning

Thinking Reasoning Judgment

Data


e.g. DATA

ENTERPRISE ARCHITECTURE - A FRAMEWORK

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONING

ENTERPRISE

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 Entity

Reln = Data Relationship

e.g. Semantic Model

Ent = Business Entity

Reln = Business Relationship

List of Things Important

to the Business

ENTITY = Class ofBusiness Thing

List of Processes the

Business Performs

Function = Class ofBusiness Process

e.g. Application Architecture

I/O = User ViewsProc .= Application Function

e.g. System Design

I/O = Data Elements/Sets

Proc.= Computer Function

e.g. Program

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business Process

I/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Business Logistics System

Node = Business Location

Link = 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 = Condition

Means = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business Objective

Means = 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 Cycle

Time = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business Event

Cycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization Unit

Work = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = User

Work = 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

TMModels are the secret to aligning systems to strategy

TERMS GLOSSARY Terms & Definitions

Fact Types List of Values

KNOWING

BUSINESS PROCESS MODELS

KNOWLEDGE MODELS Terms & Meaning Domain Models

Fact Models Concept Maps

UNDERSTANDING

WORK FLOW MODELS

Mission and Goals Laws and Regulations Strategies and Policies

USER INTERFACE ARCHITECTURE

RULEBASE

Architecture Rule Designs

BUSINESS RULE

ENGINE

Rule Specifications Rule Code

Business Rules If [Conditions Events] Then [Conclusions Decisions Actions] [Goals]

Reprinted by permission – www.zifa.com Enterprise Architecture – A Framework™

©John A. Zachman, Zachman International (810) 231-0531

DATA MODELS

Fact Tables ER Diagrams

BUSINESS RULE MODELS

Rule Family Tables Business Logic Models

EVENT MODELS BUSINESS DECISION MODELS

Decision Model Diagrams

BRE > Code

BDMS > BRMS

BDM / BDMS

BRMS > BRE

DBMS Model

DATABASE

Data Table Designs

DBMS SQL DDL DML

BPM / BPMN

BPMN > BPMS

BPMS > Programs

DBMS / Database Engine Programs > Code

Legal Entities Management Entities

Suppliers Customers Regulators

PLACES Locations

Jurisdictions

http://www.zifa.com/


Everything connects to everything else

“Principles for the development of a Complete Mind: Study the science of art.

Study the art of science. Develop your senses - especially learn how to see. Realise that everything connects to

everything else.”

Leonardo da Vinci


Data

Process

Rulebase

Events Facts and Fact Models

Rulebase Hierarchy

Rules

Sequential Steps, Activities, and Tasks Procedures, Instructions, Code

Conclusions Deduction , Induction

Inference Global Rules

Common Rules

Local Rules

Specialized Rules Laws Rules & Regulations Policies Rules of Thumb Heuristics Expert Rules Single and Multiple Inheritance

Logic Business Rules If/Then Rules Decision Models Rule Family Tables Decision Tables

Decision Trees Rulesets Directed Acyclic Graph (DAG)

Instances (Records) Logic Time

Terms Words

Rev. 5 November 2012

What we think we know

Think and Decide What to do & Why

What to do and How-to do it

Conditions

Reuse Inheritance

The Decision The Moment of Truth

Terms & Definitions

Concepts Ontology

Semantic Map

Terms & Relationships

Knowing Understanding Meaning Terms & Meaning

What we truly understand

Terms & Conditions

Thinking Reasoning Judgment

Intermediate Conclusions

Doing

BIZRULES® RULEMAP™ EXAMPLE GLOBAL ENTITY MANAGEMENT: U.S. EMPLOYER COMPLIANCE RULES

ENTITY MANAGEMENT RULEBOOK

1 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-9 Compliant Misdemeanor

Violate the Law Penalty 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

who

imposes

is a

are guilty of a are

required to complete a

used to verify

has

is an

is given to an

Is evidence of is 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?

notifies HR

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 Work Illegal Alien

Individual U.S. Citizen

Lawful Permanent Resident Bureau of Citizenship and Immigration Services

U.S. Employers Employing

Employment Eligibility Identify

Employees Hired to Work

Employment Eligibility Verification Form (Form I-9) Work Authorization Status

Guilty Misdemeanor

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 Rules Business Rules for Employment Eligibility

RULE NO.

1 2 3 4 5

NOTES IF

THEN

Company is _______

Company wants to hire an ______

Candidate Work Location

is ______

Candidate Hire Date is ______ Nov. 6, 1986

Company must verify Candidate’s Employment

Eligibility

Company must verify Candidate’s Identity

Submit I-9 form

Work Authorization Rules

Candidate Work Authorization

Status?

Candidate is Authorized to

Work in US

Candidate is not Authorized to

Work in US

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

Terms

Facts

Governing Rules

(i.e. Ontology)

Concept Map Semantic Model

Process Model

Rule Model

Decision

Decision


The Moment of Truth

What do we do?

We must decide now!

Long Term Survival

Short Term Profits

1-800 CALL-SME

The Moment of Truth

Build decision models to

make consistent, legal,

and profitable decisions

Ignore experts,

rules and regulations.

Guess, hope and pray

1-800 CALL-SME

The Moment of Truth

Update Your Models

then change the System

Make changes to

the system and

forget the models

1-800 CALL-SME

The Moment of Truth


A general framework for building any complex system

How to transform idea into implementation


The result of architecture Design & Build

Implementation Physical

Instantiation

Architecture Engineering

Idea Logical

Representation


A general framework for building any system

Architecture Engineering Design Build

Name it

Define it

Represent it

Specify it

Configure it

Instantiate it




Name it

Define it

Represent it

Specify it

Configure 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…

Instantiate it




Name it

Define it

Represent it

Specify it

Configure 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…

Consequences are the need for reiteration & rework in the process.

That takes more time, and costs more money.

Instantiate it


Define it

Represent it

Specify it

Configure it

Instantiate it

Architecture

Engineering

Designing

Building


Name it


e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Name it

Define it

Represent it

Specify it

Configure it

Architecture

Engineering

Designing

Building



Instantiate it



e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Enterprise Architecture – A Framework TM





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Enterprise Architecture – A Framework TM Complete “Data Model” Architecture

Terms

Glossary

Terms & Definitions

Semantic Models

Fact/Concept Models Terms & Meaning



Logical Data Models




e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Enterprise Architecture – A Framework TM Complete “Business Process Model” Architecture





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Complete “Business Rule Model” Architecture

Mission Goals and Objectives

Strategy & Policy Decision Models

Business Rule Models

Formal/Detailed Rules Designs and Specifications

Automated Rules Source Code

Management Intention

Informal or Detailed Description

Detailed Logical Definition

Detailed Technical Specification

Implementation

Enterprise Decision / Prescription





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Enterprise Architecture – A Framework TM Complete “Business Model” Architecture





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Enterprise Architecture – A Framework TM Complete “System Model” Architecture





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Enterprise Architecture – A Framework TM Complete “Technology Model” Architecture





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Object Oriented Modeling (UML; Use Cases)





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Structured Methods Modeling (Mainframe Era)





e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TMModels are the only known way to transform ideas into implementations

TERMS


KNOWLEDGE MODELS

Fact Models

WORK FLOW MODELS

MISSION & GOALS


BUSINESS DECISION MODELS


RULE DESIGNS AND SPECIFICATIONS

RULES SOURCE CODE

Business Rules If [Events or Conditions] Then [Decisions or Actions] [Goals]



DATA MODELS



e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEM

MODEL(LOGICAL)

TECHNOLOGY

MODEL(PHYSICAL)


Sub-Contractor

FUNCTIONING

ENTERPRISE








Ent = Data Entity


e.g. Semantic Model




to the Business



Business Performs




e.g. System Design



e.g. Program


e.g. FUNCTION
















e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action













Time = Execute



e.g. SCHEDULE








Work = Work Product




People = User




e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TMModels are the secret to aligning systems to strategy

TERMS GLOSSARY Terms & Definitions

Fact Types List of Values

KNOWING


KNOWLEDGE MODELS Terms & Meaning Domain Models

Fact Models Concept Maps

UNDERSTANDING

WORK FLOW MODELS

Mission and Goals Laws and Regulations Strategies and Policies


RULEBASE

Architecture Rule Designs

BUSINESS RULE

ENGINE

Rule Specifications Rule Code

Business Rules If [Conditions Events] Then [Conclusions Decisions Actions] [Goals]



DATA MODELS



Rule Family Tables Business Logic Models

EVENT MODELS BUSINESS DECISION MODELS

Decision Model Diagrams

BRE > Code

BDMS > BRMS

BDM / BDMS

BRMS > BRE

DBMS Model

DATABASE

Data Table Designs

DBMS SQL DDL DML

BPM / BPMN

BPMN > BPMS

BPMS > Programs

DBMS / Database Engine Programs > Code

Legal Entities Management Entities

Suppliers Customers Regulators

PLACES Locations

Jurisdictions


30

CONFIDENTIAL & PROPRIETARY Copyright © 2002-2008 BizRules is a registered trademark of BizRules.com

Decisions and Rules are the glue that connects the elements of the Enterprise Architecture and aligns the systems to strategies

DECISION Condition/Event

Conclusion/Action/Decision Permission/Constraint

WHO people / organization

WHY goal / motivation

31


A general framework for Decision/Rules/Process Integration

Decision Model Condition/Event

Conclusion/Decision/Action Permission/Constraint

Business Rule Model Logic Model

Strategy Mission Vision

Goals & Objectives

User Interface model

WHO people / organization

WHY goal / motivation

32


What do you get when you use a rules architecture framework and knowledge engineering?

Alignment / Quality

The implemented systems (Row 6) align with the business objectives (Rows 1/2 )

Integration

Vertical integration from intention to decision

Horizontal integration of rules with process, code, and data

Flexibility / Time to market

Can change one concept without impacting the entire implementation

Can change things with minimal time, cost, and disruption

Reuse

Standard interchangeable parts

You get success… and a Mission Accomplished!

The Framework

helps you minimize

risk and ensure

success of your

business rules,

decisions, and

process initiatives

33


What will you get without rules architecture knowledge engineering ?

No Alignment / Quality

The implemented systems (Row 6) WILL NOT align with the business objectives (Rows 1/2 )

No Integration

NO Vertical integration from intention to decision

NO Horizontal integration of rules process, code, and data

No Flexibility / Time to market

Changing one concept IS LIKELY TO impact the entire implementation

Changing things takes more time, costs more money, causes destruction

No Reuse

NO Standard interchangeable parts

You get to hope and pray that the whole system doesn’t fall like dominoes


Good luck! Rolando Hernandez

Rules Coach

BIZRULES

BIZRULES has been helping Fortune 500 firms and large government agencies document business rules

and preserve expert knowledge since 1995