Advance School Management

System

Dissertation Submitted in Partial fulfilment of the

Requirement for the Award of the Degree of

Bachelor Of Computer Application

Semester V

Aug-Dec, 2021

Under The Guidance of Submitted By

Mr. Pankaj Jagtap Gitali Bhawasar 1911218
Shweta Singh 1911247
Vidushi Chaubey 1911252

School of Computer Science & IT

Devi Ahilya Vishwavidyalaya, Indore, M.P.2022

1
 School of Computer Science & IT
Devi Ahilya Vishwavidyalaya, Indore, M.P.2022
.

DECLARATION

I hereby declare that the project titled “Advance School Management System”
submitted by me for the partial fulfilment of the requirement for the award of
Bachelor of Computer Applications to School of Computer Science & IT, Devi
Ahilya Vishwavidyalaya, Indore, comprises my own work and due
acknowledgement has been made in text to all other material used.

Signature of Student:
Date:
Place:

2
 School of Computer Science & IT
Devi Ahilya Vishwavidyalaya, Indore, M.P.

CERTIFICATE FROM GUIDE

It is to certify that dissertation on “Advance School Management System”,

submitted by Miss. Gitali Bhawasar, Miss. Shweta Singh, Miss. Vidushi
Chaubey to the School of Computer Science & IT, DAVV, Indore has been
completed under my supervision and the work is carried out and presented in a
manner required for its acceptance in partial fulfilment for the award of the
degree of Bachelor of Computer Applications.

Project Guide
Signature:

Name:
Date:

3
 School of Computer Science & IT
Devi Ahilya Vishwavidyalaya, Indore, M.P.

CERTIFICATE

It is to certify that we have examined the dissertation on “Advance School

Management System”, submitted by Miss Gitali Bhawasar, Miss Shweta Singh,
Miss Vidushi Chaubey to the School of Computer Science & IT, DAVV, Indore
and hereby accord our approval of it as a study carried out and presented in a
manner required for its acceptance in partial fulfilment for the award of the
degree of Bachelor of Computer Applications.

Internal Examiner External Examiner

Signature: Signature:

Name : Name :

Date : Date :

4
 ACKNOWLEDGEMENT

The Group Members are grateful to our respectable teacher Mr. Pankaj Jagtap.
Whose insightful leadership and knowledge benefited. The Group Members to
steer out this project successfully. Thank you for your continuing support for
our important work in this field! We would also like to underscore dynamic
efforts of teamwork and their expert advice and contributions to the preparation
of this report.

Date -16/12/2021 Group Members-

Gitali Bhawasar
Shweta Singh
Vidushi Chaubey

5
 TABLE OF CONTENTS

1. Table of Figures Page Number

2. Abstract 7
3. Chapter 1: Introduction 8
1.1 Title of project 8
1.2 Introduction of project 8
1.3 Aim 8
1.4 Objective 8
1.5 Scope 8
4. Chapter 2: Requirement Analysis 9
2.1 Introduction 9
2.2 Functional and Non-Functional Requirements 9
5. Chapter 3: System Analysis 10
3.1 Introduction 10
3.2 Software Requirements 10
3.3 Hardware Requirements 10
3.4 Feasibility Analysis 10-11
6. Chapter 4 : System Design 12-16
4.1 Introduction 12
4.2 Data Flow Diagram 12-14
4.3 Entity-Relationship Diagram(E-R Diagram) 14-16
7. Chapter 5: Output Forms 17-23
8. Chapter 6: Data Dictionary 24-25
9. Chapter 7: System Design 26
10. Chapter 8: Conclusion 27

6
 Abstract

This system is designed to complete the digital management of students’ result files in middle
schools’ daily education work. The system focuses on conforming the business process to the
operation, and strives for comprehensiveness and versatility, making the system not only
applies to one education organisation. The combined method of life cycle approach and
prototyping are adopted on the choice of development methods, which follows four phases,
including research, analysis, design and implementation of the system to carry on the design.
And in the detailed design, evolutionary prototyping is adopted. With the deepening
understanding in the using, a fresh analysis, design and implementation of one part or several
parts will be processed. Finally through the test, this system has reached the design
requirements of various functions, and achieved the expected design goal.

7
 Chapter 1
Introduction

1.1 Title Of Project : Advance School Management System

1.2 Aim :
Aim of this system is to create an advanced school management system.

1.3 Introduction of project :

Student information management system is an indispensable part of education. A functional,
simple and easy information and performance management system can not only effectively
reduce the workload of the related work personnel, but its content is very important to
decision makers and managers in schools. Over the recent years, the performance and
efficiency of the education industry have been enhanced by using the Student Management
System. This tool has productively taken over the workload of the admin department with its
well-organised, easy, and reliable online school management software.

1.4 Objective :
● Well-organised Management and Organisation of Programs.
● Helps to maintain the record of All Students.
● Can be accessed by all Parents.
● Reduction of Human Labour, Papers, and Workload.
● Reduce time consumption.
● Interviewing new recruits and error scope.
● The project is totally built at the administrative end and thus only the administrator is
guaranteed access.

1.5 Scope :
Even if schools in India were hesitant to use educational technology, they are slowly and
steadily accepting school management systems for all the benefits that it offers them.
In the future, as the need to adopt technological solutions for education increases, more
schools will integrate a school management system for completing their daily tasks at the
school.

8
 Chapter 2
Requirement Analysis

2.1 Introduction:
Requirements Analysis is the process of understanding the customer needs and Expectations
from a proposed system or application and is a well-defined stage in the Software
Development Life Cycle model. Requirements are a description of how a system should
behave or a description of system properties or attributes. It can alternatively be a statement
of what an application is expected to do.
The Software Requirements Analysis Process covers the complex task of eliciting and
Documenting the requirements of all these users, modelling and analysing the requirements
and documenting them as a basis for system design. Requirement analysis is a software
engineering method that bridges the gap between system requirements and engineering
software design. Requirement allows the software engineer or analyst to refine the software
allocation and build the model of data functional behaviour domains that will be treated by
software.

2.2 Functional Requirements:

The functional requirements describe the interaction between the system and its environment
1. Register new students.
2. Record the attendance of students.
3. Record the internal marks of students.
4. Record the fees details of students.
5. Register a new teacher/employee.
6. Register a new user for the system.

2.3 Non Functional Requirements:

It describes a restriction on the system that limits our choice for developing a solution to a
problem. The non-functional requirements in our project are :
1. The system should be designed as a secured system applying security Measures.
2. Special exception handling mechanism should be in place to avoid system errors.
3. Should be capable of giving access to concurrent users without degrading the system
performance and accept answers.

9
 Chapter 3
System Analysis

3.1 Introduction :
System Analysis is a detailed study of the various operations performed by a system and their
relationship within and outside the system .It is a systematic technique that defines goals and
objectives. The goal of the development is to deliver the system in line with the user’s
requirements, and analysis is this process.
System study has been conducted with the following
(1) objectives in mind: -
(2) Identify the client’s needs.
(3) Evaluate the system concept for feasibility.
(4) Perform economical and technical analysis.

3.2 Software Requirement :

1. OS : Windows 7
2. IDE: NetBeans or Eclipse
3. DBMS: Ms Access
4. Programming Language : Java(Swing)

3.3 Hardware Requirement :

1. RAM : 1GB (Minimum)
2. Processor : i3 processor
3. System bus : 32-bit, 64-bit

3.4 Feasibility Study:

Feasibility study is the process of determination of whether or not a project is worth doing.
Feasibility studies are undertaken within tight time constraints and normally culminate in a
written and oral feasibility report. I have taken two weeks in a feasibility study with my co-
developer. The following is the process diagram for feasibility analysis. In the diagram, the
feasibility analysis starts with the user set of requirements. With this, the existing system is
also observed. The next step is to check for the deficiencies in the existing system. By
evaluating the above points a fresh idea is conceived to define and quantify the required goals.
The user consent is very important for the
new plan. Along with, for implementing the new system, the ability of the organisation is also
checked. Besides that, a set of alternatives and their feasibility is also considered in case of
any failure in the proposed system. Thus, feasibility study is an important part in software
development. After doing the project Online Examination System, study and analyse all the

10
existing or required functionalities of the system, the next task is to do the feasibility study
for the project. All projects are feasible given unlimited resources and Infinite time.
Feasibility study includes consideration of all the possible ways to provide a solution to the
given problem. The proposed solution should satisfy all the user requirements and should be
flexible enough so that future changes can be easily done based on the future upcoming
requirements.

A. Economical Feasibility
Economic justification is generally the “Bottom Line” consideration for most systems.
Economic Justification includes a broad range of concerns that includes cost benefit analysis.

B. Technical Feasibility
This system is a small student information and performance management system, which
needs a small amount of resources. School computers can meet the conditions both in
hardware and software.

11
 Chapter 4
System Design

4.1 Introduction:
The objective of the system design is to deliver the requirements as specified in the feasibility
report. System design involves first logical design (logical design) and then physical
construction (detailed design) of the system. The logical design describes the structure and
characteristics of features, such as the outputs, inputs, files, databases, and procedures. The
physical construction produces actual program software, files, and a working system.
System design goes through two phases of development: -

1. Logical Design
2. Physical Design

4.2 Data Flow Diagram(DFD)

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modelling its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be used for
the visualisation of data processing (structured design). A DFD shows what kinds of data will
be input to and output from the system, where the data will come from and go to, and where
the data will be stored. It does not show information about the timing of processes, or
information about whether processes will operate in sequence or in parallel (which is shown
on a flowchart). Data flow diagrams can be used in both Analysis and Design phases of
SDLC.
A data flow diagram (DFD) is a significant modelling technique for analysing and
constructing information processes. DFD literally means an illustration that explains the
course or movement of information in a process. DFD illustrates this flow of information in a
process based on the inputs and outputs.

Level 0 DFD

12
Level 1 DFD

Level 2 DFD
For Students

13
 For Teachers

4.3 Entity-Relationship Diagram :

An entity-relationship (ER) diagram is a specialised graphic that illustrates the
relationships between entities in a database. ER diagrams often use symbols to
represent three different types of information. Boxes are commonly used to
represent entities. Diamonds are normally used to represent relationships and
ovals are used to represent attributes.
A database can be modelled as:
➔ A collection of entities,
➔ Relationship among entities.
➔ An entity is an object that exists and is distinguishable from other Objects.
➔ Entities have attributes
➔ Example: people have names and addresses
➔ An entity set is a set of entities of the same type that share the same
Properties.
➔ Example: set of all persons, companies, trees, holidays.

Entity Relationship Diagram Notations:

Peter Chen developed ERDs in 1976. Since then Charles Bachman and James
Martin have added some slight refinements to the basic ERD principles.

1. Entity :
An entity is an object or concept about which you want to store information.

14
2. Weak Entity :
A weak entity is an entity that must be defined by a foreign key relationship
with another entity as it cannot be uniquely identified by its own attributes alone.

3. Key attribute :
A key attribute is the unique, distinguishing characteristic of the entity. For
Example, an employee's social security number might be the employee's key
attribute.

4. Multivalued attribute :
Multivalued attribute A multivalued attribute can have more than one value. For
Example, an employee entity can have multiple skill values.

5. Derived attribute :
A derived attribute is based on another attribute. For Example, an employee's
monthly salary is based on the employee's annual salary.

6. Relationships :
Relationships illustrate how two entities share information in the database
structure.
7. Cardinality :
Cardinality specifies how many instances of an entity relate to one instance of
another entity. Ordinarily is also closely linked to cardinality. While cardinality
specifies the occurrences of a relationship, ordinality describes the relationship
as either mandatory or optional. In other words, cardinality specifies the
maximum number of relationships and ordinality specifies the absolute
minimum number of relationships.

8. Recursive relationship :
In some cases, entities can be self-linked. For Example, employees can
supervise other employees.

15
16
 Chapter 5
Implementation
1. Main Page

17
2. Apply Page
For Students

For Teachers

18
3. Instructions Page
Student Instruction Page

Teacher Instruction Page

19
4. Test Page
Student Test Page

Teacher Test Page

20
5. Score Page

6. Signup Page

Student signup Page

21
Teacher Signup Page

22
7. Congratulation Page

23
 Chapter 6
Database Design

6.1 Data Dictionary

Usually, a collection of interrelated data is referred to as a database.
The database contains information about one particular enterprise.
Database systems are designed to shear and manage large volumes of
information .The management of data involves both the manipulation
of information. In addition ,the database system must provide for
safety information storage in the database ,despite system crashes or
unauthorised access

24
25
 Chapter 7
System Testing

System Testing
Testing is the penultimate step of software development. An elaborate testing of data is
prepared and the system is using test data. While doing testing, errors are noted and
corrections are made. The users are trained to operate the developed system. Both hardware
and software securities are made to run the developed system successfully. System testing is
aimed at ensuring the system works accurately before live operation commences. Testing is
vital to the system. System testing makes a logical assumption that if all parts of the system
are correct, the goal will be successfully achieved. The candidate system is subjected to a
variety of tests: Online Response, Volume, Stress Recovery & Security and Usable tests. A
series of testing are performed for the proposed system before the system is ready for user
acceptance testing. Nothing is complete without testing, as it is vital to the success of the
system. The entire testing process can be divided into 3 phases 1 Unit Testing Integration
Testing Final/ System testing

7.1. Unit Testing

Unit testing focuses verification effort on the smallest unit of software designing the module.
To check whether each module in the software works properly so that it gives desired outputs
to the given inputs. All Validations and conditions are tested at the module level in the unit
test. Control paths are tested to ensure the information properly flows into, and out of the
program unit and out of the program unit under test. Boundary condition is tested to ensure
that the modules operate at boundaries. All independent paths through the control structure
ensure that all statements in a module have been executed at- least once.
7.2. Black Box Testing
This testing method focuses on the functional requirements of the software. It attempts to find
out the error of the following categories such as incorrect and missing functions, interface
error, error in data structure, performance error and initialization and termination errors.

7.3. White Box Testing

This testing method is also called path testing. It is a test case design method that uses the
control structure of the procedural design to drive the test case. In this system, Unit testing
has been successfully handled. The test data was given to each and every module in all
respects and got the desired output. Each module has been tested and found working properly.

26
 Chapter 8
Conclusion

The development of the system is based on deep study of school management and related
issues. This system is designed after a comprehensive investigation and analysis, and
integrates professional theory knowledge and computer skills. After a series of application
processes of requirements analysis, database design, system design, system implementation
and system test, the design has basically completed the requirement of graduation design.

27