Embed Size (px)
Citation preview
Mastering Business Modeling –(Soft) Skills for Business Analysts
BPM in Practice, October, 2013
Dr. Jürgen Pitschke
BCS – Dr. Jürgen Pitschke
www.enterprise-design.eu
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
About me
I‘m a coach, consultant, speaker, writer, teacher, …
Engineer
Page 2
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Why do we model?
„If you can‘t describe it, you can‘t build it“.
John A. Zachman
Understand – Trace – Maintain
Page 3
BusinessScope
BusinessConcepts
SystemLogic
TechnologyPhysics
ComponentAssemblies
OCL
Standards for Enterprise Models
Page 4
BMM
BPMMBPDM
BPMN
VDM SBVR
ODMPRR
UMLSysML
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
DMNCMMN
ERD
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
How many notations do we need?
• “Every type of model, …, has strengths and weaknesses. As a result each model type is appropriate for certain uses. Effective modelers have a large number of model types in their intellectual toolkit and thereby have a greater chance of using the right technique for the situation that they face.”
Scott Ambler on LinkedIn
Page 5
Why all these notations?
Seite 6© BCS - Dr. Jürgen Pitschke 2003-2013, www.enterprise-design.eu
© BCS - Dr. Jürgen Pitschke 2003-2013, www.enterprise-design.eu
Why all these notations?
• How to represent the Business Logic?
Seite 7
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Decision Model and Notation
Seite 8
Source: DMN, 1.0, bmi-13-08-01.pdf
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
BTW: What is a model?
A model is an abstract presentation of an subject of
interest.
Model Elements: Primitives
Single Variable Models: Primitive Models
Connect Models: Complex Models
A Model is much more than a Picture.
Model ≠ Model Output
Page 9
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Architecture, Method, Process, Tools
• Tools: support Process, Method, Architecture
• Process: application of the method in projects
• Method: planned step-by-step-procedure
• Architecture: set of descriptive representations
Page 10
Source: I. Jacobson, Object-Oriented Software Engineering
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
The Zachman Framework for EA
Page 11
Source: Zachman International™www.zachman.com
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
What is a model good for?
System Model versus Business Model
The main purpose of most models is communication between
humans.
Page 12
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Model Views and Model Output
Page 13
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Define your Architecture
Start with the Content!
• Specify Model Output
• Specify Viewpoints and Views
• Select Primitives
• Specify Single-Variable Models
• Specify Relations between Model Elements andModels
Page 14
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
How notations are often adopted
Learn – Apply – Learn more – Apply more - …
The “hammer-and-nail effect”
The phenomenon of “unwanted learning”
Competencies: “Communication”, “Learning”
Page 15
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Business Vocabulary
• You need a Business Vocabulary to understand.
Page 16
© BCS - Dr. Jürgen Pitschke 2003-2013, www.enterprise-design.eu
Business Rules and Business Analysis
Seite 17
• Business Vocabulary and Business Rules areused to
– Scope processes
– Identify events, activities, actors
– Describe restrictions
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Build your team
• Tool Specialist
• Project Manager
• ?
• Business Analyst, Subject Matter Expert, System Designer, Requirements Engineer, …
Page 18
Source: I. Jacobson, Object-Oriented Software Engineering
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
Build your team
• Tool Specialist
• Project Manager
• Method Team
• Business Analyst, Subject Matter Expert, System Designer, Requirements Engineer, …
Page 19
Source: I. Jacobson, Object-Oriented Software Engineering
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
The Method Team
… enables Business and IT towork together
• … defines the Enterprise Architecture andselects notations
• … selects and defines working techniques andteaches BAs, SME, IT to apply it
Page 20
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu
The only slide you need …
Standard Notations are great.
Content first: You need an architecture.
Be systematic: Define a method to create your architecture.
Apply it to the real world: Build your team!
Page 21
Thank You!
Dr. Jürgen Pitschke
www.enterprise-design.eu
www.row-two.com
© BCS – Dr. Juergen Pitschke 2003-2013, www.enterprise-design.eu Page 22
