The goal of modeling domain concepts through objects set by OOP has for a long time been handled in insufficient ways. In this article we introduce the concept of Composite Oriented Programming, and show how it avoids the issues with OOP and reignites the hope of being able to compose domain models with reusable pieces.
Based on the book Domain Specific Modeling by S. Kelly and J.-P. Tolvanen, the author of Learning Lisp blog exposed some thoughts on how a modeling language should look like and where UML stands with regard to this. While it appears that UML doesn’t provide enough precision and high enough level of abstraction, another blogger suggests a different approach that may allow its successful use in MDD.
During PDC 2008, David Langworthy, Architect at Microsoft, and Don Box, Distinguished Engineer at Microsoft, held a presentation about Oslo, focusing especially on the modeling language M, explaining what is and what is not, and also demonstrating using M to create a data model.
Based on their vision to deliver on the promise of model-driven development in SOA where business users, SOA architects and developers will be able to use the modeling tools to collaborate on composite applications, Microsoft has recently made several announcements about its modeling strategy.
During Oracle’s Open World conference last month, Oracle has revealed their BPM strategy and roadmap. The centerpiece of this strategy is building a unified BPM platform based on the strength of existing Oracle’s assets and BEA acquisition.
Microsoft has unveiled Visual Studio 2010 and .NET Framework 4.0.
There has been some debate recently to understand the meaning of Microsoft's support for UML. Is Microsoft going away from Domain Specific Languages or are UML and DSL complementary? Is UML becoming a notation more than a language? InfoQ spoke with Jack Greenfield to get some of these answers.
When you want to build model-driven software you’ll need to devise a methodology based on ideas and experiences from others. Johan den Haan shares 8 gotchas of Model Driven Engineering. One of the key points in the article focuses on the use of graphical tools vs general purpose languages.
Domain driven design can be most readily applied to stable domains but it becomes more challenging when the domain itself is in a state of flux and development. This is common in Agile projects, and happens also when the business itself is trying to evolve. This article examines how we used DDD in the context of a two-year programme of work to rethink and rebuild guardian.co.uk.
Managing commonality and variability is the core of product line engineering. In this presentation, Markus Völter illustrates how model-driven and aspect oriented software development help addressing the challenge of managing variability in product line engineering.
MindScape has released version 2.0 of their domain modeling and ORM tool. LightSpeed 2.0 includes a visual domain model designer integrated with Visual Studio 2008, support for LINQ and the ability to access multiple databases concurrently.
Model-driven software development no longer belongs to the fringes of the industry but is being applied in more and more software projects with great success. In this article, experienced MDD practitioners pass on some best practices based on the experiences gathered over years of development.
Microsoft seems to think so as they prepare to deliver on the Oslo vision. Back in November 2007 Doug Purdy made a veiled reference to a new project in development calling it "Emacs.NET". This fueled rampant speculation far from the intended mark.
Olaf Zimmermann and his colleagues have developed a general Architectural Decision Framework. In this paper presented at WWW 2008, they demonstrate how this framework can be used to compare REST and WS-* an possibly end an almost decade long debate.
InfoQ interviewed Markus Voelter about the importance of writing software architecture documentation and the problems noticed by him when it comes to creation of useful software design documents.