REQUIREMENTS ENGINEERING
REQUIREMENTS GATHERING AND ANALYSIS
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
Organizing requirements
|
|
Requirement gathering
|
|
Negotiation & discussion
|
|
Documentation
|
Detailed explanation-1: -Requirements gathering-The developers discuss with the client and end users and know their expectations from the software. Organizing Requirements-The developers prioritize and arrange the requirements in order of importance, urgency and convenience.
Detailed explanation-2: -Explanation: The process to gather the software requirements from client, analyze and document them is known as requirement engineering.
Detailed explanation-3: -Business analyst and subject experts are responsible for requirement gathering process. Business customers have a tendency to expect software teams to be mind-readers, and to deliver a solution based on unspoken or unknown requirements. Hence, all of the requirements need to be formally captured in a mammoth document.
Detailed explanation-4: -Requirements elicitation (also known as Requirements Gathering or Capture) is the process of generating a list of requirements (functional, system, technical, etc.) from the various stakeholders (customers, users, vendors, IT staff, etc.) that will be used as the basis for the formal Requirements Definition.