Objective Identify the elements in software Requirements Specification document Estimated Time: 40 minutes The output of requirement analysis place is the Soltware requirements Specificaticn it should specify what a system shoald do. Atypical SRS usually comsists of the system overiew (both current and proposed). Objectives of the proposed system such that it is peoven to be significant development over the existing system, business analysis of the client functional and non-functional requirement, glossary, etc. Problem Description (6 points) Article Systems (AS), a giant books franchise has approached IT company ABCLtd. To belp them automate their business processes and shift them online so all of its outlets across the globe would be under one portal. AMC Ltd.agrees to take on the project and both the companies sit down and strike a deal. After detailed discussion and analysis, ABC Lad. decides to follows the waterfall model for development of the project. This discussion covered topics such as the business analysis and operations of AS. The expectations of the cliem (AS) from ABC Lad. their needs and requirements from the software, their current existing system including its limitations and what the proposed system would do to address these issues. Taking into accoant all the input, the concerned team at ABC designed and developed the SRS Which of the following are typically expected to be found in the SRS created by ABC Ltd Towards the AS Project? Put an X mark in the second column of Table 2 for those SRS elements that will be included in the SRS document then explain why you have selected these elements in table 3. Table 2 Elements in software Requirements Specificatiorn To be System Overview Class Source Code Use Cases Flow Charts for al Code revicw Comments test resalts The Difference in the Non-Functional requirements Features of new the funct of the of the current s to be Table 3