“SCHOOL MANAGEMENT SYSTEM”
MAIN PROJECT REPORT
Subm Submi tted by GIRI KUMAR (Reg. No. 120011013004)
in partial fulfillment for the award of the degree of
M.Sc. INFORMATION TECHNOLOGY in
V.N.S COLLEGE OF ARTS AND SCIENCE KONNAPPARA, KONNI - 680 692
(Affiliated to MG University, Kottayam) MARCH 2014
V.N.S COLLEGE OF ARTS AND SCIENCE KONNAPPARA, KONNI - 680 692
(Affiliated to MG University, Kottayam) Department of Information Technology MAIN PROJECT WORK
MARCH 2014
This is to certify that the project entitled
SCHOOL MANAGEMENT SYSTEM is the bonafide record of project work done by
GIRI KUMAR (Reg. No. 120011013004)
of M.Sc. Information Technology during the year
-----------------------------
-----------------------------
Project Guide
Head of the Department
Submitted for the Project Viva-Voce emanication held on ........................ ........................
-----------------------------
-----------------------------
Internal Examiner
External Examiner
DECLARATION I affirm that the project work titled SCHOOL MANAGEMENT SYSTEM being submitted in partial fulfillment for the award of M.Sc Information Technology is the original work carried out by me. It has not formed the part of any other project work submitted for award of any degree or diploma, either in this or any other University.
Giri Kumar
ACKNOWLEDGEMENT Each and every moment, throughout the period of my Mini Project work, the unseen hands of almighty almight y led me. My are thankful and loyal to him.
My wish to express my sincere gratitude to Prof.T.S.ABDHUL RAHIMAN Principal and Miss.RAMZANA.S, Head of the Department for
give me the opportunity to complete this Mini Project successfully.
It is with deep sense of indebtedness and gratitude, that my wish to express my sincere feelings to Mrs.RAJ MOHAMMED, Internal guide of my Mini Project, V N S College of Arts and Science, Konni.
It is a great sense of satisfaction satis faction and a matter of privilege to me to work at Team Higherstudieonline, Higherstudiesonline.com , Adoor. It is my pleasure
to thank Mr .Joseph Mathew, MCA, Project Head of Higherstudiesonlne to whom my omy a lot for giving me an opportunity to do my training in this organization.
I would like thank all my friends who supported me to do the project.
Finally, I would like to express my sincere thanks to all other members of the faculty and each and everyone who helped me directly and indirectly in the completion of my Mini Project work.
ABSTRACT
School Management System, is a web based application which can be
used for managing a school. As the school comprises of faculty, students, management staff and parents, each of them have separate login to fetch their requirement. The students can login to their accounts and can do lot of things like scheduling works, checking assignment submission dates and they can communicate with each other. Discussion forums are provided for discussion among students. The parents can login and can follow the progress of their child's activities. They can check the mark list, attendance of their child, and the comments of their teachers about their child. They can also communicate with the faculties through the site. The faculties can login to their accounts and do several things like adding marks of the students, adding comment about the students, checking their scheduled jobs from the management or principal. The management staff as well as the principal can manage the faculties as well as the students. The personnel can add new faculty, delete a faculty, can change the details of faculty including the wage and other details.
CONTENTS 1.
Introduction ........................................................................ 1 1.1 Background ............................................................... 2 1.2 Objectives .................................................................. 3 1.3 Purpose ..................................................................... .4 1.4 Scope ........................................................................ .5
2.
Survey Of Technologies ..................................................... 6 2.1 Waterfall Model ........................................................ 6 2.1.1 Requirement Analysis .................................... 7 2.1.2 Design. ........................................................... 7 2.1.3 Coding ........................................................... .7 2.1.4 Testing........................................................... .8 2.1.5 Maintenance ................................................... 8 2.2 Feasibility Study ..................................................... ...9 2.2.1 Economic Feasibility. .................................... 9 2.2.2 Technical Feasibility ...................................... 9 2.2.3 Behavioral Feasibility .................................... 9 2.3 Technological Survey Report.................................. 10 2.3.1 PHP .............................................................. 10 2.3.2 MYSQL........................................................ 11
3.
Requirement Analysis. .................................................. ...12 3.1 Problem Definition .................................................. 12 3.2 Requirement Specification ...................................... 13 3.3 Software and Hardware Specification .................... 14
4.
Design and Implementation. Implementation. ............................................ 16 4.1 Database Design ...................................................... 16 4.1.1 Structure Of Tables ...................................... 16 4.1.2 Entity Relationship Diagram.. ..................... 27 4.2 Conceptual Models..... ............................................ 28 4.2.1 Data Flow Diagram...................................... 28
5.
Bibliography ..................................................................... 35
LIST OF FIGURES 1. Snapshots 1.1
Login Screen.
1.2
Admin: - Adding Faculty.
1.3
Admin: - Adding Student.
1.4
Admin: - Adding Parent.
1.5
Adniin: - Private Messaging.
1.6
Admin: - Sending E-mail.
1.7
Admin: -Adding Events
1.8
Admin: - Viewing Complaints.
1.9
Faculty:-Adding Mark list.
1.10
Faculty: -AddingAttendance. -AddingAttendance.
1.11
Faculty: - Adding Notification.
1.12
Faculty:-Viewing Faculty:-Viewing Students.
1.13
Faculty: - Changing Password.
1.14
Parent: - Viewing Attendance,
1.15
Parent: - Viewing Mark list.
1.16
Parent: - Viewing Events.
1.17
Parent: - Adding Complaint.
1.18
Student: - Viewing Mark list.
1.19
Student: - Students Forum.
1.20
Student: - Adding Feedback.
1.
INTRODUCTION
School Management System provides complete solution for managing a school. As the school comprises of faculty, students, management staff and parents, each of them have separate login to fetch their requirement. The students can login to their accounts and can do lot of things like scheduling works, checking assignment submission dates and they can communicate with each other. Discussion forums are provided for discussion among students. The parents can login and can follow the progress of their child's activities. They can check the mark list, attendance of their child, and the comments of their teachers about their child. They can also communicate with the faculties through the she. The faculties can login to their accounts and do several things like adding marks of the students, adding comment about the students, checking their s cheduled jobs from the management or principal. The management staff as well as the principal can manage the faculties as well as the students. The personnel can add new faculty, delete a faculty, can change the details of faculty including the wage and other details.
1
1.1
BACKGROUND
For the purpose of effective interaction between school management and parents, management had to collect information and details of students and manage them according to various streams. If any modification is r equired that is to be done manually. This is so tedious and time consuming. There are a lot of limitations limitat ions for the existing systems. Time consuming. Not accurate. Error prone. Large amounts of records are to be kept. Paper work is tedious. Report production is very slow. Interactions between various users are difficult.
So to reduce the job required to manage students' details and informing their performance to parents, a new system is proposed which is proposed through computers.
2
1.2
OBJECTIVE
The proposed system is aimed at removing the drawbacks of the existing system. The main objectives of the project are:
Reduce the paper work and storage area.
Allow interaction with different types of users.
Improve accuracy in results.
It has user friendly interface having quick authenticated access to documents.
Save time and work load for staffs parents and students.
Avoid fake entry.
Improve students' performance by periodically informing parents about their performance by messaging.
3
1.3
PURPOSE
This system aims at computerization of school management to manage the student information and catch the details so that management can inform parents about their performance. Computer based information system are designed to improve existing system. It provides the facility to effective interaction between parents and faculty. It will reduce the paper work as well as save time and money which are spending in making reports and sending man made letters for informing parents about their child's performance. It can be accessed throughout the organization and outside as well with proper login provided. This system system can be used as an application for school to manage the student information and performance detail so that they can be informed to their parents', which may help in improving their performance with the guidance of faculty and parent.
4
1.4
SCOPE
Project has a big scope to do. Administrator can maintain the students' information, parent information and faculty information and can update it. Students can access previous information i nformation about ab out their performance and can interact with other students in discussion forum, parents and faculty can interact with each other. This system has scope of improvement / amendments. This application can be modified from time to time as per the changing requirement of the user with lesser cost and also the backend of the software can-be changed as per the storage requirement of the application and to provide more security level features. This limitation with the application can also be looked into and enhancement can be made as per the user requirement. Although this project is made made only for a particular institute and supports a particular operating system platform. The wide application of the projectthis small drawback hence proving its worth.
5
2.
SURVEY OF TECHNOLOGIES
2.1
WATERFALL MODEL
The waterfall model is a sequential design process, used in software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production / Implementation and Maintenance. The waterfall model is a popular version of the system development life cycle model for software engineering. Often considered the classic approach to the system development life cycle, the waterfall model describes a development method that is linear and sequential. Waterfall development has distinct goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the edge of the cliff and has begun its journey down the side of the mountain, it cannot turn back. It is the same with waterfall development. Once a phase of development is completed, the development proceeds to the next phase and there is no turning back.
6
2.1.1
REQUIREMENT ANALYSIS
In requirement analysis phase, the development team visits the customer to collect all relevant information regarding the product to be developed. The requirement analysis and information gathering process is intensified and focused speciall y on software. The analysis should be done in a way, so that it may not too time consuming or very less informative. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase phase of the model.
2.1.2 DESIGN Before the starting of actual coding, it is highly important to understand what we are going to create and what it should look like? The requirement specifications from first phase are studied in this phase and the whole whole software development process, the overall software structure and its layout is created. There are a lot of suggestions and changes from the customer side, and all changes should be freeze before moving into the next phase. Any fault in the design des ign phase could be very expensive to solve in the t he software development process. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. The system design specifications serve as input for the next phase of the model.
2.1.3 CODING In coding phase, the design must be decoded into a machine readable form. If the design of software product is done in a detailed manner, then code generation can be achieved without much complication. For generation of code, programming tools like compilers, interpreters and debuggers are used. For coding purpose different high level programming languages like C, C++, Pascal and Java are used.
7
2.1.4 TESTING 4
Testing is the major quality measure employed during software development. It is an expensive but critical process that can take as much as 50% of the budget for program development. Different testing methods are available to detect the bugs that were committed during the previous phases. A software product goes through three level of testing. They are: Unit testing Integration testing System testing
2.1.5 MAINTENANCE Software will definitely go through change once when it is delivered to the customer. There are large numbers of reason for the change. Change would happen due to some unpredicted input values into the system. In addition to this, the changes in the system directly have an effect on the software operations. The software should be implemented to accommodate changes that could be happen during the post development period.
8
2.2
FEASIBILITY STUDY
The initial investigation points to the question whether the project is feasible. A feasibility study is conducted to identify the best system that meets the entire requirement.
2.2.1 ECONOMIC FEASIBILITY The system being developed is economic with respect to college's point of view. It is cost effective in the sense that t hat has eliminated the paper work completely. The system is time effective because the transactions are automated as per the user requirement. The result obtained contains minimum errors and are highly accurate as the data required.
2.2.2
TECHNICAL FEASIBILITY
The technical requirement for the system is economic and it does not use any other additional hardware and software.
2.2.3
BEHAVIORAL FEASIBILITY
The system working is quite easy to use and learn due to its simple but attractive interface. User requires no special training for operating the system.
9
2.3
TECHNOLOGICAL SURVEY REPORT
2.3.1 PHP PHP stands for hypertext preprocessor, which is usually called Personal Home Page (PHP).PHP is a server side scripting language. There are two types of webpages 1 .static web page 2.dynamic web page. Static web page is a page which is static, which can only be viewed by user. Dynamic web page is a page which is user interactive which means that type of page can interact with user.PHP is a server side scripting/language used for creating dynamic web pages. Main features of PHP:
PHP interact with one main external tool, the MYSQL database management system to access data stored in database.
PHP. is a server side scripting language that can be embedded with HTML.
PHP scripts are parsed and interpreted on the server side of a web application.
PHP has promising future because it is popular withWeb developers and Web designers. It is powerful and easy to use. It can handle larger projects as well as smaller personal home pages.PHP is an open-source software which means that it can be redistributed free of charge and its source s ource code is available for development.
10
2.3.2 MYSQL
SQL stands for Structured Query Language. According to ANSI (American National Standards Institute), it is the standard language for relational database management systems. MYSQL is a database computer language designed for managing data in relational database management systems (RDBMS), and originally based upon relational algebra. Some common relational database management systems that use SQL are: MYSQL, Oracle, Sybase, Microsoft SQL Server, Access, Ingres, etc. MYSQL is an open source language to retrieve data from database. However, the standard SQL commands such as "Select", "Insert", "Update", "Delete", "Create", and "Drop" can be used to accomplish almost everything that one needs to do with a database. MYSQL has proved to be a standard language as it allows users to learn one set of commands and use it to create retrieve alter and transfer information regardlesVof whether they are working PC a mini mainframe It is a high level la nffuage that provides a greater degree of abstraction increased acceptance and availability It can be easily ported
11
3.
REQUIREMENT ANALYSIS
3.1
PROBLEM DEFINITION
Now a day, parents are busier and had not much time to interact with their child's teachers so that it may help to improve their child's studies. In traditional method all details regarding their performance are sending to parents as letters and they have to comeschool to discuss with teachers about their child's performance. All the transactions are done manually. Fake entries can be there. System is more error-prone & time consuming. Difficulty in managing data ofstudents.Difficult to handle de tails of faculty and parents. Large piles of records are t o be maintained. It is a time consuming activity of managing, updating and informing specific student's details to their parent and the meeting of parent with faculty.
12
3.2
REQUIREMENT SPECIFICATION The primary goal of the system is to improve the efficiency of the existing
system. For that study of specification of the requirement is very essential. For the development of the new project of the new system, a preliminary survey was conducted. Moreover, the analysis involved the study of various functions within and outside the system.
13
33. SOFTWARE & HARDWARE SPECIFICATION
3.3.1
HARDWARE SPECIFICATION: SPECIFICATION :
Processor: Pentium IV, 1.2GHz or better RAM: 256 MB or better Monitor: 15" Hard disk capacity: 10GB or better Keyboard: Standard Mouse: Any Printer: Any Web connectivity
3.3.2
SOFTWARE SPECIFICATION: SPECIFICATI ON:
Operating system: Windows 2000 or above Front end: PHP Back end: MYSQL Web browser: Internet Explorer 6 or above Mozilla Firefox 7 or above Google Chrome 10 or above
14
4.
DESlGN AND IMPLEMENTATION
4.1
DATABASE DESIGN
4.1.1 STRUCTURE OF TABLES: We have 14 tables in our application 'School Management System'. The important tables are only included.
LOGIN TABLE:
COLUMN NAME:
DATATYPE:
SIZE:
int
5
iisemame
varchar
55
password
varchar
55
usertype
int
1
status
int
5
userid
PRIMARY KEYtuserid DESCRIPTION: User can enter username and password for logging in.
15
ATTENDANCE TABLE: Column Name:
Data Type:
Size:
studentid
int
10
parentid
int
10
facultyid
int
11
varchar
20
year
int
10
totaldays
int
11
presentdays
int
11
absentdays
int
11
percentage
int
3
comment
varchar
50
int
15
month
attendanceid
PRIMARY KEY attendanceid DESCRIPTION: Faculty can insert the attendance details of students.
16
CLASS TABLE:
Column Name:
Data Type:
Size:
int
10
ckssname
varchar
15
facultyid
int
11
strength
int
11
classid
PRIMARY KEY:classid DESCRIPTION; Administrator can insert the above class details.
17
COMPLAINT TABLE:
Column Name
Data Type
Size
int
10
userid
varchar
20
subject
varchar
50
complaintid
date complaint status
date varchar
250
int
1
PRIMARY KEY:complaintid DESCRIPTION: All users can insert the above Complaint details.
18
EVENT TABLE:
Column Name:
eventid venue
Data Type:
Size:
int
10
varchar
55
date
date
event
varchar
250
eventname
varchar
55
PRIMARY KEY: eventid DESCRIPTION: Administrator can enter details in event table.
19
FEEDBACK TABLE:
Column Name:
Data Type:
Size:
feedbackid
hit
10
name
int
20
varchar
255
feedback date
date
status
int
2
email
varchar
55.
PRIMARY KEY: feedbackid DESCRIPTION: Feedbacks are entered in feedback table.
20
FORUM TABLE:
Column Name:
forumid
userid
Data Type:
Size:
int
15
varchar
20
date
date
time
time
message
varchar
250
PRIMARY KEY:forumid
DESCRIPTION: All messages and details of message entered by students are entered in forum table.
21
MARKLIST TABLE:
Column Name:
Data Type:
Size:
marklistid
int
10
studentid
int
10
parentid
int
10
subl
int
3
sub2
int
3
sub 3
int
3
sub 4
int
3
sub 5
int
3
sub 6
int
3
total
int
3
percent
float
10
grade
char
1
int
15
facultyid
PRIMARY KEY:marklistid DESCRIPTION: Marks obtained by various students are entered in this table by faculty.
22
MESSAGE TABLE:
Data Type:
Size:
messageid
int
15
userid
int
10
Column Name:
date
date
time
time
message
varchar
150
subject
varchar
150
PRIMARY KEY:messageid DESCRIPTION: All messages between various types of users are saved in message table.
23
NOTIFICATION TABLE:
Column Name:
Data Type:
Size:
int
11
notification
varchar
55
subject
varchar
250
notificationid
date
date
notificationdate
date
PRIMARY KEY:notificationid DESCRIPTION: Notification details are saved in notification table.
24
PARENT DETAILS TABLE:
Column Name:
Data Type:
Size:
varchar
55
int
10
name
varchar
55
children
varchar
55
address
varchar
100
int
10
email
varchar
55
occupation
varchar
55
username parentid
contactno
dob
date
bloodgroup
varchar
15
qualification
varchar
55
int
10
annualincome
PRIMARY KEY: parented
DESCRIPTION:Parent DESCRIPTION:Parent details are added by administrator in parent details table.
25
4.1.2 ENTITY RELATIONSHIP DIAGRAM
4,2 CONCEPTUAL MODELS 4.2.1
DATA FLOW
DIAGRAM: LEVEL f 0' DFD
26
LEVEL'l'DFD *
27
LEVEL ' V DFD Admin:
28
[ Faculty:
29
I Parent:
30
[student:
31
32
LEVEL '3'DFD
User Data Control:
33
5.
BIBLIOGRAPHY I
TEXT REFERENCE
[1] "INTERNET PROGRAMMING",XueBal [2] David powers, "Dynamic Web Design Made Easy",. [3] Paul Dubois, "MYSQL" .. [4] "Internet & World Wide Web, How To Program", P.J. DEITEL, H.M. DIETEL
WEBSITES [1]
www.w3schools.com
LIST OF FIGURES 1. Screenshots
1.1 Login Screen.
34
1.2
Admin: - Adding Faculty.
35
1.3
Admin: - Adding Student.
36
1.4
Admin: - Adding Parent.
37
1.5
Admin: - Private Messaging.
38
1.6
Admin: - Sending E-mail.
39
1.7
Admin: - Adding Events
40
1.8
Admin: - Viewing Complaints.
41
1.9
Faculty: - Adding Mark list. +
42
1.10 Faculty: - Adding Attendance
43
1,11 Faculty: - Adding Notification. t
44
1.12 Faculty: - Viewing Students.
45
1.13 Faculty: - Changing Password.
46
1.14 Parent: - Viewing Attendance.
47
1.15 Parent: - Viewing Mark list. *
48
1.16 Parent:-Viewing Events.
49
1.17 Parent: - Adding Complaints.
50
1.18 Student: - Viewing Mark list. *
51
1.19 Student: - Students Forum.
52
1.20 Student:-Adding Feedback.
53
54
