At 01:22 PM 3/22/2003 -0500, you wrote:
At 11:55 AM -0600 3/22/03, Scott A Crosby wrote:
This had better be a wish list; if a solution must satisfy all of
these requirements, I'm packing up and going home.
That's standard practice for a requirements list. First you wish
everything you could possibly want. Then you start to compromise. Ditto
on architectures.
I find that from a practical stand point this may be backwards. First, you
set down in writing and get written buy-in from the parties in authority
(assuming there are any) what the proposed system/product will NOT DO and
once set you don't allow this to change for at least the first release
(assuming there are several release possible or planned). Doing otherwise
invites constant feature/mission creep. After many years of successful and
unsuccessful project developments I've learned to walk away if I can't get
this first item resolved.
steve
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg