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?- 100 words. please be direct
part two: Lynn Jennings is the IT manager at Lazy Eddie, a chain that specializes in beanbag chairs and
recliners. She
asked Jan Lauten, a senior systems analyst, to review the large number of printed reports that are
distributed to Lazy Eddie’s 35 store managers. “Jan, I just can’t believe that our people really read all of
those reports,” Lynn said. “We constantly add new reports, and we never seem to eliminate the old ones.
Sometimes I think all we’re doing is keeping the paper companies in business!” Jan replied, “I agree, but
what can we do? The managers say they want the reports, but I always see them stacked on top of file
cabinets. I’ve never seen anyone read a report.”
“I have an idea,” Lynn said. “I want you to come up with a procedure that requires users to review
and justify their information needs to see if they really use the reports, we send them. You could design a
form that asks if the information still is required, and why. Try to get users to decide if a report is worth
the cost of producing it. Do you think you can do it?”
“Sure, I can,” Jan replied. When Jan returned to her office, she wondered where to begin. What
advice would you give to Jan?