Professional Documents
Culture Documents
College Management System SRS PDF
College Management System SRS PDF
SPECIFICATION
for
Release 1.1
Prepared by Team 3
Contents
1 Introduction 4
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Project Scope and Product Features . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Intended Audience and Document Overview . . . . . . . . . . . . . . . . . . . . . 4
1.4 Definations, Acronyms, and Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5
1.4.1 Definations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4.2 Acronyms, and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Overall Description 7
2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 User Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Specific Requirements 9
3.1 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.1 User Class one - Student . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.2 User Class two - Administrative head(Super user) . . . . . . . . . . . . . 14
3.2.3 User Class three - Faculty . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2.4 User Class four - HEC head . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.5 User Class Mess committee head- Student . . . . . . . . . . . . . . . . . . 24
3.3 Non Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.2 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.3 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.4 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4 Supporting information 28
4.1 upadate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2
Revision History
Revision Revision Date Description of Change Author/Modifier
v1.0 Sept 12,2015 Initial Document Shubham Subhankar Sharma/Vikash Saini
v1.1 Sept 25,2015 Second Document Shubham Subhankar Sharma/Vikash Saini
3
1 Introduction
The title of the project is COLLEGE MANAGEMENT SYSTEM (CMS). CMS is an Internet
based application that aims at providing information to all the levels of management within an
organization. This system can be used as a information management system for the college.
For a given user, the administrator will create a loginid & password, using this user can access
the system to either upload or download some information from the database.
The front-end will be HTML pages with Java Script for client side validation where as all
business logics will be in PHP reside at middle layer. And these layers will interact with third
layer of database, which will be MySql database. The web server will be Apache. To start
working on this project environment required is a server having Apache as web server, MySql
as database and XAMPP as development environment
1.1 Purpose
The purpose of this document is to present a detailed description of the College Management
System. It will explain the purpose and features of the system, the interfaces of the system,
what the system will do, the constraints under which it must operate and how the system will
react to external stimuli. This document is intended for both the client and the developers of
the system and will be proposed to the Administrative head for its approval.
4
1.4 Definations, Acronyms, and Abbreviations
1.4.1 Definations
• Browser : Software used to view hypertext documents. Internet Explorer and Netscape
Navigator are examples of browsers.
• Web Portal : A web portal is most often one specially designed web page that brings
information together from diverse sources in a uniform way.
• Data Integrity : Data integrity refers to maintaining and assuring the accuracy and
consistency of data over its entire life-cycle, and is a critical aspect to the design, imple-
mentation and usage of any system which stores, processes, or retrieves data.
Acronyms Meaning
AJAX Asynchronous Java-Script and XML
API Application Programming Interface
XML Extensible Markup Language
DBMS Database Management System
IEEE Institute of Electrical and Electronics Engineers
kbps Kilo-Byte Per Second
HTML Hypertext Markup Language
CSS Cascading Style Sheets
GUI Graphical User Interface
mbps Mega-Byte Per Second
OS Operating System
RAM Random Acess System
SDLC Software Development Life Cycle
URL Universal Resource Locator
5
1.5 References
• http://www.cse.msu.edu/~chengb/RE-491/Papers/SRSExample-webapp.doc
• https://web.cs.dal.ca/~arc/teaching/CS3130/Templates/SRS%20and%20Project%20Plan%
20Templates/SRS-template1.doc
• http://regisindia.com/wp-content/uploads/2013/10/SRS-Development-of-Web-GIS-Tool_
IEEE-SA-830-SRS-Format_Final_27082013.pdf
• https://en.wikipedia.org/wiki/Software_requirements_specification
• https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=
8&ved=0CBwQFjAAahUKEwjXre2yxILIAhVNjo4KHXS3Bug&url=http%3A%2F%2Fhome.agh.edu.
pl%2F~jsw%2Fio%2FIEEE830.doc&usg=AFQjCNEfca8yYVNSEGzj6a5NT6TvIaKbXQ&sig2=osOXYy-hIwIb
bvm=bv.103073922,d.c2E
• http://www.cse.chalmers.se/~feldt/courses/reqeng/examples/srs_example_2010_
group2.pdf
6
2 Overall Description
2.1 Product Perspective
The product will be a standalone application and may be run on multiple systems within an
Internet network. The product will require a keyboard, mouse and monitor to interface with
the users. The minimum hardware requirements for the product are specified in this document
• Administrator The Super user of the system. Mainly focuses on administratiive and
academic related issues.
• Staff A user of the system who has more access rights than a normal user.
2.3 Constraints
The current constraints on the project are related to the provision of hardware resources and
software resources.
• At present, we have a i3 gen4 intel core processor running on top of the Linux/windows
operating system.
• In the feedback forms, the replies will not be frequent and the petitioner will not be
anonymous.
• There will not be any moderater to filter out the fake complains with the genuine ones.
The superuser have to do it himself manually.
• The Internet connection is also a constraint for the application. Since the application
fetches data from the database over the Internet, it is crucial that there is an Internet
connection for the application to function.
7
• The web portal will be constrained by the capacity of the database. Since the database
may be forced to queue incoming requests and therefor increase the time it takes to fetch
data.
• College will provide funds for SMS service if SMS service is not free.
• After submitting the course evaluation form, the user cannot revert his or her actions.
• The user cannot change his/her all personal or academic details. He/she first have to get
permission from the super user to do so.
• It is assumed that only one person from the different department will have the access to a
module.i.e. Only heads of administration, academics, HEC and Mess will have the access
to their department except the faculty.
• The complaints and the feedback given by the students and other members of the organi-
zation are assumed to be reliable.
• The schedule for the exam , the registration window will be open for only few days only
after that these pages will be inactive until next exams or registration period.
• Apportioning of requirements
In the case that the project is delayed, there are some requirements that could be trans-
ferred to the next version of the application. Those requirements are to be developed in
the third release.
8
3 Specific Requirements
This section contains all the software requirements at a level of detail sufficient to enable design-
ers to design a system to satisfy those requirements, and testers to test that the system satisfies
those requirements. Throughout this section, every stated requirement should be externally
perceivable by users, administrator, or, other external systems.
• Software Platform:
Browser :
- Mozilla Fire-Fox v12.0 or higher
- Google Chrome v27.0.1453.116m or higher.
Server:
• Hardware Platform:
- PIII or above with
- RAM of 512 or above MB
- HardDisk 20GB or above GB.
• SoftwarePlatform:
-HTML,PHP,JavaScript,MySql,Apache,CSS,MVC,Bootstrap
• User Interface:
A first-time user of the web portal should see the log-in page when he/she opens the portal.
If the user has not registered, he/she should be able to do that on the log-in page. It will
also have a remember me button.If the user is not a first-time user, he/she should be
able to see the dashboard which contains different domains like academics, Hostel, Profile,
Mess, Transport.A news bulliten, some general information, list of holidays and different
timetables will also be visible on this page.Every user should have a profile page where
they can edit their e-mail address, phone number and password and other personal details.
• Communications interfaces
The communication between the client and the server will be done through internet.
9
3.2 Functional Requirements
This section includes the requirements that specify all the fundamental actions of the software
system
10
3.2.1.5 Functional Requirement
ID:FR5
TITLE:Timetables
DESC:The user can view timetable for classes, mess and buses on the front page of the portal
after logging into the system.
RAT:By geting this information, user can schedule his routine and better utilize his/her precious
time.
DEP:FR1
11
RAT:This feature makes the process move convinient,fast and less cumbersome.
DEP:FR1,FR8
12
3.2.1.14 Functional Requirement
ID:FR14
TITLE:Exam Schedule
DESC:The user can view the exam schedule.
RAT:By using this feature,the user can prepare and plan his efforts in a better way.
DEP:FR1,FR8
13
3.2.1.19 Functional Requirement
ID:FR19
TITLE:Mess Rebate
DESC:The user can request for his/her mess rebate by formally applying providing a valid rea-
son and the period of his abscence. After the verification of his request, the mess committee
will either accept or deny the request and the user will be informed accordingly. The system
will keep track of the days the rebate request was succesfully accepted.
RAT:The user can easily get rebate from mess and can also keeps track of his rebate request.
DEP:FR1,FR10
14
and address details. The profile will contain name, age,permanent address, parent’s name, their
address, their contact details, branch, year, semester, room alloted, hostel name and no. etc.
RAT:To update his/her profile and know his or her status.
DEP:FR21
15
DEP:FR21
16
3.2.2.12 Functional Requirement
ID:FR32
TITLE:Assignments and reading references
DESC:The user can download the reading and writing assignments uploaded by the faculty for
their course.
RAT:The user will have a remote access to the assignments.
DEP:FR21,FR28
17
DESC:The user can view details of the fee transaction details of all the students batchwise.
RAT:This feature makes the process move convinient,fast and less cumbersome.
DEP:FR21,FR28
18
3.2.3 User Class three - Faculty
3.2.3.1 Functional Requirement
ID:FR42
TITLE:Login into the Portal.
DESC: The user can login into the system by providing its loginid and password to the portal
which are unique and provided by the college.
RAT:To login into the portal and take advantage of the services provided by it.
DEP:None
19
after logging into the system.
RAT:By geting this information, user can schedule his routine and better utilize his/her precious
time.
DEP:FR42
20
3.2.3.10 Functional Requirement
ID:FR51
TITLE:Assignments and reading references
DESC:The user can upload the assignments on to the portal according to the year, batch and
course.
RAT:The user will have a remote access to the assignments.
DEP:FR42,FR49
21
DEP:None
22
3.2.4.6 Functional Requirement
ID:FR60
TITLE:List of upcoming holidays
DESC:The user can view the list on upcoming holidays on the front page of the portal after
logging into the system.
RAT:He/she could plan for vacations and other co-curricular activites.
DEP:FR55
23
DEP:FR55
24
3.2.5.2 Functional Requirement
ID:FR69
TITLE:Change password
DESC:Change the password after logging into the system.The user will be asked a security
question if he/she forgets his/her password. In case, he/she is unable to do so, the user has to
formally apply to the admin for the change of his/her password providing the necessary proof.
RAT:For security purposes, the user can choose his/her password
DEP:FR68
25
logging into the system.
RAT:He/she could plan for vacations and other co-curricular activites.
DEP:FR68
26
and the feedback of mess related issues.
RAT:The user can get relieve from his/her problems without much effort or conflicts.
DEP:FR68
3.3.2 Reliability
Must maintain data integrity. Computer crashes and misuse should not affect a user’s history
3.3.3 Availability
The CMS Portal shall be available, up and running for 24*7 throughout the year except due to
the routine maintenance activities.
27
4 Supporting information
4.1 upadate
• Transpotation Funcationally is removed from our project.
28