A programming proposition

TalkBack 1 of 16:

Next »

• Thread View
• Flat View

The problems with prototyping

(1) Validation and verification, especially of non-trivial functionality (beyond CRUD + basic aggregation), can be as or more costly than implementation activities. All changes to a production system require regression testing first.

(2) Validation and verification are short-changed, leading to applications that yield incorrect and misleading results. I see this ALL THE TIME coming out of "prototypes" or "tools" developed by consultants (by far the worst), interns, and users.

(3) The "wickedness" of a problem and how time consuming solving it are believed to be are treated as equivalent - i.e. hard. There are many straight forward problems that are time very consuming to solve that can yield significant benefit at low risk, but that will not be solved because they cannot be fit into a prototyping cycle.

(4) Solutions are unmaintainable because they were produced with the primary goals of verifying requirements rather than producing a maintainable system, and each prototyping cycle piles the cards higher.

Posted by: Erik Engbrecht   Posted on: 11/05/07 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• INNOV8 2.0: A Business Process Management Simulator IBM Innovate your business' process model, play against the market, compete ... Download Now
• The Impact of Virtualization Software on Operating Environments VMware Today's use of virtualization technology allows IT professionals to ... Download Now
• Wireless Lab Delivers Technology and a Better Education Dell Steve Spangler, assistant principal of Middlesboro Middle School in ... Download Now