Some systems analysts argue, "Give users what they ask for. If they want lots of reports and reams of data, then that is what you should provide. Otherwise, they will feel that you are trying to tell them how to do their jobs." Others say, "Systems analysts should let users know what information can be obtained from the system. If you listen to users, you'll never get anywhere, because they really don't know what they want and don't understand information systems." What do you think of these arguments?
2007-03-16 18:44:26 · 2 answers · asked by xladyx19 1 in Computers & Internet ➔ Programming & Design
It depends on your users and what kind of task they are trying to accomplish. As a general rule, if you are dealing with users who will build experience with the system and learn to use it as a tool, then you should stay out of their way as much as possible, and only present data when requested. Examples of this would include Microsoft Office, company-specific business software, etc. - things that are used to complete regular tasks.
However, if you are developing a system that will primarily deal with one-off user experiences or infrequent user encounters - an installer application, or a setup wizard, for example - you should present the user with as much information as possible as frequently as possible.
2007-03-16 19:29:45 · answer #1 · answered by Rex M 6 · 1⤊ 0⤋
creative arguments
2007-03-17 02:29:44 · answer #2 · answered by Anonymous · 0⤊ 1⤋