The principal benefit of developing a prototype during requirements elicitation is that it allows customers and end-users of the system to experiment with the system. They can develop an understanding of how the system can be used be used to support their work. Discuss three (3) advantages and two (2) disadvantages of using prototype for requirements elicitation.

The principal benefit of developing a prototype during requirements elicitation is that it allows customers and end-users of the system to experiment with the system. They can develop an understanding of how the system can be used be used to support their work. Discuss three (3) advantages and two (2) disadvantages of using prototype for requirements elicitation.

Principles of Information Systems (MindTap Course List)

13th Edition

ISBN:9781305971776

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter12: System Acquisition And Development

Section: Chapter Questions

Problem 7SAT: The overall emphasis of the __________ phase is on gathering data on the existing system,...

See similar textbooks

Similar questions

One of the most significant advantages of creating a prototype during requirements elicitation is that it enables customers and end users to play with the system. They may get a knowledge of how the system can be utilized to assist their job by seeing and interacting with it. In this section, we will discuss three (3) benefits and two (2) drawbacks of utilizing prototypes for requirements elicitation.
Explain the procedures that a system requirements engineer could follow in order to maintain tabs on the connections that exist between the system's functional requirements and its non-functional requirements.
In the context of requirement analysis, discuss the concept of non-functional requirements as constraints and how they impact system design.
Provide some examples of how a system requirements engineer can go about tracking the interdependencies between the system's functional and non-functional needs.
Q-1 In your opinion, why for a system under- development the requirements discovery is needed? Justify your answer by giving an example. Q-2 If a system’s end- user stakeholders are not involved during its development or updation requirement engineering process then what type of functional requirements related problems are expected? Name and explain any two of them.
Show how a system requirements engineer may keep tabs on the interdependencies between functional and non-functional needs, and explain why this is useful.
Explain the concept of a use case diagram in requirement analysis. How does it help in understanding system behavior and interactions?
7. If requirements are easily understandable and defined then which model is best suited? a. Spiral model b. Waterfall model c. Prototyping model d. None of the above
Explain how prototyping works in tandem with the requirements gathering process. What makes this method unique, and how does it compare to other common approaches?
In K. Wieger’s paper, “Validating Requirements”, he wrote: “On many projects, testing is a late-stage activity. Requirements-related problems linger in the product until they’re finally revealed through time-consuming system testing or by the customer.” Based on what we discussed recently in the peer reviews module, how can we address this problem and reduce requirements-related problems?
Show how a system requirements engineer may keep track of the relationships between functional and non-functional demands, and explain why doing so would be beneficial.
Describe the use of use case diagrams in requirement analysis. How do use cases help in understanding system functionality and user interactions?