Your SlideShare is downloading. ×
0
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
Me2011 presentation by Victoria Torres
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

Me2011 presentation by Victoria Torres

820

Published on

Turning Method Engineering into Reality

Turning Method Engineering into Reality

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
820
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
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. Turning Method Engineering Support into Reality<br />MARIO CERVERA, MANOLI ALBERT, <br />VICTORIA TORRES AND VICENTE PELECHANO<br />
  • 2. Agenda<br />Motivation<br />Overview of the proposal<br />MDD infrastructure<br />Methodological framework<br />Real aplication contexts<br />Prototype demo<br />Conclusions and further work<br />
  • 3. 1of4<br />Motivation<br />Method Engineering is defined as the engineering discipline to design, construct and adapt methods, techniques and tools for the development of Information Systems.<br />S. Brinkkemper (1996)<br />
  • 4. 2of4<br />Motivation<br />Method Engineering is defined as the engineering discipline to design, construct and adaptmethods, techniques and tools for the development of Information Systems.<br />S. Brinkkemper (1996)<br />Proposals:<br /><ul><li>Brinkkemper
  • 5. Ralyté
  • 6. Henderson-Sellers</li></li></ul><li>3of4<br />Motivation<br />Method Engineering is defined as the engineering discipline to design,constructandadaptmethods, techniques and tools for the development of Information Systems.<br />S. Brinkkemper (1996)<br />metaCASEenvironments:<br /><ul><li>MetaMOOSE
  • 7. KOGGE
  • 8. MetaEdit+</li></li></ul><li>4of4<br />Motivation<br />Method Engineering is defined as the engineering discipline to design, construct and adapt methods, techniques and tools for the development of Information Systems.<br />S. Brinkkemper (1996)<br />Butlack of feasibleproposalsfor complete supportto ME<br />Proposal:<br /><ul><li>Adoptingexisting ME techniquesformethodbuilding
  • 9. Intensive use of MDD
  • 10. Prototypedevelopmentbasedon Eclipse</li></li></ul><li>1of2<br />Overview of theproposal<br />Software Platform<br />Configured Method Model<br />Method Model<br />Method Process Support<br />ProcessEngine<br />references<br />references<br />references<br />Method Product Support<br />Asset Base<br />Method Base<br />Method Configuration<br />Method Design<br />Method Implementation<br />
  • 11. 2of2<br />Overview of theproposal<br />Software Platform<br />Method Model<br />Configured Method Model<br />Method Process Support<br />ProcessEngine<br />references<br />references<br />references<br />Method Product Support<br />Method Base<br />Asset Base<br />Method Design<br />Method Configuration<br />Method Implementation<br />MethodEngineer<br />ModelTransformation<br />
  • 12. 1of1<br />MDD infrastructure<br />Meta-modeling:<br /><ul><li>SPEM
  • 13. Methodfragments</li></ul>Modeltransformations:<br /><ul><li>Modeltotexttransformation (XPand)
  • 14. From a Methoddescriptiontoits CASE tool</li></ul>Software Platform<br />Configured Method Model<br />Method Process Support<br />ProcessEngine<br />Method Product Support<br />ModelTransformation<br />
  • 15. 1of5<br />Methodological framework<br />Method Design<br />-- Building a generic description of the SPM --<br />Method Model<br /><ul><li>By means of a SPEM model that contains:
  • 16. The fragments of the method (tasks, products, roles)
  • 17. The process of the method
  • 18. Fragments and process parts can be designed:
  • 19. From scratch
  • 20. Based on existing fragments (from the Method Base)</li></ul>Method Base<br />Method Design<br />
  • 21. 2of5<br />Methodological framework<br />Method Design<br />-- Building a generic description of the SPM --<br /><ul><li>Editor to build the Method Model
  • 22. EPF Composer editor
  • 23. Method Base Repository (plugin)
  • 24. Support to Method fragment Integration
  • 25. Support to fragment search
  • 26. Guide to Build the method model
  • 27. Cheat sheet</li></li></ul><li>3of5<br />Methodological framework<br />Method Configuration<br />-- Building a specific description of the SPM --<br />Configured Method Model<br /><ul><li>By means of associations between fragments and software assets:
  • 28. New assets
  • 29. Using the infrastructure provided by Eclipse (e.g. EMF)
  • 30. Existing Software Assets
  • 31. From the Asset Base</li></ul>references<br />references<br />references<br />Asset Base<br />Method Configuration<br />
  • 32. 4of5<br />Methodological framework<br />Method Configuration<br />-- Building a specific description of the SPM --<br /><ul><li>Asset Base Repository (plugin)
  • 33. Support to task/product configuration
  • 34. Support to asset search
  • 35. Guide to Configure the Method Model
  • 36. Cheat sheet </li></li></ul><li>5of5<br />Methodological framework<br />Method Implementation<br />-- Automating as much as possible the CASE construction --<br />Software Platform<br />Method Process Support<br />ProcessEngine<br />Method Product Support<br />Method Implementation<br />1<br />2<br />3<br />Identify Software Resources<br />Solve <br />Dependen-cies<br />Software Resources Deployment<br /><ul><li>Model-to-Text transformation</li></ul><br /><br />MPS Model<br />CASE Tool<br />Productconfigurationfile<br />(partial)<br />Productconfigurationfile<br />(complete)<br />
  • 37. 5of5<br />Methodological framework<br />Method Implementation<br />-- Automating as much as possible the CASE construction --<br /><ul><li>Model-to-Text transformation</li></li></ul><li>1of3<br />Real application contexts<br />Industrial Domains:<br /><ul><li>PublicAdministration
  • 38. Valencian Regional Ministry of Infrastructure and Transport
  • 39. EmbeddedSystems
  • 40. Open Platform for the Engineering of Embedded Systems - itea2
  • 41. www.opees.org</li></li></ul><li>2of3<br />Real applicationcontexts<br />Public Administration<br />MDD<br />Método-V<br />AUP<br />RUP<br />Virtual FiniteState Machine<br />Programación Estructurada<br />Prototipado<br />MétricaIII<br />Proceso Unificado Ágil<br />RAD<br />OOP<br />Desarrollo de Software Dirigido por Modelos<br />Programación Orientada a Objetos<br />XP<br />VFSM<br />Proceso Unificado Racional<br />Programación Extrema<br />Desarrollo de Aplicaciones Rápido<br />Scenario:<br /> MÉTRICA III adaptationtothe CIT necessities: gvMétrica<br /> Use of anexistingtool: PowerDesigner<br />Adaptingthemethodologytothetool<br />Usability, integration, methodologyevolution, etc.<br />
  • 42. 3of3<br />Real applicationcontexts<br />Embedded Systems<br />Caveat<br />TINA<br />Topcased<br />UNISIM<br />MFM<br />Papyrus<br />PLUM<br />AGATHA<br />MOSKitt4ME<br />CADP<br />Gene Auto<br />ATL<br />Frama-C<br />SolFa<br />Acceleo/Eclipse MTL<br />Scenario:<br /> Integration of disparate components<br /> Ensuring long-term availability of critical/embedded systems<br /> Target domains: automotive, avionics, aerospace, energy, health, telecom<br />Componentsintegration, methodologyevolution, etc.<br />
  • 43. 1of1<br />Prototype demo<br />MOSKitt4ME demos:<br /><ul><li>SPM Design
  • 44. SPM Configuration &amp; Implementation
  • 45. SPM Execution</li></ul>4ME<br />
  • 46. 1of2<br />Conclusions and further work<br /><ul><li>MDE facilitates the semi-automatic generation of the supporting CASE tools
  • 47. MOSKitt environment used for both, the CAME and CASE part
  • 48. The CASE tool:
  • 49. Product part successfully supported by the Eclipse plugin architecture (providing the flexibility required by SME)
  • 50. Process part common for all SPM’s
  • 51. Big community behind the Eclipse project
  • 52. Take advantage of new developed tools</li></li></ul><li>2of2<br />Conclusions and further work<br /><ul><li>This is just the beginning…
  • 53. Implementation of different approaches to SME
  • 54. Project Report Automatic Generation
  • 55. Process Variability Mechanisms
  • 56. Integration with a BPMN2 engine</li></ul>XPand<br />RAS<br />

×