Software Requirements Specification1. Introduction1.1 PurposeThis document is a definition of the software requirements to develop an automated evening class registration system and flexible query database required by St.John's Central College. This document will present the functional, non-functional and design constraint requirements for the system to be developed. Use case models and descriptions are included along with class diagrams to help model and specify functional requirements and system specifications. College. This document is to be used as the basis for the analysis and design of the system and test cases for the system to be built.1.3 Definitions, acronyms and abbreviationsDES: Department of Education and ScienceSRS: Software Requirements Specification1.4 References[This subsection should provide a complete list of all documents referenced elsewhere in the SRS. Each document should be identified by title, report number (if applicable), date and editorial organization. Specify the sources from which references can be obtained. Such information may be provided by reference to an appendix or other document.]2. General description2.1. User characteristics2.1.1. Student: an individual who completes the registration form with the aim of becoming an evening class student2.1.2. Administrator- a person who interacts closely with the night class enrollment system2.1.3. Director of Adult Education – a person who creates a DES return report at the end of an academic year2.2. User environment2.2.1. The traditional system platform for database is Apache server. I use MySQL database and PHP 2.3 scripting language. Assumptions and dependencies2.3.1. It is assumed that all St.John's Central College office staff receive at least 2 hours of training prior to using the database3. Re specific... half of the document... application requirements or other usage limitation requirements that the software must exhibit.]3.10 Legal Notices, Copyright and Other Notices[This section describes any necessary legal disclaimers, warranties, copyright notices, patent notices, word marks, trademarks, or logo compliance issues for the Software.]3.11 Applicable Standards[This section describes by reference any applicable standards and the specific sections of those standards that apply to the system described. For example, this could include legal, quality and regulatory standards, industry standards for usability, interoperability, internationalization, operating system compliance, etc.]4. Supporting Information[Supporting information makes the SRS easier to use. Includes: • Table of Contents • Index • Appendices May include use case storyboards or user interface prototypes. When appendices are included, the SRS should explicitly state whether or not the appendices are to be considered part of the requirements.]