School Management System
School Management System
CHAPTER
TITLE DESCRIPTION PAGE NO
NO
1 INTRODUCTION
1.1 ORGANIZATION PROFILE
1.2 SYSTEM SPECIFICATION
1.2.1 HARDWARE CONFIGURATION
1.2.2 SOFTWARE SPECIFICATION
2 SYSTEM STUDY
2.1 EXISTING SYSTEM
2.1.1 DRAWBACKS
2.2 PROPOSED SYSTEM
2.2.1 FEATURES
3 SYSTEM DESIGN AND DEVELOPMENT
3.1 FILE DESIGN
3.2 INPUT DESIGN
3.3 OUTPUT DESIGN
3.4 DATABASE DESIGN
3.5 SYSTEM DEVELOPMENT
3.5.1 DESCRIPTION OF MODULES
4 TESTING AND IMPLEMENTATION
5 CONCLUSION
BIBLIOGRAPHY
APPENDICES
A. DATA FLOW DIAGRAM
B. TABLE STRUCTURE
C. SAMPLE CODING
D. SAMPLE INPUT
E. SAMPLE OUTPUT
SYNOPSIS
2.1.1. DRAWBACKS
Schools must not have access to complete, accurate, and timely information about
students.
Present Student record system will not simplify retrieval of required information
It is a very tedious to maintain the information acquired.
Transcripts of students are prepared manually by the record officer and teachers.
2.2.1. FEATURES
Reduce complexity through automation.
User-friendly environment to operate on.
Compatible to all platforms.
Improve Administration/Accounts department’s efficiency
Improve Management reporting, maintaining capabilities.
Enhance Users satisfaction and productivity
3.SYSTEM DESIGN AND DEVELOPMENT
When the design input has been reviewed and the design input requirements are
determined to be acceptable, an iterative process of translating those requirements into a device
design begins. The first step is conversion of the requirements into system or high-level
specifications. Thus, these specifications are a design output. Upon verification that the high-
level specifications conform to the design input requirements, they become the design input for
the next step in the design process, and so on. 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.
Report design is very important concept in the computerized system, without reliable
output the user may feel the entire system is unnecessary and avoids using it. The proper output
design is important in any system and facilitates effective decision making.
The basic output considerations were as follows:
Simple and legible methods were used for output using standard display controls
All the output screens were informative and integrative in such a way the user can fulfill
his requirements
The output is verified as conforming to its input; and it then becomes the design input for another
step in the design process.
TYPES OF MODULES
FEES MANAGEMENT
Date Wise Collection, Date Wise Cash Collection, Date Wise Bank Collection, Date
Wise Class Wise Collection, Defaulter Notice, Date Wise Total Amount, Receipt Wise Details,
Refund Register, Head Wise Installment Wise Collection, Fees Summary, Summary, Student
Receipt, Student Wise Full Ledger, Transport Ledger Monthly Outstanding and the Annual
Register details.
STAFF AND PAYROLL MANAGEMENT
Staff details, Designation Wise, Single Employee Report, Pay Slip Reports, Salary
Statement, Head Printing Priority Setting, Salary Register, Old Month Reports
ATTENDANCE
Attendance section plays roles for student and employee. Student’s attendance details act
as a tool to identify irregularities in the academic interests of the students. The same can be used
to assess the student and give individual attention to the causes to repetitive or long absences.
This system is integrated with attendance gate fixed on school main entrance, which enable SMS
to parents about their ward.
4. SYSTEM TESTING AND IMPLEMENTATION
SYSTEM TESTING
Testing is a series of different tests that whose primary purpose is to fully exercise the
computer based system. Although each test has a different purpose, all work should verify that
all system element have been properly integrated and performed allocated function. Testing is
the process of checking whether the developed system works according to the actual requirement
and objectives of the system.
The philosophy behind testing is to find the errors. A good test is one that has a high
probability of finding an undiscovered error. A successful test is one that uncovers the
undiscovered error. Test cases are devised with this purpose in mind. A test case is a set of data
that the system will process as an input. However the data are created with the intent of
determining whether the system will process them correctly without any errors to produce the
required output.
Types of Testing
Unit testing
Integration testing
Validation testing
Output testing
User acceptance testing
UNIT TESTING
All modules were tested and individually as soon as they were completed and were
checked for their correct functionality. Unit testing conducted to verify the functional
performance of each modular component of the software. Unit testing on the smallest unit of the
software design (i.e.) the module. The white testing techniques were heavily employed for unit
testing. In this project first testing admin login it is have the sample inputs if admin username is
incorrect the admin cannot login if username is correct the admin is login, in this way all
modules testing one by one.
FUNCTIONAL TESTS
Functional test cases involved exercising the code with nominal input values for which
the expected result are known, as well as boundary values and special values, as logically inputs,
files of identical elements, and empty files. In this project testing the ranking module for
functionally work is correct. Three types of test in functional test Performance Test, Stress Test,
and Structure Test.
INTEGRATION TESTING
The entire project was split into small program; each of these single programs gives a
frame as an output. These programs were tested individually; at last all these programs where
combined together by creating another program where all these constructors were used. It give a
lot of problem by not functioning is an integrated manner.
The user interface testing is important since the user has to declare that the arrangements
made in frames are convenient and it is satisfied. When the frames where given for the test, the
end user gave suggestion. Based on their suggestions the frames where modified and put into
practice.
VALIDATION TESTING
At the culmination of the black box testing software is completely assembled as a
package. Interfacing errors have been uncovered and corrected and a final series of test i.e.,
Validation succeeds when the software function in a manner that can be reasonably accepted by
the customer.
OUTPUT TESTING
After performing the validation testing the next step is output testing of the proposed
system. Since the system cannot be useful if it does not produce the required output. Asking the
user about the format in which the system is required tests the output displayed or generated by
the system under consideration. Here the output format is considered in two ways. One is on
screen and another one is printed format.
The output format on the screen is found to be corrected as the format was designed in
the system phase according to the user needs. And for the hardcopy the output comes according
to the specifications requested by the user.
SYSTEM IMPLEMENTATION
When the initial design was done for the system, the client was consulted for the
acceptance of the design so that further proceedings of the system development can be carried
on. After the development of the system a demonstration was given to them about the working of
the system. The aim of the system illustration was to identify any malfunction of the system.
After the management of the system was approved the system implemented in the
concern, initially the system was run parallel with existing manual system. The system has been
tested with live data and has proved to be error free and user friendly.
Implementation is the process of converting a new or revised system design into an
operational one when the initial design was done by the system; a demonstration was given to the
end user about the working system.
This process is uses to verify and identify any logical mess working of the system by
feeding various combinations of test data. After the approval of the system by both end user and
management the system was implemented.
System implementation is made up of many activities. The major activities are as
follows.
Coding
Coding is the process of whereby the physical design specifications created by the analysis
team turned into working computer code by the programming team.
Testing
Once the coding process is begin and proceed in parallel, as each program module can
be tested.
Installation
Installation is the process during which the current system is replaced by the new system.
This includes conversion of existing data, software, and documentation and work procedures to
those consistent with the new system.
5.CONCLUSION
In recent years, School Management has moved away from being viewed as a school
administration tool and developed into an integrated Management Information System (MIS) for
managing school business processes and whole school improvement. It supports schools in
responding to The Children's Plan by enabling them to view a more rounded picture of a child;
BIBLIOGRAPHY
BOOKS
“visual basic 2010 unleashed” by Alessandro Del Sole, Foreword by Beth Massi.
“Moving to Microsoft Visual Studio 2010” by Patrice Pelland, Pascal Paré, and Ken
Haines
“Beginning T-SQL with Microsoft SQL Server 2005” by Paul Turley, Dan Wood
WEB SITES
1. www.w3schools.com/aspnet/
2 .www.dotnetwatch.com/
3. www.tutorialspoint.com/listtutorials/asp-dot-net/1
4. www.homeandlearn.co.uk/NET/vbNet.html
5. asp.net-tutorials.com/
6. www.dotnetperls.com/
APPENDICIES
B.TABLE STRUCTURE
LOGIN
STUDENT
STAFF
REPORTS
STUDENT ADMISSION DETAILS
STUDENT ATTENDANCE DETAILS
EXAM MARK DETAILS
STAFF DETAILS
STAFF SALARY DETAILS
STUDENT FEES DETAILS
E.SAMPLE OUTPUT
LOGIN
STUDENT
STAFF
REPORTS
STUDENT ADMISSION DETAILS
STUDENT ATTENDANCE DETAILS
EXAM MARK DETAILS
STAFF DETAILS
STAFF SALARY DETAILS
STUDENT FEES DETAILS
ADMISSION REPORT
STAFF REPORT
STAFF SALARY REPORT
FEES REPORT