COMPUTER SCIENCE AND ENGINEERING
SOFTWARE ENGINEERING
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Bounding scope
|
|
|
Understanding user need
|
|
|
Requirements volatily
|
|
|
All of the above
|
Detailed explanation-1: -Why is Requirements Elicitation a difficult task ? Explanation: Users specify unnecessary technical detail that may confuse, rather than clarify overall system objectives.
Detailed explanation-2: -This is a difficult problem to overcome with diversity of variables that can get in the way. One way is to communicate in terms of what’s in it for the other person rather than your firm or someone else in your client’s company.
Detailed explanation-3: -Requirement elicitation is the process of communicating and collaborating with key stakeholders to assemble the insight and identify the project’s needs.
Detailed explanation-4: -The requirements elicitation process may appear simple: ask the customer, the users and others what the objectives for the system or product are, what is to be accomplished, how the system or product fits into the needs of business, and finally, how the system or product is to be used on a day-to-day basis.