Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Lessons learned on applying BPM and MDD practices to large banking and industrial scenarios with BPMN, WebML, and WebRatio


Published on

Recent trends combine business process modeling (BPM) with model driven development (MDD) practices at the purpose of increasing the effectiveness of the development of software applications that must comply with business process requirements.
In this chapter we report our experience of applying a MDD approach and tool to a set of representative industrial scenarios: one in the banking field, one focused on marketing content management, and one for managing company administration issues.
To help close the gap between the modeling of business processes and the running software applications, we introduce automatic conversion of business process models (represented with BPMN) into application models (represented with WebML, Web Modeling Language), defined as abstract, platform-independent representations of the application structure and behavior. Application models are themselves amenable to the semi-automatic transformation into application code, resulting in extremely rapid prototyping and shorter time-to-market. We show how the proposed approach, based on a chain of transformations that ultimately produce the source code of the application, has proven effective in different industrial scenarios and we report some quantitative measures that demonstrate the increased development productivity.

Published in: Technology
  • Be the first to comment

Lessons learned on applying BPM and MDD practices to large banking and industrial scenarios with BPMN, WebML, and WebRatio

  1. 1. Lessons learned from applying BPM and MDD practices to a large-scale banking scenario<br />with BPMN, WebML, and WebRatio<br />Marco Brambilla<br />WebRatio - partner, Politecnico di Milano - A. Professor<br />Stefano Butti<br />WebRatio- co-founder and CEO<br />
  2. 2. <ul><li> Overview of the approach
  3. 3. WebRatio BPM
  4. 4. Banking scenario requirements
  5. 5. Organization of the work
  6. 6. Size and effort
  7. 7. Lessons learned
  8. 8. Comparison to other projects
  9. 9. Conclusions</li></ul>Agenda<br />
  10. 10. <ul><li>Model-Driven Development
  11. 11. Not only BP. Also UI, business logics, architectural issues
  12. 12. Reduce development effort, time to market
  13. 13. Increase prototype based interactions
  14. 14. Business Process based applications
  15. 15. Main requirements are driven by processes and flowing data
  16. 16. Web/SOA environment
  17. 17. Wrap and reuse legacy systems
  18. 18. Build new applications with SOA backend for (future) integration and reuse needs</li></ul>Our approach: BPM + MDD + SOA<br />
  19. 19. Different models concur to define the application requirements:<br />1. Design the Model<br />
  20. 20. The generation rules used by WebRatio for building the final Web application are fully customizable and extensible. More specifically, you can define:<br />2. Customize the Rules<br />
  21. 21. Starting from the models and rules defined in the previous steps, WebRatio is able to automatically generate the final application. The result is:<br />astandard and open Java Web application, with no proprietary runtime<br />deployable on any Java Application Server<br />3. Generate the Application<br />Process layer<br />Presentation layer<br />Visual identity<br />Business layer<br />Servicelayer<br />Datalayer<br />Integrationlayer<br />Standard Java<br />Web application<br />IBMWebSphere<br />Caucho Resin<br />ApacheTomcat<br />OracleApplicationServer<br />JBoss<br />Application Server<br />
  22. 22. <ul><li>Major leasing holding in Europe
  23. 23. 2,900 employees, 17 European countries
  24. 24. products sold through 10,000 branches of the group
  25. 25. porting the entire software infrastructure from a legacy canned environment to an open and configurable platformcombining
  26. 26. BPM
  27. 27. Model-Driven development
  28. 28. SOA
  29. 29. On one pilot country first, and then throughout Europe</li></ul>Banking scenario<br />
  30. 30. Size<br /><ul><li> The pilot application covers 52 business processes, comprising more than 1,100 activities spanning 30 user roles. </li></ul>Effort<br /><ul><li>Distribution:
  31. 31. 18% for BP analysis and modeling,
  32. 32. 12% for wrapping existing legacy procedures in SOA
  33. 33. 55% for the design and refinement of the application models
  34. 34. ...</li></ul>Application size and effort<br />
  35. 35. <ul><li>Awareness and willingness
  36. 36. Understanding
  37. 37. customers were able to discuss the process models but they weren't actually able to focus on the actual issues
  38. 38. Continuous feedback and prototyping
  39. 39. Several processes issues were identified only through feedbacks on the running application prototypes
  40. 40. Separation of concerns
  41. 41. BPM is not everything! BPM, Data model, Application model, EA (SOA)
  42. 42. Teamwork
  43. 43. Evolution support
  44. 44. Process versioning</li></ul>Lessons learned <br />
  45. 45. <ul><li> 12 mid-size business process models
  46. 46. Fairly simple processes are often used. Trivial ones?!
  47. 47. The share of effort:
  48. 48. 12% process analysis
  49. 49. 53% application modeling
  50. 50. 20% graphical style
  51. 51. General purpose application to be sold as off-the-shelf vertical to SMEs
  52. 52. It condensates requirements from several concrete cases</li></ul>CMS (Content Management System)<br />Project and order management<br />
  53. 53. <ul><li> Good interaction and complementarity between:
  54. 54. Software producer (WebRatio)
  55. 55. Research center (Politecnico di Milano)
  56. 56. Big industrial customers (Unicredit, Acer, ... and bigger ones I’ll tell you about in private)
  57. 57. Extremely high value of real, running prototypes for interaction with customers
  58. 58. Separation of concerns and identification of interface between different roles</li></ul>Conclusion<br />
  59. 59. Some resources<br /><br /><br /> + slideshare, twitter, linkedin, youtube<br />FREE BPM editor and prototype generation<br />We were at the BPM 2010 conference in Hoboken, NJ<br />
  60. 60. Questions?<br />Marco Brambilla <br />, @marcobrambi<br />Stefano Butti<br />, @stebutti<br />Thank you for your attention<br />