Discussion Topic 2 p 272 Some systems analysts argue Give us

Discussion Topic #2, p. 272

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 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?

Solution

First of all, there are 2 arguments:

1. “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 feel that you are trying to tell them how to do their jobs.”

2. “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.”

Details:

1. “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 feel that you are trying to tell them how to do their jobs.”

~>This argument stands correct in situations where there only less work required by a system analyst (User has basic or medium level understanding about the system). When a user knows exactly what he wants, he tries to get only the reports and data which is needed for him.

For ex., Consider one user wants to know how to add 3 numbers.He knows how to add 2 numbers (i.e, C = A + B). So, basically what he wants from a system analyst is how to add 3 numbers instead of 2. In this scenario, an analyst should provide him/her with the knowledge on how to add 3 numbers.

(i.e, C = A + B + D - in one step or

C = A + B & C = C + D - in two steps). This will satisfy the users need of how to add 3 numbers. In this scenario user already knows 2 numbers addition(i.e, C = A + B). So, all he wants to know is how to apply this knowledge in advance calculus.

2. “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.”

~> In this case, a user has no knowledge about the system and all he wants to know is basics about the system, but sometimes a user can have lots of questions(irrelative) on the system which simply makes no sense and only increase problems of the analyst.

For ex., If a user wants to know about a calculator and it\'s functionality and he has never seen a calculator in his/her entire life. In this scenario, that user can have multiple questions like:

a. Does this calculator give him info about time/date?

b. Can this calculator be used as an alarm?

c. Is this calculator capable of giving him answers like \"What movie is playing in nearby theater\"?

In this scenario, we(system analyst) know that a calculator can never perform such tasks but the user has no knowledge about that. So, the System Analyst us supposed to let the user know the detailed functionality of the Calculator.

The analyst should tell the user that this device can only be used to do arithmetical calculations. All the other questions that user is raising makes no sense until the analyst explains these features to the user.

So, in conclusion, it is said that \"Every coin has two faces\" that means every aspect has two sides. Sometimes it is better to get to know the user\'s understanding and sometimes it is better to explain the user about the functionality and limitations of the system. A system analyst should always take into consideration both sides of the system and user\'s thought process.

Thank you for posting this question. Please give a \"Thumbs Up\" if you agree with this solution also feel free to leave a comment.

Keep posting question. Thanks...!