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
About me I m a coach, consultant, speaker, writer, teacher, Engineer Page 2
Why do we model? If you can t describe it, you can t build it. John A. Zachman Understand Trace Maintain Page 3
Standards for Enterprise Models Business Scope BMM Business Concepts VDM BPDM BPMM CMMN SBVR DMN System Logic BPMN Technology Physics ERD SysML UML OCL PRR ODM Component Assemblies Page 4
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? BCS - Dr. Jürgen Pitschke 2003-2013, www.enterprise-design.eu Seite 6
Why all these notations? How to represent the Business Logic? BCS - Dr. Jürgen Pitschke 2003-2013, www.enterprise-design.eu Seite 7
Decision Model and Notation Source: DMN, 1.0, bmi-13-08-01.pdf Seite 8
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
Architecture, Method, Process, Tools Tools: support Process, Method, Architecture Process: application of the method in projects Method: planned step-bystep-procedure Architecture: set of descriptive representations Source: I. Jacobson, Object-Oriented Software Engineering Page 10
The Zachman Framework for EA Source: Zachman International www.zachman.com Page 11
What is a model good for? System Model versus Business Model The main purpose of most models is communication between humans. Page 12
Model Views and Model Output Page 13
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 and Models Page 14
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
Business Vocabulary You need a Business Vocabulary to understand. Page 16
Business Rules and Business Analysis Business Vocabulary and Business Rules are used to Scope processes Identify events, activities, actors Describe restrictions BCS - Dr. Jürgen Pitschke 2003-2013, www.enterprise-design.eu Seite 17
Build your team Tool Specialist Project Manager? Business Analyst, Subject Matter Expert, System Designer, Requirements Engineer, Source: I. Jacobson, Object-Oriented Software Engineering Page 18
Build your team Tool Specialist Project Manager Method Team Business Analyst, Subject Matter Expert, System Designer, Requirements Engineer, Source: I. Jacobson, Object-Oriented Software Engineering Page 19
The Method Team enables Business and IT to work together defines the Enterprise Architecture and selects notations selects and defines working techniques and teaches BAs, SME, IT to apply it Page 20
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 jpitschke@enterprise-design.eu Page 22