ant-dev mailing list archives

On 12/18/00 9:11 AM, "Ken Wood" <kwood@i2.com> wrote:

> How about the good old fashioned way:
> 
> 1. A requirements specification that spells
>  out WHAT the software must do, without
>  ANY indication of how it should be done.
> 
> 2. A design document that specifies HOW the
>  requirements will be met via a proposed
>  implementation.

Good points.


-- 
James Duncan Davidson                                        duncan@x180.net
                                                                  !try; do()