A Framework A Framework for for Business Process Business Process Architecture Architecture Brett Champlin, MBA, CSP/CCP VP Online Services, DAMA International Board of Directors & Vice President, ICCP Adjunct Faculty, Heller College of Business, Roosevelt University Process Center of Expertise, Allstate Insurance Company
28
Embed
A Framework for Business Process Architecture Brett Champlin, MBA, CSP/CCP VP Online Services, DAMA International Board of Directors & Vice President,
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
A Framework A Framework for for Business Process ArchitectureBusiness Process Architecture
Brett Champlin, MBA, CSP/CCP
VP Online Services, DAMA International Board of Directors & Vice President, ICCP
Adjunct Faculty, Heller College of Business, Roosevelt UniversityProcess Center of Expertise, Allstate Insurance Company
Business Integration & Web Services Conference – Chicago, April 22, 200322
Do you know where your processes are?Do you know where your processes are?• Are you doing Process Re-Design?
– Reengineering? Improvement?
• Are you implementing Workflow?– Document Management? Task Management?
• What’s a core process?– Support Process? Control Process?
• What’s the difference between a Process– Activity, Task, Operation, Method
• Where do you put all those process models and designs?
• Should you buy a Process Modeling, Process Engineering, or Business Process Management package?
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200333
Business Process ArchitectureBusiness Process Architecture
• Business NOT Systems Architecture• Define the Key Terms and Components
– “the stack”
• Represent Key Points of View• Support Process Innovation Methods• Support Process Management Program• The Business “Blueprint”
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200344
A Short StoryA Short Story
The Three Stone Masons
• Imagine a 14th Century Monk
• An Encounter with 3 Stone Masons
• Carving Stones
• Building a Wall
• Building a Cathedral
• Context
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200355
A Process Architecture is built with models
as a house is built with stones
- but a collection of models is no more a
Process Architecture than a heap of stones is a
house.(with apologies to Poincare)
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
Business Integration & Web Services Conference – Chicago, April 22, 200366
Introduction
A Short Story
The ZachmanFramework
A BusinessProcess
Framework
The Goal
How to Build It
Benefits
Discussion
“A rock pile ceases to be a rock pile
the moment a single man [sic] contemplates it,
bearing within him the image of a cathedral”
- Antoine de Saint Exupery, author and aviator (1900-1945)
Business Integration & Web Services Conference – Chicago, April 22, 200377
The Zachman Information Systems ArchitectureThe Zachman Information Systems Architecture
BUSINESSSCOPEBUSINESSSCOPE
BUSINESSMODELBUSINESSMODEL
INFORMATIONSYSTEMSMODEL
INFORMATIONSYSTEMSMODEL
TECHNOLOGYMODELTECHNOLOGYMODEL
TECHNOLOGYDEFINITIONTECHNOLOGYDEFINITION
INFORMATIONSYSTEMINFORMATIONSYSTEM
List of things important to the business.
ENTITY: class of business thing
List of processes the business performs
PROCESS: class of business processes.
List of locations in which the business operates
NODE: business location.
DATADATA PROCESSPROCESS LOCATIONLOCATION
Business entities & their inter-relationships
Flows between business processes
Communications links between locations
ENTITY: business entityREL'SHIP: business rule
PROCESS: business processI/O: business resource (including information)
NODE: business unitLINK: business relationship (org., product, information)
Model of the business dataand inter-relationships
Flows between application functions
Distribution network
ENTITY: data entityRELTNSHIP: data relationship
NODE: I.S. function (processor, storage, etc.).LINK: line characteristics
Database Design System Design System Architecture
ENTITY: segment, row, recordRELTNSHP: pointer, key, index