Send
Close Add comments:
(status displays here)
Got it! This site "robinsnyder.com" uses cookies. You consent to this by clicking on "Got it!" or by continuing to use this website. Note: This appears on each machine/browser from which this site is accessed.
How it is really done
1. How it is really done
2. How it is really done
1. ?
2. ?
3. ?
4. ?
5. ?
6. ?
In the real world, things seldom go as planned.
This is especially true when humans and committees get involved in what one would think is a simple matter.
3. What the user needed
A request starts out simple enough.
1. What the user needed/wanted.
4. As proposed by the project sponsor
Then, the project sponsor gets into the act - who may not have practical knowledge of the area.
2. As proposed by the project sponsor.
5. As specified in the project request
Soon, things get out of control as the project request is due.
3. As specified in the project request.
6. As designed by the systems analyst
4. As designed by the systems analyst.
Under time pressure, the systems analyst needs to finish this project and move on to the next one.
7. As produced by the programmers
The programmers are just as overworked and short of time, and cobble together a system.
5. As produced by the programmers.
8. As installed at the user's site
Now, it just needs to be made to work at the user's site.
6. As installed at the user's site.
9. Source
From: Roberts, D., et al. 1998. Designing for the user with OVID: Bridging user interface design and software engineering. Indianapolis, IN: Macmillan Technical Publishing. ISBN 1-57870-101-5. p. 50-51.
Original source: Unknown. Circulated as a joke in many companies for many years.
10. End of page
