 |
Professor von Clueless in the Blunder Dome |
status privacy about contact |
|
Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.
Atom Feed Associated Blogs 
Recent Items Archives |
Wednesday, June 22, 2005MDDi: Integrated Tool Chains for Software Development
ACM News Service: FP6 Project Aims to Increase EU Competitiveness in Software Systems Development. Uh, “programmers put on your chains and mechanize?” Maybe not. The MDDi project is making the Eclipse Model Driven Development integration (you parse that, I gave up, but I think it’s e[MDD]i sort-of—oh, it’s Eclipse MDDi). The expectation is that the open-source modeling tool will provide an integrated tool chain to help European system engineers make new software. It bugs me that this is heralded as an economic maneuver to avoid falling behind those pesky Americans and Japanese and reduce the cost of software development. That’s a peculiar motivation for wanting to improve the quality of software delivery. The 2005-06-15 CORDIS News article starts out a little more affirmatively, based on conversation with Serge Salicki: “Europe is faced with the double expectation from end-users of better, more complex and more reliable software systems, developed in an increasingly shorter time span at reduced costs.” The overall program is a European Sixth Framework Programme (FP6) project called MODELWARE. It is this effort that has the objectives of
MODELWARE (MODELing solution for softWARE systems) seems to be a two-year project and [e]MDDi is emerging about half-way through. Hmm. And we have new nomenclature: modellisation for becoming model-centric, somehow in contrast to being code- and document-centric in our development methodologies. The pilot applications (air-traffic control, for example) seem rather ambitious, too. I think my problem is with the blurb and the puffery, not the objectives of the effort. The idea is to produce open development platforms for software and services, and when we figure out what open means here, we can assess the value of the approach. One aspect of “open” is the choice of Eclipse as a development platform, although the participation of IBM in the effort is understated in the materials at the project site. I find fixing on a specific platform (in the sense Eclipse is used here) to be unsatisfying. I think it’s more than Eclipse is not my platform of choice. I’m wondering, rather, whether the methodology is abstracted enough that it can be rehosted and retargeted with the Model-Driven Development used to accomplish that. I’m curious about that. Comments: Post a Comment |
|
|
You are navigating the Blunder Dome |
template created 2004-06-17-20:01 -0700 (pdt)
by orcmid |