1 / 11

EMWDA Working Group on MDA is the Wrong Answer

EMWDA Working Group on MDA is the Wrong Answer. I ssue. MDA is the wrong answers What is the question. Oliver Sims Andrew Watson Jos Warmer Tracy Gardner Dave Pilfold Tony Mallia Ian de Beer Marcus Alanen. Nelly Bencomo Lea Kutvonen. P eople Attending. What is the Problem.

morwen
Download Presentation

EMWDA Working Group on MDA is the Wrong Answer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMWDA Working Group on MDA is the Wrong Answer

  2. Issue • MDA is the wrong answers • What is the question

  3. Oliver Sims Andrew Watson Jos Warmer Tracy Gardner Dave Pilfold Tony Mallia Ian de Beer Marcus Alanen Nelly Bencomo Lea Kutvonen. People Attending

  4. What is the Problem • Sw. Dev’t is tedious • There has to be a better way • Higher quality • Documentation generation • Application Generation • Lack of “chauffeurs” • 60% of IT projects fail

  5. The Problem • Survive technology changes • Support for collaboration • Building better product lines • Integration of SOA, Workflow, Bus. Rules, etc. • Relationships between domains • Avoiding getting into the same problem again

  6. Advantages of the solution • MDA allows separation between technology and business in product lines • 40% overall savings measured • MDA is the catalyst (glue) to combine different issues

  7. Why MDA won’t work • CASE and Shlear Mellor failed • Lack of will to change • no formalized process • Not relevant to many area’s like GUI’s • MDA is too vague • UML is too complicated • Dev’t is not a problem to managers

  8. Why MDA won’t work • Fear of loss of jobs • UML is not at a high enough abstraction level • Lack of tools • No tools from big vendors • Vendors will make proprietary models

  9. To Be Done • Better Tools, better tools, better tools • Clarify new skills needed • Define a new software development process • and a way to get there

  10. Roadmap for the solution • See “How to sell MDA” this afternoon

  11. Related Issues • Need UML profiles • Need meta-models • Need models of architectures • Product line approach • Need (much) higher level modeling languages • Need time ...

More Related