On Wed, 2005-08-24 at 10:44, Aylesworth Marc A Ctr AFRL/IFSE wrote: > You should not get programming specs from a customer but should get general > functionality that is desired. The customer should say I want to have remote > clients that can do the same thing as local clients, or that I can enter all > the information for a patient from a remote station, then we the programmers > turn those general statements into specifications that are realistic in > terms of what they want in the time frame that it is desired. Usually doing > this in small increments makes both the customer and the programmer happy. > There is no need to get from a client a request for remote access to an application. This should be built right into the program and the operating system. Secure remote access is never an issue with GNU Unix based software anyway.
The model your describing for client/developer relations is a disaster as soon as the first bill hits the desk. It just ropes the developer in to more and more irrational expectations. This is a model which sows failure. And with Free Software, who is going to be lead around by the nose like that? Your truly Ruben ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
