Software Requirements Specifications1. Introduction1.1 PurposeThis document is a definition of software requirements for developing an automated evening course registration system and flexible query database required by St.John's Central College. This document will present the functional, non-functional requirements and design constraints for the system to be developed. Models and use case descriptions are included along with class diagrams to help model and specify functional requirements and system specifications.1.2 ScopeThe software application that this SRS applies to an automated registration system of night classes and a flexible query database required by St. John's Central College. This document should be used as a basis for system analysis and design 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 must be identified by its title, report number (if applicable), date and issuing body. Specify the sources from which references can be obtained. This information may be provided by reference to an annex or another document.]2. Overall description2.1. User characteristics2.1.1. Student - a person completing the registration form with the aim of becoming a student in the evening course2.1.2. Administrator - a person in close interaction with the evening course registration system2.1.3. Director of Adult Education – an individual who creates the DES report returns the DES at the end of an academic year2.2. User environment2.2.1. The traditional system platform for database is Apache server. I'm using MySQL database and PHP2.3 scripting language. Assumptions and dependencies2.3.1. It is assumed that all office staff at St. John's Central College will receive at least two hours of training before using the database3. Specific restriction...... middle of paper ...... application requirements or other usage restriction requirements that must be presented by the software.]3.10 Legal, copyright and other notices [ This section describes all necessary legal notices, warranties, copyright notices, patent notices, wordmark, or logo compliance issues for the Software.]3.11 Applicable Standards[This section describes by references 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. Additional information[Additional information facilitates the use of the SRS. It includes: • Table of contents • Index • Appendices These may include use case storyboards or user interface prototypes. Where annexes are included, the SRS must explicitly state whether or not the annexes are to be considered part of the requirements..]