110 likes | 214 Views
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.
E N D
EMWDA Working Group on MDA is the Wrong Answer
Issue • 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. People Attending
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
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
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
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
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
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
Roadmap for the solution • See “How to sell MDA” this afternoon
Related Issues • Need UML profiles • Need meta-models • Need models of architectures • Product line approach • Need (much) higher level modeling languages • Need time ...