This article is a comparison, not a encyclopedic entry. I think it's not in line with Wikipedia's principles. Rui curado71 ( talk) 23:51, 19 November 2010 (UTC)
This article reads like a textbook, and its quality of writing and formatting is questionable- there really should be some restyling.
There's also some confusion with its relationship with the article for Model-driven engineering (MDD); there are three similar suggested search terms, two of which lead to this article and a third which leads to the MDD article. If these two topics are indeed related, a merge might be worthy of consideration, or otherwise there should be some reconciliation with the aliases of the two articles. Musicmaster890 ( talk) 20:34, 30 January 2013 (UTC)
Current Model-Driven Engineering article starts with the words "software development methodology". Are other engineers not allowed to do model-driven engineering? The rest of the article does go on to talk as if this were applicable to engineering at large, but the intro sentence limits applicability to software only.
Older versions of this article DO state it's applicable to a much larger domain - I highly recommend changing the intro of Model-Driven Engineering back to a version from around May 21, 2008 (before Gordon.Morrison deleted everyone but software). Anyone else agree? Garykempen ( talk) 23:46, 15 January 2015 (UTC)
As a layperson (software engineer), I am concerned at the discussion here about merging with the topic Model-driven engineering. These seem to me to be about to very different things, though in the abstract they are obviously related conceptually. One (this article) is quite possibly simply titled incorrectly (I can agree completely that the title implies overlap with Model-driven engineering). This article seems to be about designing and/or implementing programming languages, whereas Model-driven engineering seems to be about a Software_development_process, e.g. on par with other development processes such as Test-driven_development ( Software_development_process). I don't believe this article is about a process -- or if it is, it's not a Software_development_process. I have a hard time understanding it, but it sounds more like something regarding the design of the language or compiler itself, not the use of said language or compiler to build software (which is the process part). They just don't seem to be the same thing -- I'm not sure if I can better articulate why (partly because I agree with the first commenter that this is not particularly well written and seems a bit arcane (my words). My preference would be to change the title of this article to better describe what it is about (but I don't have a good proposal). And yes, I believe other engineers are not "allowed" to do Model-driven engineering because it's about a specific approach to building software. Though that hints that the title of that article may also need to change. Steve Goldberg ( talk) 03:08, 11 April 2016 (UTC)
As illustrated in "model driven software engineering in practice" book, MDD or MDSD are subsets of MDE, so, instead of merging we must work more on clarifying those concepts. BTW, the topics are too much related, and all advocate generating software from models, automatically. — Preceding unsigned comment added by MDSERG ( talk • contribs) 22:30, 15 August 2016 (UTC)
This article is a comparison, not a encyclopedic entry. I think it's not in line with Wikipedia's principles. Rui curado71 ( talk) 23:51, 19 November 2010 (UTC)
This article reads like a textbook, and its quality of writing and formatting is questionable- there really should be some restyling.
There's also some confusion with its relationship with the article for Model-driven engineering (MDD); there are three similar suggested search terms, two of which lead to this article and a third which leads to the MDD article. If these two topics are indeed related, a merge might be worthy of consideration, or otherwise there should be some reconciliation with the aliases of the two articles. Musicmaster890 ( talk) 20:34, 30 January 2013 (UTC)
Current Model-Driven Engineering article starts with the words "software development methodology". Are other engineers not allowed to do model-driven engineering? The rest of the article does go on to talk as if this were applicable to engineering at large, but the intro sentence limits applicability to software only.
Older versions of this article DO state it's applicable to a much larger domain - I highly recommend changing the intro of Model-Driven Engineering back to a version from around May 21, 2008 (before Gordon.Morrison deleted everyone but software). Anyone else agree? Garykempen ( talk) 23:46, 15 January 2015 (UTC)
As a layperson (software engineer), I am concerned at the discussion here about merging with the topic Model-driven engineering. These seem to me to be about to very different things, though in the abstract they are obviously related conceptually. One (this article) is quite possibly simply titled incorrectly (I can agree completely that the title implies overlap with Model-driven engineering). This article seems to be about designing and/or implementing programming languages, whereas Model-driven engineering seems to be about a Software_development_process, e.g. on par with other development processes such as Test-driven_development ( Software_development_process). I don't believe this article is about a process -- or if it is, it's not a Software_development_process. I have a hard time understanding it, but it sounds more like something regarding the design of the language or compiler itself, not the use of said language or compiler to build software (which is the process part). They just don't seem to be the same thing -- I'm not sure if I can better articulate why (partly because I agree with the first commenter that this is not particularly well written and seems a bit arcane (my words). My preference would be to change the title of this article to better describe what it is about (but I don't have a good proposal). And yes, I believe other engineers are not "allowed" to do Model-driven engineering because it's about a specific approach to building software. Though that hints that the title of that article may also need to change. Steve Goldberg ( talk) 03:08, 11 April 2016 (UTC)
As illustrated in "model driven software engineering in practice" book, MDD or MDSD are subsets of MDE, so, instead of merging we must work more on clarifying those concepts. BTW, the topics are too much related, and all advocate generating software from models, automatically. — Preceding unsigned comment added by MDSERG ( talk • contribs) 22:30, 15 August 2016 (UTC)