Blogs - The Model Driven Software Network. The Enterprise Architect - by Johan den Haan. Peter Friese's blog. Steven Kelly on DSM. Code Generation 2011 is coming up fast: less than 3 weeks now!
If you haven't already got your ticket, book now -- as I write, there's one discounted ticket left. As in previous years, the lineup is impressive: Ed Merks, Terence Parr, Jos Warmer, Johan den Haan, Pedro Molina and of course experts from MetaCase, Itemis, and Microsoft. It's great to see 10 out of 27 sessions are Experience Reports or Case Studies: Model-Driven Development is an industrial reality, and the media attention comes from real world successes, not academic theory or vendor hype. Still, MDD has a long way to go to fulfill all its promise, and there are many misunderstandings and prejudices to be corrected.
Looks like there’s an interesting three-way divide on these MDD issues, depending on the kind of language and who supplies it: vendor-supplied general purpose language (e.g. Juha-Pekka on DSM. I have a pleasure joining the workshop on language design and implementation to defend my claim that the best level of abstraction for a language is as high as possible.
I have no arguments against DSL'ish ideas of extending current programming languages, embedding a DSL to a host language, using better naming for API calls etc., but I don't see them raising the level of abstraction much from the implementation level. I'm afraid that these efforts then don't provide significant benefits to the development teams either. At the workshop I plan to proof my claim by showing results from cases (partly public like 4, 5, 6, 7, 8, 9, 10) that develop and test different type of software, such as consumer electronics, telecommunication, product lines, medical, and automation systems with domain-specific languages, models and generators.
These industry cases report 5-10 fold productivity increase. New Thoughts. Carnets de bord. InShare0 This post is a synthesis of two posts I originally published on my other blog "unRelated".
One of the key foundations and most attractive principle of Agile or Lean methodologies is that "Everyone can help each other remain focused on the highest possible business value per unit of time". I am certainly a strong supporter of that principle. However, value is often difficult to assess, I would actually argue that it is easier to identify what has less or little value, but what we think as valuable can potentially lead to many false positive, or simply be "business-as-usual" and hide the broader structure of the solution.
"User Stories" are the corner stone of identifying and delivering value: An argument can be made that the user story is the most important artifact in agile development, because it is the container that primarily carries the value stream to the user, and agile development is all about rapid value delivery. Voelterblog. The Gordian. Object-Oriented or Model-Driven Society? The Metalevel. The thinker, Paris.
Photo CC by Dano Decisions in all contexts of life are taken under the best information we can collect and under the assumption of many factors. Changes to the surrounding context could lead to changing assumptions and then, it is time to question and rethink about our overall strategy. Software architecture and design decisions are taken based on principles as the following ones: SimplicityEase of useMaintainabilitySeparation of ConcernsUnderstandableLow couplingHigh cohesionRobustnessPerformanceSpeed These principles lead to methods and low level techniques in the process of software creation.
Every language, tools and framework comes with its own boilerplate code, ceremony and plumbing. My hypothesis here is that: many development choices we take rely on the cost of changing code. Models Everywhere. Software Modeling blog. Model Driven Blogging. Meta plop. Karsten's Blog. This Is The Frequency. Jo MD blog. With or without a name. Fred Madiot. Ekkes-corner: eclipse. Merks' Meanderings.
Eclipse mde. The R&D director’s blog. Sven Efftinge's Blog. Jérôme BENOIS's Weblog "MDE 2.0 :)" Les news d'Aspectize. Plusieurs entrepreneurs viennent nous voir avec leurs idées de projet. Notre approche les intéresse parce qu’ils voient de la valeur à développer rapidement et être capable d’adapter les solutions au fur et à mesure. Le Lean Startup commence vraiment à prendre, et c’est une très bonne nouvelle pour nous; il colle parfaitement à notre approche, et nous avons des atouts indéniables pour les aider à le mettre en oeuvre.
Parmi les entrepreneurs que nous rencontrons et qui sont séduits par l'approche Lean Startup, et notamment le fait de ne pas écrire de cahier des charges, beaucoup se demandent quelle forme doit avoir l'expression de leur projet pour réaliser un MVP. Petit à petit, au fur et à mesure de nos rencontres et nos expèriences, nous avons pu affiner et préciser ce qui constituait une forme adequate à notre bonne compréhension du projet afin d’être le plus efficace et créer le plus de valeur possible. 1/ Vision 2/ Persona L’expèrience utilisateur est au coeur de notre préoccupation. Active Knowledge Modeling. Actifsource. News from the front. Executable models, as the name implies, are models that are complete and precise enough to be executed.
One of the key benefits is that you can evaluate your model very early in the development life cycle. That allows you to ensure the model is generally correct and satisfies the requirements even before you have committed to a particular implementation platform. One way to perform early validation is to automatically generate a prototype that non-technical stakeholders can play with and (manually) confirm the proposed model does indeed satisfy their needs (like this). Another less obvious way to benefit from executable models since day one is automated testing.
The requirements. Andreas Graf's Software Engineering Blog.