Why is Rapid Application Development really Implementation and NOT Architecture?
Usually, by its very name, a “rapid application development”- style methodology’s Enterprise engineering design objective is “IMPLEMENT” as soon as possible. The engineering design objective for rapid application development-style methodologies is NOT Alignment, NOT Integration, NOT Flexibility, NOT Interoperability, NOT Reduced Time-to-Market, NOT Quality, NOT Security, etc. Those Enterprise engineering design objectives actually require ENGINEERING. Engineering requires PRIMITIVE MODELS, the “raw material” for engineering. Primitive Models are “analysis/paralysis” relative to rapid implementations… UNLESS, you already have the Primitive Models in inventory, in which case, implementations are virtually instantaneous, a click of a mouse, ASSEMBLE TO ORDER… BUT, the investment has to be made in the Primitive Models BEFORE you get the order for the implementation.So, if you want the short-term approach, that is, to get to implementation as soon as possible, forget about models, write the
