Experiment 4 (Requirement Development) ObjectiveTo identify the various requirement development activities viz. elicitation, analysis, specification and verification for the given scenarios. Background Requirement engineering produces a specification of what a system should do. The intention of requirement engineering is to provide a clear definition of requirement of the systems. This phase is avery important phase because, if the customer requirements are not clearly understood, the ambiguity can get into the other phase of the development. To avoid such issues, requirement has to be elicited using the right elicitation techniques, to be analyzed effectively specified clearly and verified thoroughly All activities are collectively termed as requirement development activities. Problem Description following scenarios, Identify the requirement development activities associated with each of the a. Joe is creating an online survey questionnaire for requesting user feedback on the desired features of the application to be developed. b. Mark is preparing a formal document which includes all of the desired features identified by the survey c. Jack identified an incomplete requirement statement. d. Jones is identifying all security related requirement and separating them from e. Merlin a team member is sent to client to observe the business case and t. Leo is team member is working on requirement and ensuring that g. Lee is conducting a facilitated meeting with the stakeholder to capture the h. Amit a team member is distributing questionnaires to stack holder for the performance related requirements. collect typical user requirements. requirement collected should not be vague and unclear. requirements. gathering user requirements. enario Requirement Development Activiti