Software engineering project for a pong game in python\ Title\ Group Name\ Student Names\ Course\ Professor\ Submission Date\ Version No.\ Note: Instruction only: This project template will be used for all submissions. In fact,\ the document will be the used through the project. Each submission will be an update\ from a previous version. No other documents will be accepted except for the installation\ instructions for installing the project environment needed to run it. This document will be\ given a new version number when there is an update to it. A change page will be used to\ show the differences between each version of the document. The method for version\ control will be up to the team to decide. - remove paragraph before submitting.\ Change Pages\ Title Project\ Software Engineering Report\ Executive Summary\ Note: Instruction only: This is a high-level summary of the entire project. You should\ summarize the entire project using the following topics (no less/more than 1 page)-\ usually written last (Remove paragraph before submitting)\ a. Background\ b. Project purpose\ c. General high-level requirements\ d. Feasibility\ e. Software Engineering Methodology\ f. Conclusions\ Project Outline\ Project Title\ Project Problem Statement\ Project Purpose\ Project Features\ Project Stakeholders\ Project Team Name\ Project Members and Roles\\\\Responsibilities\ Glossary of Terms\ Project Plan\ Project Tools\ Project Development Tools and Rationale\ Programming Tools\ Configuration Management Tools\ Source Code Version Control Tools\ Communications Tools\ Documentation Tools\ Presentation Tools\ Miscellaneous Tools\ Project Schedule\ Note: Instruction only: detailed outline of schedule to include at a minimum all\ meetings (team, client, etc.), deliverables, milestones, etc.) - remove before submitting\ Project Budget\ Requirements\ System Requirements\ Note: Instruction only: All requirements are to be numbered and detailed, Each\ requirements must stand on its own and be testable, i.e. non ambiguous. remove before\ submitting.\ Functional Requirements\ Non-Functional Requirements\ Use Cases Descriptions\ Note: Instruction only: For all use cases that you can think of (based on your System\ Requirements), write a brief or casual text description. List explicitly the requirements that each\ use case responds to. Each Use case must be named and numbered. remove this before\ submitting\ Use Case Diagram\ Note: Draw the use case diagram with all the use cases remove this before submitting.\ Requirements Traceability Matrix (RTM)\ Note: Instruction only: The RTM is used to map the requirements, to use case, to the design,\ to the code, t the test procedures, to the test cases. Each of these must be numbered. The RTM\ is usually created as a table in Excel or Word with columns that represent the each of the\ elements listed above. The cells the numbered identifier of for that element such as the design\ the coincides with a particular requirement or the code module that implements a certain design\ remove before submitting.\ Note: Instruction only: The RTM table should be placed as an Appendix. Simply refer to the\ appendix in this section remove before submitting.\ Project Design\ Preliminary Design\ Screen Mock-Ups\ Navigation Methodology (User Interface)\ Data Dictionary\ Critical Design\ Business Rules\ Note: Instruction only: Select some method such as pseudo code or flow charts to present\ these remove before submitting.\ Data Structure\ Note: Instruction only: Show how the data elements relate such as tables that aggregate\ the data elements that relate to each other, such as customer information. remove before\ submitting.\ Project Topology\ Infrastructure Diagram\ Project Testing\ Testing Methodology\ Test Procedures\ Note: Instruction only: Test procedures must be numbered and relate to requirements or use\ cases. Test procedures test code which implements the requirements as addresses by the design.\ The RTM must be updated to show these relationships. remove before submitting.\ Test Reports\ Note: Instruction only: Test reports must be numbered and relate to the test procedures that are\ used. The RTM must be updated to show these relationships. remove before submitting.\ Conclusion\ Note: Instruction only: The conclusion should briefly restate the project and summarize its main\ points, to include a brief recap of each of the sections. remove before submitting.\ References