Mini Project-2014

CHAPTER 1

INTRODUCTION
1.1. PROJECT OVERVIEW
The Project Title as Hostel Management System is an application that provides
facility to make the management of hostel in an easy manner. The hostel management
system is developed in favour of the students about their rooms and other details. This
System includes three user admin, warden and student. The admin can add warden and can
see the warden details and student details. The warden manages the students and room
details. The student can enter their complaints, sign in/ out, visitors in the system.
1.2. OBJECTIVE
The project aims to develop a reusable and maintainable storage of data in the
canteen . This project aims at:

Storage of data in a system in a more accessible manner.

Placing order and billing becomes easier.

Helps to calculate Income

The administration on appointing the staff becomes easy.

Dept.of Information Technology

page 1

Mini Project-2014

CHAPTER 2
SYSTEM ANALYSIS
2.1. EXISTING SYSTEM
In the existing system, accessibility of data become hilarious when data to be stored
exceeds the data storage limit. Users cannot handle such huge amount of data, which will
cause errors and certain other factors of time. It becomes completely difficult to manage and
its unmaintainable. The availability and usability of data are not secured in this system.
2.1.1. Drawbacks
Some drawbacks for manual system

Time consumption

Error factor

Bulk volume of data cannot be handled

Accessibilty

Security factor

2.2. PROPOSED SYSTEM

In this project all disadvantages of the existing system can be removed. Our system
can be guarantee security to the data as well as user information .All the particulars
regarding the members of a group are kept private. Since the proposed system is
maintainable error correction becomes easy.
Our system has following features:2.2.1 Advantages

Cost effective solution

Possibility of upgrading

Easy of usage

High speed& accuracy

Enhanced security

Maintainability

Dept.of Information Technology

page 2

Mini Project-2014

2.3. FEASIBILITY STUDY

Feasibility study is a test of a system proposal, according to its workability, impact on
the organization, ability to meet the user needs and effective use of resources. Thus when a
new application is proposed, it normally goes through a feasibility study before it goes for
development. The main objective of feasibility study is not solving the problem but not to
acquire a sense of its scope. During the study, the problem definition is crystallized and
aspects of the problem to be included in the system are determined. Every project is feasible,
given unlimited resources and infinite time. It is both necessary and prudent to evaluate the
project at the earliest possible time. So a detailed study is carried out to check the
workability of the system.
The result of feasibility is a formal proposal. This is simply a document detailing the
nature and scope of the proposed solution. The proposal summarizes what is known and
what is going to be done.
The three important test for feasibility are

Operational feasibility

Technical feasibility

Economic feasibility

2.3.1. Economical Feasibility

Economical analysis system is the most frequently used method for evaluating the
effectiveness of the candidate system. It is more commonly known as cost/benefit and
saving that are expected from the candidate system and compare them with costs. It benefits
outweigh costs; the decision is made to design and implement the system. Otherwise, further
justification or alteration in the proposed system will have to be made if it is having a chance
of being approved.

Dept.of Information Technology

page 3

Mini Project-2014

2.3.2. Operational Feasibility

Proposed projects are beneficial only if they can be turned into information system
that will meet the operating requirements of the organization. This test of feasibility asks if
the system will work when it is developed and installed. Some of the important questions
that are useful to test the operational feasibility of a project can be given below:

Is there sufficient support for the project from the management? From users? If the
present system is well liked and used to extent that the persons will not able to see
reasons for a change, there may be resistance.

Are current business methods acceptable to the users? If they are not? Users may
welcome a change that will bring about a more operational and useful system.

Are the users been involved in the planning and development of the project? If
they are involved at the earlier stage of the project developed, the changes of
resistance can be possibly reduced.

Issues that appear to be quite minor at the earlier stage can grow into major
problems after implementation. Therefore, it is always advisable to consider
operational aspects carefully.

2.3.3. Technical Feasibility

The assessment of technical feasibility must be based on outline design of system
requirements of input, outputs, files, programs, procedures and staff. This can be quantified
in terms of volumes of data , trends, frequency of updating , etc. having identified an outline
system , the investigator must go on to suggest the type of equipment required , methods of
developing the system, and methods of running the system.
With regard to the processing facilities, the feasibility study will need to consider the
possibility of using a bureau or , if in-house equipment is available the nature of the
hardware to be used for data collection ,storage output and processing . On this system
development side , the feasibility study must consider the various ways of acquiring the
system .
These include the purchase of the package the use of consultancy organization or software
house to design the system and write the programs. Thereare a numberof technical issues,

Dept.of Information Technology

page 4

Mini Project-2014

which are generally raised during the feasibility stage of the investigation .they are as
follows:

Does the necessary technology exists to do what is suggested (and can it be

acquired)?

Does the proposed equipment have the technical capacity to hold the data required
to use the new system?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and security?

Dept.of Information Technology

page 5

Mini Project-2014

CHAPTER 3
SYSTEM SPECIFICATION
Hardware and software requirements for the installation and smooth functioning of this
product could be configured based on the requirements needed by the component of the
operating environment that works as front-end system here we suggest minimum
configuration for the both hardware and software components.
Working off with this software is requirements concrete on system environments. It
includes three phases.

Hardware Requirements

Software Requirements

3.1. HARDWARE REQUIREMENTS

Processor: AMD Athlon processor

RAM:2GB memory

HDD: 250 GB

Monitor: HDLCD

3.2. SOFTWARE REQUIREMENTS

Operating System: Windows 7

Platform: Netbeans IDE

Front End: JAVA

Back End: MySQL

Dept.of Information Technology

page 6

Mini Project-2014

CHAPTER 4
SOFTWARE DESCRIPTION
4.1. FRONT END: JAVA
Java is a general-purpose computer programming language that is concurrent, classbased, object-oriented, and specifically designed to have as few implementation
dependencies as possible. It is intended to let application developers "write once run
anywhere" (WORA), meaning that code that runs on one platform does not need to be
recompiled to run on another. Java applications are typically compiled to bytecode that can
run on any java virtual machine (JVM) regardless of computer architecture. Java is, as of
2014, one of the most popular programming languages in use, particularly for client-server
web applications, with a reported 9 million developers. Java was originally developed by
James Gosling at Sun Microsystems (which has since merged into Oracle Corporation) and
released in 1995 as a core component of Sun Microsystems' java platform. The language
derives much of its syntax from C and C++, but it has fewer low level facilities than either
of them.
The original and reference implementation Java compiler, virtual machines, and class
libraries were originally released by Sun under proprietary licences. As of May 2007, in
compliance with the specifications of the java community process, Sun relicensed most of
its Java technologies under the GNU general public licence. Others have also developed
alternative implementations of these Sun technologies, such as the GNU compiler for
java (bytecode compiler), GNUclasspath(standard libraries), and iced-tea-Web (browser
plugin for applets).
4.1.1 Java platform
The main goal of Java is portability, which means that programs written for the Java
platform must run similarly on any combination of hardware and operating system with
adequate runtime support. This is achieved by compiling the Java language code to an
intermediate representation called java bytecode, instead of directly to architecturespecific machine code. Java bytecode instructions are analogous to machine code, but they
are intended to be executed by a virtual machine (VM) written specifically for the host
hardware. End users commonly use a java runtime environment (JRE) installed on their own
machine for standalone Java applications, or in a web browser for Java applets.
Standardized libraries provide a generic way to access host-specific features such as
graphics, threading and networking.
A major benefit of using bytecode is porting. However, the overhead of interpretation means
that interpreted programs almost always run more slowly than programs compiled to native

Dept.of Information Technology

page 7

Mini Project-2014

executables would. Just-in-Time (JIT) compilers were introduced from an early stage that
compile bytecodes to machine code during runtime.

4.1.2 Implementation:
Oracle corporation is the current owner of the official implementation of the Java SE
platform, following their acquisition of Sun Microsystems on January 27, 2010. This
implementation is based on the original implementation of Java by Sun. The Oracle
implementation is available for Microsoft Windows, Mac OS X, Linux and Solaris. Because
Java lacks any formal standardization recognized by Ecma International, ISO/IEC, ANSI, or
other third-party standards organization, the Oracle implementation is the de facto standard.
The Oracle implementation is packaged into two different distributions: The Java
Runtime Environment (JRE) which contains the parts of the Java SE platform required to
run Java programs and is intended for end users, and the java development kit (JDK), which
is intended for software developers and includes development tools such as the java
compiler, javadoc, jar, and a debugger.
Open JDK is another notable Java SE implementation that is licensed under the GNU
GPL. The implementation started when Sun began releasing the Java source code under the
GPL. As of Java SE 7, Open JDK is the official Java reference implementation.
The goal of Java is to make all implementations of Java compatible. Historically,
Sun's trademark license for usage of the Java brand insists that all implementations be
"compatible". This resulted in a legal dispute with Microsoft after Sun claimed that the
Microsoft implementation did not support RMI or JNI and had added platform-specific
features of their own. Sun sued in 1997 and in 2001 won a settlement of US$20 million, as
well as a court order enforcing the terms of the license from Sun. As a result, Microsoft no
longer ships windows with Java.
Platform-independent Java is essential to java EE, and an even more rigorous
validation is required to certify an implementation. This environment enables portable
server-side applications.
4.1.3 Performance
Programs written in Java have a reputation for being slower and requiring more
memory than those written in C++. However, Java programs' execution speed improved
significantly with the introduction of just-in-time-compilation in 1997/1998 for java 1.1, the
addition of language features supporting better code analysis (such as inner classes, the
String Builder class, optional assertions, etc.), and optimizations in the Java virtual machine,
such as Hotspot becoming the default for Sun's JVM in 2000.

Dept.of Information Technology

page 8

Mini Project-2014

Some platforms offer direct hardware support for Java; there are microcontrollers that can
run Java in hardware instead of a software Java virtual machine, and ARM based processors
can have hardware support for executing Java bytecode through their jazelle option.

4.2. BACK END: MYSQL

There are many databases that support the use of SQL to access their data, among
them MySQL and PostgreSQL. In other words, MySQL is just the brand of one database
software, one of many. The same goes for PostgreSQL. These two databases are very
popular among programs that run on websites (probably because they are free), which is
why you often see one or both of them being advertised in the feature lists of web hosts, as
well as being listed as one of the "system requirements" for certain web software (like blogs
and content management systems).

Dept.of Information Technology

page 9

Mini Project-2014

CHAPTER 5
PROJECT DESCRIPTION
5.1. PROBLEM DEFINITION
Canteen management system focuses on the easy facilitation of the item details
and in canteen. The accessing and data storage require a large amount of time. Thus time
consumption can be reduced and accessing becomes easy. The availability and accessibility
of data become secured in this system. The proposed system is a cost effective solution and
provides the possibility of upgradation. The project also facilitates the working of canteen
with high speed and accuracy.

5.2. MODULE DESCRIPTION

There are mainly three modules in the system design for the project. These three
modules associated with different login. The three modules does entirely different operations
in database.

5.2.1. MODULES
5.2.1.1. Admin Module
The admin here indicates the administrator for our application. The admin for the
application is the concerned owner of canteen. The admin has control over the entire
activity. The admin has the provision to verify the workers, employees and add or delete
existing workers etc. The major functions of admin are:
Registration
Login
View food items
View employees
Manage employees
Check income in a day
Check income in a selected period

Dept.of Information Technology

page 10

Mini Project-2014

5.2.1.2. Cashier Module

The Cashier has the right to process the bill and print the bill accordingly. The major
functions of the user of this module are:
Login
Enter Item
Calculate total
print
5.2.1.3. Stock Manager Module
The function of stock manager is to add and delete items in database with modified
price tag
Login
Edit / add new item

Dept.of Information Technology

page 11

Mini Project-2014

5.3 DATA FLOW DIAGRAM

5.3.1 LEVEL 0

5.3.2 LEVEL 1

Dept.of Information Technology

page 12

Mini Project-2014

5.3.3 LEVEL 1

5.3.4 LEVEL 1

Dept.of Information Technology

page 13

Mini Project-2014

5.4. DATABASE DESIGN

5.4.0 TABLES

5.4.1. LOGIN TABLE

Dept.of Information Technology

page 14

Mini Project-2014

5.4.2. STAFF DETAILS

5.4.3. AVAILABLE FOODS

Dept.of Information Technology

page 15

Mini Project-2014

5.4.4. BILL

Dept.of Information Technology

page 16

Mini Project-2014

CHAPTER 6
SYSTEM TESTING
Test Plan
The Software Test Plan describes plans for qualification testing of Computer
Software configuration Items and software systems. It describes the Software test
environment to be used for the testing, identifies the test to performed, and provides
schedules for test activities.
Testing strategy
The overall strategy for Software testing is described in the following section. We
will use four different methods to test our software.
6.1. UNIT TESTING
In unit testing, the analyst tests the programs making up a system. This is also called
program testing. The software units that make up the system are modules and the routines,
which are assembled and integrated to perform a specific function in a large system. Many
modules at different levels are needed. Unit testing, independent of one another, focuses on
modules to locate error. This enables the tester to detect error in coding and logic that are
contained within that module alone. Those resulting from the interaction between modules
are initially avoided. Unit Test comprises the test of performed prior to integration of the
unit into the entire project. Four categories of test are performed on each unit.

Functional Test
The code is exercised with nominal input values for which the expected results are

shown, as well as boundary values (Minimum values, Maximum values) and values on and
just outside the functional boundaries and special values such as logically related inputs.

Performance Test

Dept.of Information Technology

page 17

Mini Project-2014

Performance test is done to determine the amount of execution time spent in various
parts of the unit, program throughput, and response time and device utilization by the
program unit. Some time is taken initially to link to the SQL.

Stress Test
Stress Test has been done to intentionally break the unit. This helps in the learning

about the strength and limitations of the program by examining the manner in which a
program unit breaks.

Structure Test
Structure test are done to test the internal logic of a program and traversing particular

exercise, deriving test data to exercise those paths, determining the test coverage criteria to
be used.
6.2. ACCEPTANCE TESTING
After the developers complete the system testing successfully acceptance testing is
done at the customer end. It is the customer or the end user who knows designs the test cases
in this type of testing emphasis is on the usability of the product. Acceptance testing is
supported through alpha and beta testing. Alpha testing is done when the software is made
operational for the first time to be tested by the users at developers site. Hence it is possible
that it will involve making lot of changes to program code. Beta testing follows alpha testing
but now the testing is done at the customers site that validate the product after using it for
few days.At this stage few changes as compared to alpha testing would make to the product.
6.3. TEST CASES
The evaluation of test cases is done through test case review. And for any review, a
formal document or work product is needed. This is the primary reason for having the test
case specification in the form of document. The test case specification document is
reviewed, using a formal review process, to make sure that the test cases are consistent with
the policy specified in the plan, satisfies the chosen criteria, and in general cover the various
aspect of the unit to be tested.
For this process, the reason for selecting the test case and the expected output are
also given in the test case specification document. By looking at the conditions being tested

Dept.of Information Technology

page 18

Mini Project-2014

by the test cases, the reviewer can check if all the important conditions are being tested. As
conditions can also be based on the output, by considering the expected output of the test
cases it can also be determined the production of all the different types of output the unit is
supposed to produce are being tested.

Dept.of Information Technology

page 19

Mini Project-2014

CHAPTER 7
SYSTEM IMPLEMENTATION
Implementation is the process of converting a new or revised system design into an
optional one. It is the key stage in achieving a successful new system because usually it
involves a lot of upheaval in the user department. It must therefore be carefully planned and
prepared. Once the software is fully developed and implemented, the department starts to
use the software. The department also grows and more divisions may be attached, or the
database of the department can grow in size. So after sometime the software, this has to be
installed need some modification. If the software need modification all the needed to
develop new software has to be executed. The need has to be studied, the design has to be
made and the coding has to be done. The new module has to be connected to the existing
software modules Even if the software working perfectly also we have to do routine testing
and new bug if found out, has to be fixed. No software ever developed will be bug free
forever.

Dept.of Information Technology

page 20

Mini Project-2014

CHAPTER 8
APPENDIX
8.1 SCREEN SHOT
8.1.1 Login Screen

Dept.of Information Technology

page 21

Mini Project-2014

8.1.2 Admins Screen

Dept.of Information Technology

page 22

Mini Project-2014

8.1.3 Add Staff

Dept.of Information Technology

page 23

Mini Project-2014

8.1.4 Billing UI

Dept.of Information Technology

page 24

Mini Project-2014

8.1.5 Cashier Ui

Dept.of Information Technology

page 25

Mini Project-2014

8.1.6 Income Ui

Dept.of Information Technology

page 26

Mini Project-2014

8.1.7 Stock Manager Ui

Dept.of Information Technology

page 27

Mini Project-2014

8.1.8 Add Food Items

Dept.of Information Technology

page 28

Mini Project-2014

8.1.9 Available Food Items

Dept.of Information Technology

page 29

Mini Project-2014

8.1.10 Edit Food Items

Dept.of Information Technology

page 30

Mini Project-2014

CHAPTER 9
CONCLUSION
This application provides a user friendly approach towards the system. The system
has been well developed and is found to satisfy all of the requirements. There is a hope that
this software will be utilized to its maximum and will do a good job in long run. This phase
gives me a good idea on developing full-fledge software satisfy the user requirements. The
programming technique used in the design of the system provides scope for further
expansion and implementation of any changes which may occur in future. The design was
developed in a Java platform with Netbeans it is expected to leave up to the objective for
which it was designed.
The application provides an easy way to manage the details of employee working
under the canteen sections. The project can be modified by including more features .

Dept.of Information Technology

page 31

Mini Project-2014

REFERENCES
1.

Herbert Schildt,Java The Complete Reference, Seventh Edition.

2.

Stephen Potts,AlexPestrikov,Java 2 Unleashed,sams,Published 2002.

3.

Paul DuBois,MySQL (4th Edition).

4.

David Cash,Stock Market Basics.

5.

https://java.sun.com 10/ 10/ 14

6.

www.w3schools.com 15 /10 /14

7.

www.learnjavaonline.org 20 /10 /14

8.

www.NSE.in 2/ 10/ 14

9.

www.moneycontrol.com 10 /10 /14

Dept.of Information Technology

page 32