Project Report

2. Introduction
CHAPTER 1

INTRODUCTION

The “HOSTEL MANAGEMENT SYSTEM” is software developed for managing various

activities in the hostel. Aim of Hostel Management System is to automate the Hostel
management process to ensure smooth functionality and reduced paperwork. Through this
application the admin can register & manage students & employees of the hostel.

1.1 What is the need of DBMS?

Database systems are basically developed for large amount of data. When dealing with
huge amount of data, there are two things that require optimization: Storage of data and
retrieval of data.

Storage: According to the principles of database systems, the data is stored in such a way
that it acquires lot less space as the redundant data (duplicate data) has been removed
before storage. Let’s take a layman example to understand this:In a banking system,
suppose a customer is having two accounts, one is saving account and another is salary
account. Let’s say bank stores saving account data at one place (these places are called
tables we will learn them later) and salary account data at another place, in that case if the
customer information such as customer name, address etc. are stored at both places then
this is just a wastage of storage (redundancy/ duplication of data), to organize the data in a
better way the information should be stored at one place and both the accounts should be
linked to that information somehow. The same thing we achieve in DBMS.

Fast Retrieval of data: Along with storing the data in an optimized and systematic manner, it
is also important that we retrieve the data quickly when needed. Database systems ensure
that the data is retrieved as quickly as possible.
⦁ The choice of a database product is often influenced by factors such as:

⦁ the computing platform (i.e., hardware, operating system)

⦁ the volume of data to be managed

⦁ the number of transactions required per second

⦁ existing applications or interfaces that an organization may have

⦁ support for heterogeneous and/or distributed computing

⦁ cost

⦁ vendor support

1.2 Design and Modeling:

The first task of a database designer is to produce a conceptual datamodel that reflects the
structure of the information to be held in the database. A common approach to this is to
develop an entity-relationship model, often with the aid of drawing tools. Another popular
approach is the Unified Modeling Language. A successful data model will accurately reflect
the possible state of the external world being modeled: for example, if people can have more
than one phone number, it will allow this information to be captured.

1.3 Objective

The main objective of this project is to create an interactive Hostel management software
which helps in the management of of Hostel records pertaining to registration of students
and employees, fee and salary management.

1.4 Problem Statement

The hostel management System is developed for automating the activities of hostel.
The software will be great relief to the employees. This software will help user in case of
reporting, registration and searching the information about residents and rooms. The aim of
the Hostel Management System is to carry out the activities of Hostel in an efficient way. It
will take the operations of Hostel to an upper level by providing faster access to data and
allowing addition, up gradation, modification, and deletion of data in a very systematic and
reliable manner.

1.5 Scope of the report

The essential framework of this report would be to elaborate the design of E.R-diagram,
schema Diagram. This project is a three-tier architecture application.

2.1 Problem Definition

CHAPTER 1

INTRODUCTION

The “HOSTEL MANAGEMENT SYSTEM” is software developed for managing various

activities in the hostel. Aim of Hostel Management System is to automate the Hostel
management process to ensure smooth functionality and reduced paperwork. Through this
application the admin can register & manage students & employees of the hostel.

1.1 What is the need of DBMS?

Database systems are basically developed for large amount of data. When dealing with
huge amount of data, there are two things that require optimization: Storage of data and
retrieval of data.
Storage: According to the principles of database systems, the data is stored in such a way
that it acquires lot less space as the redundant data (duplicate data) has been removed
before storage. Let’s take a layman example to understand this:In a banking system,
suppose a customer is having two accounts, one is saving account and another is salary
account. Let’s say bank stores saving account data at one place (these places are called
tables we will learn them later) and salary account data at another place, in that case if the
customer information such as customer name, address etc. are stored at both places then
this is just a wastage of storage (redundancy/ duplication of data), to organize the data in a
better way the information should be stored at one place and both the accounts should be
linked to that information somehow. The same thing we achieve in DBMS.

Fast Retrieval of data: Along with storing the data in an optimized and systematic manner, it
is also important that we retrieve the data quickly when needed. Database systems ensure
that the data is retrieved as quickly as possible.

⦁ The choice of a database product is often influenced by factors such as:

⦁ the computing platform (i.e., hardware, operating system)

⦁ the volume of data to be managed

⦁ the number of transactions required per second

⦁ existing applications or interfaces that an organization may have

⦁ support for heterogeneous and/or distributed computing

⦁ cost

⦁ vendor support

1.2 Design and Modeling:

The first task of a database designer is to produce a conceptual datamodel that reflects the
structure of the information to be held in the database. A common approach to this is to
develop an entity-relationship model, often with the aid of drawing tools. Another popular
approach is the Unified Modeling Language. A successful data model will accurately reflect
the possible state of the external world being modeled: for example, if people can have more
than one phone number, it will allow this information to be captured.
1.3 Objective

The main objective of this project is to create an interactive Hostel management software
which helps in the management of of Hostel records pertaining to registration of students
and employees, fee and salary management.

1.4 Problem Statement

The hostel management System is developed for automating the activities of hostel.
The software will be great relief to the employees. This software will help user in case of
reporting, registration and searching the information about residents and rooms. The aim of
the Hostel Management System is to carry out the activities of Hostel in an efficient way. It
will take the operations of Hostel to an upper level by providing faster access to data and
allowing addition, up gradation, modification, and deletion of data in a very systematic and
reliable manner.

1.5 Scope of the report

The essential framework of this report would be to elaborate the design of E.R-diagram,
schema Diagram. This project is a three-tier architecture application.

2.2 Need for the New System

CHAPTER 1
INTRODUCTION

The “HOSTEL MANAGEMENT SYSTEM” is software developed for managing various

activities in the hostel. Aim of Hostel Management System is to automate the Hostel
management process to ensure smooth functionality and reduced paperwork. Through this
application the admin can register & manage students & employees of the hostel.

1.1 What is the need of DBMS?

Database systems are basically developed for large amount of data. When dealing with
huge amount of data, there are two things that require optimization: Storage of data and
retrieval of data.

Storage: According to the principles of database systems, the data is stored in such a way
that it acquires lot less space as the redundant data (duplicate data) has been removed
before storage. Let’s take a layman example to understand this:In a banking system,
suppose a customer is having two accounts, one is saving account and another is salary
account. Let’s say bank stores saving account data at one place (these places are called
tables we will learn them later) and salary account data at another place, in that case if the
customer information such as customer name, address etc. are stored at both places then
this is just a wastage of storage (redundancy/ duplication of data), to organize the data in a
better way the information should be stored at one place and both the accounts should be
linked to that information somehow. The same thing we achieve in DBMS.

Fast Retrieval of data: Along with storing the data in an optimized and systematic manner, it
is also important that we retrieve the data quickly when needed. Database systems ensure
that the data is retrieved as quickly as possible.

⦁ The choice of a database product is often influenced by factors such as:

⦁ the computing platform (i.e., hardware, operating system)

⦁ the volume of data to be managed

⦁ the number of transactions required per second

⦁ existing applications or interfaces that an organization may have

⦁ support for heterogeneous and/or distributed computing

⦁ cost

⦁ vendor support

1.2 Design and Modeling:

The first task of a database designer is to produce a conceptual datamodel that reflects the
structure of the information to be held in the database. A common approach to this is to
develop an entity-relationship model, often with the aid of drawing tools. Another popular
approach is the Unified Modeling Language. A successful data model will accurately reflect
the possible state of the external world being modeled: for example, if people can have more
than one phone number, it will allow this information to be captured.

1.3 Objective

The main objective of this project is to create an interactive Hostel management software
which helps in the management of of Hostel records pertaining to registration of students
and employees, fee and salary management.

1.4 Problem Statement

The hostel management System is developed for automating the activities of hostel.
The software will be great relief to the employees. This software will help user in case of
reporting, registration and searching the information about residents and rooms. The aim of
the Hostel Management System is to carry out the activities of Hostel in an efficient way. It
will take the operations of Hostel to an upper level by providing faster access to data and
allowing addition, up gradation, modification, and deletion of data in a very systematic and
reliable manner.

1.5 Scope of the report

The essential framework of this report would be to elaborate the design of E.R-diagram,
schema Diagram. This project is a three-tier architecture application.
2.3 Project Scope
CHAPTER 1

INTRODUCTION

The “HOSTEL MANAGEMENT SYSTEM” is software developed for managing various

activities in the hostel. Aim of Hostel Management System is to automate the Hostel
management process to ensure smooth functionality and reduced paperwork. Through this
application the admin can register & manage students & employees of the hostel.

1.1 What is the need of DBMS?

Database systems are basically developed for large amount of data. When dealing with
huge amount of data, there are two things that require optimization: Storage of data and
retrieval of data.

Storage: According to the principles of database systems, the data is stored in such a way
that it acquires lot less space as the redundant data (duplicate data) has been removed
before storage. Let’s take a layman example to understand this:In a banking system,
suppose a customer is having two accounts, one is saving account and another is salary
account. Let’s say bank stores saving account data at one place (these places are called
tables we will learn them later) and salary account data at another place, in that case if the
customer information such as customer name, address etc. are stored at both places then
this is just a wastage of storage (redundancy/ duplication of data), to organize the data in a
better way the information should be stored at one place and both the accounts should be
linked to that information somehow. The same thing we achieve in DBMS.

Fast Retrieval of data: Along with storing the data in an optimized and systematic manner, it
is also important that we retrieve the data quickly when needed. Database systems ensure
that the data is retrieved as quickly as possible.

⦁ The choice of a database product is often influenced by factors such as:

⦁ the computing platform (i.e., hardware, operating system)

⦁ the volume of data to be managed

⦁ the number of transactions required per second

⦁ existing applications or interfaces that an organization may have

⦁ support for heterogeneous and/or distributed computing

⦁ cost

⦁ vendor support

1.2 Design and Modeling:

The first task of a database designer is to produce a conceptual datamodel that reflects the
structure of the information to be held in the database. A common approach to this is to
develop an entity-relationship model, often with the aid of drawing tools. Another popular
approach is the Unified Modeling Language. A successful data model will accurately reflect
the possible state of the external world being modeled: for example, if people can have more
than one phone number, it will allow this information to be captured.

1.3 Objective

The main objective of this project is to create an interactive Hostel management software
which helps in the management of of Hostel records pertaining to registration of students
and employees, fee and salary management.
1.4 Problem Statement

The hostel management System is developed for automating the activities of hostel.
The software will be great relief to the employees. This software will help user in case of
reporting, registration and searching the information about residents and rooms. The aim of
the Hostel Management System is to carry out the activities of Hostel in an efficient way. It
will take the operations of Hostel to an upper level by providing faster access to data and
allowing addition, up gradation, modification, and deletion of data in a very systematic and
reliable manner.

1.5 Scope of the report

The essential framework of this report would be to elaborate the design of E.R-diagram,
schema Diagram. This project is a three-tier architecture application.

2.4 Model Methodology

CHAPTER 1

INTRODUCTION

The “HOSTEL MANAGEMENT SYSTEM” is software developed for managing various

activities in the hostel. Aim of Hostel Management System is to automate the Hostel
management process to ensure smooth functionality and reduced paperwork. Through this
application the admin can register & manage students & employees of the hostel.
1.1 What is the need of DBMS?

Database systems are basically developed for large amount of data. When dealing with
huge amount of data, there are two things that require optimization: Storage of data and
retrieval of data.

Storage: According to the principles of database systems, the data is stored in such a way
that it acquires lot less space as the redundant data (duplicate data) has been removed
before storage. Let’s take a layman example to understand this:In a banking system,
suppose a customer is having two accounts, one is saving account and another is salary
account. Let’s say bank stores saving account data at one place (these places are called
tables we will learn them later) and salary account data at another place, in that case if the
customer information such as customer name, address etc. are stored at both places then
this is just a wastage of storage (redundancy/ duplication of data), to organize the data in a
better way the information should be stored at one place and both the accounts should be
linked to that information somehow. The same thing we achieve in DBMS.

Fast Retrieval of data: Along with storing the data in an optimized and systematic manner, it
is also important that we retrieve the data quickly when needed. Database systems ensure
that the data is retrieved as quickly as possible.

⦁ The choice of a database product is often influenced by factors such as:

⦁ the computing platform (i.e., hardware, operating system)

⦁ the volume of data to be managed

⦁ the number of transactions required per second

⦁ existing applications or interfaces that an organization may have

⦁ support for heterogeneous and/or distributed computing

⦁ cost

⦁ vendor support
1.2 Design and Modeling:

The first task of a database designer is to produce a conceptual datamodel that reflects the
structure of the information to be held in the database. A common approach to this is to
develop an entity-relationship model, often with the aid of drawing tools. Another popular
approach is the Unified Modeling Language. A successful data model will accurately reflect
the possible state of the external world being modeled: for example, if people can have more
than one phone number, it will allow this information to be captured.

1.3 Objective

The main objective of this project is to create an interactive Hostel management software
which helps in the management of of Hostel records pertaining to registration of students
and employees, fee and salary management.

1.4 Problem Statement

The hostel management System is developed for automating the activities of hostel.
The software will be great relief to the employees. This software will help user in case of
reporting, registration and searching the information about residents and rooms. The aim of
the Hostel Management System is to carry out the activities of Hostel in an efficient way. It
will take the operations of Hostel to an upper level by providing faster access to data and
allowing addition, up gradation, modification, and deletion of data in a very systematic and
reliable manner.

1.5 Scope of the report

The essential framework of this report would be to elaborate the design of E.R-diagram,
schema Diagram. This project is a three-tier architecture application.
3. Objective
CHAPTER: 3

ER DIAGRAM, SCHEMA DIAGRAM

This chapter of the report describes the structure of the project, followed by Entity
Relationship Diagram, Schema Diagram and the table structures.

3.1 ER Diagram with relationships and cardinality ratio

An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical

representation of entities and their relationships to each other, typically used in computing
in regard to the organization of data within databases or information systems. An entity is a
piece of data-an object or concept about which data is stored.

The cardinality or fundamental principle of one data aspect with respect to another is a
critical feature. The relationship of one to the other must be precise and exact between each
other in order to explain how each aspect links together. In simple words Cardinality is a
way to define the relationship between two entities.

The following are the notations of the ER diagram:

ER Diagram Hostel Management System

3.2 Schema Diagram

In any data model it is important to distinguish between the description of the database and
the database itself. The description of a database is called the database schema, which is
specified during database design and is not expected to change frequently.

A displayed schema is called a schema diagram. A schema diagram displays only some
aspects of a schema, such as the names of record types and data items, and some types of
constraints.

ADMIN

STUDENT

FEE

EMPLOYEE

SALARY

UPDATELOG

4. Research Methodology
CHAPTER: 4

IMPLEMENTATIONS

This chapter of the report describes the Functions, packages and API used in the project.

MySQL:

MySQL is an open-source relational database management system. It was originally

produced under the GNU General Public License, in which source code is made freely
available. MySQL is very popular for Web-hosting applications because of its plethora of
Web-optimized features like HTML data types, and because it's available for free. It is part of
the Linux, Apache, MySQL, PHP (LAMP) architecture, a combination of platforms that is
frequently used to deliver and support advanced Web applications. MySQL runs the back-
end databases of some famous websites, including Wikipedia, Google and Facebook- a
testament to its stability and robustness despite its decentralized, free-for-all philosophy.

SWING:

Swing is a GUI widget toolkit for Java. It is part of Oracle's Java Foundation Classes –
an API for providing a graphical user interface for Java programs. Swing was developed to
provide a more sophisticated set of GUI components than the earlier Abstract Window
Toolkit.Swing provides a look and feel that emulates the look and feel of several platforms,
and also supports a pluggable look and feel that allows applications to have a look and feel
unrelated to the underlying platform. It has more powerful and flexible components than
AWT. In addition to familiar components such as buttons, check boxes and labels, Swing
provides several advanced components such as tabbed panel, scroll panes, trees, tables, and
lists.

Java Database Connectivity (JDBC):

It is an application programming interface (API) for the programming language Java, which
defines how a client may access a database. It is a Java-based data access technology used
for Java database connectivity. It is part of the Java Standard Edition platform, from Oracle
Corporation. It provides methods to query and update data in a database, and is oriented
towards relational databases. A JDBC-to-ODBC bridge enables connections to any ODBC-
accessible data source in the Java virtual machine (JVM) host environment.

4.2 Functional Modules

The functional modules included in the project are listed below.

Insert Module:

This module provides the functionality of collecting the required data from the designed
interface and transmitting it to the appropriate table present in the database designed for
this project. If the provided data does not satisfy the given constraints, it must refrain from
storing it into the database.

Update Module:

This module again has the functionality of collecting the data from the designed interface,
but it updates the already existing tuple that matches the provided primary key of the tuple
to be updated, by replacing the existing attribute values with the newly collected data.
Again, if the newly provided data does not satisfy the given constraints, it must refrain from
updating the corresponding tuple.

Delete Module:

The delete counterpart is loaded with the ability to delete a single or multiple records from
the table. It searches for the tuple, in the query specified table, based on the provided value
for an attribute. Admin can delete in the interface, based on which delete module searches
for the record corresponding to that provided attribute value and deletes the record.

Retrieve Module:

The retrieve module has a basic functionality of accessing the entire specified table from the
database and displays it.

5. System Design
CHAPTER 5

MODULES IN HOSTEL MANAGEMENT SYSTEM

Admin:
 Admin can login to the software using the Username and password provided by the
developers. After login he can register students and employees. He has to update the data of
all the participants of the system i.e., Students and employees. He can Insert, update and as
well as delete records from the system.

Student:

This module is pertaining to the residents of the hostel. It holds the data of the
students residing in the hostel eg. Name,Address,USN,RoomNo & Phone. The complete
information of a particular student can be obtained from referring to this module.

FEE Payment (Insert):

This module is necessary to hold the information related to the Fees of the residents of
the hostel. It has fields for Name,total fees, amount paid,mode of payment and balance
amount remaining to be paid by every individual student. The individual student details can
be accessed by providing unique USN.

Employee:

This module is related to the employees of the hostel. It holds the data of the
employees like Name, Age, Eid, Designation & Salary. The complete information of a
particular employee can be obtained by the unique employee ID.

Salary Payment(Insert & Update):

This module is necessary to hold the information related to the salary of the
employees of the hostel. It has fields for Name,Eid,total salary, amount paid and balance
amount remaining to be paid for every individual employee. The individual employee
details can be accessed by providing unique Eid.

Update Log:

This is a special module that triggers when update operation is initiated. The Data
updated and the time.

Triggers:
Triggers are mainly applied on the table which will executed automatically when insertion,
deletion or update is done on the database.

In our project we have applied trigger on the student table, which inserts the time and date
of any update to the student details

Stored procedure:

Stored procedure is mainly applied on the database, where procedure will execute as soon
as we call in the program.

In our project the stored procedure is applied on the register table to retrieve the data.

5.1 Snapshots
APPENDIX A

SNAPSHOTS

Snapshot 1: Login Page of the project

Snapshot 2: Features page of the project

Snapshot 3: Registration page for new Students

Snapshot 4: Employee registration page

Snapshot 5: Options for employee management

Snapshot 6: Fee update and fetch page

Snapshot 7: Fetch fee details of individual students

Snapshot 8: Maintain student records of the system.

Snapshot 9: Update fee details of specific student.

6. Analysis
CHAPTER 6

CONCLUSION

The project is based on the requirement specification of the user and the analysis of the
existing system, with flexibility for future enhancement. The expanded functionality of
today’s software requires an appropriate approach towards software development. This
hostel management software is designed for people who want to manage various activities
in the hostel. For the past few years the numbers of educational institutions are increasing
rapidly. Thereby the numbers of hostels are also increasing for the accommodation of the
students studying in this institution. And hence there is a lot of strain on the person who are
running the hostel and software’s are not usually used in this context. This particular
project deals with the problems on managing a hostel and avoids the problems which occur
when carried manually. Identification of the drawbacks of the existing system leads to the
designing of computerized system that will be compatible to the existing system with the
system which is more user friendly and more GUI oriented.

SCOPE OF ENHANCEMENT

There are also few features which can be integrated with the system to make it more
flexible.

Below list shows the future points to be considered.

Budget manager: We can include the facility in this system that will help to manage the
budget and calculate profit/Loss of the organisation.

Resident attendance: The attendance of resident will be marked each time the resident
enters or leaves the hostel premises.

Accounting Details: All the other accounting details can be maintained in addition to the fee
detail. The software can be automatically read and update the online fee payments.

6.1 Software Requirement

CHAPTER 6

CONCLUSION

The project is based on the requirement specification of the user and the analysis of the
existing system, with flexibility for future enhancement. The expanded functionality of
today’s software requires an appropriate approach towards software development. This
hostel management software is designed for people who want to manage various activities
in the hostel. For the past few years the numbers of educational institutions are increasing
rapidly. Thereby the numbers of hostels are also increasing for the accommodation of the
students studying in this institution. And hence there is a lot of strain on the person who are
running the hostel and software’s are not usually used in this context. This particular
project deals with the problems on managing a hostel and avoids the problems which occur
when carried manually. Identification of the drawbacks of the existing system leads to the
designing of computerized system that will be compatible to the existing system with the
system which is more user friendly and more GUI oriented.

SCOPE OF ENHANCEMENT

There are also few features which can be integrated with the system to make it more
flexible.

Below list shows the future points to be considered.

Budget manager: We can include the facility in this system that will help to manage the
budget and calculate profit/Loss of the organisation.

Resident attendance: The attendance of resident will be marked each time the resident
enters or leaves the hostel premises.

Accounting Details: All the other accounting details can be maintained in addition to the fee
detail. The software can be automatically read and update the online fee payments.

6.2 Hardware Requirement

CHAPTER 6

CONCLUSION

The project is based on the requirement specification of the user and the analysis of the
existing system, with flexibility for future enhancement. The expanded functionality of
today’s software requires an appropriate approach towards software development. This
hostel management software is designed for people who want to manage various activities
in the hostel. For the past few years the numbers of educational institutions are increasing
rapidly. Thereby the numbers of hostels are also increasing for the accommodation of the
students studying in this institution. And hence there is a lot of strain on the person who are
running the hostel and software’s are not usually used in this context. This particular
project deals with the problems on managing a hostel and avoids the problems which occur
when carried manually. Identification of the drawbacks of the existing system leads to the
designing of computerized system that will be compatible to the existing system with the
system which is more user friendly and more GUI oriented.

SCOPE OF ENHANCEMENT

There are also few features which can be integrated with the system to make it more
flexible.

Below list shows the future points to be considered.

Budget manager: We can include the facility in this system that will help to manage the
budget and calculate profit/Loss of the organisation.

Resident attendance: The attendance of resident will be marked each time the resident
enters or leaves the hostel premises.

Accounting Details: All the other accounting details can be maintained in addition to the fee
detail. The software can be automatically read and update the online fee payments.

7. Challenges and Limitations

CHAPTER 2

System and software requirements and specifications

2.1 FUNCTIONAL REQUIREMENTS

A description of the facility or feature required. Functional requirements deal with what the
system should do or provide for users. They include description of the required functions,
outlines of associated reports or online queries, and details of data to be held in the system.

2.1.1 Interface Requirements:

The system shall provide an option for new student and employee Registration.

The system should give option for admin login.

The system shall provide facility to calculate fees and balance.

The system shall provide an interface to track salaries

2.2 NON FUNCTIONAL REQUIREMENTS:

Non-functional requirements define the overall qualities or attributes of the resulting

system.
2.2.1 Usability

Usability is the ease with which a user can learn to operate and register
students/employees, get instant info about a particular student/employee or room.

2.2.2 Security

Security requirements are included in a system to ensure

Enquiries from the end users as well as from any organization are highly secured.

2.2.3 Reliability

Reliability is the ability of a system to perform its required functions under stated
conditions for a specific period of time. Constraints on the run-time behavior of the system
can be considered fewer than two separate headings

Availability: is the system available for service when requested by end-users.

Failure rate: how often does the system fail to deliver the service as expected by end-users.

2.2.4. Efficiency

The comparison of what is actually produced or performed with what can be achieved with
the same consumption of Clouds (money, time, labor, etc.). It is an important Factor in

determination of productivity.

2.3 Software Requirements

Programming language : Java.

Operating system : ANY OS (Recommended: Windows8, Windows Vista, Windows
XP)

Application required : Any IDE, Xampp

2.4 Hardware Requirements

C.P.U : Pentium IV 2.4 GHz or above

Memory (Primary) : 512 MB, 1 GB or above

Hard Disk : 40 GB, 80GB, 160GB or above

Monitor : 15 VGA color

8. Conclusion
CHAPTER 2

System and software requirements and specifications

2.1 FUNCTIONAL REQUIREMENTS

A description of the facility or feature required. Functional requirements deal with what the
system should do or provide for users. They include description of the required functions,
outlines of associated reports or online queries, and details of data to be held in the system.

2.1.1 Interface Requirements:

The system shall provide an option for new student and employee Registration.

The system should give option for admin login.

The system shall provide facility to calculate fees and balance.

The system shall provide an interface to track salaries

2.2 NON FUNCTIONAL REQUIREMENTS:

Non-functional requirements define the overall qualities or attributes of the resulting

system.

2.2.1 Usability

Usability is the ease with which a user can learn to operate and register
students/employees, get instant info about a particular student/employee or room.

2.2.2 Security

Security requirements are included in a system to ensure

Enquiries from the end users as well as from any organization are highly secured.

2.2.3 Reliability

Reliability is the ability of a system to perform its required functions under stated
conditions for a specific period of time. Constraints on the run-time behavior of the system
can be considered fewer than two separate headings

Availability: is the system available for service when requested by end-users.

Failure rate: how often does the system fail to deliver the service as expected by end-users.

2.2.4. Efficiency

The comparison of what is actually produced or performed with what can be achieved with
the same consumption of Clouds (money, time, labor, etc.). It is an important Factor in

determination of productivity.
2.3 Software Requirements

Programming language : Java.

Operating system : ANY OS (Recommended: Windows8, Windows Vista, Windows

XP)

Application required : Any IDE, Xampp

2.4 Hardware Requirements

C.P.U : Pentium IV 2.4 GHz or above

Memory (Primary) : 512 MB, 1 GB or above

Hard Disk : 40 GB, 80GB, 160GB or above

Monitor : 15 VGA color

9. Future Scope
CHAPTER 2

System and software requirements and specifications

2.1 FUNCTIONAL REQUIREMENTS

A description of the facility or feature required. Functional requirements deal with what the
system should do or provide for users. They include description of the required functions,
outlines of associated reports or online queries, and details of data to be held in the system.

2.1.1 Interface Requirements:

The system shall provide an option for new student and employee Registration.

The system should give option for admin login.

The system shall provide facility to calculate fees and balance.

The system shall provide an interface to track salaries

2.2 NON FUNCTIONAL REQUIREMENTS:

Non-functional requirements define the overall qualities or attributes of the resulting

system.

2.2.1 Usability

Usability is the ease with which a user can learn to operate and register
students/employees, get instant info about a particular student/employee or room.

2.2.2 Security

Security requirements are included in a system to ensure

Enquiries from the end users as well as from any organization are highly secured.

2.2.3 Reliability

Reliability is the ability of a system to perform its required functions under stated
conditions for a specific period of time. Constraints on the run-time behavior of the system
can be considered fewer than two separate headings

Availability: is the system available for service when requested by end-users.

Failure rate: how often does the system fail to deliver the service as expected by end-users.

2.2.4. Efficiency

The comparison of what is actually produced or performed with what can be achieved with
the same consumption of Clouds (money, time, labor, etc.). It is an important Factor in

determination of productivity.
2.3 Software Requirements

Programming language : Java.

Operating system : ANY OS (Recommended: Windows8, Windows Vista, Windows

XP)

Application required : Any IDE, Xampp

2.4 Hardware Requirements

C.P.U : Pentium IV 2.4 GHz or above

Memory (Primary) : 512 MB, 1 GB or above

Hard Disk : 40 GB, 80GB, 160GB or above

Monitor : 15 VGA color

10. Reference

BIBLIOGRAPHY

BOOK REFERENCE

[1] Database System Models, Languages, RamezElmasri and Sham Kant B.Navathe, 7th
Edition, 2017 Pearson.

[2] Java: The Complete Reference, Eleventh Edition (Complete Reference Series) 11th
Edition by Herbert Schildt

[3]Uttam K Roy, Advanced JAVA programming, Oxford University press, 2015.

[4] Silberschatz Korth and Sudharshan, Database System Concepts, 6th Edition, Mc-
GrawHill-2013

WEBSITES

[1]

[2] (Trigger and Stored Procedure)

[3] (Images and Icons)

[4]

[5]