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.

The WebML innovation cycle

10 years of WebRatio is a good occasion for thinking about the path that led from a university research project to a recognized modeling language (WebML) and a solid, industrialized version of a toolsuite (WebRatio).
The main ingredient of our history are basically:
- a substrate for cross-fertilization coming from European Research projects (W3I3, WebSI, Cooper, BPM4People, ...)
- valuable inputs and requirements from customers (both final customers and software integrators)
- a strong research team that continuously worked on innovating the approach
- the teaching activities within the university
- and the professional developers and analysts at Web Models that work hard for making a good product out of the rough ideas and experiments produced in the university.

These ingredients allowed more than 10 years of evolution of the language and the tool. I tried to summarized this in the virtuous cycle of our experience.

While research provides innovation to both teaching and industrialization, and finally produces the upto date version of the language and methodology.
The tool vendor provides the tool itself and also requirements coming from real industrial customers. The tool is extremely useful for teaching and research purposes not only within our group, but throughout the world (thanks to an academic program that allows education institutions to get free licenses of the tool).
The role of customer is crucial in this picture, because it's from their input (business, technical and UI requirements) that we extract the actual needs of the industry. The whole innovation cycle start there.
Furthermore, customers provide feedback and feasibility/acceptability check upon our findings and solutions.

This virtuous cycle has been able to carry the core idea of the WebML language through 10 years of history in the product (and 15 years of history of the language). The lesson learned is that, if you have a core concept which is flexible and innovable, a good strategy can lead to continuous evolution, improvement and expansion of the idea. In these years the language underwent a huge number of incremental additions:

support of web services
support of business processes
support of semantic web features
support of RIA - AJAX features

If you want to get a flavour of the experience, you may check out this paper, published in John Mylopoulos Festschrift by Springer:S. Ceri, M. Brambilla, P. Fraternali: “The History of WebML Lessons Learned from 10 Years of Model-Driven Development of Web Applications“. In book: Conceptual Modeling: Foundations and Applications, Essays in honor of John Mylopoulos, Springer LNCS, Festschrift series, vol. 5600, 2009, pp. 273-292

  • Login to see the comments

  • Be the first to like this

The WebML innovation cycle

  1. 1. WebML<br />WebML 10 (or 15?) years, without showing it<br />Marco Brambilla<br />Politecnico di Milano<br />marco.brambilla@polimi.itmarcobrambimarcobrambi<br />
  2. 2. Agenda<br /><ul><li>The need
  3. 3. The strategy
  4. 4. The history</li></li></ul><li>The need<br />Abstraction<br />
  5. 5. The need<br />Conceptual modeling<br />Abstraction from the technology<br />.. But NOT <br />From the technological opportunities<br />From the requirements<br />Innovation<br />Extensibility<br />
  6. 6. The Strategy<br />Virtuous innovation cycle<br />
  7. 7. The Strategy<br />Retrospective<br />Virtuous Cycle<br />At two levels:<br />Macro-innovations <br />Refinement of each innovation<br />Repeatability of the experience.. Not granted!<br />
  8. 8. innovation<br />Research <br />(Politecnico)<br />Tool vendor <br />(WebRatio)<br />Toolsuite, industrial requirements<br />Teaching (university courses)<br />innovation<br />toolsuite<br />WebML<br />Design method, language, and platform<br />innovation<br />Customers (requirement providers)<br />requirements<br />use cases<br />Final customers<br />(EU) Research Project consortia<br />Software houses and integrators<br />
  9. 9. The history<br />“Amarcord”?<br />(F. Fellini, 1973)<br />
  10. 10. 1. AutoWeb<br />Once upon a time ...<br /> 1998<br />W3I3 project<br />The research starts<br />
  11. 11. 2. WebML<br />And then ...<br /> 1999<br />Teaching and consolidation at Politecnico<br />
  12. 12. 3. WebML in action<br />And then ...<br />2000<br />The first “customer”<br />
  13. 13. 3. WebML in action<br />And then ...<br />2000<br />The first “customer”<br />No company or product yet<br />Features implemented at night in Italy upon customers request in the US during the day<br /> <br />
  14. 14. 4. Web Services<br />And then ...<br /> 2003<br />SOA, Services, Mashups<br />First research solution:<br />
  15. 15. 4. Web Services<br />And then ...<br /> 2005<br />Refinement and implementation<br />
  16. 16. 5. Business Processes<br />And then ...<br /> 2004<br />Business processes andorchestrations<br />Research proposal:<br />
  17. 17. 5. Business Processes<br />And then ... <br /> 2010<br />Industrial implementation and refinement<br />Directly in the WebRatio tool<br />After a few years (based on customers need)<br />
  18. 18. 6. Semantic Web<br />And then ...<br />2005<br />
  19. 19. 6. Semantic Web<br />Still a research project only<br />But.. What about the future? <br />Linked data, ...<br />
  20. 20. 7. RIA - AJAX<br />And then ...<br /> 2005<br />Rich Web interfaces<br />Theoretical model in the research group<br />And simplified model implemented in the tool immediately available<br />Future: a new, comprehensive model coming up<br />
  21. 21. 8. Social Web / BPM<br />Today<br />
  22. 22. 8. Social Web / BPM<br />Oggi<br />
  23. 23. 9. Standardization<br />Today<br />Strategic effort within OMG (Object Management Group)<br />
  24. 24. 9. ... <br />What about the future?<br />Search, Interfaces, Modernization<br />And...?<br />
  25. 25. Conclusion<br />Virtuous cycle <br />