A PROJECT REPORT ON

ENTERPRISE SCHOOL MANAGEMENT UNDER THE GUIDENCE OF:

Mr. ABHISHEK GUPTA

(SESESSION 2011 2012)

DEPARTMENT OF INFORMATION TECHNOLOGY

GNIT GIRLS INSTITUTE OF TECHNOLOGY 6-B, KNOWLEDGE PARK-II, Gr. NOIDA-201304 Affiliated To Uttar Pradesh Technical University Lucknow. SUBMITTED BY:
ANJALI VARSHNEY HIMANSHI DHYANI DIVYA SHREE SANGYA VENU

CERTIFICATE
This is to certify that Himanshi Dhyani, Anjali Varshney, Divya Shree and Sangya Venu of B.Tech., Information Technology at GNIT Girls Institute of Technology, Greater Noida have successfully completed their project on ENTERPRISE SCHOOL MANAGEMENT in an authentic way under our guidance and supervision.

Mr.Umesh Yadav

ACKNOWLEDGEMENT

Before getting into the thick n thin of the things we would like to add a few heartfelt words for the people who were a part of this report in numerous ways. We wish to express our gratitude & heartiest

thanks to Mr.Umesh Yadav, Assistant Professor of, G.N.I.T.Girls

Institute of Technology, Greater Noida, who helped us a lot and also gave us a lot of suggestions regarding the presentation of this project. And a tone of thanks to our comrades who gave very valuable suggestion for the improvement of the project. Finally, thanks to all our family members for the encouragement we got from them.

Team Member:
Anjali Varshney (0941613002) Himanshi Dhyani (0941613008) Divya Shree (0941613007) Sangya Venu (0941613029)

ABSTRACT

This School Management Software is designed for better interaction between students, teachers, parents & management. This management software very gracefully handles all the requirements for easy school management. The school management system being web based can be accessed from anywhere in the world, which enables the students, teachers, parents & the management be in touch with each other at all times. Right School Management Software can provide a great relief to the district superintendents, principals, teachers, students, and parents to enhance their performance exponentially.

TABLE OF CONTENTS
1: Introduction........................................................................1
1.1 About the Project..........................................................................2
1.2 1.3

Problem Statement........................................................................3 Objective.......................................................................................4 overview......................................................................5

1.4 Functional

2: System Analysis..................................................................6
2.1Existing System...............................................................................7
2.2 Proposed

System.............................................................................8 Analysis...............................................................9-10

2.3 Requirement

2.4 Methodology Used...................................................................11-12 2.1.1 Waterfall Methodology........................................................13 2.5 Software requirement specification.............................................14 2.6Software and Hardware Requirement...........................................15

3: System Design...................................................................16
3.1 Introduction................................................................................17 3.2 Data Flow Diagram....................................................................18 3.2.1 Data Flow Diagram of 0-level............................................18 3.2.2 Data Flow Diagram of 1-level............................................19 3.4 Database Design.....................................................................20-23

4: Implementation........................................................................24
4.1 Introduction..............................................................................25-26

5: Screens.............................................................................27-33

6: Benefits.........................................................................................34 7: Future Scope.........................................................35 8: References...................................................................................36

INTRODUCTION

ABOUT THE PROJECT:

E - School Management System Management Software. It is designed for better interaction between students, teachers, parents & management. This management software very gracefully handles all the requirements for easy school management. The school management system being web based can be accessed from anywhere in the world, which enables the students, teachers, parents & the management be in touch with each other at all times. ESM has been developed by the teachers and for the teachers, in order to ease their day to day activities. It also provides greater visibility of all the functions, such as grading and attendance, and evaluation of reports at any point of the school year. At present, attendance, grading, lesson planning and other key activities are very tedious and time consuming and need to be done repetitively. Moreover, Enterprise School Management (ESM) will prevent all overheads, repetitive work, and provide you more time to focus on teaching or constructive activities. This also helps to ensure that you have all the tools needed to effectively build a solid overall growth path for your students while also focusing on your own career.

 PROBLEM STATEMENT:

There are many schools that have their own website nowadays but those websites are not enterprise websites. Those websites are only websites which are for popularity of the school and to provide information of the school. Problem: The basic problems with the traditional websites are that they only provide information about the school. Such websites do not let the users to fill up admission form. The parents and all other related members like teachers and administrator cant create notices n view, create or modify information about students, teachers or other staff of the school. Use of traditional and non user friendly interfaces that are hard to use

OBJECTIVE:

The motive of this website is to facilitate parents to view their childs academic report and their activity from any remote corner by just logging in the website. Provide Interactive interface through which a user can interact with different areas of application easily. One more objective is to increase the schools business and facilitate the people who wish to join the school. The other aim of this enterprise school website is to make the administrator to put notices over the website which may be urgent so that the target audience can read it as soon as possible.

 FUNCTIONAL OVERVIEW:

This website is basically for growing the business of the school and to facilitate the students, parents, teachers and the school management i.e. administrator. The students would be facilitated by letting them login and know the school news, notices and curriculums. And so as the parents and all are facilitated. This Enterprise School Management website has following modules. Student Parents Teachers/Class teachers Admin/Principal/Data Entry

SYSTEM ANALYSIS

 Existing system:
The existing system does not have any kind of automation services.

The existing system is the traditional way of making admissions in the college.

We have to go to the school for interacting with the teachers and for any other information. If the parents are out of station and are not able to attend the PTMs. The administrator have to waste a lot of time in first typing, printing and then putting it over the notice board.

 Proposed System:

This is been developed by the teachers and for the teachers, in order to ease their

day to day activities. It also provides greater visibility of all the functions, such as grading and attendance, and evaluation of reports at any point of the school year. Main Features: View/Take Attendance Report Cards Section School time-table Assignments Homework Exam Schedule Student/Teachers Profile Holidays List Discussion Forum / Message Board Internal Messaging System School/Class Notices

REQUIREMENT ANALYSIS:

Once the project was found to be feasible, requirement analysis or detailed study was done which involved detailed study of all the schedules (Input) and formats of the reports to be generated for the analysis purpose. Series of discussions helps to analyze various issues involved with the study which are:

Procedures for Data Collection, Compilation, Preparation and Problems involved.

Quality of data coming from field level.

Conversion of data into structured format.

Time limit for entry and validation of data.

 Number of reports to be generated for various schedules.

Level of Complexity of Analysis.

In which form the Reports to be produced (printed copy, in excel format, etc.).

10

METHODOLOGY USED :
The ultimate objective of software engineering is to produce good quality maintainable software within reasonable time frame and at affordable cost. This is achieved only if we have matured processes to produce it. For a mature process, it should be possible to determine in advance how much time and effort will be required to product. This can only be done using data from the past experience, which requires that we must measure the software process. In IEEE STANDARD glossary of software engineering technology, the software life cycle isThe period of time of time that starts when a software product is conceived and ends when the product is no longer available for use. The software life cycle typically include requirement phase, implementation phase, design phase, installation phase and check out phase, operation and maintenance phase, and some time retirement phase.

11

This project is divided primarily into four modules: Administrators: The administrator can create, update, delete and modify students and facultys profile. She/he can also create, update and delete notices, curriculums and school news. Students: They are the genuine customers of the website. They can view their performance, attendance, etc by logging into the website. Faculty: These people can upload student performance, result and attendance of the student. They can interact with the parents through this website. Parents: The parents of the students can view teachers and their childs profile by simply logging into the site. They can interact to the teachers to keep a track of their child.

For the development of this project we have used the most basic software development life cycles namely the Waterfall Model.

12

 WATERFALL METHODOLOGY:
Req. & Analysis System Design Detailed Design Coding & Unit Testing System & Integration Testing Operation & Maintenance

13

Software Requirement Specification

The Software Requirement Specification (SRS) is a document that completely describes what the proposed software should do without describing how the software will do it. Since, the system specifications prepared as a plain; it become sometime necessary to modify it after taking it into consideration the practical difficulties or errors found during later stages of development. However, producing the SRS is easier said done. System Specifications should include all the working of the system. One of the main purposes of SRS is to bridge the communication gap. Another important purpose of developing the SRS is helping the clients understand their own needs. The advantages are:

An SRS establishes the basis for agreement between the client and the supplier and what the software product will do.

An SRS provides a reference for validation of the final product. 14

Hardware and Software Platform

HARDWARE REQUIREMENT:

512 MB RAM 1 GB HARD DISK

SOFTWARE REQUIREMENT:

LANGUAGE USED: HTML JSP Java SE 7

OPEATING SYSTEM: WINDOW XP

DATABASE USED: SQL SERVER 2005

IDE USED: NetBeans IDE 7.0

15

SYSTEM DESIGN

16

 INTRODUCTION:

The purpose of the design phase is to plan a solution for the problem specified by the requirement document. This phase is the first step in moving from the domain to the solution domain.

In other words, starting with what is needed; design takes us towards how to satisfy the need. The output of this phase is the design document. This document is similar to a blueprint or plan for the solution and is used later during implementation, testing and maintenance

17

Data Flow Diagram :

Data Flow Diagram Of 0-level

18

Data Flow Diagram Of 1-leval:

19

DATABASE DESIGN:
The tables used are:
1.

LOGINTBL : The Login table deals with the validation of correct username, user_ID and password. This table contains the information about different users and their login id and their passwords.

2.

Student_Details : This student detail table contain all the information about the student. It bears the names of the student, admission number, address, date of birth, blood group, fathers name, mothers name, etc.

3.

Teacher_Detail : This teacher detail table contains the information about the teachers. Such as teacher name, address, contact, department, qualification, etc.

20

LOGINTBL Table Field Name USERNAME PASSWORD USERTYPE Data Type nvarchar nvarchar nvarchar

21

Teacher_Detail Table
Field Name TeacherNo Tname DateofJoining DOB Qualification Experience Data Type nvarchar Text Text Text Text Text

22

Student_Detail Table
Field Name Admission Name FName MName Address DOB Blood Group DateofAdmission ContactNo. Data Type nvarchar Text Text Text Text nvarchar nvarchar Text Numeric

23

IMPLEMENTATION

24

Introduction
After the successful testing of software, we implement our system in a particular lab. It is very important part of software development as we complete our software, then we go for the installation of the software to the user end. Here we keep in mind the hardware and software requirements and we also train the employees who do not have knowledge of computers. The software should be such that even a naive user can easily operate all its functions properly. In the implementation phase, we make sure that the software is performing its entire desired task properly using the minimum possible software and hardware requirements. In the implementation phase, we make sure that the software is user friendly so that any new user can easily operate on it. Any changes in the software and hardware requirements must be in this phase.

25

Hence, the implementation of this project can be achieved by the users who have knowledge about the computer and the language. The implementation is over only when the software or in this case the project fulfils the required function for which it has been developed.

26

SCREENS

27

28

29

30

31

32

33

BENEFITS
The enterprise school management is developed to facilitate the parents to interact with the teachers. This website is basically for growing the business of the school and to facilitate the students, parents, teachers and the school management i.e. administrator. The students would be facilitated by letting them login and know the school news, notices and curriculums. And so as the parents and all are facilitated.

34

Future Scope:

This project has a very good future scope. The following are the areas for the future scope Automatic mailing to the parents Automatic mail generation Online fee deposition Guest module can also be added

35

RESOURCES AND REFERENCES

The successful completion of the project is being supported by a number of resources which were being used in various phases of the development. These resources include; The study material in the form of e-books which were very helpful in teaching all the basic concepts of the html language.

The Websitesi. W3cschool.com

Online forums were also very helpful as they contain a number of frequently ask question and various answer to those questions.

36