Re: TDD: Test-Driven Design or Test-Driven Development?

From: Phlip (phlip_cpp_at_yahoo.com)
Date: 02/03/04 

Date: Tue, 03 Feb 2004 13:13:53 GMT

Vladimir wrote:

> > > For example, the author seems to view engineering and manufacturing as
> > > isolated phases in a waterfall process.
> >
> > Hardware expense forces the process to be waterfall.
>
> You meant expenses TO CHANGE hardware? That comes from the need to
customize
> assembling conveyor, create new moulding forms etc?

Yup. In this version of the hardware design metaphor, we need phases -
napkins, paper, CAD, mock-ups, hand-made versions, then production versions.
Phase phase phase. Hardware has high cost of manufacture and high cost of
re-design, due to re-tooling. So its cost of change curve goes up, requiring
a classic waterfall.

You could next declaim using multiple differing metaphors between hardware
and software design. That's why they are metaphors; to illustrate bridges
between concepts.

There is more than one mapping between hardware and software design
situations. Each metaphor illustrates something different; that's why they
are useful.

Nice learning with you. 

--
  Phlip
    http://www.xpsd.org/cgi-bin/wiki?TestFirstUserInterfaces

Relevant Pages

  • Re: Reminder, blatant ad
    ... It is used as a model, a metaphor. ... Any computer can be divided in two disjoint parts: the hardware and the ... The software is the part that can be easily changed to modify the function ... Prev by Date: ...
    (comp.databases.theory)
  • Re: Full bare metal restore to different hardware.
    ... change hardware to this degree. ... > I'm trying to setup my disaster recovery for a windows 2003 server. ...
    (microsoft.public.windows.terminal_services)
  • Re: Damn Microsoft Activation!!!!
    ... >reactivate every goddamn time I change my motherboard!!! ... >enthusiasts who change hardware regularly to constantly ...
    (microsoft.public.windowsxp.hardware)