MCQ IN COMPUTER SCIENCE & ENGINEERING

Detailed explanation-1: -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.

Detailed explanation-2: -But gathering is part of what we do, it is not all-encompassing. With all the possible information gathered together, we analyze it, and then go about figuring out what’s missing. That’s where the elicitation starts. That’s when we begin to draw out what’s latent in our stakeholder’s minds.

Detailed explanation-3: -Observation. Also referred to as job shadowing, observation is an excellent elicitation technique that helps understand requirements based on observations related to process flows and work environments of stakeholders.

Detailed explanation-4: -requirements gathering/collecting is a process that takes place before product analysis, which is a technique within the process of scope definition. Product analysis includes an activity ‘requirements analysis’ and it creates the definition of the product, sometimes in the form of a PBS (product breakdown structure).

Detailed explanation-5: -Requirement elicitation is the process of communicating and collaborating with key stakeholders to assemble the insight and identify the project’s needs.