SRS School Management Sys

\
School
Management System
SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENT
09-07-2019
BUSHRA TARIQ Roll No 171605

SESSION: 2017 - 2019 | COMPUTER SCIENCE & IT, IDEAL COLLEGE HASILPUR
School Management System
Revision History
Date Description Author Comments
09-07-2019 Version 1 Bushra Tariq First Revision
Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
Signature Name Title Date

Supervisor, CSIT 21306 09/07/2019
ii
Table of Contents
Chapter.1 Introduction Error! Bookmark not defined.

1.1 Purpose 1
1.2 Scope 1
1.3 Definitions, Acronyms, and Abbreviations. 1
1.4 References 2
1.4 Overview 2
Chapter.2 The Overall Description 3

2.1 Product Perspective 3
2.2 Product Functions 3
2.3 User Characteristics 3
2.4 General Constraints 4
2.5 Assumptions and Dependencies 4
Chapter.3 Specific Requirements 5

3.1 External Interface Requirements 5
3.1.3 Hardware Interfaces 5
3.1.4 Software Interfaces 5
3.1.4.1 Microsoft SQL Server 7 6
3.2 Functional Requirements 6
3.2.2 User Login 6
3.2.4 Exams Schedule 7
3.2.5 Attendance 7
3.2.6 Fee Schedule 7
3.2.7 Reports 8
3.3 Use Cases 8
3.5 Non-Functional Requirements 11
Chapter.4 Analysis Models 12

4.1 Sequence Diagrams 12
4.2 Data Flow Diagrams (DFD) 13
4.2.1 Context Level Diagram 13
4.2.2 First Level Data Flow Diagram 14
4.2.3 Second Level Data Flow Diagram 17
Chapter .5 INTRODUCTION 19
iii
5.1 Purpose 19
5.2 Scope 19
5.3 Overview 19
5.4 Reference Material 19
5.5 Definitions 19
Chapter.6 SYSTEM OVERVIEW 20

6.1 Assumptions 20
6.2 General Constraints 20
6.3 System Environment 20
Chapter.7 SYSTEM ARCHITECTURE 21

7.1 Architectural Design 21
7.2 Decomposition Description 21
7.3 Design Rationale 22
Chapter.8 DATA DESIGN 22

8.1 Data Description 22
8.2 Data Dictionary 23
8.3 Employee Database 24
8.4 Employee Data Dictionary 25
8.5 Exams Data Description 27
8.6 Exams Data Dictionary 27
Chapter.9 COMPONENT DESIGN 29

9.1 Home 29
9.2 Admin 29
9.3 Student 29
9.4 Information records 29
9.5 Exam 29
9.6 Fee structure 29
9.7 Reports 30
Chapter.10 HUMAN INTERFACE DESIGN 30

10.1 Overview of User Interface 30
10.2 Screen Images 30
10.2.1 Home Page 30
10.2.2 Description Error! Bookmark not defined.
10.2.3 Login 31
10.2.4 Description 31
iv
10.2.5 Admin Page 32

10.2.6 Description 32
10.2.7 Student Page 33
10.2.8 Description Error! Bookmark not defined.
10.2.9 Exam Page 34
10.2.11 Fee Structure Page 35
7. REQUIREMENTS MATRIX 35
v
Chapter.01 Introduction
Education is point to spotlight for evolution the society and various educational
systems that are using to increase the nature of education they provide. Generally it
used to adapt modern instrument for advancement and smooth activity of the institute.
School Management System is the Database System that used for managing the
day to day tasks of the organization and is employed on a web server, which is
accessible to users worldwide, but with the constraint of authorization imposed before
being able to use the administrative tasks of the organization.
1.1 Purpose
It used to get requirements and specifications of School Management System. It will be
provides the functionalities of School Management System and encompasses interface
details, design constrictions, and characteristics. In that case when any user wants to take
information it is very difficult for management to provide information immediately. It is
time consuming process.
1.2 Scope
This application has a very broad scope including the management of staff,
admitting students, managing credentials of users, admitting new students into the
school via this system by creating profile of each student, marking attendance of
employees as well as students, managing and maintaining salaries of the staff,
management of fee information, store information into the databases with absolute
validation, and any other tasks related to manage and maintain records of the
organization and the Examination control system and also the result of the
examination.
The scope of the School Management System is very huge. It will be manage
the much functionality that will be necessary for the management of the system. It
also manages the many functions at a time.
1.3 Definitions, Acronyms, and Abbreviations.

1.3.1 CSS
 CSS (Cascading Style Sheet) is a language which is used to define a document in markup
language. CSS is used by most of the websites in order to design interfaces of web
applications and mobile apps.
 CSS describes how HTML components are to be advertised on screen, paper, or in other
media.
1.3.2 PHP
 PHP is composition for "PHP: Hypertext Preprocessor"

 PHP is a widely-used, open cause scripting language
 PHP scripts are performed on the server
 PHP is download and use without charge
PHP is designed language resolve on server-side which is used for

implement websites.
1
1.3.3 MYSQL
MySQL is an open source that is widely used to relational database
management system.
1.3.4 HTML
HTML (Hyper Text Markup Language) are used for creating the web
pages and the websites.
1.3.5 JavaScript
JavaScript is a programming language which is used with HTML and CSS and
World Wide Web. It is based on prototypes and it provides object oriented functionalities as
well.
1.4 References
Bert, B. (1999, June). Cascading_Style_Sheets. Retrieved April 12, 2016, from Wikipedia:
https://en.wikipedia.org/wiki/Cascading_Style_Sheets
Bos, B., & Lie, H. W. (1996, December 17). Cascading Style Sheet. Retrieved March 21, 2016, from
Wikipedia: https://en.wikipedia.org/wiki/Cascading_Style_Sheets
Corporation, O. (1995, May 23). MySQL. Retrieved March 21, 2016, from Wikipedia:
https://en.wikipedia.org/wiki/MySQL
Lerdorf, R. (1995). PHP. Retrieved March 21, 2016, from Wikipedia:
https://en.wikipedia.org/wiki/PHP
Lerdorf, R. (2015, December 03). PHP#PHP_7. Retrieved April 12, 2016, from Wikipedia:
https://en.wikipedia.org/wiki/PHP#PHP_7
World Wide Web Consortium, W. (2014, October 28). HTML5. Retrieved April 04, 2016, from
Wikipedia: https://en.wikipedia.org/wiki/HTML5
1.4 Overview
This SRS are including in three Chapters. In chapter 1, there are introduction
about the school management system. In Chapter 2, discussed that provides
general view of the application and activities required for school environment.
In Chapter 3 describes research work carried out for the application including
different requirement segments.
2
Chapter.02 The Overall Description

In this particle of SRS, common condition of the product and its
requirements are representing.
2.1 Product Perspective
2.1.1 Operations
Present system is managed the manual record keeping which makes it very
difficult to manage and maintain the day to day operations of the institute. Following
are the list of component constitute by this self-contained product.
Attendance Personal
Information
School
Fee Schedule Managemen
Repots
t
System
Exams
Schedule Management
2.1.2 Site Adaptation Requirements

No requirement
2.2 Product Functions

Following are the list of functions that the software product will perform.
 Manage personal data of students and teachers.
 Provide access to staff members to manage exams activities of students and
prepare reports about the results.
 Admin manage attendance of staff and teachers manage attendance of
students.
 Admin manage fee structure of students and salary of staff.
 Ability to generate various types of reports.
2.3 User Characteristics

Admin: A Person that is responsible for managing of school.
Teacher: Persons that are teaching different course in school.
User: Persons who communicate with system generally.
3
2.4 General Constraints

General constraints specify information about what is that will be enter in system and it
is valid or not valid for system.
2.5 Assumptions and Dependencies

In this project these features are include such as authentication so in order
to create any changes within the database, user must be able to login to an account
therefore leaving no effect on rest of the operations of the application.
4
Chapter.03 Specific Requirements

3.1 External Interface Requirements
3.1.1 System Interfaces

Different interfaces are provided for each type of user which provides relevant interface and
also provide the environment.
3.1.2 Interfaces
There will be three types of interfaces available to users.
(1) Admin Interface:
 Login to system.
 Manage the all main activities like creating user accounts, add new
students, check student details, add new teachers, check teacher
information, manage fee and pay structure, manage attendance of staff and
students, generate reports and also manage the advertisement of the
system.
(2) Teacher Interface:
 Login to system.
 Manage the all students activities like student attendance repots, exams
repots, and view academic reports.
(3) User Interface:
Users visit the website for to get the information about the system.
3.1.3 Hardware Interfaces

 Pentium-IV or higher processor
 4GHZ Speed of Processor
 40GB Dard Disk Space
 2GB RAM
3.1.4 Software Interfaces

 CSS
 PHP
 Xampp Server
 Window 7 or above
 HTML
 JavaScript
 Wamp Server
5
3.1.4.1 Microsoft SQL Server 7

For storing records into the database, MySQL database engine will be used.
3.1.5 Communications Interfaces

The communication will be access between the user and the admin through Internet.
3.2 Functional Requirements
3.2.1 User Registration

3.2.1.1 Introduction
To manage the records that resides on database and ability to create user accounts
and their management and also to check and control the working of the user.
3.2.1.2 Inputs
Create the password and IP address for the authorized person can be access.
3.2.1.3 Processing
Provide the list of features for the different operations of the user for maintain the
system.
3.2.1.4 Outputs
The result to performed the currently operations.
3.2.1.5 Error Handling
If unauthorized give wrong password then give message error and also show for again
Login.
3.2.2 User Login

Create new user accounts and their management and also to check and control the
working of the user.
3.2.2.2 Input
Give the Password and IP address for login the system.
3.2.2.3 Processing
The list of features for the different operations of the user.
3.2.2.4 Output
The result of the operations that will be performed.
For to give the wrong password message error show for try again.
3.2.3 Personal Information

All of the details are maintains in the database system’
3.2.3.2 Input
6
User provides to create record about Staff and the students.

3.2.3.3 Process
Each record entry in database as respective tables.
3.2.3.4 Output
After processing the data display the relevant results to the user for verification
purpose.
3.2.4 Exams Schedule

3.2.4.1 Introduction:
In this part of the system includes the details of tests.
3.2.4.2 Inputs:
Enter the marks into the system after selecting a class from the list.
3.2.4.3 Processing
Information is stored in index.
3.2.4.4 Outputs
Acceptance of records are displayed and submitted.
In case of error the data is not full fill the requirements.
3.2.5 Attendance
The user maintaining the attendance of staff and students. Admin has rights to mark
attendance of staff and Staff right to mark attendance of students.
3.2.5.2 Inputs:
After selecting Class give the list for mark attendance of each student.
3.2.5.3 Processing
Attendance will be sorted in the system and calculate present and absent students on
daily and monthly base.
3.2.5.4 Outputs
After the attendance is marked, items to be submitted are displayed to user for
confirmation.
In case of error, message is display for entry again.
3.2.6 Fee Schedule

This component is used to deals the Fee Schedule of students and manages their
records.
3.2.6.2 Inputs:
7
Enter the amount that will be received from the students.

3.2.6.3 Processing
Calculate the input data and give remaining fee of that student is calculated.
3.2.6.4 Outputs
A report of the amount received is generated which indicates Total Fee; Amount
Received and Amount Due along with the details of the student.
In case of error the message is display that the data has been updated or not.
3.2.7 Reports
Two types of report will be generating.
(i) Admin:
Generate reports of teachers and staff, examination and test reports of students.
(ii) Teacher:
Generate reports of student.
3.2.7.2 Inputs:
User provides inputs from list.
3.2.7.3 Processing
Manage and stored the giving list.
3.2.7.4 Outputs
Results are displayed for given input.
3.3 Use Cases

3.3.1
Diagram of use cases.
8
9
3.3.2
Use Case Diagram for School Management System
The admin is manage resources such as manage admission of students, create new account
for the any relevant person about the system, check account information, mark attendance,
view exam details, update attendance, manage income and fee and conduct new exam.
The teacher is managing activities such as about exams, update attendance, schedule exam,
exam reports, create new exam, exam marks and create test reports.
The user is facilitated with following functionalities such as view faculty information, view
results, and view available courses.
10
3.5 Non-Functional Requirements
3.5.1 Performance
To check that the all application will be performed work accurately. Furthermore, the system
should be providing the good quality of the user.
3.5.2 Reliability
The reliability will be depending on the performance of the system. How much the
performance is better of the system then the system much reliable.
3.5.3 Availability
The applications or requirements are available the all-time of the user.
3.5.4 Security
The main and the important part for the protection of the system is security. Security is used
to save the data from the unauthorized person that will be not access of the user personal data.
3.5.5 Maintainability
Requirements are the module base of data that it is easy to maintain.
11
Chapter.4 Analysis Models

4.1 Sequence Diagrams
4.1.1 Diagram 1:
12
4.2 Data Flow Diagrams (DFD)
4.2.1 Context Level Diagram
13
4.2.2 First Level Data Flow Diagram
4.2.2.1 Diagram 1:
14
4.2.2.2 Diagram 2:
4.2.2.3 Diagram 3:
15
16
4.2.3 Second Level Data Flow Diagram
4.2.3.1 Diagram 1:
17
4.2.3.2 Diagram 2:
18
Chapter .05 INTRODUCTION

5.1 Purpose
Motivation behind this archive will be to gatherings give point by point outline representation
about school administration framework which could a chance to be used to give acceptable
rules for making the provision Furthermore aide for the procedure from claiming
improvement.
5.2 Scope
Recommended archive incorporates those configuration periods of proposed
requisition and the requisition exhibits digitized functionalities to Dealing with these
exercises efficiently, which incorporate regulatory control, disappointments and outrage on
his/her staff management, person management, advertisement, examination control system,
reports generation, Furthermore expense oversaw economy. These functionalities will make
Gave of the client through over specified interfaces.
5.3 Overview
Initially segment of this report gives prologue over this document, segment two
overlays the considerations obliged should settle on When planning and At whatever
imperatives whether vital. Area three gives points something like that construction modeling
of the system, What's more At last area five incorporates the Interfaces What's more their
points.
5.4 Reference Material

https://www.w3schools.com
https://www.w3schools.com/php/php_intro.asp
https://en.wikipedia.org/wiki/PHP
https://en.wikipedia.org/wiki/HTML
5.5 Definitions
SDD
Stands for system design documentation
PK
Stands for primary key
FK
Stands for foreign key
19
Chapter.06 SYSTEM OVERVIEW

6.1 Assumptions
In place with see the requisition client must need introduced most recent form claiming web
browser, preferably Google chrome alternately Firefox What's more a web association.
6.2 General Constraints

Those provisions will a chance to be finished utilizing shroud IDE Furthermore
MySQL as database. To the reason for improvement this provision the designer entails
shroud defaces for PHP alternately essentially notepad could additionally make utilized to
development, to onsite testing, apache Web server,PHP, MySQL. There will be additionally a
haven for picture altering device around for example, adobe Photoshop alternately Corel
draw.
6.3 System Environment

Requisition need and proficiency will run under whatever working framework due to its
improvement surroundings under at whatever most recent web program.
20
Chapter.07 SYSTEM ARCHITECTURE

7.1 Architectural Design
School administration framework may be client-server web based requisition and the
client will have the capacity to cooperate for the provision through a web program
Furthermore a web association. Those provision will cooperation for those database
Furthermore provide purpose of the client as needed.
Internet
Web Interface
PHP Contents Web Server PHP Pages
Database
7.2 Decomposition Description

Requisition is decayed under three portions which connect for one another
(Furthermore give those functionalities of the framework. Those in general frameworks are
exhibited for over outline and the point by point portrayal of the framework is furnished in
the outline beneath.
21
User User User User
Admin Student Exam Fee Records Reports

Home Informa Structure
Page Page Page Page Page
Page tion Page
Data
System Interface
Database
Relational Database
7.3 Design Rationale

Those purpose behind picking Web construction modeling will be on fully computerize
training framework which could a chance to be accessed starting with anywhere, Moreover
this requisition is planned to both the organization staff who could deal with those normal
procedures of the association Furthermore to overall population who wish will procure
majority of the data regarding the class
Chapter.8 DATA DESIGN

8.1 Data Description
Web Server
Student
PK Student_Name
22
FK Class, Registration_Number
Roll_Number
Father_Name
Gender
Total_Fee
Amount_Paid
Amount_Due
Student_Admittance Admission_Form
PK Student_Name
PK Serial_Number
Admittance_Number
Admittance_Date Class
Student_Name Roll_Number
Date_of_Birth Student_Name
Address Father_Name
Cast Mother_Name
Religion Religion
Father/Guardian_Occupation Cast
Class Date_of_Birth
Class_Left Identification_Mark
Date_Class_Left Past_School_Name
Dues_on_Leave Class_Left
Date_Class_Left
Guardian_Name
Guardian_Relationship
Student_Attendance Father/Guardian_Occupation
Designation
PK Class Roll_Number Place_of_Posting
Registration_Number Annual_Income
Student_Name Home- Number
Attendance_Month Mobile Number
Total_Strength Admittance_Date
Total_Present Gender
Total_Absent Father/Guardian_CNIC
8.2 Data Dictionary
Field Type Default Length Null Extra

Admittance_Number Integer(4) 0–9 No Auto Number
Admittance_Date Date Current Full Date No
Address Varchar (350) 0 – 350 No
Annual_Income Integer(9) 0 0-9 No
Attendance_Month Date Current Full Date No Month-Year
Amount_Paid Integer(5) 0–5 No
Amount_Due Integer(5) 0-5 No
Class Varchar(2) 2 No
23
Cast Varchar(15) 0 - 15 No
Class_Admitted Varchar(2) 0-2 No
Class_Left Varchar(2) 0-2 No
Dues Integer(4) 0-9 No
Date_of_Birth Date Full Date No Day-Month-Year
Employee
PK Empolyee_Name
Designation
Qualification
Empoyee_Code
Date_of_Joining
Net_Pay
Picture
CNIC_Number
Dues_on_Leave Integer(4) 0–9 No

Date_Class_Left Date Full Date No
Designation Varchar(25) 0 - 25 Yes
Father_Name Varchar(50) 0 - 50 No
Father/Guardian CNIC Varchar(15) 0 - 15 No 00000-0000000-0
Guardian_Name Varchar(50) 0 - 50 Yes
Guardian_Relationship Varchar(30) 0 - 30 Yes
Identification_Mark Varchar(100) 0 - 100 Yes
Mother_Name Varchar(50) 0 - 50 No
Mobile Number Integer(12) 0 - 12 No 0000-0000000
Picture Image JPG,JPEG No
Past_School_Name Varchar(100) 0 - 100 No
Place_of_Posting Varchar(50) 0 - 50 No
Phone Home Varchar(20) 0 - 20 No
Roll_Number Integer(3) 0-3 No
Registration_Number Varchar(15) 0 - 15 No
Reason_for_Leave Varchar(50) 0 - 50 No
Religion Varchar(15) 0 - 15 No
Student_Name Varchar(50) 0 - 50 No
Total_Fee Integer(5) 0-5 No
8.3 Employee Database
24
Employee_Attendance
PK Month_Year Teacher Agreement
Employee_Name PK Employee_Name
Designation
Qualification Father_Name
Arrival_Time Date_of_Birth
Departure_Time Cast
CNIC_Number
Address
Qualification
Experience
Salary_Register Designation
Place_of_Experience
PK Month_Year
Mobile Number
Serial_Number Agreement From
Employee_Code Agreement_To
Employee_Name Previous_Salary
Date_of_Joining Current_Salary
Days_Present Additional_Benefits
Days_Absent Apppointed_As
Paid_Days Agreement_Date
Daily_Pay Joining_Date
Gross_Pay Picture
Deductions
Net_Pay
8.4 Employee Data Dictionary

Address Varchar(350) 0 - 350 No
Arrival_Time Time Current Full Time No
Agreement From Date Current Full Date No Dd/mm/yy
Agreement_To Date Current Full Date No Dd/mm/yy
Appointed_As Varchar(35) 0 - 35 No
Agreement_Date Date Current Full Date No Dd/mm/yy
Additional_Benefits Integer(4) 0 0-4 Yes
Cast Varchar(35) 0 - 35 No
CNIC_Number Varchar(15) 0 - 15 No 00000-0000000-0
Current_Salary Integer(4) 0 0-4 No
Designation Varchar(35) 0 - 35 No
Date_of_Joining Date Current Full Date No Dd/mm.yy
25
Date_of_Birth Date Current Full Date No Dd/mm.yy

Departure_Time Time Current Full Time No
Days_Present Integer(2) 0-2 No
Days_Absent Integer(2) 0-2 No
Daily_Pay Integer(4) 0-4 No
Deductions Integer(4) 0-4 No
Employee_Name Varchar(50) 0 - 50 No
Experience Varchar(8) 0-8 No
Father_Name Varchar(50) 0 - 50 No
Gross_Pay Integer(4) 0-4 No
Month_Year Date Current Month Year No Mm/yy
Mobile-Number Varchar(11) 0 - 12 No 0000-0000000
Net_Pay Integer(4) 0-4 No
Place_of_Experience Varchar(100) 0 - 100 No
Picture Image No
Previous_Salary Integer(4) 0-4 No
Qualification Varchar(100) 0 - 100 No
Serial_Number Integer(4) 0-4 No Auto Number
26
8.5 Exams Data Description
Exams
PK Student_Name,
Class
Roll_Number
Subject
Total_Marks
Obtained_Marks
Grade
Employee_Name
8.6 Exams Data Dictionary

Class Varchar(2) 0-2 No
Employee_Name Varchar(50) 0 - 50 No
Grade Char(1) 0-1 No
Obtained_Marks Integer(3) 0-3 No
Roll_Number Integer(3) 0–3 No
Student_Name Varchar(50) 0 – 50 No
Subject Varchar(20) 0 – 20 No
Total_Marks Integer(3) 0–3 No
27
28
Chapter.09 COMPONENT DESIGN

9.1 Home
Client visits URL
Connect user with web server
Using the User brows for contents
9.2 Admin
If administrator is the user then
Show administration page
And if the user is employee then
Show attendance page
Else show error message
9.3 Student
If user is administrator
Allow edit and update student details
And if user is employee then
Allow marking exam/attendance
9.4 Information records

If user Id administrator then
Allow modify in bio data of employee/students
Else display error message
9.5 Exam
If user is authorized user
Allow enter/modify exam details
Else notify user about the problem
9.6 Fee structure

Administrator login to the application
Select student to check fee details
Make any changes to fee
Acknowledge user about changes made
Display error message if any
29
9.7 Reports
Check for user authorization
Ask user to pick report type to be generated
Generate desired report
Notify user about any error messages
Chapter.10 HUMAN INTERFACE DESIGN

10.1 Overview of User Interface
The following is a rundown of interfaces for class administration framework which speaks to
those purpose for each part from this requisition and the depiction of the interfaces would
Gave.
10.2 Screen Images
10.2.1 Home Page
10.2.2 Description
This page gives that limit of the provision and the rundown about operations that might be
performed same time client is during this page about requisition. This page holds the joins to other
pages through which client might explore starting with you quit offering on that one period will in
turn page.
30
10.2.3 Login
10.2.4 Description
This page will be outlined to organization reason for existing the place director Also instructors cam
wood log under their accounts also perform a standout amongst those errands they yearning.
31
10.2.5 Admin Page
10.2.6 Description
This director page gives director privileges with support the account majority of the data What's
more likewise incorporates joins with other pages of the provision.
32
10.2.7 Student Page
10.2.8 Description
This page of the provision holds every last bit the navigations that need aid needed with administer
the subtle elements for scholars for example, including new student, modifying their details,
expense Furthermore exam subtle elements and generating different sorts for reports.
33
10.2.9 Exam Page
10.2.10 Description
This web page contains the links of entering exam details and also the reports to be generated.
34
10.2.11 Fee Structure Page
10.2.12 Description
This web page contains the links of entering fee details.
7. REQUIREMENTS MATRIX
35
Admit Student
Admit Staff
Create Exam
Control
Admin Management
Manage Fee
Manage Salary
Mark Exam
Registered Update Grade

Test Report
Login Staff
Exam Schedule
Logout Update
Attendance
Test Schedule
View Result
User View Course

Exam View
36
Login page
Reset page
37
User home page
New Admission Page
38
Pay Fee page
Details Page
39
Transport Details Page
Fee- Paid Status Of a class Page
40
Master Insert for Academic year
Insert Attendance records for a class
41
Student Details Page
Test Marks
42
Attendance page
Subjects Staff
43
User Logout Page
44

SRS School Management Sys

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRS School Management Sys

Uploaded by

Copyright:

Available Formats

\

BUSHRA TARIQ Roll No 171605

Signature Name Title Date

Chapter.1 Introduction Error! Bookmark not defined.

Chapter.2 The Overall Description 3

Chapter.3 Specific Requirements 5

Chapter.4 Analysis Models 12

Chapter.6 SYSTEM OVERVIEW 20

Chapter.7 SYSTEM ARCHITECTURE 21

Chapter.8 DATA DESIGN 22

Chapter.9 COMPONENT DESIGN 29

Chapter.10 HUMAN INTERFACE DESIGN 30

10.2.5 Admin Page 32

1.3 Definitions, Acronyms, and Abbreviations.

 PHP is composition for "PHP: Hypertext Preprocessor"

PHP is designed language resolve on server-side which is used for

Chapter.02 The Overall Description

2.1 Product Perspective

2.1.2 Site Adaptation Requirements

2.2 Product Functions

2.3 User Characteristics

2.4 General Constraints

2.5 Assumptions and Dependencies

Chapter.03 Specific Requirements

3.1.1 System Interfaces

3.1.3 Hardware Interfaces

3.1.4 Software Interfaces

3.1.4.1 Microsoft SQL Server 7

3.1.5 Communications Interfaces

3.2 Functional Requirements

3.2.1 User Registration

3.2.2 User Login

3.2.3 Personal Information

User provides to create record about Staff and the students.

3.2.4 Exams Schedule

3.2.6 Fee Schedule

Enter the amount that will be received from the students.

3.3 Use Cases

Use Case Diagram for School Management System

3.5 Non-Functional Requirements

Chapter.4 Analysis Models

4.2 Data Flow Diagrams (DFD)

4.2.1 Context Level Diagram

4.2.2 First Level Data Flow Diagram

4.2.3 Second Level Data Flow Diagram

Chapter .05 INTRODUCTION

5.4 Reference Material

Chapter.06 SYSTEM OVERVIEW

6.2 General Constraints

6.3 System Environment

Chapter.07 SYSTEM ARCHITECTURE

PHP Contents Web Server PHP Pages

7.2 Decomposition Description

Admin Student Exam Fee Records Reports

7.3 Design Rationale

Chapter.8 DATA DESIGN

8.2 Data Dictionary

Field Type Default Length Null Extra

Dues_on_Leave Integer(4) 0–9 No

8.3 Employee Database

8.4 Employee Data Dictionary

Date_of_Birth Date Current Full Date No Dd/mm.yy

8.5 Exams Data Description