Your SlideShare is downloading. ×
0
BPMDS’08 MONTPELLIER, FRANCE How to simplify the evolution of business process lifecycles Dr Alexander Samarin
The goal  –  easy evolution of business process lifecycles <ul><li>Experience shows that business wants separate requests ...
BPM and BPM systems <ul><li>Definition of BPM (as a discipline): </li></ul><ul><ul><li>BPM allows you to  model ,  execute...
BPM view of the business (1) <ul><li>The business is driven by  business events </li></ul><ul><li>For each business event ...
BPM view of the business (2) <ul><li>Each business activity operates with some  business objects </li></ul><ul><li>A group...
Architecting an enterprise BPM system (with systems thinking) <ul><li>A BPM system is a dynamic set of artefacts  </li></u...
Principal artefacts: services and processes <ul><li>The business world understood a long time ago that services and proces...
Relationships between services and processes <ul><li>All processes are services </li></ul><ul><li>Some operation(s) of a s...
All BPM artefacts <ul><ul><li>added-value chain </li></ul></ul><ul><ul><li>events </li></ul></ul><ul><ul><li>processes </l...
Main architecting principles <ul><li>All artefacts must be evolved to become  digital ,  external  and  virtual </li></ul>...
Improvement of artefacts <ul><li>Digitalised – available in electronic form </li></ul><ul><li>Externalised – available as ...
Relationships between artefacts <ul><li>Reveal all hidden relationships and structure them  </li></ul><ul><ul><li>Examples...
Explicit and executable models <ul><li>Process model is an aggregation of  </li></ul><ul><ul><li>events, activities, roles...
Synergy between BPM and SOA <ul><li>SOA is an architectural approach for constructing complex software-intensive systems f...
Role of architecture <ul><li>Consider a complex and dynamic system with many artefacts, relationships, stakeholders </li><...
An architectural framework for improving BPM systems  <ul><li>Considerable reduction of Total Cost of Ownership (TCO) </li...
Modelling of executable business processes <ul><li>Diagramming style in BPMN </li></ul><ul><li>A dozen practical patterns ...
Diagramming style in BPMN 2008-06-17   How to simplify the evolution of business process lifecycles
The modelling procedure <ul><li>Its purpose is: </li></ul><ul><ul><li>to analyse a building block (what it is supposed to ...
Four phases 2008-06-17   How to simplify the evolution of business process lifecycles
Blackboxing phase <ul><li>The purpose  </li></ul><ul><ul><li>to analyse a building block as a whole </li></ul></ul><ul><ul...
Structuring phase (1) <ul><li>Steps </li></ul>2008-06-17   How to simplify the evolution of business process lifecycles
Structuring phase (2) <ul><li>Steps and artefacts </li></ul>2008-06-17   How to simplify the evolution of business process...
Re-construction phase <ul><li>The diagram </li></ul>2008-06-17   How to simplify the evolution of business process lifecyc...
Instrumentation phase <ul><li>The diagram </li></ul>2008-06-17   How to simplify the evolution of business process lifecyc...
Conclusions <ul><li>The formal expression of relationships enables their automated validation </li></ul><ul><li>The aggreg...
Thank you! <ul><li>Contact information: </li></ul><ul><li>+41 76 573 40 61 </li></ul><ul><li>[email_address] </li></ul>200...
Principles of the modelling procedure <ul><li>it treats human and automated activities equally </li></ul><ul><li>it is pri...
<ul><li>An enterprise solutions architect </li></ul><ul><ul><li>From a programmer to a systems architect  </li></ul></ul><...
<ul><li>Current specialisation is improving business process management systems </li></ul><ul><ul><li>effectiveness (“Do t...
Pattern DBL Decoupled Business Logic  2008-06-17   How to simplify the evolution of business process lifecycles
Anti-Pattern PRF Process Realisation Faked 2008-06-17   How to simplify the evolution of business process lifecycles
Structuring phase (1) <ul><li>The purpose  </li></ul><ul><ul><li>to analyse a building block from within to determine its ...
Re-construction phase (1) <ul><li>The purpose  </li></ul><ul><ul><li>to synthesize an initial version of the formal coordi...
Instrumentation phase (1) <ul><li>The purpose  </li></ul><ul><ul><li>to enrich the process skeleton by adding more automat...
An architectural framework for improving BPM systems  <ul><li>A comprehensive set of recommendations, models, patterns and...
Upcoming SlideShare
Loading in...5
×

How to simplify the evolution of business process lifecycles

2,814

Published on

Presentation at the BPMDS’08, Montpellier, France

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,814
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
113
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Transcript of "How to simplify the evolution of business process lifecycles"

  1. 1. BPMDS’08 MONTPELLIER, FRANCE How to simplify the evolution of business process lifecycles Dr Alexander Samarin
  2. 2. The goal – easy evolution of business process lifecycles <ul><li>Experience shows that business wants separate requests for change to be implemented quickly </li></ul><ul><li>These changes are typically small (from the point of view of the business) and unpredictable (from the point of view of IT) </li></ul><ul><li>To carry out these changes easily and in a managed way, BPM systems must be properly architected and implemented </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  3. 3. BPM and BPM systems <ul><li>Definition of BPM (as a discipline): </li></ul><ul><ul><li>BPM allows you to model , execute , control , automate , measure and optimise the flow of business activities that span your enterprise’s systems, people, customers and partners within and beyond your corporate boundaries </li></ul></ul><ul><li>Obviously, all enterprises have their own BPM system, but often a BPM system: </li></ul><ul><ul><li>is a “problem” of its history, </li></ul></ul><ul><ul><li>suffers from problems of complexity, inefficiency </li></ul></ul><ul><li>Not surprisingly, many enterprises want to improve their BPM systems </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  4. 4. BPM view of the business (1) <ul><li>The business is driven by business events </li></ul><ul><li>For each business event there is an associated business process to be executed </li></ul><ul><li>A business process coordinates the execution of business activities </li></ul><ul><li>The execution is carried out in accordance with business rules </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  5. 5. BPM view of the business (2) <ul><li>Each business activity operates with some business objects </li></ul><ul><li>A group of staff members ( business roles ) is responsible for the execution of each human activity </li></ul><ul><li>The execution of business processes produces audit trails , which are used for the calculation of key performance indicators </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  6. 6. Architecting an enterprise BPM system (with systems thinking) <ul><li>A BPM system is a dynamic set of artefacts </li></ul><ul><li>Artefacts are interconnected and interdependent </li></ul><ul><li>We have to anticipate potential changes: </li></ul><ul><ul><li>policies, priorities, compliance, technology, etc. </li></ul></ul><ul><li>Implementation of such changes necessitates the evolution of some artefacts and the relationships between them </li></ul><ul><li>It must be easy to modify all artefacts and relationships without causing any negative effects </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  7. 7. Principal artefacts: services and processes <ul><li>The business world understood a long time ago that services and processes are the backbones of most businesses </li></ul><ul><li>The IT world recently “re-discovered” and accepted the notion of services, and so emerged SOA </li></ul><ul><li>But IT is still not very comfortable with processes (often, an application is a mixture of data-entry and workflow-driven approaches) </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  8. 8. Relationships between services and processes <ul><li>All processes are services </li></ul><ul><li>Some operation(s) of a service can be implemented as a process </li></ul><ul><li>A process may include services in its implementation </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  9. 9. All BPM artefacts <ul><ul><li>added-value chain </li></ul></ul><ul><ul><li>events </li></ul></ul><ul><ul><li>processes </li></ul></ul><ul><ul><li>rules </li></ul></ul><ul><ul><li>activities </li></ul></ul><ul><ul><li>roles </li></ul></ul><ul><ul><li>objects (data structures) </li></ul></ul><ul><ul><li>objects (documents) </li></ul></ul><ul><ul><li>audit trails </li></ul></ul><ul><ul><li>performance indicators </li></ul></ul><ul><ul><li>services </li></ul></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  10. 10. Main architecting principles <ul><li>All artefacts must be evolved to become digital , external and virtual </li></ul><ul><li>All artefacts must be versionable throughout their lifecycle </li></ul><ul><li>All relationships between these artefacts are modelled explicitly </li></ul><ul><li>All models are made to be executable </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  11. 11. Improvement of artefacts <ul><li>Digitalised – available in electronic form </li></ul><ul><li>Externalised – available as separate entities with proper definition, naming, versioning, storage, security, traceability, etc. </li></ul><ul><ul><li>e.g. transportation of objects between services </li></ul></ul><ul><li>Virtualised – available independently of traditional IT resources (servers, databases, media, browsers) as services </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  12. 12. Relationships between artefacts <ul><li>Reveal all hidden relationships and structure them </li></ul><ul><ul><li>Examples: </li></ul></ul><ul><ul><li>static (in design phase) </li></ul></ul><ul><ul><li>dynamic (in execution phase) </li></ul></ul><ul><ul><li>composition (from atomic artefacts to a composite artefact) </li></ul></ul><ul><ul><li>instantiation (from a template to instances) </li></ul></ul><ul><ul><li>compatibility (between different versions) </li></ul></ul><ul><li>If possible, model relationships as formal, explicit, traceable, testable, secure, SLA aware and executable </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  13. 13. Explicit and executable models <ul><li>Process model is an aggregation of </li></ul><ul><ul><li>events, activities, roles, objects, rules, audits, etc. </li></ul></ul><ul><li>Versioning is vital </li></ul><ul><li>In an implementation, a model acts as a skeleton or foundation to which we attach services ( what you design is what you execute ) </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  14. 14. Synergy between BPM and SOA <ul><li>SOA is an architectural approach for constructing complex software-intensive systems from a set of universally interconnected and interdependent building blocks, called services (stand-alone units of functionality) </li></ul><ul><li>BPM, by revealing the artefacts and the relationships between them, provides the necessary context (e.g. granularity) for the definition of services </li></ul><ul><li>SOA provides recommendations for the implementation, execution and governance of services </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  15. 15. Role of architecture <ul><li>Consider a complex and dynamic system with many artefacts, relationships, stakeholders </li></ul><ul><li>Understand the concerns of each group of stakeholders </li></ul><ul><li>Provide the step-by-step improvement of a system (like the Deming wheel) </li></ul><ul><ul><li>Plan, Do (or implement), Check (or validate), Act (or refactor) </li></ul></ul><ul><li>Consider together different technologies, such as BPM, SOA, ECM, EA and IT governance </li></ul><ul><li>Build an agile system in an agile way </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  16. 16. An architectural framework for improving BPM systems <ul><li>Considerable reduction of Total Cost of Ownership (TCO) </li></ul>v.1 v.2 v.3 v.4 Life-cycle TCO First BPM/SOA project Further BPM/SOA projects Maintenance approx. 80 % Initial development approx. 20 % Typical IT projects 2008-06-17 How to simplify the evolution of business process lifecycles
  17. 17. Modelling of executable business processes <ul><li>Diagramming style in BPMN </li></ul><ul><li>A dozen practical patterns </li></ul><ul><li>Structuring for better “executability” </li></ul><ul><li>Modelling procedure </li></ul><ul><li>Tool for prototyping – Intalio BPM suite </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  18. 18. Diagramming style in BPMN 2008-06-17 How to simplify the evolution of business process lifecycles
  19. 19. The modelling procedure <ul><li>Its purpose is: </li></ul><ul><ul><li>to analyse a building block (what it is supposed to do) </li></ul></ul><ul><ul><li>to synthesise its implementation (how it does this) as explicit coordination of other building blocks (processes or activities) </li></ul></ul><ul><li>It is iterative: we can apply it until we only have left indivisible building blocks (i.e. activities) </li></ul><ul><li>Artefacts are constructed recursively, like Russian dolls </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  20. 20. Four phases 2008-06-17 How to simplify the evolution of business process lifecycles
  21. 21. Blackboxing phase <ul><li>The purpose </li></ul><ul><ul><li>to analyse a building block as a whole </li></ul></ul><ul><ul><li>to discover its functional characteristics and some related artefacts </li></ul></ul><ul><li>The method </li></ul><ul><ul><li>the business story behind this building block should be carefully analysed to recognise its artefacts </li></ul></ul><ul><li>Recommendations </li></ul><ul><ul><li>don’t go into excessive detail for each artefact; this can be done later </li></ul></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  22. 22. Structuring phase (1) <ul><li>Steps </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  23. 23. Structuring phase (2) <ul><li>Steps and artefacts </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  24. 24. Re-construction phase <ul><li>The diagram </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  25. 25. Instrumentation phase <ul><li>The diagram </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  26. 26. Conclusions <ul><li>The formal expression of relationships enables their automated validation </li></ul><ul><li>The aggregation or assembly of services becomes the main implementation activity </li></ul><ul><li>Small cycles “model–implement–test–refactor” considerably simplify both modelling and implementation </li></ul><ul><li>There is a good match between BPM (provision of the context for services) and SOA </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  27. 27. Thank you! <ul><li>Contact information: </li></ul><ul><li>+41 76 573 40 61 </li></ul><ul><li>[email_address] </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  28. 28. Principles of the modelling procedure <ul><li>it treats human and automated activities equally </li></ul><ul><li>it is primarily for capturing the flow of control within a building block, but not for optimisation </li></ul><ul><li>it is a tool for both business and IT (maybe with coaching by a process analyst) </li></ul><ul><li>it provides validation by simulation </li></ul><ul><li>it provides validation by quick prototyping – real services can be invoked </li></ul><ul><li>it is visual programming </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  29. 29. <ul><li>An enterprise solutions architect </li></ul><ul><ul><li>From a programmer to a systems architect </li></ul></ul><ul><ul><li>Experience in scientific, international, governmental and industry environments: CERN, ISO, IOC, BUPA, Groupe Mutuel, State of Geneva, Swiss federal government </li></ul></ul><ul><ul><li>Co-author of the book “The LaTeX Companion” </li></ul></ul><ul><ul><li>Have created systems which work without me </li></ul></ul><ul><ul><li>Practical adviser for design and implementation of enterprise solutions </li></ul></ul>About me (1) 2008-06-17 How to simplify the evolution of business process lifecycles
  30. 30. <ul><li>Current specialisation is improving business process management systems </li></ul><ul><ul><li>effectiveness (“Do the right things”) </li></ul></ul><ul><ul><li>efficiency (“Do the things right”) </li></ul></ul><ul><li>Knowledge how to use together the following technologies: </li></ul><ul><ul><li>BPM, SOA, EA, ECM and IT governance </li></ul></ul>About me (2) 2008-06-17 How to simplify the evolution of business process lifecycles
  31. 31. Pattern DBL Decoupled Business Logic 2008-06-17 How to simplify the evolution of business process lifecycles
  32. 32. Anti-Pattern PRF Process Realisation Faked 2008-06-17 How to simplify the evolution of business process lifecycles
  33. 33. Structuring phase (1) <ul><li>The purpose </li></ul><ul><ul><li>to analyse a building block from within to determine its internal structure and its major artefacts </li></ul></ul><ul><li>The method </li></ul><ul><ul><li>determine the main functional (or logical) steps </li></ul></ul><ul><ul><li>classify artefacts for these steps </li></ul></ul><ul><ul><li>add check-points between steps </li></ul></ul><ul><li>Recommendations </li></ul><ul><ul><li>don’t have more than 7 steps </li></ul></ul><ul><ul><li>avoid loop-back over check-points </li></ul></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  34. 34. Re-construction phase (1) <ul><li>The purpose </li></ul><ul><ul><li>to synthesize an initial version of the formal coordination: some kind of process skeleton </li></ul></ul><ul><li>The method </li></ul><ul><ul><li>add intra-step logic </li></ul></ul><ul><ul><li>start formalising the business objects involved </li></ul></ul><ul><ul><li>collect test scenarios </li></ul></ul><ul><li>Recommendations </li></ul><ul><ul><li>consider implementation of human activities as interactive forms </li></ul></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  35. 35. Instrumentation phase (1) <ul><li>The purpose </li></ul><ul><ul><li>to enrich the process skeleton by adding more automated activities </li></ul></ul><ul><li>The method </li></ul><ul><ul><li>add pools </li></ul></ul><ul><ul><li>apply different practical patterns </li></ul></ul><ul><ul><li>use a business rule engine if available </li></ul></ul><ul><ul><li>collect test scenarios </li></ul></ul><ul><li>Recommendations </li></ul><ul><ul><li>work iteratively (step-by-step) </li></ul></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  36. 36. An architectural framework for improving BPM systems <ul><li>A comprehensive set of recommendations, models, patterns and examples of how to transform existing disparate IT systems into a coherent, agile and flexible BPM/SOA solution </li></ul><ul><li>Documented in soon-to-be-published book www.improving-BPM-systems.com </li></ul><ul><li>Further slides are examples of what this framework brings to different stakeholders </li></ul>2008-06-17 How to simplify the evolution of business process lifecycles
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×