TABLE OF CONTENTS

CHAPTER: 1 INTRODUCTION _________________________________________ 4

1.1 INTRODUCTION:- __________________________________________________ 4

1.2 NEED OF PROJECT MOTIVATION:-__________________________________ 4

1.3 PRODUCT:- ________________________________________________________ 4

1.4 SCOPE:-____________________________________________________________ 5

1.5 BUSINESS GOALS:- _________________________________________________ 5

1.6 PURPOSE:- _________________________________________________________ 5

1.7 ADVANTAGES OF THE NEW SYSTEM:- ______________________________ 6

CHAPTER:2 REVIEW OF LITERATURE _______________________________ 7

2.1 THE EXISTING SYSTEM (MANUAL):- ________________________________ 7

2.2 DRAWBACKS OF EXISTING SYSTEM:- ______________________________ 7

2.3 PROBLEMS IN THE EXISTING SYSTEM:- ____________________________ 8

2.4 LITERATURE SURVEY:- ____________________________________________ 8

2.5 OBJECTIVES:-______________________________________________________ 8

2.6 NEED FOR THE NEW PROJECT:- ____________________________________ 9

2.7 CONSIDERATION TO ACHIEVE:- ___________________________________ 9

CHAPTER: 3 REQUIREMENT ANALYSIS ______________________________ 11

3.1 DOCUMENT CONVENTIONS:- ______________________________________ 11

3.2 OVERALL DESCRIPTION:- _________________________________________ 11

NON FUNCTIONAL REQUIREMENTS ____________________________________________ 12

3.3 PERFORMANCE REQUIREMENTS:-_________________________________ 12

3.4 HARDWARE AND SOFTWARE SPECIFICATION:- ____________________ 12

3.5 TOOLS AND TECHNOLOGY WITH REASONING:- ____________________ 13

3.6 SAFETY REQUIREMENTS:- ____________________________________________ 13

CHAPTER:4 MATERIALS, METHODS & DESIGN_______________________ 14

4.1 USE CASES:- ______________________________________________________ 14

1
 4.2 LIST OF ACTORS:-_________________________________________________ 14

4.3 OPERATING ENVIRONMENT:- _____________________________________ 15

4.4 USE CASE MODELS:- ______________________________________________ 15

4.5 ENTITY RELATIONSHIP DIAGRAM (ER DIAGRAM):- ________________ 18

4.6 ACTIVITY DIAGRAM:- _____________________________________________ 19

4.7 SYSTEM SEQUENCE DIAGRAMS:- _____________________________________ 22

4.8 CLASS DIAGRAM:- ____________________________________________________ 24

CHAPTER: 5 MYTHEDOLOGY _______________________________________ 25

5.1 SOFTWARE SELECTION OBJECTIVES:-_____________________________ 25

5.2 CONSIDERATION TO ACHIEVE:- ___________________________________ 25

5.3 DATA FLOW DIAGRAM:- __________________________________________ 26

5.4 MODEL TO USE ___________________________________________________ 29

5.5 WATERFALL MODEL:- ____________________________________________ 30

5.6 SYSTEM ANALYSIS:- ______________________________________________ 31

5.7 UNIFIED MODELING LANGUAGE:- ________________________________ 32

5.8 SYSTEM DESIGN:- _________________________________________________ 32

CHAPTER:6 RESULTS AND DISSCUSSION ____________________________ 35

6.1 RESULTS AND DISSCUSSION:- _____________________________________ 35

6.2 OUTPUT OF THE DEVELOPED SYSTEM:- ___________________________ 35

6.3 SPEED AND ACCURACY:- __________________________________________ 35

6.4 EFFICIENCY AND FLEXIBILITY:- __________________________________ 35

6.5 MANGERIAL AND ACCEPTIBLITY:- ________________________________ 35

6.6 ELIMINATING DATA REDUNDANCY:- ______________________________ 35

6.7 USER FRIENDLY:- _________________________________________________ 36

6.8 DATA ENTRY:- ____________________________________________________ 36

6.9 TIME SAVING:- ____________________________________________________ 36

6.10 NEAT AND CLEAN SETUP:- ________________________________________ 36

REFERENCES ________________________________________________________ 37
2
 ABSTRACT

This paper is on the project “THE SCHOOL MANAGEMENT SYSTEM”. The

system The School management System registration project is the School management
Systems of its kind .It is designed to bridge the gap between the police and the common
people. There are plenty of applications nowadays for shopping, travel and even for
gaming purposes. However there is no application for the purpose of registering School
management System or for helping the people while facing emergency situations. We
intend to create a system where the users could register and School management System
under various IPC sections and inform the police whenever in an emergency situation.
We believe this will help to bridge the gap between the police department and the people.

3
CHAPTER: 1 INTRODUCTION

1.1 INTRODUCTION:-
The crime rate is increasing at an alarming rate and there are no existing technical
systems in our country for the purpose of registering a case and managing the activities
related to the School management System. We intend to create a project which will help
bridge the gap between the police department and the common man. ‘The School
management System Registration and system’ project will have an app from where the
users can file School management System against the offender under the admin (from the
police) who will then notify the user if the School management System has been
registered and the necessary action has been taken .There will be a robust authentication
process so that only the genuine citizens can register a case .The users will be notified if
the police have filed the School management System. This project is cop friendly too. The
end site will have a database various sections. The main site the criminals which the
police can access anytime. There will be an ‘SOS’ capability wherein the user can press
the button in the app and his location will be sent to the police. There will be a special
module for hospitals, wherein preference will be given to accident victims. The School
management System in such cases will be registered quickly so that the doctors can start
the treatment as early as possible will be maintained.

1.2 NEED OF PROJECT MOTIVATION:-

There is a gap between the common man and the police. People are very hesitant
to go to the police and register the case. School management System registration has to be
done manually even though it can be done the through an application. Slow registration of
School management System in Accidents and assault cases is one of the biggest problems
which we believe needs to be taken care of as it can save time leading to early treatment
of the victims. The ‘100’ dialing system is not time efficient. Also it may occur that the
person does not know his/her exact location The SOS system which will be created will
be a better option than the ‘100’ dialing system. We believe it will be a very efficient
system. Even though there exists database for criminals in existing systems a more
efficient database can be created.

1.3 PRODUCT:-
1) The system for School management System registration.
2) A system in which a person can register his complain the.
3) A brief introduction of police public services is included.
4
 4) Important contacts of police department.
5) User can give feedback about his registered complain.

1.4 SCOPE:-
School management System is web based applications where a person can register
his complain. This application is for running smoothly the procedure of School
management System of police department.

1.5 BUSINESS GOALS:-

• Effective system to reduce burden on police department.
• Simplify the process of School management System registration.
• Usable for a common less educated person also.
• Saves time.
• Instant response from department after completing registration process.
• Helpful in maintaining law and order situation.

1.6 PURPOSE:-
Purpose of the new system is to provide an easy access to the people so that they
can easily get information about the School management System.
Its main purpose to facilitate the general public that cannot waste their time. They
can easily School management System the School management System on at place where
is standing.

1.6.1 DATA STORAGE:-

In this new the system data will be stored in computer which will be available at
any time and place as this database will be connected to the web page, giving information
to the people everywhere.

1.6.2 ELIMINATING THE DATA REDUNDANCY:-

Since there is only one storage place where whole information is saved i.e.
information of criminal, so there is no chance of duplication of data.

1.6.3 FLEXIBILITY:-

This system is flexible as there is no rigid School management System, they can
be later on changed as required by the admin. People does not go to the police station but
they can get this information from the site. Thus in this way it provides flexibility to the
general public as well as shop manager.

1.6.4 SOLVING PROBLEM:-

5
 Solving the problem of the people and general public is necessary if the School
management System registered the and it’s also in record automatically.

1.7 ADVANTAGES OF THE NEW SYSTEM:-

New system is the, this feature provides a lot of benefits to the both parties in
following aspects.

1.7.1 UER FRIENDLY:-

System is a GUI-based Web Site having Links, Buttons, Check boxes, Text,
Navigation Tabs so user can easily navigate throughout the website. Using such GUI
features user can easily use this system.

1.7.2 ECONOMICAL:-

This system saves money spent of the paper work, and reducing number of
employees on the shop to giving information to the customers about products.

1.7.3 RELIABLE:-

This system is confidential. There is backup if computer OS fails to Load, from

that backup admin can reload the information after reinstalling the OS.

1.7.4 TIME SAVING:-

This system saves a lot of time of both parties (traveling time to police station for
confirmation).

1.7.5 EFFICIENT:-

After a single click on the page you can get information about whole School
management System so it works very fast, if you have proper speed internet connection
and a fast machine.

1.7.6 SECURITY:-

In the manual system everyone can get the information about the original
RECORD OF AN CRIMINAL thus no secure system but our system is protected by the
login accounts. User you can access the real information if you have admin account
otherwise you will use the information that is available on the site .there is not only front
end based passwords but also at database level passwords.

1.7.7 ACCESSIBILITY:-

6
 The School management System System is accessible at every corner of the
world where internet is available, accessible by everyone provided that he has a machine
with internet connection and accessible at any time.

CHAPTER: 2 REVIEW OF LITERATURE

There are no existing technical systems in our country for the purpose of registering a
case and managing the activities related to the School management System. The victims
have to go and personally register the case in the police stations. Slow registration of
School management System in Accidents and assault cases is one of the biggest problems
of the existing system. Often the victims are told by the hospital authorities that the
treatment would not be started unless an School management System has been registered.
The slow registration of School management System leads to loss of precious time often
leading to the loss of blood which.

2.1 THE EXISTING SYSTEM (MANUAL):-

It is much important to keep pace with Time and with the Increasing and to
stand on the present environment of the modern world. It is very difficult to handle a
large amount of data manually and to achieve the required results. Currently the user is
using the manual system. They record the entries manually on registers (of any criminal)
and there is more chance of errors. Productivity is usually lower, particularly in routine or
operational situations. It is difficult to make corrections, if a manual document contains
errors or needs updating, it is often necessary to create the whole document from scratch
rather than just a new version. If officer wants to get information about a particular
criminal, then it is a very difficult and time consuming job. The existing system consumes
too much stationary that results high cost and information handling is very difficult as
more manpower is required. A manual system relies heavily on the actions of people,
which increases the possibility of human error. This system also needs continuous
monitoring to ensure that the record will accurate.

2.2 DRAWBACKS OF EXISTING SYSTEM:-

Various drawbacks of manually handling the operations in the manual system are:
• Though paper work acts as the basis for any activities by now-a-days, but this is
considered as slower way of performing as compared to computerized system.
• Manual system is unreliable and in-accurate.
• It consumes a lot of time waste.
• In manual system, security of record (of an School management System) is at
risk. It can be harmed or theft anytime, information can be misused.
7
 • Record of School management System can be inconsistent.
• Searching records of individual will take time.
• Manual reporting is very difficult for many criminals.
• Un-economical due to the large number of manpower, time investment and
stationeries.
• Report generation is difficult in manual system.
• Risk of errors, mistakes and miscalculations of data.
• Retrieving information like reports and queries is very time consuming and almost
impossible practicably if time has to be considered.
• No proper backup of record because the manual database can be lost or burn.

2.3 PROBLEMS IN THE EXISTING SYSTEM:-

In the existing system reporter as well as officers is in trouble. At School
management Systems, they do not know the standard of the report submission in the
police station.
The other side of the picture is the police man who is also in trouble .He feels
difficulty in maintaining the records of the criminals.

2.4 LITERATURE SURVEY:-

As mentioned earlier, the ‘The School management System Registration and SOS
system ’is the School management Systems of its kind .There are no exact technical
papers published on this topic. However there were few technical papers related to this
topic which gave us some ideas. The only difference was that it contained all the
information related to the police officers. There were various departments like traffic,
narcotics and anti-trafficking and all the officers and their names and all the necessary
details were there in the database. This report was again database related .It covered all
the information related to a Criminal database which had details of all the criminals and
the crimes they had committed. The technical paper was about a project which was like
an interactive system for the police and the people. The People could voice their concerns
about the crimes or possibility of crimes in their regions and the police could attend to all
their concerns.

2.5 OBJECTIVES:-
The objective is to build an effective School management System registration
system which will have various sections and a proper notification system once action has
been taken. To have a robust authentication and registration system for users.
Authentication would include valid documents so that there would not be any false cases

8
registered by mischief mongers. To have an SOS system which will ensure round the
clock safety to the users and offer security? To ensure early School management System
registration of accident and assault victims so that that early treatment can be given to the
victims, thus helping in saving lives. To build a system which is compact as well as
efficient? One of the objectives is to build a database which will be properly integrated
with the server and will hold all the details of the criminals. To build an integrated system
which is user friendly as well as cop friendly? The user interfaces, user actions and
functionalities are designed using it. Software development kit (SDK) includes a
comprehensive set of development tools. It consists of a Java Virtual Machine and all of
the class libraries present in the production environment, as well as additional libraries
only useful to developers.

2.6 NEED FOR THE NEW PROJECT:-

There are a number of incidents and accidents in the world. Some time there is a great
rush of people and management system works slowly. So, the new System is developed
keeping in mind the general needs and requirements of the people when they go to police
station. Also, the developed system should be easy to understand and easy to use. The
new computerized system completely fulfills the managerial requirements and end user
requirements as the tasks related to both parties are accomplished in an efficient manner
in the new system. To compete in a highly competitive world, a Management has to meet
a single user’s needs and expectations so that is why this system is being developed.

2.7 CONSIDERATION TO ACHIEVE:-

The process of giving careful thought to something. The process of using your
mind to consider something carefully, thinking always made him frown. So, the School
management System designs after deep consideration of new computerized system. There
are a number of many key considerations. The scope of your final project is not just about
final result you expect to attain, it also accounts for step you take along the way. The
consideration about the Computerized School management System project to design the
system in that ways so there are no chance of errors occurred in the system. What are the
five key things they need to consider very carefully when starting to develop it?
. School management Systems a system needs to be truly inspiring and should
describe future state for the organization.
. Second, the new system strategy needs to ambitious in terms of providing the
basic to break away from the competition, beat the competition, and create new spaces.
. Third, the process of developing the new system needs to be open.

9
. Fourth, an innovation strategy must also be specific to the time in which it is
developed.
. Finally, an innovation strategy needs to be adaptive to evolve over time.

10
CHAPTER: 3 REQUIREMENT ANALYSIS

The School management Systems System providers to focus on creating effective

assessment questions and focusing on School management Systems feedback delivery to
Users. In the School management System we present techniques that are pertinent to the
elements of assessment process: School management System submission, computerized
Registration, and feedback after submission.
3.1 DOCUMENT CONVENTIONS:-
Document language elements and attributes:

 CSS property, descriptor, and pseudo-class names are delimited by single quotes.
 CSS values are delimited by single quotes.
 Document language element names are in upper case letters.
 Document language attribute names are in lower case letters and delimited by
double quotes.

3.1.1 CSS PROPERTY DEFINITIONS:-

Each CSS property definition begins with a summary of key information that resembles
the following:
3.1.2 PROPERTY-NAME:-
No table of figures entries found.Value: Possible constant values or value types

Initial: The initial value

Applies to: Elements this property applies to

Inherited: Whether the property is inherited

Percentage values: How percentage values should be interpreted

3.1.3 HTML CONVENTIONS:-

In this specification, most of the examples refer to HTML. For clarity, HTML elements
are written with upper case letters (e.g., HTML, BODY, EM, and P) and HTML attributes
are written with lower case letters (e.g., sec, class, and id).

3.2 OVERALL DESCRIPTION:-

Product features:-
1. User can find main contact details of police department
2. User register and the School management System application
3. Users can submit feedback for their application
4. System admin can login to view secure area of this portal
5. System admin from police department can view all the applications submitted
6. System admin can view the feedbacks submitted
11
 NON FUNCTIONAL REQUIREMENTS
3.3 PERFORMANCE REQUIREMENTS:-
1. Latest web server
2. Latest version of browser
3. Latest file server
4. MS Office 2013

3.4 HARDWARE AND SOFTWARE SPECIFICATION:-

PLATFORMS HARDWARE SOFTWARE

Window up, window Pentium-IV Operating System :

vista window7, (Processor). Windows
window 8, 256 MB Ram
window10, 512 KB Cache Memory Web-Technology: PHP
Hard disk 10 GB Use of software to configure:
Microsoft Compatible Wimp /Amp Sever installed on
101 or more Key Board windows 7/8
Front-End:
HTML,CSS,JAVASCRIPT
Back-End:
MySQL

Web Server: Apache

SERVER.

BROWSERS INTERNET E_MAIL

CONNECTIONS
Mozilla School Any Email account is
management System Different networks like recommended
fox Ethernet, DSL,
Google chrome, Wireless and Dial up
Opera mini connections
Other internet
services

12
3.5 TOOLS AND TECHNOLOGY WITH REASONING:-
We chose these tools and technologies because our all team members are well
experienced in these tools and technologies so we use these following are mentioned
there
HTML JavaScript and CSS for web interface
PHP for server side scripting
SQL server for Database
MS Office

3.6 SAFETY REQUIREMENTS:-

3.6.1 RISK LIST:-

Risk is in fact the difference between the actual output and expected output. We
make our project out of risk made the analysis of all the expected risk and try to mitigate
them.
 Schedule Risk.
 Budget Risk.
 Operational Risks.
 Technical risks.
 Goal risk.
 Communication Risk.
 Change risk.
 Usability risk.

3.6.2 SECURITY REQUIREMENTS:-

1. Restricted access to file server

2. Restricted access to database server
3. Restricted access to admin section

3.6.3 SOFTWARE QUALITY ATTRIBUTES:-

It is easy to access, webpage is simple and clear. It is allow using to all types of user.
Long time benefits gained by the user and admin. It is change and modified according
to the new technologies

13
CHAPTER: 4 MATERIALS, METHODS & DESIGN
4.1 USE CASES:-
This section defines the use case, is excellent technique to understand and
describe requirement. This chapter defines the use case model; it is a model of the
System’s functionality and environment. Use case model is the set of all use cases, is a
technique that is used to describe the requirements. In this chapter we also create activity
diagram, sequence diagram and class diagram to show the design detail.

4.2 LIST OF ACTORS:-

 Admin
 Operator
 Visitor

4.2.1 OPERATOR:-

Name: ___________
F Name: ___________
CNIC: _____________
Land line No: _____________
Mobile No: ____________
Present Address: ____________
E-Mail: _____________
Home Dust: _____________
Date &Time of Incident: ______________
Place Incident: ______________
Dust of Incident: ________________
Detail Incident: _________________
Visit Police Station: ______________
Officer Name and Rank: _____________
Visit Date & Time: ________________

4.2.2 ADMIN:-

Login: ___________
Access the back end data: _________________
Check the feedback: ___________________
Check the School management Systems: __________________

14
4.2.3 VISITOR:-

Writ the feedback by the users: ______________

Contact: ____________________

4.3 OPERATING ENVIRONMENT:-

System will require following tools to run
1. web server e.g. apache
2. Database e.g. MySQL
3. Web browser to view web pages

4.3.1 ASSUMPTIONS AND DEPENDENCIES:-

1. Users should be educated enough to use any the web application

2. Admin will be trained enough to manage this system
3. Operating environment should be mature enough to handle large amount of
requests

4.4 USE CASE MODELS:-

In system engineering, a use case diagram at its simplest is a representation of
user’s instruction with the system, which shows the relationship between user and the
different use case in which the user is involved. A use case diagram can identify the
different types of users of a system and the different use cases and will often be
accompanied by other types of diagrams as well.

15
4.4.1 USE CASE MODEL 1 NAME USER:-

Name

Fame

C.N.I.C

Contact

Present
Address
E-mail

Register Dust of Incident

School
management
Date & Time of Incident
System

Detail of Incident

Visit P.S

Visit Date

Visit time

Name of P Officer

Visit of Incident Place

Figure 1 Use case model Users

16
4.4.2 USE CASE MODEL 2 USER:-

Name

Feedback E-mail

Contact Message

Contact us

Figure 2 Use Case Model 2 Users

4.4.3 USE CASE MODEL 3 ADMIN:-

Access Back end

Data in Database

Login
Check feedback

Check
School
managemen
Figure 3 Use Case Model 3 Admin
t Systems

17
 4.5 ENTITY RELATIONSHIP DIAGRAM (ER DIAGRAM):-

C.N.I.C Date Time

Name Fame Status
C
Address Place of Incident

Victim Field-for School

Register
School I.D
Complaint management
Fame
Against
I.DI.D System Age
Address

Name Accused I.D

Files
Fame

Login_Admin

Name

views
Contact
Feedback

Contact Us
Name Message

Cell. No
E-mail

Data of School
management
Systems
Figure 4 ER Diagram

18
4.6 ACTIVITY DIAGRAM:-
In Unified Modeling Language (UML), an activity diagram is a graphical
representation of an executed set of procedural system activities and considered a state
chart diagram variation. These diagrams describe parallel and conditional activities of
system, use cases and System functions at a detailed level.

4.6.1 ACTIVITY DIAGRAM FOR USERS:-

User entered the

Personal &School
management System
Detail

No
Invalid Detail
Condition

Yes

User successful to
entered detail

Figure 5 Activity Diagram for User

19
4.6.2 ACTIVITY DIAGRAMS FOR VISITS THE POLICE STATION:-

Visit the Police

Station

Entered Detailed

System validates

No

Correct Details Error Message

Yes

Successful auto Save

Figure 6 Activity Diagram for Visit PS

20
4.6.3 ACTIVITY DIAGRAM FOR DELETE VISIT POLICE STATION &School
management System:-

Requests to delete
existing Visits of
PS&FIR

No
Check if Visits Error
PS &School
management
System Exists

Yes

System deletes
Visits PS
&School
management
System

Figure 7 Activity Diagram for Delete PS

21
4.7 SYSTEM SEQUENCE DIAGRAMS:-

A system sequence diagram (SSD) is a sequence diagram that shows, for a

particular scenario of a use case, the events that external actors generate their order, and
possible inter-system events. The sequence diagram is used primarily to show the
interactions between objects in the sequential order that those interactions occur. It is
basically a construct of a message sequence chart.

4.7.1 SYSTEM SEQUENCE DIAGRAM FOR REGISTERING USER:-

Admin GUI System Database

Request RU ()
Forward R auto
()

Verify auto U Detail

Add U Auto

Show Results

Figure 8 System Sequence Diagram for User

22
4.7.2 SYSTEM SEQUENCE DIAGRAM FOR ADDING School management
System:-

User System Database

GUI

Request Add School

management System abase
Forward Request Auto
Verify auto Details

Add
School
managem
ent
System

Show Results

Figure 9 System Sequence Diagram for Adding School management System

4.7.3 SYSTEM SEQUENCE DIAGRAM FOR ADMIN:-

Admin GUI System DB

Request to login

Forward Request Verify

Check any Details of

School management
Systems and
Feedbacks

Log out

23
 Figure 10 System Sequence Diagram for Admin

4.8 CLASS DIAGRAM:-

A UML class diagram describes the object and information structures used by your
application, both internally and in communication with its users. It describes the
information without reference to any particular implementation. Its classes and
relationships can be implemented in many ways, as database tables.
Class Diagram for School management System is as follow.

User Admin

U_idinteger Add integer

Name string
Email string
Address string
Contact No String
Create detail
Date and time
Up date
Date and time

+Index ()
+adminauthelogin () Operator
.
+create ()
+Store ()
+Edit (ID integer) Op integer

State District Visit PS

St It integer
St Name string Did integer
Id integer
Dynamo string
#create detail date and Name string
time #create date time
Address string
#update date and
#update date and time #create date and time
time #update date and
+index () time
+create () +index ()
+store () +create () +index ()
+edit (id integer +store () +create ()
+update id integer +edit id integer +store ()
+destroy id integer +update id integer +edit Id integer
+destroy id integer +update id integer
+destroy id integer

FIR Type FIR Report

-ct.id integer Reno integer

-ct.name string -details string
#create date and time Occur don date
#destroy id integer Location string
Lot string
+index () Ling string
+create () Status string
+store () #create date and
+edit id_ integer time
+update Id integer #Update date and
+destroy id integer time
+index ()
+create ()
+store ()
+edit id_ integer
+update Id integer
+destroy id integer

24
 Figure 11 Class Diagram

CHAPTER: 5 MYTHEDOLOGY
5.1 SOFTWARE SELECTION OBJECTIVES:-
This project having following objectives in our mind.
• The developed system must be eliminating drawback of the current system.
• The system will eliminate the need for maintaining the records on the papers
about the School management System.
• Only the authorized users can access the developed system. Hence it provides
high level of security to the data.
• No delay in availability of information in the system, so decision making is
faster and easier.
• Better performance of the system.
• There is no risk of errors, mistakes and miscalculations of data...
• New system will be economical.
• There will be no distributed existence of data like manual files in the new
system. All data will be stored at a centralized database with backup.
• Accuracy of the system.
• Data safety, searching and updating using database.
• The developed system is flexible for future enhancement.

5.2 CONSIDERATION TO ACHIEVE:-

The process of giving careful thought to something. The process of using your
mind to consider something carefully, thinking always made him frown. So, the School
management System designs after deep consideration of new computerized system. There
are a number of many key considerations. The scope of your final project is not just about
final result you expect to attain, it also accounts for step you take along the way. The
consideration about the computerized project to design the system in that ways so there
are no chance of errors occurred in the system. When an organization or university
realizes that they need a better Innovation strategy, what are the five key things they need
to consider very carefully when starting to develop it?
. School management Systems a system needs to be truly inspiring and should describe
future state for the organization.
.Second, the new system strategy needs to ambitious in terms of providing the basic to
break away from the competition, beat the competition, and creates new spaces.
. Third, the process of developing the new system needs to be open.
25
. Fourth, an innovation strategy must also be specific to the time in which it is developed.
. Finally, an innovation strategy needs to be adaptive to evolve over time.

5.3 DATA FLOW DIAGRAM:-

A data flow diagram (DFD) is a graphical representation of the “flow” of data through an
information system by modeling its process aspects. A DFD is often used as preliminary
step to create an overview of the system, which can later be elaborated. DFD’s can be
used for the visualization of data processing.

5.3.1 CONTEXT LEVEL DFD:-

HOME
Admin

PUBLIC
SERVICES School
management
Feedback
System of Punjab
Their
police CONTACT
US

Figure 12 Context Level DFD

26
5.3.2 DFD FOR ADMIN LOGIN MODULE:-

1.1

Accept the
Admin
user Name &
Password

1.2

Authenticate
The data about
The
School
Password
management
System

Figure 13 DFD For Admin

27
5.3.3 DFD FOR THE RESERVATION MODULE:-

Saving data in site

PUBLIC Entering about

an Incident
REQUEST
COMPLETE
PEOPLE

The School

management

System
CHECK BY
ADMIN
SYSTEM

DEPARTMENT

Seduce
VISIT BY THE
TEAM

Figure 14 DFD for the Reservation Module

28
5.4 MODEL TO USE

5.4.1 THE WATERFALL MODEL:-

The Waterfall Model was School management Systems Process Model to be

introduced. It is also referred to as a linear-sequential life cycle model. It is very simple
to understand and use. In a waterfall model, each phase must be completed fully before
the next phase can begin. This type of model is basically used for the project which is
small and there are no uncertain requirements.
At the end of each phase, a review takes place to determine if the project is on the
right path and whether or not to continue or discard the project. In this model the testing
starts only after the development is complete. In waterfall model phases do not overlap.

DIAGRAM OF WATERFALL MODEL

Figure 15 the waterfall Model

5.4.2 STEPS INVOLVED IN WATERFALL MODEL:-

5.4.2.1 ANALYSIS:-

Analysis phase of software development starts with a user requirement document which is
a very high level description of the end-users requirement. . Usually a single page
document describing the user’s requirements. Requirements for software system are
documented and reviewed with the people and usually a System Requirement

29
Specification (SRS) document is produced at the end of the phase. SRS is a document
usually signed by the Customers and developer.

5.4.2.2 DESIGN:-

Design is a very critical part of software life cycle. The life of a system is usually
determined by the design quality. Design involves translating the requirements into a
solution. This usually involves coming up with modules of the software system which
interact with each other to provide the system. Consequently maintenance effort for such
a design having high coupling will be high.

5.4.2.3 CODING:-

Design must be translated into a programming language so that a machine

executable code can be generated. Coding involves developing the software in the chosen
programming language. It is important to follow known coding conventions so that the
code is readable and can be understood by the other developers, testers and maintenance
personnel.

5.4.2.4 TESTING:-

Testing is a process that ensures that software is functioning as per the requirements.
Adequate testing has to be done to ensure that software is free from bugs. Both functional
and structural testing is performed to ensure software quality.

5.4.2.5 MAINTENANCE:-

Maintenance phase involves changes to the software to correct bugs discovered in the
software during its operation, requirement changes due to evolution of the software in a
changing context and environment. Often maintenance accounts for a larger portion of the
life cycle cost of software development. Hence improvement in maintenance of the
software becomes a key goal of software development process.

5.5 WATERFALL MODEL:-

5.5.1 WHEN TO USE THE WATERFALL MODEL:-

This model is used only when the requirements are very well known, clear and fixed.
 Product definition is stable.
 Technology is understood.
 There are no ambiguous requirements
 Ample resources with required expertise are available freely
 The project is short.
30
Very less customer enter action is involved during the development of the product. Once
the product is ready then only it can be demoed to the end users.

5.5.2 ADVANTAGES OF WATERFALL MODEL:-

 This model is simple and easy to understand and use.

 It is easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
 In this model phases are processed and completed one at a time. Phases do not
overlap.
 Waterfall model works well for smaller projects where requirements are very well
understood.

5.5.3 DISADVANTAGES OF WATERFALL MODEL:-

 Once an application is in the testing stage, it is very difficult to go back and

change something that was not well-thought out in the concept stage.
 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high risk of
changing.

5.6 SYSTEM ANALYSIS:-

In feasibility analysis we considered different separate types of feasibility. These
are equally important if any of the type gives unsatisfactory results then system is
considered unfeasible.
 Technical Feasibility
 Scheduled feasibility
 Economic Feasibility

5.6.1 TECHNICAL FEASIBILITY:-

A system is said to be technically feasible if the organization has the ability to

obtain all those equipment and personnel, which can develop, install and operate the
system. Ultimately the final goal of every business is to earn money, FIC Committee can
afford a PC while This Management is free for them so technically it is feasible to get to
design and develop this system.

31
5.6.2 SCHEDULED FEASIBILITY:-

Schedule Feasibility is defined as the probability of a project to be completed

within its scheduled time limits, by a planned due date. If a project has a high probability
to be completed on-time, then its schedule feasibility is appraised as high. In many cases
a project will be unsuccessful if it takes longer than it was estimated some external
environmental conditions may change, hence a project can lose its benefits, expediency
and profitability. If a work to be accomplished at a project does not fit the timeframes
demanded by its Customers, then a schedule is unfeasible (amount of work should be
reduced or other schedule compression methods applied).Our Project is to handle only
attendance of Customers& daily paid & time for me to design this functionality was 3
months less or more So there was scheduled feasibility for my project.

5.6.3 ECONOMIC FEASIBILITY:-

The economic feasibility of the system is said to be achieved when all the cost of
developing the system are fulfilled. These costs include development, installing and
operating costs. The expected new system is considered as economically feasible.
During this phase one should not be expected to define the entire problem in a system,
and should not attempt to propose an absolute solution to the problem stated in the
original system request. So, my evaluation for the project is that it is feasible and can be
processed further.

5.7 UNIFIED MODELING LANGUAGE:-

UML is general purpose developmental Modeling Language in the field of
software engineering intended to provide a standard way to visualize the design of a
system. UML was originally motivated by the desire to standardize the disparate
notational systems and approaches to software design developed by Grady Brooch , Liar
Jacobson and JamesRumbaugh at Rational Software in 1994/95.

5.8 SYSTEM DESIGN:-

System design is the process of defining the elements of a system such as the
architecture, modules and components and the data that goes through that system.it is
meant to satisfy specific need and requirements of a business or organization through the
system.

32
5.8.1 INPUT DESIGN:-

Input facilities the entry of data into the computer system. Input design involves
the selection of the best strategy for getting data into the computer system at the right
time and as accurately as possible.

5.8.2 INPUT FORM DESIGN:-

The input form is an essential element of almost any website or application these
days. Input is a core method of interaction, and in many cases it represents the hard
conversion point between success and failure. With the amount time and effort we put
into bringing users to our sign-up and contact forms, it’s surprising that we tend not to
spend a proportional amount of time on the forms themselves.

5.8.3 CODE DESIGN:-

A design code is a document that sets rules for the design of a new development.
It is a tool that can be used in the design and planning process, but goes further and is
more regulatory than other forms of guidance commonly used in the English planning
system over recent decades.

5.8.4 OUTPUT DESIGN:-

The output design during system design usually communicates all the important
milestones and problems that arise during system testing. Output design proposes to the
system; some remedies to various possibilities.

5.8.5 CONSIDERATION AND REPORT DESIGN:-

This section provides additional information for advanced deployment scenarios

that supplements core planning tasks typical of most installations. It describes best
practices for setting up extranet or Internet access to a report server, design considerations
for supporting multiple languages, and steps to estimate requirements for the report server
databases.

5.8.6 REPORT DESIGN TIPS:-

To attract and hold users’ attention, your quality report needs to be designed in a
way. Looks appealing and approachable at School management Systems glance. Helps
readers notice what information is available and important. Makes it easy for them to
skim and find topics of personal interest.

33
5.8.7 DATABASE DESIGN:-

In this project MySQL language are used in database design. Deferent types of
table are created in this database like post table category table contact table and user table.
Which stores the data related about this project and tables which are created in this
database.

5.8.8 PHYSICAL DATABASE DESIGN:-

During the physical design process, you convert the data gathered during the
logical design phase into a description of the physical database, including tables and
constraints.

34
CHAPTER: 6 RESULTS AND DISSCUSSION

6.1 RESULTS AND DISSCUSSION:-

The School management System is developed in order to overcome the problems
that have occurred due to the current manual system. The newly introduced system will
provide an easy access to the system and it will contain user friendly functions with
attractive interfaces. The system will give better options for the problem of handling large
scale of physical file system, for the errors occurring in all the other required tasks that
have been specified by the DEPARTMENT. The final outcome of this project will
increase the efficiency of almost all the tasks done at the Accessory in a much convenient
manner.

6.2 OUTPUT OF THE DEVELOPED SYSTEM:-

The output of the developed system is ease which is provided to the end user.

6.3 SPEED AND ACCURACY:-

After a single click on the page you can get information so it works very fast, if
you have proper speed internet connection and a fast machine. This system is also very
accurate as calculations performed by the computer are very correct up to several digits
after decimal point.

6.4 EFFICIENCY AND FLEXIBILITY:-

School management System is very efficient as it provides the information to the
user at a greater speed provided that he/she has internet
connection and Web Brower running on a simple machine.

6.5 MANGERIAL AND ACCEPTIBLITY:-

School management System is accessible at every corner of the NATION where
internet is available; accessible by everyone provided the he has a machine with internet
connection and accessible at any time.

6.6 ELIMINATING DATA REDUNDANCY:-

In this new the system data will be stored in computer which will be available at
any time and place as this database will be connected to the web page, giving facility
everywhere.
Since there is only one storage place where whole information is saved. There is
no chance of duplication of data.

35
6.7 USER FRIENDLY:-
System is a GUI-based Web Site having Links, Buttons, Check boxes, Text,
Navigation Tabs so user can easily navigate throughout the website. Using such GUI
features user can easily use this system.

6.8 DATA ENTRY:-

School management System Data is entered VERY EASILY AND ALSO
UNDERSTANDABLE.

6.9 TIME SAVING:-

This system save s a lot of time of both parties (Public and Police)

6.10 NEAT AND CLEAN SETUP:-

This system is clean as information getting and registering School management
System.

36
 REFERENCES

o Beginning PHP6, Apache, MySQL6 Web Development-Book

o Practical PHP and MySQL Website Databases- A simplified Approach-Book
o http://www.phpro.org/tutotials/Model-view-controller.html
o http://developers.google.com/maps/documentation/geocoding/#geocoding
o https://developers.google.com/maps/tutotials/customizing/custom-markers
o https://diveintohtml5.info/geolocation.html
o https://msdn.microsoft.com/en-us/magazine/hh563893.aspx
o https://www.google.com.pk
o https://en.wikipedia.org
o https://www.w3schools.com
o https://www.studmafia.com

37