Software Requirements Specification 1. Introduction 1. 1 Purpose This document is a definition of software requirements to develop an automated night class enrollment 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 the functional requirements and specifications of the system. 1. 2 Scope The software application that this SRS applies to a night class automated enrollment system and flexible query database required by St. John’s Central College.
This document is to be used as basis for the analysis and design of the system and test cases for the system that is to be built. 1. 3 Definitions, Acronyms and Abbreviations DES: Department of Education and Science SRS: Software Requirement Specification 1. 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 publishing organization.
Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document. ]2. Overall Description 2. 1. User characteristics 2.
1. 1. Student- an individual filling out Enrolment Form with the purpose of becoming a night class student 2. 1.
The Essay on Systems Gathering Requirements Document
During the systems planning phase a feasibility analysis was performed in determining if purchasing a software program would meet the demands of operations (need), technical (practicality), and economic (financial) factors of the project. Given the fact that over time, collateral analysts spend a tremendous amount of time manually calculating borrowing base ineligibles from cumbersome agings, ...
2. Administrator- a person closely interacting with the Night class enrollment system 2. 1. 3. Director Of Adult Education – a person who creates DES returns report at the end of an academic year 2. 2.
User environment 2. 2. 1. The traditional system platform for the database is Apache server.
I am using my SQL database and PHP scripting language 2. 3. Assumptions and dependencies 2. 3. 1. It’s assumed that all the office staff of St.
John’s Central College will get at least 2 hours training prior to the using of the database 3. Specific Requirements 3. 1. All fees are payable on enrollment 3.
2 The formation of any classes is dependent upon adequate enrollment (minimum 8 students per class maximum 20 students per class) 3. 3 Enrolment of all courses will be on first come first serve basis 3. 4 Senior citizens (over 65 years) are entitled to 50% reduction fees 3. 1 Functionality 3. 1. 1.
Night class enrollment form should be available on-line for all potential students; 3. 1. 2. After submission of filled out enrollment form, student should get a confirmation message; 3. 1.
3. Administration part of the software should contain office use only enrollment form; 3. 1. 4. The system should have provisions for entering fee payments and refunds for the students; 3. 1.
5. The system should provide the way to view the number of students enrolled for every course; 3. 1. 6.
The system should automatically generate receipt number after the fee is paid, this receipt should be in printable format; 3. 1. 7. The system should provide the way to view, e-mail or print Class Register; 3. 1. 8.
The system should provide the way to enter and view examination results for every student; 3. 1. 9. The system should provide the way to enter and view attendance for every student enrolled; 3.
1. 10. The system should provide the end of the year Department of Education and Science report, including total number of students enrolled for the course, total fee paid and number of enrollment hours per course 3. 1. 11. The system should provide a search engine by which the user can browse by enrollment year, enter key words, or enter student specific information.
The Term Paper on Group Member System Student Information
System Development ITC 712 Project Proposal Prepared for: Mr. Samsudin Md. Strip Prepared by: Lizawati Bakri (2003215593) Mohd. Farhan Md.Fudzee (2003661166) Shadil Akimi b. Zainal Abidin (2003215952) Masters of Science in Information Technology (MSc. IT) CS 770 Project Title: "STARIS" Sekolah Tuanku Abdul Rahman Information System Due date: 1 August 2003 TABLE OF CONTENTS 1) Introduction To The ...
Based on this input, the system will list possible matches. 3. 2 Usability 3. 2.
1. The web server System User Interface">user interface must be accessible by versions of Internet Explorer and Netscape Navigator released since 1998. 3. 2. 2. A random group of 10 non-handicapped people who have filled out an application form on the internet at least once before, should be able to fill out the Enrolment form.
They should be able to do this on a LAN connected computer with an unloaded server within 10 minutes. 3. 2. 3. The application should have a “Help” link that will pop-up a window explaining the instructions. 3.
3 Reliability 3. 3. 1. The system should be available and accessible online 99% of each month.
3. 3. 2. For system should never be allowed to permanently loose database memory. 3. 3.
3. For fatal failures that temporarily disable the entire system, the MTBF should be at least 6 weeks 3. 3. 4. For fatal failures that temporarily disable the entire system, the M TTR should be within 30 minutes 90% of the time, and within 2 hours 99. 9% of the time.
3. 3. 5. The system should have no more than 2 open defects per thousand lines of code. 3. 4 Performance 3.
4. 1. The average response time should be less than 4 seconds 80% of the time, and less than 8 seconds 99% of the time for clients that are connected to the server directly. 3. 4. 2.
The network capacity should be able to support more than 10 Gbps. 3. 5 Supportability 3. 5. 1 Use of open source software The database management system is my SQL, scripting language is PHP and its function libraries. In this system, PHP is used to develop the application logic that brings together the Web and the relational database management system.
Apache is a web server of a choice. 3. 6 Design Constraints 3. 6. 1 Software requirements. 3.
The Term Paper on Software Requirements Specification On E-Library
... describe how the software operates inside various constraints. 2.1.1 System Interfaces List each system interface and identify the functionality of the software to accomplish the system requirement and the interface ... you need to specify i.e. 2.1.4.1 Microsoft SQL Server 7. The system must use SQL Server as its database component. Communication with the ...
6. 1. 1. Server should support PHP scripting language 3. 6. 1.
2. Apache as a web server 3. 6. 1. 3.
Database management system is my SQL 3. 6. 2 Hardware Requirements. 3. 6. 2.
1 Pentium 4 1. 6 G HZ Windows PCs 3. 6. 2.
2 Unix Box running Sun OS for web server 3. 6. 2. 3 Windows 2000 web server 3. 7 On-line User Documentation and Help System Requirements[Describes the requirements, if any, for on-line user documentation, help systems, help about notices, etc. ]3.
8 Interfaces 3. 8. 1 User Interfaces[Describe the user interfaces that are to be implemented by the software. ]3.
8. 2 Hardware Interfaces 3. 8. 3 Input Devices 3. 8. 3.
1 Mouse The mouse is the major input device, allowing the models to be created and edited. Many functions can be done without a mouse, but a mouse is required for full functionality. This does not strictly have to be a mouse, any two buttoned pointing device should be sufficient. 3. 8. 3.
2 Keyboard The keyboard is required for entering textual information. Most of the node properties will be text based so require the keyboard for input. Some GUI based functions can also be performed using the keyboard. 3.
8. 4 Output Devices 3. 8. 4. 1 Screen The screen is the major output device. It supports the GUI interface by providing the user with feedback relating to the mouse and keyboard, as well as the content of the application, namely the models.
The screen should support 256 colors in 1024 x 768 resolution. 3. 8. 4. 2 Printer A printer allows hard copies of the models to be printed. Either a local or networked printer should be suitable.
A printer capable of printing black and white in 300 dpi should be sufficient. 3. 8. 5 Software Interfaces[This section describes software interfaces to other components of the software system. These may be purchased components, components reused from another application or components being developed for subsystems outside of the scope of this SRS but with which this software application must interact. ]3.
8. 6 Communications Interfaces[Describe any communications interfaces to other systems or devices such as local area networks, remote serial devices, etc. ]3. 9 Licensing Requirements[Defines any licensing enforcement requirements or other usage restriction requirements that are to be exhibited by the software. ]3. 10 Legal, Copyright, and Other Notices[This section describes any necessary legal disclaimers, warranties, copyright notices, patent notice, word mark, trademark, or logo compliance issues for the software.
The Essay on Software Requirement Specification 2
... requirements of the system are described here. It gives a detailed description of the system and all its features. 3. 1 External interface requirements The DACM system ... Practice for Software Requirements Specifications”, October 20, 1998. [2] Pressman, Roger (2010). Software Engineering: A ... will use the standard input/output devices for a personal ...
]3. 11 Applicable Standards[This section describes by reference any applicable standard and the specific sections of any such standards which apply to the system being described. For example, this could include legal, quality and regulatory standards, industry standards for usability, interoperability, internationalization, operating system compliance, etc. ]4. Supporting Information[The supporting information makes the SRS easier to use.
It includes: o Table of content so Index Appendices These 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. ].