Abstract
Everyone is talking about Model Driven Development (MDD) BUT why do we need it? Is it the answer to IT productivity? The core problem of software development is to balance increased productivity with flexibility and control. This presentation will look beyond MDD and will reveal an approach that allows you to develop applications faster, while leveraging your expertise and leaving you in control.
Goal
MDD is enjoying high visibility but this presentation will look beyond MDD and will reveal an approach that allows you to develop applications faster, while leveraging your expertise and leaving you in control. This presentation will outline the essence of Model Driven Architecture (MDA) - the reality not the hype. It is no exaggeration to say that MDA has the potential to revolutionise the way we create and maintain software. Since MDA is becoming so popular, it is important to understand clearly why we need it, what it is - and what it is not. The goal of this presentation is to answer these questions.
The Essence of MDA
What is it about MDA that offers such drastic improvements over conventional methods of software development? The answer to this question lies in its "separation of concerns". MDA divides domain knowledge and platform knowledge allowing domain experts, platform experts and application developers to contribute their respective knowledge independently.
Increase Productivity and Control
Over the years the level of abstraction has risen, allowing programmers to create more and more powerful applications in return for a given investment of time and effort. The drawback was that they sacrificed other desirable factors, such as flexibility and standardisation, for this productivity. That is why, 15 years after 4GLs looked set to replace 3GLs, most of today's programming is done in 3GLs like C, C++ and Java. MDA strikes a compromise between power, flexibility and standardisation. It allows development to move smoothly between levels of abstraction, with much of the tedious, plumbing work being automated.
What MDA is NOT
The essence of MDA requires the separation of domain and platform expertise, which numerous approaches don't allow.
The presentation will make use of pictures and examples.
Date and Time
Wednesday - 15 December 2004, 12:15 - 13:15
Audience
Novice
Speaker(s)
