Why Systems Work

50 %
50 %
Information about Why Systems Work
Business & Mgmt

Published on November 7, 2008

Author: RolandoHernandez

Source: slideshare.net

Description

Why systems work, change, and last. Presented at October Rules Fest ORF2008 (www.rulesfest.org)

Why Systems Work CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008  BizRules is a registered trademark of BizRules.com 1

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

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

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

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

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

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

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

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

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

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

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

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

The bridge between  business and IT CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008  BizRules is a registered trademark of BizRules.com 14

Business and IT are in different worlds Business Technology Dollars Data CONFIDENTIAL & PROPRIETARY Copyright © 2002‐2008  BizRules is a registered trademark of BizRules.com 15

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

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

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

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

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

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

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

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

TM ENTERPRISE ARCHITECTUREA Framework TM Enterprise Architecture – - A FRAMEWORK Complete “Data Model” Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE to the Business Business Performs the Business Operates Important to the Business to the Business (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model

Add a comment

Related presentations

Related pages

How Sewer and Septic Systems Work - Why Do We Need a Sewer ...

Why Do We Need a Sewer System? - Each time you flush the toilet or wash something down the drain, you create sewage. Find out where it goes before it flows ...
Read more

How Ignition System Works - YouTube

Know the basic working of an automobile ignition system working on battery.
Read more

How a septic tank works - YouTube

How a septic tank works ... Why We Had a Septic System Installed ASAP by Contractors - Duration: 25:14. Pure Living for Life 87,074 views.
Read more

Why To Work for SAP? - SAP Software Solutions | Technology ...

Why Work at SAP? Studio SAP ... we deploy new systems, we ... Why To Work for SAP? Subject: Why to work for SAP infographic
Read more

Why Nutrisystem Works - What is Nutrisystem®? How Does ...

Nutrisystem is a convenient, easy to follow weight loss program. Discover how Nutrisystem diet plans work in four easy steps!
Read more

How Do Global Positioning Systems, or GPS, Work? | NASA

Product Type: Video Learning Clip Audience: Educators, Students Grade Levels: K-8 Year: 2005 Subjects: Technology A NASA expert explains why GPS ...
Read more

How Payroll Systems Work - Money | HowStuffWorks

Payroll systems help employers meet their financial responsibilities to their employees and ... How Payroll Systems Work. ... That's why all businesses ...
Read more

How the Solar System Works - UW-Green Bay

How the Solar System Works. Steven Dutch, Natural and Applied Sciences, University of Wisconsin - Green Bay First-time Visitors: Please visit Site Map and ...
Read more

How Does It Work - TomTom, portable GPS car navigation systems

How does GPS work? With modern navigation technology you always know your location and where to go. But how does it all work?
Read more

How Burglar Alarms Work | HowStuffWorks - Home & Garden ...

How Burglar Alarms Work. ... These systems range from do-it-yourself kits you can pick up for $10 to sophisticated whole-house security networks that ...
Read more