C. N. Itall has been a systems analyst for Tun-L-Vision Corporation for many years. When he came on board as part of the systems analysis team and suggested prototyping as part of the SDLC for a current project, C. N. said, “Sure, but you can’t pay any attention to what users say. They have no idea what they want. I’ll prototype, but I’m not ‘observing’ any users.”

Question

a. As tactfully as possible, so as not to upset C. N. Itall, make a list of the reasons that support the importance of observing user reactions, suggestions, and innovations in the prototyping process.
b. In a paragraph, describe what might happen if part of a system is prototyped and no user feedback about it is incorporated into the successive system.

Answer 1

a. The following is a list of reasons why prototyping is important:

1. Through gathering reactions of users about the prototype, many perspectives about the system will be obtained, including whether there will be difficulty in selling or implementing it.

2. Suggestions from users can point out the ways of refining the prototype, changing it, or “cleaning it up” so that it better fits users’ needs.

3. Innovations that have not been thought of prior to interaction with the prototype can add new features to the current one.

4. Prototyping helps to preview the future system and helps to identify priorities for what should be prototyped next. This approach will help set priorities and in turn redirect plans inexpensively, with a minimum of disruption.

b. If no user feedback is incorporated into the successive system, user needs will not be adequately addressed. In addition, users will think that their suggestions were not considered. They will not be as helpful in the future.