Model-driven architecture outside of the enterprise?
From: Richard Grossman (rgrossmanDELETE-THIS-PART_at_techIII.com)
Date: 12/30/03
- Next message: Richard Grossman: "Re: Delphi 8 Edition Strategy"
- Previous message: Richard Grossman: "Re: Borland Layoffs?"
- Next in thread: Trevor de Koekkoek: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Trevor de Koekkoek: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Kostya Poukhov: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Brion L. Webster: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Daniel Mauric: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Patrick Moloney: "Re: Model-driven architecture outside of the enterprise?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Dec 2003 13:38:16 -0800
I've been watching the advent of model-driven architecture.
My big reservation is that I do small projects, either for small
businesses or single departments of large enterprises.
Although I may do a lot of work for one client during the course of a
year, it's still an accumulation of small projects.
So what I am looking for is upfront efficiences that result in
cost-reductions. The clients don't want to pay for long-range benefits.
My clients often say they don't have time to look at a model or
prototype or plan, and if they do, they do not discover errors at the
conceptual stage anyway.
It's all about bang-give them what they asked for cheap, then
bang-change it when they need more or realize they asked for the wrong
thing.
There are a few exceptions, and for these clients, I give them what will
actually produce the highest ROI for their businesses: sometimes talking
them into less than what they think they wanted and sometimes more.
These are the smart managers and business-owners, who focus on ROI on
the project including revenue-increases, staff-productivity and
software-maintenance, and not just software-development costs.
For the rest, it's mostly about competing on price. The fact that the
competition are flakes who won't be around next year to fix the problems
they created does not enter into the decision-making process, because
everyone is free to make the same claims of reliability and track-record
that I make whether their claims are true or not.
When MDA advances to the point of a 4GL where I define the app and the
app pops out, then there will be a productivity gain for me.
So, to the point: where does model-driven architecture fit into the
scenario described?
- Next message: Richard Grossman: "Re: Delphi 8 Edition Strategy"
- Previous message: Richard Grossman: "Re: Borland Layoffs?"
- Next in thread: Trevor de Koekkoek: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Trevor de Koekkoek: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Kostya Poukhov: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Brion L. Webster: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Daniel Mauric: "Re: Model-driven architecture outside of the enterprise?"
- Reply: Patrick Moloney: "Re: Model-driven architecture outside of the enterprise?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|