3.1 Discuss the significance and use of requirement engineering. What arethe problems in the formulation of requirements?3.2 Requirements analysis is unquestionably the most communicationintensive step in the software engineering process. Why does thecommunication path frequently break down ?3.3 What are crucial process steps of requirement engineering ? Discuss withthe help of a diagram.3.4 Discuss the present state of practices in requirement engineering. Suggestfew steps to improve the present state of practice.3.5 Explain the importance of requirements. How many types ofrequirements are possible and why ?3.7 What do you understand with the term “requirements elicitation” ?Discuss any two techniques in detail.3.8 List out requirements elicitation techniques. Which one is most popularand why ?3.6 Describe the various steps of requirements engineering. Is it essential tofollow these steps ?

Question 2What is a Requirements Specification?1 pointA process, how the requirements are written (specified)A product, a written specification of the requirementsBothNeither

Question 2Specifying requirements is difficult because (select three):2 pointsThere is no guideline for writing a software requirement specification document.The client or end users might not be clear about what they want.Software is intangible, which makes it difficult to comprehend and communicate.Terminology can be interpreted in multiple ways depending on the person or the context in which it was used.

All of the following are elements of the requirements management plan except which one? A. Requirements of the project B. Processes for how requirements will be collected, tracked, and prioritized C. Process for how changes to the product will be initiated D. Product metrics and the reasons for using them

Specifying requirements is difficult because (select three):2 pointsTerminology can be interpreted in multiple ways depending on the person or the context in which it was used.There is no guideline for writing a software requirement specification document.Software is intangible, which makes it difficult to comprehend and communicate.The client or end users might not be clear about what they want.

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.