The Model Driven Software Network

Raise your level of abstraction

Bads news today for MDD practitioners!

Accordingly to Douglas Purdy's post: From “Oslo” to SQL Server Modeling: OSLO will change as a chamaleon to be a different thing as originally promised.

My impressions about it: The end of the MDD in OSLO

What do you think?

Reply to This

Replies to This Discussion

It seems to me that a large majority of current projects are doing a bottom up approach. I mean from database to code and not a MDD top down approach from model to code and database.
The main problem is the non understanding of the object development concept among a large majority of developers.What is happening in project today is that developers model there database (e.g. business classes), then add a glue between these classes and keep going developing on the top of entities coming from the database they have created.
It is simple, not really intelligent but covers the average low education level of many developers.

This Microsoft decision is therefore on business point of view logical in order to save research costs and target a larger community.
btw, it is still possible for Microsoft to buy a company and add MDD extensions to dotnet. Why should there bother about MDD if they have the cash ?

Reply to This

I saw your tweet on this. It's too bad, but not very different from what happened with DSL tools: where others were trying to define DSLs for narrow, specific domains, Microsoft aimed for the ambiguous, broad domain of '.NET enterprise applications'. This is almost the same thing all over. Vlad could be right: there's no quick money in MDD for Microsoft right now, so why should they bother? I agree only partly on the education level, but bottom line I guess Microsoft sees no market pull for MDD, while it does see a market pull for modeling of databases. That's doing business...

Reply to This

I have followed Oslo since its very origin, because it seemed to be a drastic change and almost the first approach to a model driven point of view for designing from Microsoft; a more consistent way than Software Factories was, a return to UML consideration, and other known lines of development. But as soon it started its way, Oslo became oversold: too much promises, but few real stuff. I´m astonished on how a product with no clear goals and fundaments have created expectations, having adopters without almost anything to test.
Microsoft seems to be a giant without a head moving from side to side. I don´t agree that an erratic plan could be recovered easily. It would hurt its customer base, and shows a bad business model. Is it possible to commit with a tool that is abandoned a year later?

Reply to This

Only in Oslo?

Reply to This

Could you explain yourself a little more?

Reply to This

More opinions about Purdy's post:
- JJ. Dubray
- Jordan Terrel

Reply to This

More than the rebranding issue by itself, I guess what really annoys JJ and a some of us in more or less degree is the over-hype generated during a year and half to finally change the course in the last moment and pretend it is the logical path to follow.

Reply to This

Ceyhun Ciper bitter-acid comments about Oslo MGrammar in the Microsoft SQL Modeling Forum.

Reply to This

I think that MDD should be developed by smaller companies and if it is successful then Microsoft would certainly acquire few of them.
It is not really a bad decision and let full of opportunities for smaller vendors.
If big companies are competing on niche markets then it is unfair !!

I have found the following niche market definition which is really good:
A niche market is a focused targetable segment of a market. A business that is focused on a niche market is usually offering a product or service that is not being addressed by mainstream providers. In other words a niche market is a narrowly defined segment of potential customers. Niche markets are typically ignored by large businesses because the market is too small to be interesting or to make their economies of scale effective. Niche markets are therefore ideal for small, specialised businesses. That is because these small specialised businesses can generally charge a premium or enjoy the benefit of little (or even no) competition..........

The only real problem I see is that DSL and MDD are still niche markets and could never emerge !!

Reply to This

"The only real problem I see is that DSL and MDD are still niche markets and could never emerge !!"

I guess it all comes down to tools. Would UML be so widespread if there weren't tools like EclipseUML? ;-)

Projects like Xtext and MPS are also taking DSL's out of their niche.

So we need better and easier DSL and MDD tools if we want these approaches to be accessible to the wide developer audience. This is the first hurdle. The second one is to put the average developer in a "modeling state".

Reply to This

Vlad: today, MDD can be considered as a niche market if you take in account the number of practitioners and projects.

However, MDD has the potential to be the next revolution in software development: faster and with more quality.

Specially, if you consider the numbers predicted by Jean Bézivin: The impossible equation. I think this step is unavoidable.

So, I agree with Rui: with better MDD tools we will get enough critical mass to make the parading change possible.

Reply to This

I agree there is a need for MDD in 2015 but with the current credit crunch how many companies will still be alive in 5 years ?
ISV needs to be profitable now in order to survive. Don't forget that we don't get any financial helps from investors (e.g. modeling is not interesting anymore capital ventures) or governement (e.g. no more research budgets for software modeling).

Who will invest ? I will certainly not invest our few cash left today in a new DSL+MDD project which could only be profitable in 2015 !!

Reply to This

RSS

Badge

Loading…

© 2010   Created by Mark Dalgarno on Ning.   Create a Ning Network!

Badges  |  Report an Issue  |  Privacy  |  Terms of Service