Your SlideShare is downloading. ×
0
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Model Driven Method Engineering. A Supporting Infrastructure
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Model Driven Method Engineering. A Supporting Infrastructure

748

Published on

A methodological framework and software architecture to support model driven method engineering

A methodological framework and software architecture to support model driven method engineering

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

  • Be the first to like this

No Downloads
Views
Total Views
748
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Centro de Investigación ProS Model Driven Method Engineering. A Supporting Infrastructure MARIO CERVERA ÚBEDA
  • 2. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 3. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 4. Motivation <ul><li>Software development projects </li></ul><ul><ul><li>High diversity </li></ul></ul><ul><ul><ul><li>Economic resources, duration, etc. </li></ul></ul></ul>1 of 2 <ul><li>Software production methods </li></ul><ul><ul><li>Must be adapted to project needs </li></ul></ul><ul><ul><li>Software support </li></ul></ul><ul><ul><ul><li>CASE environments  Little flexibility </li></ul></ul></ul>
  • 5. Motivation Method Engineering 2 of 2 <ul><li>The engineering discipline to design, construct and adapt methods, techniques and tools for the development of information systems </li></ul><ul><li>(Brinkkemper, 1996) </li></ul>
  • 6. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 7. State of the Art <ul><li>Method Engineering approaches </li></ul><ul><ul><li>Assembly-based, paradigm-based and extension-based </li></ul></ul><ul><li>Method Engineering languages </li></ul><ul><ul><li>ASDM, GOPRR, MEL, MRSL, NATURE, SPEM and ISO/IEC 24744 </li></ul></ul><ul><li>Method Engineering tools </li></ul><ul><ul><li>MERET, Decamerone, MENTOR, Method Editor, MetaEdit+ and MERU </li></ul></ul>1 of 4
  • 8. State of the Art 2 of 4 <ul><li>Method Engineering approaches </li></ul><ul><ul><li>The assembly-based approach is the most common </li></ul></ul><ul><ul><ul><li>Modular vision of methods  Facilitates reusability </li></ul></ul></ul><ul><ul><ul><li>Usually used in combination with the paradigm-based approach </li></ul></ul></ul><ul><ul><li>There is no approach that takes all the 4 method dimensions ( product , process , people and tool ) into account together </li></ul></ul>
  • 9. State of the Art 3 of 4 <ul><li>Method Engineering languages </li></ul><ul><ul><li>Most of them are product-oriented and defined by means of a meta-model </li></ul></ul><ul><ul><li>Latest standardization efforts: SPEM and ISO/IEC 24744 </li></ul></ul><ul><ul><li>Method Engineering proposals that make use of these standards are still non-existent </li></ul></ul>
  • 10. State of the Art 4 of 4 <ul><li>Method Engineering tools </li></ul><ul><ul><li>Two types: CAME 1 and metaCASE environments </li></ul></ul><ul><ul><li>Most of them are non-commercial prototypes </li></ul></ul><ul><ul><li>They provide inadequate coverage of the Method Engineering lifecycle </li></ul></ul><ul><ul><ul><li>CAME tools focus on the method design </li></ul></ul></ul><ul><ul><ul><li>metaCASE tools focus on CASE tool construction </li></ul></ul></ul>1 Computer Aided Method Engineering
  • 11. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 12. Problem Statement <ul><li>Many theoretical proposals in Method Engineering </li></ul><ul><li>Standards are hardly used </li></ul><ul><li>Lack of software support </li></ul><ul><ul><li>Incomplete prototypes </li></ul></ul><ul><ul><ul><li>Only one tool (MetaEdit+) has been commercialized </li></ul></ul></ul><ul><ul><li>High complexity </li></ul></ul>1 of 1
  • 13. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 14. Proposed Solution 1 of 7 <ul><li>Methodological Framework to support from a MDD perspective the specification of methods and the generation of the CASE tool support </li></ul>
  • 15. Proposed Solution 2 of 7 <ul><li>Method Design </li></ul><ul><ul><li>Construction of the method model following the SPEM standard </li></ul></ul><ul><ul><li>This construction can be performed from scratch or reusing method fragments </li></ul></ul><ul><ul><li>These fragments are stored in the Method Base repository following the RAS standard </li></ul></ul><ul><ul><li>This model does not contain technological details </li></ul></ul>
  • 16. Proposed Solution 3 of 7 <ul><li>Method Configuration </li></ul><ul><ul><li>Configuration of the method built in the previous step </li></ul></ul><ul><ul><li>Technical fragments stored in the Asset Base repository are associated to the tasks and products of the method </li></ul></ul><ul><ul><li>These fragments contain transformations, editors, etc. that will support the method elements in the generated CASE tool </li></ul></ul><ul><ul><li>This model contains technological details </li></ul></ul>
  • 17. Proposed Solution 4 of 7 <ul><li>Method Implementation </li></ul><ul><ul><li>A software tool supporting the method is generated from the method model by means of model transformations </li></ul></ul><ul><ul><li>This software tool supports: </li></ul></ul><ul><ul><ul><li>Product part  Technical fragments </li></ul></ul></ul><ul><ul><ul><li>Process part  Process engine </li></ul></ul></ul>
  • 18. Proposed Solution 5 of 7 <ul><li>A software architecture for supporting the methodological framework </li></ul>
  • 19. Proposed Solution 6 of 7 EPF Composer Cheatsheets Eclipse view 4ME
  • 20. Proposed Solution 7 of 7 4ME
  • 21. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 22. Case Study 1 of 5 <ul><li>The OOWS-BP method </li></ul>
  • 23. Case Study 2 of 5 <ul><li>Method Design </li></ul>Process Roles Products Tasks
  • 24. Case Study 3 of 5 <ul><li>Method Configuration </li></ul>Technical fragments Association of a Product with a Technical Fragment
  • 25. Case Study 4 of 5 <ul><li>Method Implementation </li></ul>MOSKitt Transformation Manager Transformation Wizard Product Configuration File Export Wizard
  • 26. Case Study 5 of 5 <ul><li>Method Implementation </li></ul>Final CASE tool Product Configuration File
  • 27. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 28. Main Contributions 1 of 1 <ul><li>Application of the MDD paradigm in the Method Engineering field </li></ul><ul><ul><li>Method definition  Models </li></ul></ul><ul><ul><li>CASE tool generation  Model transformations </li></ul></ul><ul><li>Definition of a methodological approach and development of a prototype that make use of an standard language (SPEM) </li></ul><ul><li>Coverage of the four dimensions of methods </li></ul><ul><li>Coverage of both the method design and implementation </li></ul><ul><li>Definition of a software architecture that establishes the required components to support Model Driven Method Engineering </li></ul>
  • 29. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 30. Future Work 1 of 1 <ul><li>Process engine </li></ul><ul><ul><li>Integration with </li></ul></ul><ul><li>Method as a Service </li></ul><ul><li>Method variability </li></ul><ul><li>Megamodeling </li></ul>
  • 31. Agenda <ul><li>Motivation </li></ul><ul><li>State of the Art </li></ul><ul><li>Problem Statement </li></ul><ul><li>Proposed Solution </li></ul><ul><li>Case Study </li></ul><ul><li>Conclusions </li></ul><ul><ul><li>Main Contributions </li></ul></ul><ul><ul><li>Future Work </li></ul></ul><ul><ul><li>Publications </li></ul></ul>
  • 32. Publications 1 of 1 <ul><li>Cervera, M. , Albert, M., Torres, V., Pelechano, V.: A Methodological Framework and Software Infrastructure for the Construction of Software Production Methods . International Conference on Software Processes (2010) </li></ul><ul><ul><li>ICSP is classified as A in the CORE australian ranking </li></ul></ul><ul><li>Cervera, M. , Albert, M., Torres, V., Pelechano, V., Cano, J., Bonet, B.: A Technological Framework to support Model Driven Method Engineering . 7th Taller sobre Desarrollo de Software Dirigido por Modelos (2010) </li></ul><ul><li>Cervera, M. , Albert, M., Torres, V., Pelechano, V.: Turning Method Engineering Support into Reality . To be published in: the 4th IFIP WG8.1 Working Conference on Method Engineering (2011) </li></ul>
  • 33. Thanks Model Driven Method Engineering. A Supporting Infrastructure Mario Cervera Úbeda– mcervera@pros.upv.es

×