Student Management System

Table of Contents

1. INTRODUCTION ................................................................................................................................................... 1
1.1 PURPOSE .............................................................................................................................................................. 1
1.2 SCOPE .................................................................................................................................................................. 1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS ................................................................................................ 1
1.4 REFERENCES ........................................................................................................................................................ 2
1.5 OVERVIEW ........................................................................................................................................................... 2
2. GENERAL DESCRIPTION ................................................................................................................................... 2
2.1 PRODUCT PERSPECTIVE ....................................................................................................................................... 2
2.2 PRODUCT FUNCTIONS .......................................................................................................................................... 2
2.3 USER CHARACTERISTICS ..................................................................................................................................... 3
2.4 ASSUMPTIONS AND DEPENDENCIES ..................................................................................................................... 3
3. SPECIFIC REQUIREMENTS ............................................................................................................................... 4
3.1 EXTERNAL INTERFACE REQUIREMENTS ............................................................................................................... 4
3.1.1 User Interfaces ............................................................................................................................................ 4
3.1.2 Hardware Interfaces ................................................................................................................................... 4
3.1.3 Software Interfaces...................................................................................................................................... 4
3.1.4 Communications Interfaces ......................................................................................................................... 4
3.2 FUNCTIONAL REQUIREMENTS .............................................................................................................................. 5
3.2.1 Student Registration .................................................................................................................................... 5
3.2.2 Student Attendance Management ................................................................................................................ 5
3.2.3 Opinion Management .................................................................................................................................. 5

3.3.1 Student Processes........................................................................................................................................5

3.3.2 Administrator Process ................................................................................................................................. 5
3.4 VIEWS..........................................................................................................................................................................................................6
3.5 NON-FUNCTIONAL REQUIREMENTS ..................................................................................................................... 7
3.5.1 Performance ................................................................................................................................................ 7
3.5.2 Reliability .................................................................................................................................................... 7
3.5.3 Availability .................................................................................................................................................. 7
3.5.4 Security ....................................................................................................................................................... 8
3.5.5 Maintainability ............................................................................................................................................ 8
3.5.6 Portability ................................................................................................................................................... 8

3.6 OTHER REQUIREMENTS ....................................................................................................................................... 8

4. Design Constraintss............................................................................................................................................. 9
4.1 SEQUENCE DIAGRAMS ......................................................................................................................................... 9
4.2 DATA FLOW DIAGRAMS (DFD) ......................................................................................................................... 10
4.3 STATE-TRANSITION DIAGRAMS (STD) .............................................................................................................. 11
4.4 Use Case Diagram ............................................................................................................................................. 12
4.5 Entity – Relationship Diagram...........................................................................................................................13

Software Requirements Specification Page iii

 Student Management System

1. Introduction
Student management system has become important factors in modern education field.
This system should help the institutional to streamline the administrative task and provide
real-time access to the data. Building this system in web based interface will further help the
ease of accessibility through any web browser. The study findings enable the definition of the
project problem statement, its objectives, scopes and advantages of the student management
system.

1.1 Purpose
The purpose this documents is to present a detailed description of the Student
Management System. It will explain the purpose and features of the software, the interfaces
of the software, what the software will do, the constraints under which it must operates and
how the software will react to external stimuli. This document is intended for both the end
users and the developers of the software.

1.2 Scope
This document covers the requirements for the Student Management System. This
software will provide a graphical environment in which the users of the system will be able
to perform various operations that are associated with storing, marinating, updating and
retrieving Student information. The purpose of this is to guide developers in selecting a
design that will be able to accommodate the full-scale application.The system will capture
information about student’s personal details lectures and the courses . Storing updating and
retrieving in a fast and accurate way.

1.3 Definitions, Acronyms, and Abbreviations

The Student Management System has to handle records for many number of students
and maintenance was difficult. Though it has used an information system, it was totally
manual. Hence there is a need to upgrade the system with a computer based information
system.

Software Requirements Specification Page 1

 Student Management System

1.4 References
An Integrated Approach to Software Engineering Approach - Pankaj Jalote
Software Engineering A Practitioner’s Approach - Roger S Pressman

1.5 Overview
The purpose this documents is to present a detailed description of the Student
Management System. It will explain the purpose and features of the software, the
interfaces of the software, what the software will do, the constraints under which it must
operates and how the software will react to external stimuli. This document is intended for
both the end users and the developers of the software.

2. General Description
2.1 Product Perspective
The product Student Management system, is an independent product and does not
depend on any other product or system. The product will automate various tasks associated
with handling student details and better organizing the stored information and optimum
performance, thus helping the Colleges to ensure smooth working of these processes.

2.2 Product Functions

Our system has two types of accessing modes,
1. Administrator
2. User
2.1 Teacher
2.2 Student
i) Administrator:
SMS is managed by Administrator. Administrator has to update and monitor the registered
student details, add a new student, provide register number for all students, assign each
student a course etc., Administrator can update his profile, and also can give help to the
teachers and students.

Software Requirements Specification Page 2

 Student Management System

ii) User:
There are two users:
a. Student:
User can only view their personal details, course assigned, and edit their
assigned course and can view their attendance.
b. Teacher:
User can add them onto the portal and view their schedules, marks
attendance of the students, also can view the students details in graphical order,
also of a single student and about the views from the students.

2.3 User Characteristics

This software gives access to two kinds of users.
1. Administrator: The personnel and College administrator will have
administrator access to add, delete and modify information stored in the
database.
2. Authorized User: Teaching staff will have access to only view the data stored
in the database and can update the student’s attendance in the form of
formatted reports.

2.4 Assumptions and Dependencies

 We assume that the Office personnel do all the data entry based and the correct
values obtained from forms and registers.
 We assume that the computers that will use the software will be part of the
college LAN.
 Users with administrator access should be careful in deleting or modifying any
information knowingly or unknowingly which will lead to inconsistency of the
database.
 The end users of this software are assumed to have basic level of computer
knowledge i.e. point and click.

Software Requirements Specification Page 3

 Student Management System

3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
 GUI along with meaningful Frames and buttons
 Reports are generated as per the requirement
 Refer Appendices 2.

3.1.2 Hardware Interfaces

Hardware Environment Dual Core 2nd generation/

System Configuration RAM-512 MB HDD-80GB

Operating system Windows XP/Vista/7/8/8.1

3.1.3 Software Interfaces

Front End PHP 5.3.0

Back End MySQL 5.1.36

When invalid inputs are given to the modules then the error messages will be popped up
in order to inform the user that the input provided is not taken by the database. When
incomplete information is provided by the user and the user tries to submit the form in
order to store the details in the database the system will pop up a message box asking the
user to enter all the details required.

3.1.4 Communications Interfaces

The machine will have to be part of the college Local area Network to access the
central database.

Software Requirements Specification Page 4

 Student Management System

3.2 Functional Requirements

Student Management System involves the following functions
3.2.1 Student Registration:
- SMS provides online registration and status information to the student to view
their status.
- SMS provides automatic student register number generation based on course and
year.
- SMS provides to students to add them in their course they want to study.

3.2.2 Student Attendance Management:

- Easily track attendance information of students.
- Quickly produce single or multiple day attendance bulletins.

3.2.3 Opinion Management:

- SMS provides a comprehensive opinion scheduling based on course.
- Students can facilitate to give their opinions by giving the teacher rank.

3.3 Use Cases

Software Requirements Specification Page 5

 Student Management System

3.4 Classes / Objects

Software Requirements Specification Page 6

 Student Management System

3.5 Non-Functional Requirements

3.5.1 Performance
Easy tracking of records and updating can be done. All the requirements relating to
performance characteristics of the system are specified in the section below. There are
two types of requirements.
A. Static Requirements
These requirements do not impose any constraints on the execution characteristics of the
system. They are:
1) Number of Terminals:
The software makes use of an underlying database that will reside at the server,
while the front end will be available online to the administrative and departmental
computers as well as students and teachers.
2) Number of Users:
The number of users may vary, as this software finds applications in almost all
department of the organization.

B. Dynamic Requirements
These specify constraints on the execution characteristics of the system. They typically
include response time and throughout of the system. Since these factors are not
applicable to the proposed software, it will suffice if the response tine is high and the
transactions are carried out precisely and quickly.

3.5.2 Reliability
The software will not be able to connect to the centralized database in the event that the
college LAN fails or in the event of the server being down due to a hardware or software
failure.

3.5.3 Availability
The software will be available only to authorized users of the colleges like teachers to
mark the students attendance, student to view their enrolled course, admin to add an
update students records

Software Requirements Specification Page 7

 Student Management System

3.5.4 Security
The security requirements deal with the primary security. The software should be handled
only by the administrator and authorized users. Only the administrator has right to assign
permission like creating new accounts and generating password. Only authorized users
can access the system with username and password.

3.5.5 Maintainability
Backups for database are available.

3.5.6 Portability
The Software is a web-based application and is built in PHP and MYSQL so it is
platform independent and is independent of operating system.

3.6 Design Constraints

This software provides security. The login form prevents the system from being
misused by unauthorized users. Only an authorized operator will be granted rights to
modify as per requirements. This software is also reliable and fault tolerant. The system
developed is designed to handle invalid inputs. Since reliability is major area of concern
the system has a backup to avoid data loss. The user should know the programming
language very well that is used to develop a software.

3.7 Other Requirements

Database
All the data will be stored in a relational database

Software Requirements Specification Page 8

 Student Management System

4. Analysis Models
4.1 Sequence Diagrams

Student
Registration
Class Administration

Attendance
Student
Student
Administration

Student
Performance

Students Opinions about

Students Profile subjects
Updation

Software Requirements Specification Page 9

 Student Management System

4.2 Data Flow Diagrams (DFD)

username
password
id

Admin

Access

dept
id Student Phone no

Name
e email

username
address
password
view

Attend_id

Date Attendance Schedule Subject

Subject event time name

Student name schedule venue Mentor name

description

Software Requirements Specification Page 10

 Student Management System

4.3 State-Transition Diagrams (STD)

Software Requirements Specification Page 11

 Student Management System

A. Appendices

A.1 Appendix 1: Glossary

Following abbreviations have been used throughout this document:

DFD : Data Flow Diagram

ERD : Entity Relationship Diagram
SRS : Software Requirement Specification
SQL : Structured Query Language
SMS : Student Management System
STD : State Transition Diagram

Software Requirements Specification Page 12

 Student Management System

A.2 Appendix 2: User Interface

A) ADMIN LOGIN

1) STUDENT MENU 2) ADMIN MENU 3) TEACHER MENU

C) TEACHER SCHEDULE

Software Requirements Specification Page 13

 Student Management System

D) ATTENDACE MARKER E) STATICS

F) STUDENT COURSES MENU

G) STUDENT ENROLLMENT MENU

Software Requirements Specification Page 14

 Student Management System

H) STUDENT’S ATTENDANCE

Software Requirements Specification Page 15