School Management System

SCHOOL MANAGEMENT SYSTEM
BACHELOR IN COMPUTER APPLICATION

Of
GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY, DELHI
Under Supervision
Submitted by: of:ANISH SAHNI
Ms. Ayeena Malik02490202014
(Assistant Professor)
Session 2014 - 2017

Sri Guru TeghBahadur Institute Of Management &
Information Technology
Gurdwara Nanak Piao Campus, Delhi-110033
(Affiliated to Guru Gobind Singh Indraprastha University,
Sector 16 C, Dwarka ,Delhi - 110078,
India)
DECLARATION
I hereby declare that this project report entitled MANAGEMENT
ONLINEMANAGEMENT SYSTEM, submitted to the Sri Guru
TeghBahadur
Institute Of
Management &
Information
Technology, Guru Gobind Singh Indraprastha University in

the partial fulfillment for the award of the Degree of Bachelor of
Computer Application is a authentic record of work done by me
under the guidance of Ms. AYEENA MALIK.The project has not
previously formed the basis for the award of any other degree,
Diploma, Associate ship, Fellowship or other title.
ANISH SAHNI
BCA 5th SEMESTER
02490202014
CERTIFICATE
This is to certify that Mr. ANISH SAHNI, University Enrollment

Number- 02490202014, has worked under my supervision to
prepare this project report of SCHOOL MANAGEMENT SYSTEM.
The work embodied in this report is original and is of the standard
expected of B.C.A student and has not been submitted in part or
full to this or any university for the award of any degree or
diploma, he has completed all requirement of guidelines for
research project and the work is fit for evaluation.
Signature of Director: Prof. (Dr.)NAVNEET KAUR
Signature of HOD (IT): Ms. AMANPREET KAUR
Place: Delhi
Signature of Guide: Ms. AYEENA MALIK
ACKNOWLEDGEMENT
I am extremely grateful and remain indebted to my guide Ms.

AYEENA MALIK for being a source of inspiration and for her
constant support in the Design, Implementation and Evaluation of
the project. I am thankful to her for constant constructive criticism
and invaluable suggestions, which benefited me a lot while
developing the project on SCHOOL MANAGEMENT SYSTEM, he
has been a constant source of inspiration and motivation for hard
work, he has been very co-operative throughout this project work.
With candor and pleasure I take opportunity to express my sincere
thanks and obligation to Ms. AMANPREET KAUR (HOD IT). Through
this column, it would be my utmost pleasure to express my warm
thanks to her for the encouragement, co-operation and consent
without which we mightnt be able to accomplish this project.
Finally, I gratefully acknowledge the support, encouragement &
patience of my family, and as always, nothing in my life would be
possible without God, Thank You!
ANISH SAHNI
ABSTRACT
Arrival of the computers in the last two decades, so every

organization
is
going
under
the
process
of
computerization. Schools needs to create their online
website
The
project
will
automate
theSCHOOL
MANAGEMENT SYSTEM, which involved the process of
adding activities, registration, Viewing activities, giving
feedbacks , viewing Users , admissions and feedbacks
etc.It is an online School management system, which is
involved in the process of providing facility to people to
take pre admission in the SMS Public School online. SMS
public school is the name of the School. In this system
three persons are involved Admin , User and Visitor. Earlier
times people needs to go physically to join Schools, but
with the help of this system people can save time and
energy they can take admission from home also.
TABLE OF CONTENT
S.no
TOPIC
1
CANDIDATES DECLARTION
ACKNOWLDGEMENT
CERTIFICATE
ABSTRACT
PageNo.
LIST OF TABLES
5
6
LIST OF FIGURES
LIST OF SYMBOLS
CHAPTER 1- INTRODUCTION
1.1Introduction About the Topic
10
1.2Objective Of The Project
11
1.3Scope Of Project
12
13
1.4 SDLC Approach

CHAPTER 2-REQIREMENT ANALYSIS
14
2.1 Introduction
15
2.2 Software Requirement

Specification
16
2.3 Functional Requirements Of
The Project
17
2.4 Hardware Requirements
18
2.6 Technologies Used
19
20
2.7 Use Case Diagram

CHAPTER 3-SOFTWARE DESIGN
21
3.1 Introduction
22
3.2 Module Description
23
3.3Data Flow Diagram
24
0-level
25
1-level
26
2-level
27
CHAPTER 4-DATABASE DESIGN
28
4.1 Introduction
29
4.2 Database Fields Specification
30
4.3 Entity Relationship Diagram
31
CHAPTER 5-TESTING
32
6.1 Introduction
33
6.2 Test Plan
34
CHAPTER 6- Roles and

Responsibilities
CHAPTER 7 CONCLUSION
35
36
37
8.1Future Enhancement
APPENDICES
38
Biblography
LIST OF TABLES
s.no
1
2
3
Table
Table 1- Hardware
requirement
Table 2- Software
requirement
Table3- Technologies
used
Page number
LIST OF FIGURES
Sno
Figure
Page
Number
Figure 1: The Waterfall Model
Figure 2:Use Case
Figure 3: E-R Diagram
LIST OF SYMBOLS
Icon
Name
Use Case
Association
Actor
System
Include
Data Flow
Dependency
Generalization
Process
Source
Data Store
Entity
Attribute
Multivalued Attribute
Derived Attribute
CHAPTER-1
INTRODUCTION
1.1 Introduction
Education system forms the backbone of every nation. And hence
it is important to provide a strong educational foundation to the
young generation to ensure the development of open-minded
global citizens securing the future for everyone. Advanced
technology available today can play a crucial role in streamlining
education-related processes to promote solidarity among
students, teachers, parents and the school staff.
Education is central to development. It is one of the most
powerful instruments for reducing poverty and inequality and lays
a foundation for sustained economic growth. With this aim
currently our government has given special emphasis to the
educational sector and school improvement activities such as
continuous professional development for teachers, training and
upgrading teachers and capacitating schools with manpower and

materials are among the major actions which have been taken in
both primary and secondary schools. In order to facilitate and
simplify these actions one of the major tool is to have automated
school management system.
School Management System(SMS) consists of tasks such as
registering students, attendance record keeping to control
absentees, producing report cards, producing official transcript,
preparing timetable and producing different reports for teachers,
parents, officials from kebele or kefleketema education bureaus
and other stakeholders.
Automation is the utilization of technology to replace human
with a machine that can perform more quickly and more
continuously [2]. By automating SMS documents that took up
many large storage rooms can be stored on few disks.
Transcript images can be annotated. It reduces the time to
retrieve old transcripts from hours to seconds. However, the
school system in the government schools of Addis Ababa is not
automated and the record officers generate transcripts and
reports manually and the school administrators use their
experienced knowledge of miss and hit approaches to prepare
timetables.
1.2 Objective of Project

The major objectives of this project are as follows: The main purpose using computerized system is to avoid
manual problems and also documentation storage problem we
cant
maintain
long
period
data
thats
why
we
used
computerized system to overcome all problem related to

schools data storing and other arias.
This website handles online student admission procedure.
School Management System is a web based project that

maintains all the activity related to school. This project works
on dynamic website handling.
Project show time to time event information related to school. It
also provides the facility for sending mail to parent regarding
student activity.
The proposed website controls student information and faculty
details.
This is web based project its provide privilege facility for
security purpose and provide login facility according to
designation and restrict unauthorized used, if user is not admin
then it cant access everything, this project provide four type of
designation facility and access permission.
We can generate report according to date & show all report
also; Because of manual system we faced many problems. The
maintenance cost of manual system was very high. And they
didnt store historical information and not possible to view all at
a time.
This web site reduces the time & cost and provides the facility
to retrieve student all information according to requirement.
School event and all activity related information display on this
web site, the school related latest news display on this site
1.3
Scope of Project
This web based project that is maintain all the activity related to
School, it store all the information of student, SMS public
schoolProject provide sending mail to parent regarding student

activity detail.
SMS public schoolproject show time to time event information
related to school, SMS public schoolproject provide the facility for
suggestion regarding school rules and regulation and student
complaint.
2. To provide student detailed information and faculty details.
3. To make admission procedure fast and easy.
4. To inform student with time to time event information and
notices.
5. To inform parents about student activities through email.
6. To generate separate student and faculty login Id and
password.
CHAPTER-2
REQUIREMENT AND ANALYSIS
School administrator wants to build the system that technically
and economically strong and helpful to company progress. He
wants to reduce large man-power involved
in company to
perform the task that high company cost and slow company work.
For future use all documents are kept in written or in a file in
secure manner. If a file gets lost it cannot be retrieved in any way.
A large storing area is required to store the data manually.
The purpose of software requirements specifications is to provide
a framework that enables the manager to take reasonable
estimates of resources, cost and schedule. These estimates are
made with a limited time frame at the beginning of a software
project and should be updated regularly as the project progresses.
In addition estimates should attempt to define best case and
worst case scenarios so that project outcomes can be bounded.To
gather the requirement of clients need, we take the idea about
the data flow from other school websites and also refer
documents of school.
2.1 Introduction
Requirement is determining the needs or conditions to meet for a
new or altered product.Requirement analysis is critical to the
success of a systems or software project. The requirements
should be documented, actionable, measurable, testable,
traceable, related to identified business needs or opportunities,
and defined to a level of detail sufficient for system design.
2.2 Software Requirement Specification

School administrator wants to build the system that technically
and economically strong and helpful to company progress. He
wants to reduce large man-power involved
in company to
perform the task that high company cost and slow company work.
For future use all documents are kept in written or in a file in
secure manner. If a file gets lost it cannot be retrieved in any way.
A large storing area is required to store the data manually.
The purpose of software requirements specifications is to provide
a framework that enables the manager to take reasonable
estimates of resources, cost and schedule. These estimates are
made with a limited time frame at the beginning of a software
project and should be updated regularly as the project progresses.
In addition estimates should attempt to define best case and

worst case scenarios so that project outcomes can be bounded.
To gather the requirement of clients need, we take the idea about
the data flow from other school websites and also refer
documents of school.
2.3Functional Requirements of the project

Admin
Visitor:
User:
2.4. Hardware Requirements
Component
Recommended
Processor
IntelCore (TM)i5-2520M with

2.50GHz
Secondary
Storage
500GB HDD
Memory
4 GB
Network Adaptor
WIFI
Table 1 Hardware requirement

2.5. Software Requirements
Component
Recommended
OS
Windows 7
Software
Visual Studio
Table 2- Software requirement
2.6. Technologies Used
Component
Recommended
Operating System
Windows 7
Technologies
Net Beans, C#
Front-end Tool
Asp.net ,HTML,
CSS,ado.net
Back-end Tool
SQL Server
Scripting Tool
Java Script
Table 3- Technologies Used
2.7. Use Case
A use case diagram at its simplest is a representation of a

user's interaction with the system. A use case diagram can
portray the different types of users of a system and the
various ways that they interact with the system. The purposes
of use case diagrams is as follows:
Used to gather requirements of a system.

Used to get an outside view of a system.
Identify external and internal factors influencing the system.
Show the interacting among the requirements are actors.
CHAPTER-3
SOFTWARE DESIGN
3.1. Introduction
Software design is an engineering process by which we are
representing of something that is to be built. It is a blueprint for
constructing the software... After making Software Requirement
Specification of the project, now we are in position to design the
software.
The system design shows how Software will be structured to

satisfy the requirements identified during the analysis phase. The
design process is a translation of requirements into a description
of the software structure, software components, interfaces and
data necessary for the implementation phase. The design phase
provides a complete blueprint for the implementation activity.
3.2. Module Description
User
Admin
visitor
3.3 Data Flow Diagram
. A data flow diagram is a graphical representation that depicts
information flow and the transforms that are applied as data
move from input to output.
The data flow diagram may be used to represent a system or
software at any level of abstraction. In fact, DFDs may be
partitioned into levels that represent increasing information
flow and functional detail. Therefore, the DFD provides a
mechanism for functional modeling as well as information flow
mode.
0 levels DFD:
Figure: 0 Level DFD
1st level DFD:
L ib ra ry In fo .
2 .0
L ib ra ry
M anagem ent
P ro cess
S tu d e n t R e c o rd
1 .0
S tu d e n t
A d m is sio n
P ro c e ss
S tu d e n t M a s te r F ile
F e e D a ta b a s e
F e e S tru c tu re
M a rk s D a ta b a s e
4 .0
E x a m in a tio n
T C D a ta b a s e
5 .0
T C R e co rd
U p d a tio n
M o n th ly F e e
R e c o rd
3 .0
M o n th ly F e e
C o lle c tio n
Fi
gure: 1 level DFD
st
2nd Level DFD:

S tu d e n t R e c o rd D e ta ils
1 .1
R e g is tra tio n
E n try
U p d a tio n R e q u e s t
T C G iv e n b y S c h o o l
M ark s
S tu d e n t D e ta il
S tu d e n t R e c o rd
1 .2
A d m is s io n
C o n firm
C o n firm
R e je c tio n
F e e D a ta b a s e
A d m is s io n D e ta il
1 .5
E x a m in a tio n
F e e B ill D e ta il
1 .3
F e e B ill
G e n e r a tio n
B ill D e ta ils
M a rk s D a ta b a s e
F e e S tr u c tu r e
S tu d e n t M a s te r F ile
T C D e ta il
1 .6
T C R e c o rd
U p d a tio n
F e e D e ta ils
M o n th ly F e e R e c o rd
T C D a ta b a s e
1 .4
M o n th ly F e e
C o lle c tio n
3.4System Flow Chart
CHAPTER-4
DATABASE DESIGN
4.1 Introduction
Data design is the backbone of any RDBMS related software. So
first we are creating the database. Database design is a process
by which we transform the information gathered enduring the
analysis into the data structures.
4.2Database Fields Specification
Table 1: Academic Year
Table 2: Class Name
Table3:Class Time Table
Table4:Class Day Period
Table 5: Exam Title
Table 6: Reg. Fee
Table 7: School Notice
4.3 Entity Relationship Diagram

The Entity Relationship Diagrams (ERD) is the graphical notation
of relationship between data object and attributes... The primary
purpose of the ERD is to represent data objects and their
relationship.
Relational
Database
RDBMS
-A relational
database
management system (RDBMS) is a database management
system (DBMS) that is based on the relational model as invented
by E. F. Codd. RDBMSs are a common choice for the storage of
information in new databases used for financial records,
manufacturing and logistical information, personnel data, and
other applications. Relational databases have often replaced
legacy hierarchical databases and network databases because
they are easier to understand and use. RDBMS stands
for Relational Database Management System. RDBMS is the
basis for SQL, and for all modern database systems like MS SQL
Server, IBM DB2, Oracle, MySQL, and Microsoft Access. A
Relational database management system (RDBMS) is a database
management system (DBMS) that is based on the relational
model.
ER Diagram
CHAPTER-5
TESTING
5.1. Introduction
Executing a program with the intent of finding errors is called
testing. Testing is vital to the success of any system. Testing is
done at different stages within the development phase. System
testing makes a logical assumption that if all parts of the system
are correct, the goals will be achieved successfully. Inadequate
testing or no testing at all leads to errors that may come up after
a long time when correction would be extremely implementation.
The testing of the system was done on both artificial and live
data. In order to test data test cases are developed. Following are
the various methods that are employed for testing:
Unit Testing
In unit testing the module is tested independently. It is done to
test that the module does satisfy the functional specification. This
is done to check syntax and logical errors in programs. At the
time of preparation of technical specifications, unit test data was
also prepared. The coding for that program was considered after
verifying its output against this test data.
Integration Testing
In Integration testing whole system was checked when all the

individual modules were integrated together in order to test
whether
the
system
is
performing
as
according
to
the
requirements specified. Interface errors if any were corrected

Functional Testing
This is done for each module/sub module of the system.
Functional testing serve as a means of validating whether the
functionality of the system confers the original user requirement
i.e. does the module do what it was supposed to do?
System Testing
System testing is done when the entire system has been fully
integrated. The purpose of the system testing is to test how the
different modules interact with each other and whether the entire
system provides the functionality that was expected.
5.2. Test-Plan -The test-plan is basically a list of test cases that
need to be run on the system.
No
.
1
Title
Successful
admin
verification
Description
Expected Outcome
outcome
occured
Resul
t
Admin should
be log in with
the correct
login ID and
password
Login
Login is
Passe
should be successful d
successful
Unsuccessf
ul admin
verification
due to
wrong
password
The login to
the system
with a wrong
password.
Login
should fail
with an
error
invalid ID
and
password
.
Login fails
Passe
d
Unsuccessf
ul user
verification
due to
wrong
userID
The login to
the system
with a wrong
UserID
Login
should fail
Login fails
passe
d
Successful Visitor can

registration register
by
successfully
Registrati
on
Successful
.
Registrati Passe
on
d
Successful
.
visitor.
4
User can
view /print
admission
slip
User can
successful successful Passe
view /print
d
admission slip
by entering
valid
admissionID
Successful
admission
and
payment
Databases
have entry of
new
Admissions
payment
details
Data of
should be
stored in
database
Data is
stored
successful
ly
Passe
d
6.
Successful
user
verification
User should
be logged in
with correct
UserID
Login
Login
passe
should be should be d
successful successful
CODING AND SCREENSHOTS
1. Admin Module
2.
<?xml version='1.0' encoding='UTF-8' ?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:p="http://primefaces.org/ui"
xmlns:f="http://java.sun.com/jsf/core">
<h:head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<link href="./../resources/css/default.css" rel="stylesheet"
type="text/css" />
<h:outputStylesheet library="css" name="default.css"/>
<h:outputStylesheet library="css" name="cssLayout.css"/>
<title>
<ui:insert name="title">School Management</ui:insert>
</title>
</h:head>
<h:body>
<div id="container">
<div id="top">
<ui:insert name="top">
<p:panel style="min-height: inherit; height: inherit;">
<f:view>
<p:outputPanel style="float: left;width: 150px;height: inherit;">

<center>
<p:graphicImage value="./../resources/images/logo3.jpg" width="85px"
height="90px"/>
</center>
</p:outputPanel>
<p:outputPanel>
<p:panel rendered="#{loginBean.showLogout}" style="float: right; border:

0;">
<f:view>
<h:form>
<p:outputLabel value="#{loginBean.roleName} : #{loginBean.name}"

styleClass="grbg"/>
<p:commandLink value="log out" action="#{loginBean.logout()}"

styleClass="loglink"/>
<h:link value="My Home" outcome="#{loginBean.goMyHome()}"

styleClass="loglink"/>
</h:form>
</f:view>
</p:panel>
<p:panel style="height: 60px; border: 0;padding: 0;color: #333300;">

<p:outputLabel value="SMS Public School" styleClass="schname"/>
</p:panel>
<p:panel style="margin: 0px 0px0px 150px;padding: 0;border: 0;fontvariant: normal;background: none;" styleClass="menu">
<li><h:link value="Home" outcome="../index.xhtml"/></li>
<li><h:link value="Notice" outcome="../public/publicNotice.xhtml"/></li>
<li><h:link value="Result" outcome="./../public/publicResult.xhtml"/></li>
<li><h:link value="About us" outcome="../about.xhtml"/></li>
<li><h:link value="Contact us"
outcome="./../public/contactus.xhtml"/></li>
</p:panel>
</p:outputPanel>
</f:view>
</p:panel>
</ui:insert>
</div>

<div id="center">
<div id="left">
<ui:insert name="left">
<p:panel style="border: 0; margin-left: 2px;">
<p:accordionPanel style="padding: 0;"
activeIndex="#{adminAccordionBean.activeIndex}">
<p:ajax event="tabChange"
listener="#{adminAccordionBean.onTabChange}"/>
<p:tab title="Academic">
<div class="adminMenu">
<h:link value="Academic Year" outcome="acyear.xhtml"/>
<h:link value="Class" outcome="class.xhtml"/>
<h:link value="Section" outcome="section.xhtml"/>
<h:link value="Group" outcome="group.xhtml"/>
<h:link value="Subject" outcome="subject.xhtml"/>

<h:link value="Examination" outcome="exam.xhtml"/>
<h:link value="Marks" outcome="marks.xhtml"/>
</div>
</p:tab>
<p:tab title="Class Routine">
<h:link value="Period" outcome="period.xhtml"/>
<h:link value="Teacher & Subject"
outcome="teacherSubjectAssign.xhtml"/>
<h:link value="Class Routine" outcome="classRoutine.xhtml"/>
</div>
</p:tab>
<p:tab title="Student">
<h:link value="Student Info" outcome="student.xhtml"/>
<h:link value="Attendents" outcome="attend.xhtml"/>
<h:link value="Registration" outcome="registration.xhtml"/>
</div>
</p:tab>
<p:tab title="Teacher">
<h:link value="Teacher Info" outcome="teacher.xhtml"/>
<h:link value="Teacher Grade" outcome="teacherGrade.xhtml"/>
<h:link value="Teacher Registration"
outcome="teacherRegistration.xhtml"/>
</div>
</p:tab>
<p:tab title="Notice">
<h:link value="Notice" outcome="notice.xhtml"/>
</div>
</p:tab>
<p:tab title="Others">
<h:link value="Admin Home" outcome="adminPanel.xhtml"/>
</div>
</p:tab>
</p:accordionPanel>
</p:panel>
</ui:insert>
</div>
<div id="content" class="left_content">
<p:panel style="min-height: inherit;">
<ui:insert name="content">Content</ui:insert>
</p:panel>
</div>
</div>
<div id="bottom">
<ui:insert name="bottom">
<p:panel style="min-height: inherit; margin: 0 auto;text-align: center;">
<p:outputLabel value="copyright © 2016. This Product is made as the

purpse of Education only."/>
</p:panel>
</ui:insert>
</div>
</div>
</h:body>
</html>
Exams<?xml version='1.0' encoding='UTF-8' ?>
xmlns:f="http://java.sun.com/jsf/core"
xmlns:p="http://primefaces.org/ui">
<body>
<ui:composition template="./adminTemplate.xhtml">
<ui:define name="title">
School Management - Admin - Exam info
</ui:define>
<ui:define name="content">
<f:view>
<h:form id="addform">
<p:growl id="grl" showDetail="true"/>
<p:fieldset legend="Add Exam Title" style="font-size: 9pt" >
<p:panelGrid columns="3">
<p:column>
<p:outputLabel value="Exam Title"></p:outputLabel><br/>
<p:inputText value="#{examTitleBean.examTitle}"></p:inputText>
</p:column>
<p:column>
<p:outputLabel value="Description"></p:outputLabel><br/>
<p:inputText value="#{examTitleBean.examDescription}"></p:inputText>
</p:column>
<p:column>
<p:commandButton value="Save" action="#{examTitleBean.insertExam()}"
update=":dtform:exTitle,:addform:grl" icon="ui-icon-disk"/>
</p:column>
</p:panelGrid>
</p:fieldset>
</h:form>
<h:form id="dtform">
<p:dataTable id="exTitle" value="#{examTitleBean.allExamTitle}"
var="item" style="font-size: 9pt">
<p:column style="width: 40px;">
<f:facet name="header">Exam Id</f:facet>
#{item.examTitleId}
</p:column>
<p:column style="width: 150px;">
<f:facet name="header">Exam Title</f:facet>
#{item.examTitle}
</p:column>
<p:column>
<f:facet name="header">Description</f:facet>
#{item.examDescription}
</p:column>
<p:columnheaderText="Option" style="width: 100px;">
<p:commandButton value="Edit"
action="#{examTitleUpdate.doSetSelectedRow()}"
oncomplete="editdialog.show()" update=":dtform:editpane" icon="ui-iconpencil" style="font-size: 7pt;">
<f:setPropertyActionListener target="#{examTitleUpdate.selectedRow}"
value="#{item}"/>
</p:commandButton>
<p:spacer width="3px"/>
<p:commandButton value="Delete"
action="#{examTitleBean.deleteExam()}"
update=":dtform:exTitle,:addform:grl" icon="ui-icon-close" style="color:
#D20005;font-size: 7pt;">
<f:setPropertyActionListener target="#{examTitleBean}"
value="#{item}"/>
</p:commandButton>
</p:column>
</p:dataTable>
<p:dialog id="dialog" widgetVar="editdialog" showEffect="clip"

hideEffect="fold" resizable="false" header="Edit Exam Title">
<p:panelGrid id="editpane" columns="2">
<p:outputLabel value="Exam Title ID :"/>
<p:outputLabel value="#{examTitleUpdate.examTitleId}"/>
<p:outputLabel value="Exam Title :"/>

<p:inputText value="#{examTitleUpdate.examTitle}"/>
<p:outputLabel value="Description :"/>

<p:inputText value="#{examTitleUpdate.examDescription}"/>
<p:spacer/>
<p:commandButton value="Update"
action="#{examTitleUpdate.updateExam()}"
update=":dtform:exTitle,:addform:grl" oncomplete="editdialog.hide()"/>
</p:panelGrid>
</p:dialog>
</h:form>
</f:view>
</ui:define>
</ui:composition>
</body>
</html>
Marks-

xmlns:f="http://java.sun.com/jsf/core"
xmlns:p="http://primefaces.org/ui">
<body>
School Management - Admin - Result info
</ui:define>
</ui:define>
</ui:composition>
</body>
</html>
Registration-

xmlns:p="http://primefaces.org/ui"
xmlns:f="http://java.sun.com/jsf/core">
<body>
School Management - Admin - Registration info
</ui:define>
<f:view>
<h:formenctype="multipart/form-data">
<p:panel id="all" style="font-size: 9pt;padding: 0;margin: 0;border: none;">
<p:growlshowDetail="true" id="g"/>
<p:fieldset legend="Basic Information">
<h:panelGrid columns="3" cellpadding="7"
columnClasses="firstcolumn,centercolumn,thirdcolumn" style="margin: 0
auto;">
<p:outputLabel value="Student Name :"/>

<p:inputText value="#{newStudentBean.studentName}" id="stname"
required="true" requiredMessage="please enter Student Name"/>
<p:message for="stname"/>
<p:outputLabel value="Father Name :"/>

<p:inputText value="#{newStudentBean.fatherName}" id="faname"
required="true" requiredMessage="please enter Father Name"/>
<p:message for="faname"/>
<p:outputLabel value="Mother Name :"/>

<p:inputText value="#{newStudentBean.motherName}" id="moname"
required="true" requiredMessage="please enter Mother Name"/>
<p:message for="moname"/>
<p:outputLabel value="Date of Birth :"/>

<p:calendar value="#{newStudentBean.dateOfBirth}" id="dob"
required="true" requiredMessage="please enter Date of Birth"/>
<p:message for="dob"/>
<p:outputLabel value="Age (as 01-01-2013) :"/>

<p:inputText value="#{newStudentBean.age}" id="age" required="true"
requiredMessage="please enter age"/>
<p:message for="age"/>
<p:outputLabel value="Gender :"/>
<p:selectOneRadio value="#{newStudentBean.gender}" id="gen"

style="border: #ffffff;" required="true" requiredMessage="please select
gender">
<f:selectItemitemLabel="Male" itemValue="Male"/>
<f:selectItemitemLabel="Female" itemValue="Female"/>
</p:selectOneRadio>
<p:message for="gen"/>
<p:outputLabel value="Photo :"/>

<p:fileUpload value="#{newStudentBean.photo}" mode="simple"
id="photo" allowTypes="/(\.|\/)(gif|jpe?g|png)$/" required="true"
requiredMessage="Please select photo"/>
<p:message for="photo"/>
</h:panelGrid>
</p:fieldset>
<br/>
<p:fieldset legend="Contact Information">
<h:panelGrid columns="3"
columnClasses="firstcolumn,centercolumn,thirdcolumn" cellpadding="7"
style="margin: 0 auto;">
<p:outputLabel value="Telephone NO. :"/>
<p:inputText value="#{newStudentBean.telephoneNo}" id="tel"/>
<p:message for="tel"/>
<p:outputLabel value="Mobile No. :"/>

<p:inputText value="#{newStudentBean.mobileNo}" id="mob"/>
<p:message for="mob"/>
<p:outputLabel value="Present Address :"/>

<p:inputTextarea value="#{newStudentBean.presentAddress}" id="preadd"
required="true" requiredMessage="please enter Present Address"/>
<p:message for="preadd"/>
<p:outputLabel value="Parmanent Address :"/>

<p:inputTextarea value="#{newStudentBean.parmanetAddress}"
id="paradd" required="true" requiredMessage="please enter Parmanent
Address"/>
<p:message for="paradd"/>
</h:panelGrid>
</p:fieldset>
<br/>
<p:fieldset legend="Academic Information">
<p:outputLabel value="Academic Year :" />
<p:selectOneMenu id="acy" value="#{newStudentBean.academicYearId}"
required="true" requiredMessage="Please select academic year"
style="width: 145px">
<f:selectItemitemLabel="--Select--" itemValue=""/>
<f:selectItems value="#{newStudentBean.allAcademicYear}" var="acyy"
itemLabel="#{acyy.academicYear}"
itemValue="#{acyy.academicYearId}"/>
<p:ajax event="change" update="secc"/>
</p:selectOneMenu>
<p:message for="acy"/>
<p:outputLabel value="Class Name :" />

<p:selectOneMenu id="clas" value="#{newStudentBean.classId}"
required="true" requiredMessage="Please select class" style="width:
145px">
<f:selectItems value="#{newStudentBean.allClass}" var="classes"
itemLabel="#{classes.className}" itemValue="#{classes.classId}"/>
<p:ajax event="change" update="secc"/>
</p:selectOneMenu>
<p:message for="clas"/>
<p:outputLabel id="dd" value="Section Name :" />

<p:selectOneMenu id="secc" value="#{newStudentBean.sectionId}"
required="true" requiredMessage="Please select section" style="width:
145px">
<f:selectItems value="#{newStudentBean.allSection}" var="section"
itemLabel="#{section.sectionName}" itemValue="#{section.sectionId}"/>
</p:selectOneMenu>
<p:message for="secc"/>
<p:outputLabel value="Group Name :" />

<p:selectOneMenu id="grp" value="#{newStudentBean.groupId}"
required="true" requiredMessage="Please select group" style="width:
145px">
<f:selectItems value="#{newStudentBean.allGroup}" var="group"

itemLabel="#{group.groupName}" itemValue="#{group.groupId}"/>
</p:selectOneMenu>
<p:message for="grp"/>
<p:outputLabel value="Student Roll :"/>

<p:inputText value="#{newStudentBean.studentRollNo}" id="roll"
required="true" requiredMessage="please enter your Roll Number"/>
<p:message for="roll"/>
</h:panelGrid>
</p:fieldset>
<br/>
<p:fieldset legend="Others Information">
<p:outputLabel value="Registration Date :"/>

<p:calendar id="regd" value="#{newStudentBean.registrationDate}"
pattern="dd/MM/yyyy" required="true" requiredMessage="Please enter Reg
Date"/>
<p:message for="regd"/>
<p:outputLabel value="Registation Fee :"/>

<p:inputText id="regfee" value="#{newStudentBean.feeAmount}"
required="true" requiredMessage="Please enter Fee Amount"/>
<p:message for="regfee"/>
<p:outputLabel value="Pay Date :"/>

<p:calendar id="payd" value="#{newStudentBean.payDate}"
pattern="dd/MM/yyyy" required="true" requiredMessage="Please enter Pay
Date"/>
<p:message for="payd"/>
<p:outputLabel value="User Type :" />

<p:selectOneMenu id="ut" value="#{newStudentBean.roleId}"
required="true" requiredMessage="Please select Role Name" style="width:
145px">
<f:selectItems value="#{newStudentBean.allUserType}" var="utype"
itemLabel="#{utype.roleName}" itemValue="#{utype.roleId}"/>
</p:selectOneMenu>
<p:message for="ut"/>
<p:outputLabel value="User Name :"/>

<p:inputText id="unn" value="#{newStudentBean.userName}"
required="true" requiredMessage="please enter User Name" style="color:
palevioletred"/>
<p:message for="unn"/>
<p:outputLabel value="Password :"/>

<p:password id="psss" value="#{newStudentBean.newPassword}"
required="true" requiredMessage="please enter password" style="color:
peru"/>
<p:message for="psss"/>
<p:outputLabel value="Confirm Password :"/>

<p:password id="cpsss" value="#{newStudentBean.confirmPassword}"
required="true" requiredMessage="please enter password" style="color:
peru"/>
<p:message for="cpsss"/>
</h:panelGrid>
</p:fieldset>
<h:panelGrid columns="1" style="margin: 0 auto;">
<p:commandButton value="submit"
action="#{newStudentBean.doInsert()}" update="all,g" ajax="false"/>
</h:panelGrid>
</p:panel>
</h:form>
</f:view>
</ui:define>
</ui:composition>
</body>
</html>
CHAPTER-6
ROLES AND RESPONSIBILTY
While doing my project on SCHOOL MANAGEMENT SYSTEM, my

responsibilities towards my project are:
I was involved in collection of information related to my
project.
I am responsible for designing, coding, implementation and
testing of all the modules in the project.
I have used very easy and user-friendly designing tools so
that the users can interact with the system easily.
I am responsible for approving the designing tool and
database selection.
Planning and Execution of the project were done by me.
CHAPTER-7
CONCLUSION
The conclusion of SMS PUBLIC SCHOOL is to construct such
dynamic website which will provide information about school
activities such as admission system, event schedule, school timetable, important notices and dignitary messages.
Towards the end of the School Management System, I would like
to say that the target, which was initially set up, was achieved to
a good extent. The project made me realise the significance of
developing software for client, where the sole aim is to learn.
During the School Management System, the real importance for
following all principle of system analysis and design dawned on
me. I felt the necessity of going through the several stages.
As we done the initial investigation, now we can say that this
application possible to create. But as project will progress there
may some change in functionality of the project.
8.1 Future Enhancement

Presently the website is used for primary school students but
in future it can be utilized for middle school, high school and
colleges by some minor modifications.
Database may be available in future for long times and
information may be use anytime.
SMS facility in future

School Management System

Uploaded by

Copyright:

Available Formats

School Management System

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

School Management System

Uploaded by

Copyright:

Available Formats

SCHOOL MANAGEMENT SYSTEM

BACHELOR IN COMPUTER APPLICATION

Session 2014 - 2017

Technology, Guru Gobind Singh Indraprastha University in

This is to certify that Mr. ANISH SAHNI, University Enrollment

Signature of Director: Prof. (Dr.)NAVNEET KAUR

Signature of HOD (IT): Ms. AMANPREET KAUR

Signature of Guide: Ms. AYEENA MALIK

I am extremely grateful and remain indebted to my guide Ms.

Arrival of the computers in the last two decades, so every

1.1Introduction About the Topic

1.4 SDLC Approach

2.2 Software Requirement

2.7 Use Case Diagram

3.2 Module Description

3.3Data Flow Diagram

CHAPTER 4-DATABASE DESIGN

4.2 Database Fields Specification

4.3 Entity Relationship Diagram

6.2 Test Plan

CHAPTER 6- Roles and

Figure 1: The Waterfall Model

Figure 2:Use Case

Figure 3: E-R Diagram

upgrading teachers and capacitating schools with manpower and

1.2 Objective of Project

computerized system to overcome all problem related to

School Management System is a web based project that

schoolProject provide sending mail to parent regarding student

2.2 Software Requirement Specification

In addition estimates should attempt to define best case and

2.3Functional Requirements of the project

2.4. Hardware Requirements

IntelCore (TM)i5-2520M with

Table 1 Hardware requirement

Table 2- Software requirement

2.6. Technologies Used

Table 3- Technologies Used

2.7. Use Case

A use case diagram at its simplest is a representation of a

Used to gather requirements of a system.

The system design shows how Software will be structured to

Figure: 0 Level DFD

1st level DFD:

2nd Level DFD:

3.4System Flow Chart

Table 2: Class Name

Table3:Class Time Table

Table4:Class Day Period

Table 5: Exam Title

Table 6: Reg. Fee

Table 7: School Notice

4.3 Entity Relationship Diagram

In Integration testing whole system was checked when all the

requirements specified. Interface errors if any were corrected

Successful Visitor can

CODING AND SCREENSHOTS

<?xml version='1.0' encoding='UTF-8' ?>

<p:outputPanel style="float: left;width: 150px;height: inherit;">

<p:outputLabel value="copyright © 2016. This Product is made as the