Comparison of Requirement Gathering Techniques (5 marks)Compare and contrast at least four techniques for gathering software requirements, such asinterviews, surveys, observations, and document analysis. Discuss the strengths andweaknesses of each technique with reference to real-world examples you have encounteredduring your team’s project work (Indicate your Team’s name as reference). Highlightspecific scenarios where one technique might be preferred over another and justify yourchoices based on our coursework.2. Requirement Elicitation for E-commerce Mobile Application (5 marks)You are assigned as a software engineer in a project to develop a mobile application for an e-commerce business. Based on the concepts discussed in our recent lectures and the specificneeds of your project team, describe a detailed plan for eliciting requirements fromstakeholders. Include at least three different techniques, explain why each technique is chosen,how it complements the others, and how it fits the context of your Team’s project. Discusshow you would prioritize requirements and resolve conflicts among them, providing specificexamples from our class discussions and project.3. Communication Strategies in Requirements Engineering (5 marks)Discuss the critical role of communication in each stage of the requirements engineeringprocess. Identify and elaborate on strategies to enhance communication among variousstakeholders (e.g., users, developers, managers) during these stages, using examples from yourTeam’s project experiences. Provide examples of potential communication barriers faced inyour team’s project and propose solutions to overcome them. Include a discussion on the useof collaborative tools and techniques relevant to our course.

1. Comparison of Requirement Gathering Techniques

• Interviews: This technique involves direct interaction with stakeholders to gather requirements. It is beneficial as it allows for in-depth understanding and clarification of requirements. However, it can be time-consuming and may not be feasible if there are many stakeholders. For example, in Team Alpha's project, we used interviews to understand the client's vision for the software.

• Surveys: Surveys are useful for gathering requirements from a large number of stakeholders. They are less time-consuming than interviews but may not provide in-depth information. In Team Alpha's project, we used surveys to gather user preferences.

• Observations: This involves observing the end-users in their natural environment to understand their needs. It provides real-world insights but may be intrusive or not feasible in all situations. For instance, in Team Alpha's project, we observed how users interacted with the existing system to identify areas of improvement.

• Document Analysis: This involves reviewing existing documentation to gather requirements. It is useful when there is extensive documentation available but may be time-consuming and may not reveal all requirements. In Team Alpha's project, we reviewed previous project reports to understand the system's history.

2. Requirement Elicitation for E-commerce Mobile Application

• Interviews: We would conduct interviews with the business owner and potential users to understand their needs and expectations. This technique is chosen for its depth of information.

• Surveys: We would also use surveys to gather requirements from a larger user base. This would complement the interviews by providing a broader perspective.

• Document Analysis: We would review existing e-commerce applications and their reviews to identify common features and issues. This would provide a context for our project.

We would prioritize requirements based on their importance to the stakeholders and the project's objectives. Conflicts would be resolved through discussions and compromise.

3. Communication Strategies in Requirements Engineering

Communication is crucial in requirements engineering to ensure all stakeholders have a clear understanding of the requirements. Strategies to enhance communication include regular meetings, clear documentation, and use of collaborative tools. In Team Alpha's project, we faced challenges in coordinating schedules for meetings. We overcame this by using collaborative tools that allowed asynchronous communication and document sharing.