Experiment 5 (Requirements Management) 5.1 Objective - To identify the various requirements management activities such as: elicitation, analysis, validation and management used in each scenario. Estimated time: 20 minutes Background Requirements management is a systematic approach to eliciting, organizing and documenting the requirements of a system. It is a process that establishes and maintains agreement between the customer and the project team on the changing requirements of a system. Requirements management is important because, by organizing and tracking the requirements and managing the requirement changes, you improve the chances of completing the project on time and under budget. Poor change management is a key cause of project failure. Requirements engineering process consists of four phases: . Requirements elicitation: getting the customers state exactly what the requirements are Requirements analysis: making qualitative judgments and checking for consistency and feasibility of requirements. Requirements validation demonstrating that the requirements define the system that the customer really wants. Requirements management: the process of managing changing requirements during the requirements engineering process and system development, and identifying missing and extra requirements. Problem Description Identify the requirements management activities associated with each of the following scenarios, and fill table 1 below 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 the performance related requirements. Merlin a team member is sent to client to observe the business case and collect typical user requirements E Table 1 Scenario Requirement Development Activities A D E