The customer for your proposed software application or product is providing the total funding for the project, and wants a formal Software Requirements Specification $($SRS$)$ Document. This document is to include all currently known functional and nonfunctional requirements. Although the customer representative, SCRUM Product Owner, SCRUM Master $($i$.$e$.$ you the Software Project Manager$),$ and relevant business managers are expected to sign off on the document at some point, it's understood that the requirements will certainly evolve and expand over time. It's also understood that since the agile SCRUM development approach is to be used for the project that the requirements will be implemented incrementally in different sprint deliveries vs$.$ all at one time.As the Software Project Manager you have been tasked to set up the initial requirements gathering meeting.In addition to the folks mentioned above, do you plan to invite any other stakeholders?What format of meeting do you think would be best? Totally face$-$to$-$face, or a combination of face$-$to$-$face and virtual via collaboration software?Who will you have facilitate the meeting?Who will you appoint to record the requirements that various parties mention?Will you have a list of proposed requirements to begin the discussions? If so$,$ what requirements do you have for your application or product?Is it required that all requirements gathered be testable?Will you encourage the use of use cases with actors?How long will the meeting be$?$ What is your suggestion for follow$-$up meetings and who should attend?In addition to reviewing the requirements list developed so far, do you plan to develop an models for the attendees? If so$,$ what types?How do you plan to negotiate project requirements in the SRS Document in the future if there are conflicts, redundancies, or inadequate resources?