Professional Documents
Culture Documents
Submitted To :
GOVERNMENT POLYTECHNIC BIGHAPUR,
UNNAO
COLLEGE OF MANAGEMENT STUDIES
Project Certificate
This is to certify that the project report entitled HOTEL MANAGEMENT submitted to
Government Polytechnic Bighapur, Unnao, in partial fulfillment of the requirement for the award of
the degree of BACHELOR OF COMPUTER APPLICATIONS (BCA), is original work carried out by
myself Mr Suryabhan with enrolment no. E21272135500055 Under the Supervision of Prof. –
AVINASH VERMA.
The matter embodied in this project is genuine work done by myself and has not been submitted whether
to this University or to any other University / Institute for the fulfillment of the requirement of any
course of study.
Date:
SURYABHAN
suryaaydv@gmail.com
9198293038
Date: ………………..
Self-Certificate
This is to certify that the Major Project report entitled “ HOTEL MANAGEMENT ” is done
by me, and it is authentic work carried out for the partial fulfillment of the requirements for the award
of the Diploma in Computer Science & Engineering under the guidance of Mr. ANUJ SHUKLA. The
matter and software embodies in this project has not been submitted earlier for award of any degree or
diploma to the best of my knowledge and believes.
Signature of Student
Suryabhan
(Enrollment No :- E21272135500055)
Certificate from Project Guide
This is certify that this Major Project entitled " HOTEL MANAGEMENT " submitted in
partial fulfillment of the requirements for the award of the DIPLOMA IN COMPUTER SCIENCE &
ENGINEERING in session (years 2023 to 2024) to the GOVERNMENT POLYTECHNIC
BIGHAPUR, UNNAO done by SURYABHAN is an authentic work carriedout by them.
The matter and software embodied in this project work has not been submitted earlier for the award of
any degree or diploma to the best of my knowledge and belief.
( Project Guide )
GOVERNMENT POLYTECHNI BIGHAPUR, UNNAO
Project Work Evaluation
02 Objective
03 System Analysis
04 Identification of Need
05 Preliminary Investigation
06 Feasibility Study
10 System Design
12 Technology Applied
14 Reports
15 Coding
18 Code efficiency
19 Error Handling
20 Validation Checks
22 Testing
23 Testing techniques
24 Testing strategies
25 Modularization Details
27 Database/data security
32 Bibliography
33 Glossary
ACKNOWLEDGMENT
“Task successful” makes everyone happy. But the happiness will be gold without glitter if we didn’t
state the persons who have supported us to make it a success. Success will be crowned to people who
made it a reality but the people whose constant guidance and encouragement made it possible will be
crowned first on the eve of success.
This acknowledgement transcends the reality of formality when we would like to express
deep gratitude and respect to all those people behind the screen who guided, inspired and helped me for
the completion of our project work.
I consider myself lucky enough to get such a good project. This project would add as
an asset to my academic profile. I would like to express my thankfulness to my project guide, Mr.
ANUJ SHUKLA for hir constant motivation and valuable help through the project work, and I
express my gratitude to Prof. (Mr.) ANUJ SHUKLA, Course Coordinator of BCA (MCU)
DEPARTMENT, CMS, for his constant supervision, guidance and cooperation throughout the project.
I also extend my thanks to my Team Members for their co-operation during my project
work. Finally I would like to thanks my friends for their co-operation to complete this project.
SURYABHAN
ENROLLMENT NO. – E21272135500055
Introduction:
HOTEL Management System is the administration of airports and HOTELs. It includes the activities
of setting the strategy of airports to gather and provide information on HOTEL commercial and
operational priorities. It covers a broad overview of the HOTEL management. It is also studied as a
branch of study that teaches management of airport and HOTELs. This provides a broad overview of
the HOTEL industry and creates awareness of the underlying marketing, financial, operational, and
other factors influencing HOTEL management. This study provides information on HOTEL
commercial and operational priorities, along with teaching the key characteristics of aircraft selection
and the impact of airport decision making. It provides some amount of automation in HOTELs
management and helps HOTEL system in making their business more efficient. An added attraction
for their potential customers. It will also show the attitude of the management that they are aware to
the newly introduced technology and readyto adopt them.
1.1 Problem Definition
1.2 Need
Electronically handling of flight’s record to enhance the accuracy, flexibility, reliability and to remove
the human’s error. An HOTEL provides air transport services for passengers, generally with a
recognizeoperating. To provide accurate information about the addition, deletion and modified record.
To provide, efficient, accurate, reliable, fast, and robust structure that can handle any number of
records. The global HOTEL industry continues to grow rapidly, but consistent and robust profitability
is elusive.Measured by revenue, the industry has doubled over the past decade, from US$369 billion in
2004 to a projected $746 billion in 2014, according to the International Air Transport Association
(IATA).Muchof that growth has been driven by low-cost carriers (LCCs), which now control some 25
percent of the worldwide market and which have been expanding rapidly in emerging markets; growth
also came from continued gains by carriers in developed markets, the IATA reported. Yet profit
margins are still low, less than 3 percent overall. In the commercial aviation sector, just about every
group in the aviation industry chain—airports, airplane manufacturers, jet engine makers, travel
agents, and service companies, to name a few—turns a profit. It is seemingly ironic that the HOTEL
companies that actually move passengers from one place to another, the most crucial link in the chain,
struggle to make a profit.
A few factors that directs us to develop a new system are given below -:
1) Faster System
2) Accuracy
3) Reliability
4) Informative
Objective:
This project on HOTEL Management System is the automation of registration process of HOTELs
system. The system provides information like passenger’s information, flight information, list of all
passengers, it allows storing and retrieving data related to the HOTEL industry and make transactions
related to air travel etc. The system also allows us to add records when a passenger reserves a ticket.
For data storage and retrieval we use MySQL Database. It enables us to add any number of records in
our database. The project “HOTEL Management System” comprises of a large number of flights
which belong to a particular HOTEL. The system we have implemented manages different objects
viz.
· HOTEL
· HOTEL Employees
· Customers/Traveller
Here requirements for both the system and the software are documented and reviewed
with the customer as well as companies. More focus is given on the software. The analyst
interacts and understands the different functionalities, performance of the software. During the
design phase requirements are translated into a representation of the software that can be coded.
Here focus is given on the different attributes of a program – Data structures, Software
Architecture, interface representation and Algorithm details. The design is documented. Then
a SRS – System Requirement Specification report is prepared and given to the company.
Systems analysis is an important phase of the System Development Life Cycle. Hence
we thoroughly observed the existing system, learn about their problems, define
customer’s\company’s needs & requirements and evaluated some alternative solution.
Identification of Need
HOTEL reservations system is an integrated passenger processing system, including inventory, fares,
ticket-less operations and credit card transactions. All communications are via TCP/IP network protocol
enabling the using of both intranet and internet communications world wide.
The solution includes several standard items, which are combined to provide an integrated solution with
interfaces to other business systeMr. The system is based on open architecture, using industry standard
equipment and software.
Preliminary Investigation
Preliminary Investigation of our system included collection of user needs, defining all
such areas to be computerized & suggesting some feasible solution towards fulfillment of user
requests. In our preliminary investigation we discussed many details of the functional parts and
the daily business activities of the client. We communicated with the concerned persons &
noted their requirements. In our initial observations we found the following areas that needed
to be computerized.
Getting the inventory of any particular company or product through manual method is time
consuming and some times becomes incorrect. Getting the statistics of receipt of item of any particular
company or as a whole is difficult. Getting the statistics of issue of item of any particular dealer or as a
whole is difficult. Getting the ageing of different dealer and products is difficult. To keep the track of
accounts details of different dealers and retailers .To keep the track of account details of companies the
company deals with.
While investigating the existing system, we found a lot of activities that needed to be
computerized / automated. All the paper work carried while investigating, showed the
complicacies and size of the project. Our very next step was to individualize their requirements
and put them into categories or groups. These categories / groups represented a department or
an activity or a set of activities that needed to be automated.
Feasibility Study
The project to be designed is actually beneficial or not from various angles is examined
here. For example if there are no technical persons to operate the project, whether the
development cost exceeds the budget allocated by the company, whether there are system
resources available or not to implement the solution.
For all such reasons a Feasibility study is performed to determination weather or not
the enterprise software solution is worth doing. The process followed in making this
documentation is called a feasibility study. Project specifications can only be finalized if
analysis confirms positive results from feasibility study. Thus since the feasibility study may
lead to the conferment of large resources, it become necessary that it should be conducted
completely and that no fundamental errors of judgments are made. In a quest to justify our
systems requirements specifications, we carried the following types of feasibility studies.
Technical Feasibility:
Technical Feasibility is defined as the availability of suitable technology and system
resources to support the enterprise software solution and adequate expertise to develop the
solution. Also it must be possible to implement the solution within a reasonable time. The
Client has already well-equipped systeMr. The existing PC’s comprised of efficient processors,
with appropriate size of RAM and Hard disk as well as printers. All these available hardware
met the hardware requirements of our proposed system. We were also provided with most of
the software required.
Economic Feasibility:
Economic Feasibility Analysis in the most frequently used technique for evaluating the
effectiveness of a proposed system. It is more commonly known as COST / BENEFIT
Analysis; the procedure to determine the benefits and savings that are expected from a proposed
system and compare them with costs.
If benefits outweigh costs, decision is taken to design and implement the system.
Otherwise, further justification or alternative in the proposed system will have to be made if it
is to have a chance of being approved. This is an ongoing effort that improves in accuracy at
each phase of the system life cycle. The existing system had everything except the network
between the individual stand-alone systeMr. The expenses needed to establish the network
would be worth spending, as it would in all means benefit the overall functioning of the
organization.
Operational Feasibility:
Operational Feasibility is defined as the suitability of the solution from the standpoint
of the people who will have to use that solution. In context of our proposed system we covered
the following issues under operational feasibility
The proposed system is targeted towards faster and secured data processing. Large sets
of records maintained manually and stored in files and folders would be replaced by convenient
and secured way of processing. Not only the proposed project will benefit the existing system,
but also it will make the system robust with higher degree of overall performance and
productivity.
The technical persons available at the client site are well versed with general-purpose
software available. There would be less training effort required for the technical staff to operate
on our proposed system. Hence, little time would be wasted (after the implementation &
testing), for our project to be fully operational.
The company is having existing PC’s comprised of efficient processors, with
appropriate size of RAM and Hard disk as well as printers. All these available hardware met
the hardware requirements of our proposed system. It is also having a well-networked
infrastructure. Also the cost/benefit analysis determines the benefits and savings that are
expected from a proposed system and compare them with costs. And here the benefits outweigh
costs, in such situation decision is taken to design and implement the system. The company is
also having some skilled manpower having the operational knowledge of PCs. So the proposed
system is feasible in every angle.
Analysis:
Existing System
HOTEL Reservation System is a System including Inventory, Fares, Enquiries, and Reservations etc.
All user/agents are allocated a SINE code which is used during sine-on and then appended to all
transactions carried out by the agent for security purpose.
It has the following Dis-advantages:
1> Reservations does not support up to 1 year.
2> Accessing and updating the system is slow.
3> It is a file based processing.
Proposed System:
Using the distributed technology we can handle these problems easily. In general a distributed process
means that a program in execution makes use of resources in other machine. The two technologies for
distributed processing available are J2EE and .NET. In the “HOTEL reservation system” J2EE is used
for managing distributed systeMr. So that even if the HOTEL system has lot of branches and they are
located at different places, we can handle the management of service and guarantee.
The proposed system for the problem is “HOTEL reservation system”, a web based system that
allows online reservations. The system is divided into three layers namely presentation layer, business
layer and data layer. The presentation layer is at the client side. At server side, business layer and data
layerreside.
The system requires a server side technology for its implementation. J2EE platform is chosen for
implementing the system. At server side Servlet plays the role for business layer and JDBC for the
data layer.
Problem Statement
The objective of the project is to design and implement the software which helps the HOTEL System
employees to issue reservation tickets for various Air flights and maintain the records of various
passengers and provide quick services to the passengers. It provides the following services
• Reservation and Cancellation of the HOTEL tickets.
Object Modeling:
The object model describes the structure of objects in a system. Their identity, their relationships to
other objects, their attributes, and their operations. The object model provides the essential framework
into which the dynamic and functional models can be placed.
Our goal in constructing an object model is to capture those concepts from the real world that are
important to an application.
The object model is represented graphically with object diagrams containing object classes. Classes
are arranged into hierarchies sharing common structure and behavior and are associated with other
classes. Classes define the attribute values carried by each object instance and the operations which
each object performs or undergoes.
The first step in constructing an object model is to identify relevant object classes from the application
domain. Objects include physical entities, such as houses, employees, and machines, as well as
concepts, such as trajectories, seating assignments, and payment schedules. All classes must make sense
in the application domain; avoid computer implementation constructs, such as linked lists and
subroutines. Not all classes are explicit in the problem statement; some are implicit in the application
domain or general knowledge.
Identification of Associations:
Any dependencies between two or more classes is an association. A reference from one class to another
is association. Association often correspond to verb phrases. These include physical location, directed
actions, communication, ownership, or satisfaction of some condition. Extract all the candidates from
the problem statement.
Identification of Attributes:
Attributes are properties of individual objects. Attributes should not be objects. Use an association to
show any relationship between two objects. Attributes usually correspond to nouns to follow by
possessive phases. Adjectives often represent specific enumerated attribute values. Attributes are less
likely to be fully described in the statement of problem. The knowledge must be drawn from the
application domain and the real world to find out the attributes.
Class Attributes
Registration_info FirstName,LastName,Adress,
ContactNo,City,State,Country,
Gender,Email_Id,
Customer_id, password
DFD:
Data flow diagrams (DFD) depict information flow and the transforms that are applied as data
move from input to output. It is the starting point of design phase that functionally
decomposes the requirement specifications down to the lowest level details. Thus a DFD
describes what data flows (Logically) rather than how they are processed. So, it does not
depend on hardware, software or data structures.
It is one of the most important tools used during system analysis. It is used to model the
system components such as the system process, data used by the process any external that
interact if the system and information flows in the system.
Portability:
DFD’s are made up of number of symbols, which represents system components. Data flow
modeling used four kinds of symbols. These symbols are used to represent four kinds of
system components process, data stores, data flows and external entities.
Process:
Processes show what system does. Each process has one or more data inputs and produces one
or more outputs. Circles in DFD represent processes.
Data stores:
A Data store is a repository of the data. Processes can enter data in to a store or retrieve data
from the data store. Parallel lines in the DFD represent each data store.
External Entities:
External entities are outside the system but they either supply input data in to the system or
use the system out. They are entities on which the designer has no control. They may be
organization’s customers or with which the system interacts. These are represented by
rectangles in the DFD.
Data flows:
Data flow model passage of data in the system and are represented by lines joining system
components. An arrow indicates the direction of flow and the line is labeled by the name of
the data flow. Flow of data system can takes place.
Gives to the
Customer
Enter Gets
HOTEL
New Reservation
Custome System
Selects the
operation
Reservation
ER Diagram:
Customer HOTEL
Reservationsystem
Performs
Gives
Response
Operations
Software process model is a road map or framework for the tasks that are required to
build high-quality software. Thus we can define this as the foundation for Software
Engineering. The software process defines a systematic disciplined quantifiable approach to
the development, operations and maintenance of the software. The key process areas form the
basis for management control of software projects and establish the contest in which technical
methods are applied, work products (modules, documents, data, reports, forms etc.) are
produced, milestones are established, quality is ensured, and changes is properly managed.
As selection of a software process depends mostly on the problem domain or the type
and size of the Project, it became a real tough task for us to select a particular path / process
out of a range of software processes modules available. In our Project, we had a range of tasks
and a varied set of objectives that spread over different domains viz, Stock Management,
Processing of Sales Orders & Purchase Orders, Raising and Managing Customer orders,
managing the Stock to avoid Stock out costs and the details of Finance requirement to meet all
the needs. Also generating information for the top-level management personals. Working out
a suitable process model for such a system was a difficult task.
Initially considering the size of the project and information availability we were
inclined to adopt RAD – Rapid Application Development Model, as it would have helped in
obtaining prototypes in increments. But as we started dividing the whole project into modules
and tasks, we learnt that using prototyping model (as Software Engineering Paradigm) would
be more complicating & time consuming. The reason behind it was the size of modules, which
would have consumed a lot more time using prototype model than other models.
The software design principle followed here is RAD Rapid Application Development
model with short development cycle.
As the requirements are well understood and project scope is constrained the RAD
process enables a development team to create a fully functional system within very short time
period. The requirements gathering process is intensified and focused specifically pm software
to understand the nature of the programs to built. The software engineer must be understand
the information domain for the software, as well as required function; behavior performance
and interfacing for both systems and software are documented and reviewed with the customer.
This system view is essential when software must interface with other documents such as
hardware, people & database. System engineering and analysis encompasses requirements
gathering at the system level with a small amount of top level of analysis business level and at
the business area level. The Phases of RAD models are:
1. Business Modeling:
The information and data flows among different business entities i.e. the different
modules of the application are modeled here. Also the business functions are identified and the
processes that are required to implement the business functions are defined. All the inputs,
outputs and information flow among different entities are also identified.
2. Data Modeling:
The various data objects required to support the information flow among different
models are modeled here. The relationships between data objects are also defined. Different
levels of data flow diagrams are designed.
3. Process Modeling:
The entire data objects models were transferred to achieve the information flow. The
different process required, for adding, modifying, deleting or retrieving to or from a data object
is defined. The relationships between the data objects are also defined. Input and Output data
objects are the indication for the application of process model to implement RAD.
4. Application Generation:
Here the actual coding of the business functionalities are designed by using fourth
generation techniques. To reuse existing programs, reuse components may also be created. We
have selected as per the client requirements PHP with MySQL as it is Object Oriented.
5. Testing:
As in RAD, more emphasis is given on the reuse of components, many of the program
components have already been tested which reduces the overall testing time. All other
components and their interfaced are tested.
System Design
The problem analysis is the most important phase in any project. Only after knowing precisely what the
problem is could we successfully eliminate it. The identification of the root problem is necessary.
We were able to discuss with the personnel of various departments and gather information and we got
a clear picture of what the existing problem were and what our jobs was to eliminate them by
redesigning a new design.
Design is a multi step process that focuses on data structure, software architecture, Procedural details
(algorithms etc) and interface between the modules. The design process also translates the requirements
into the representations of the software that can be assessed for quality before coding begins.
Computer software design changes continually as new methods, better analysis and border
understanding evolve. Software design is at a relatively early flexibility and quantitative nature that is
normally associated with more classical engineering design disciplines. However, techniques for
software design to exist criteria for design qualities are available and design notation can be applied.
Once the software requirements have been analyzed and specified, software design is the first of three
technical activities- Design code and test that are required to build and verify the software. Each activity
transforms information in a manner that ultimately results in validation of the computer software.
The importance of the software design can be started with a single word quality. Design is the place
where quality fostered in software development. Design provides us with representations of the
software that can be accessed for quality.
Design is the only way that we can accurately translate a customer’s requirements into a finished
software product or system. Without design, risk of building an unstable system exists one that will fail
when small changes are made. One that may be difficult to test.
Thus the system design includes following three types of design:
Data Design: The data design transforms the information domain model created during analysis into
the data structures that will be required to implement the software.
Architectural Design: The architectural design defines the relationship among the major structural
components of the program.
Procedural Design: The procedural design transforms structural components into a procedural
description of the software. Source code is generated and testing is conducted to integrate and validate
the software.
Thus, system design is a solution, a “how to” approach to the creation of the new system.
Features of Desktop Application Applied :
Client server architecture:
Client-server describes the relationship between two computer programs in which one
program, the client program, makes a service request to another, the server program. Standard
networked functions such as email exchange, web access and database access, are based on the
client-server model.
Specific types of clients software include web browsers. Specific types of servers
include web servers, ftp servers, application servers, database servers, mail servers, file servers,
print servers, and terminal servers.
2- Tier Architecture
This approach makes a separation between application layer or application logic and data layer.
In the below fig. the 1st layer is known as application layer. This results in the structure shown in
figure 2:
The advantage with this architecture is that, because of two separation data can be stored on a
single host and can be shared by multiple application, i.e. the resource sharing becomes more
efficient. This also removes all the complexities of communicating with the database to a separate
layer.
The disadvantage with the 2-Tier architecture is its maintainability because, each client point
holds the complete application and the interface together, therefore even a single change in the
application needs to be updated at each client architecture.
3- Tier Architecture
This architecture overcomes the limitations of a 2-Tier system. Under this architecture, the
application is separated into three different layers with a set of well defined interfaces. This should
then enable components in one layer to be modified without requiring changes any changes to
components in other layers. For example, changing the file system from one DBMS to another, or
changing the user interface from one system to another (e.g. from client/server to the web).
-Application/Business Layer
-Data Layer
The Presentation Layer holds the user interface for interaction with the application.
The middle layer i.e. the business layer holds the application logic i.e. basically the code called
by the user through presentation layer to retrieve the desired data.
The Data Layer holds the data to be implemented by the application/business layer. The source
of data may be SQL Server, Oracle, Sybase or XML documents.
The main advantage of this structure over the 2-Tier system is that all business logic is
contained in its own layer and is shared by many components in the presentation layer. Any changes
to business rules can therefore be made in one place and be instantly available throughout the whole
application.
N-Tier Architecture
The name implies a structure which contains ‘N’ number of tiers where ‘N’ is a variable
number. This is usually achieved by taking a component in one of the standard layers of the 3-Tier
structure and breaking it down into subcomponents, each performing a specific low-level task.
More specifically under N-Tier architecture, the middle layer containing the application logic
is functionally divided into multiple components, each one carrying a particular operation.
For example, the designers of a project have broken down each of the initial three layers into
something which resembles the structure shown in figure 4:
Enterprise Architecture
This architecture is an N-Tier architecture, but the enterprise architecture is capable to manage
multiple application types whereas N-Tier is capable to deal with one application only.The
application under this architecture can handle applications of different architectures.
Advantages
Coding:
Code Efficiency:
The task of coding is carried out once the analysis and design is over. It depends on how well
the analysis and design is done. Thus, the better the analysis and design, easier it becomes for the
programmer to code. But the code has to be judged for its efficiency and worthiness. Code efficiency
defines how efficient is the code generated and whether it satisfies the needs as expressed in the design,
or not. Thus, it reflects the overall quality of the software. Code efficiency comes in conjunction with
code optimization, total time spent on coding and validation specification. “Optimized code may not
always be efficient, but efficient code always satisfies the user requirements”
When an application is created it is expected to give the best results using minimal computer
resources, such as memory (RAM) and hard disk space. In order to ensure that the application uses the
minimum resources, it is needed to fine-tune the application for improving its performance. The steps
involved in fie-tuning an application are known as optimization. In the present system, the process of
optimization started from the designing stage and continued till the development and distribution stage.
The optimization was done for increasing
Execution speed,
Display speed and
Proper utility of available memory space
Error Handling
Validation Checks
Validation is an important part of the application being designed. This ensures the data
consistency, protects accidentally deletion, modification of the data. In the system validation checking
is applied both at database level and program level. At database level, while designing the tables to
contain the information it has been maintained to implement validation by defining constraints for
different data items in the application.
At program level proper measures and attention has been given to prevent the entry of
invalid data in to the system.
Code:
MainFrame class:
package HOTEL.management.system;
import java.awt.*;
import javax.swing.*;
import java.awt.event.*;
public Mainframe() {
super("HOTEL RESERVATION MANAGEMENT SYSTEM");
initialize(); }
setForeground(Color.CYAN);
setLayout(null);
FlightDetails.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){
new Flight_Info();
}
});
ReservationDetails.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){ try
{
new Add_Customer();
} catch (Exception e) {
e.printStackTrace();
}
}
});
PassengerDetails.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){
try {
new Journey_Details();
} catch (Exception e) {
e.printStackTrace();
}
}
});
SectorDetails_1.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){
try {
new Payment_Details();
} catch (Exception e) {
e.printStackTrace();
}
}
});
Cancellation.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){
new Cancel();
}
});
setSize(1950,1090);
setVisible(true);
}
}
Login.java:
package HOTEL.management.system;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import java.sql.*;
public Login(){
super("Login");
setBackground(Color.WHITE); f1 = new
Font("TimesRoman",Font.BOLD,20); f2 = new
Font("TimesRoman",Font.BOLD,15);
gbl=new GridBagLayout();
gbc=new GridBagConstraints();
setLayout(gbl);
l1 = new Label("Username");
l1.setFont(f1);
l2 = new Label("Password");
l2.setFont(f1);
t1 = new TextField(15); t2
= new TextField(15);
t2.setEchoChar('*');
b2 = new Button("Reset");
b2.setFont(f2);
b3 = new Button("Submit");
b3.setFont(f2);
gbc.gridx=0; gbc.gridy=0;
gbl.setConstraints(l1,gbc);
add(l1);
gbc.gridx=2;
gbc.gridy=0;
gbl.setConstraints(t1,gbc);
add(t1);
gbc.gridx=0;
gbc.gridy=2;
gbl.setConstraints(l2,gbc);
add(l2);
gbc.gridx=2;
gbc.gridy=2;
gbl.setConstraints(t2,gbc);
add(t2);
gbc.gridx=0;
gbc.gridy=8;
gbl.setConstraints(b2,gbc);
add(b2);
gbc.gridx=2;
gbc.gridy=8;
gbl.setConstraints(b3,gbc);
add(b3);
gbc.gridx=4;
gbc.gridy=8;
gbl.setConstraints(b4,gbc);
add(b4);
b2.addActionListener(this);
b3.addActionListener(this);
b4.addActionListener(this);
setVisible(true);
setSize(400,250);
setLocation(400,200);
}
t1.setText("");
t2.setText("");
}
if(ae.getSource()==b4){
System.exit(0);
}
if(ae.getSource()==b3){
try{
conn c1 = new conn();
String s1 = t1.getText();
String s2 = t2.getText();
String str = "select * from login where username = '"+s1+"' and password = '"+s2+"'";
ResultSet rs = c1.s.executeQuery(str);
if(rs.next()){
new Mainframe();
setVisible(false);
}else{
JOptionPane.showMessageDialog(null,"Invalid Login");
setVisible(false);
}
}catch(Exception e){}
}
}
HOTEL.management.syste
m;import java.awt.EventQueue;
JTextField textField,textField_1,textField_2,textField_3,textField_4,textField_5,textField_6;
public Add_Customer(){
getContentPane().setForeground(Color.BLUE);
getContentPane().setBackground(Color.WHITE);
setTitle("ADD CUSTOMER DETAILS");
setDefaultCloseOperation(JFrame.HIDE_ON_CLOSE);
setSize(778,486); getContentPane().setLayout(null);
ImageIcon i1 = new
ImageIcon(ClassLoader.getSystemResource("HOTEL/management/system/icon/emp.png"));
JLabel image = new JLabel(i1);
image.setBounds(450,80,280,410);
add(image);
Next.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){
String passport_No = textField.getText(); String
pnr_no = textField_1.getText();
String address = textField_2.getText();
String nationality = textField_3.getText();
String name = textField_4.getText();
String fl_code = textField_6.getText();
}else if(Female.isSelected()){
gender = "female";
}
try {
conn c = new conn();
String str = "INSERT INTO passenger values( '"+pnr_no+"', '"+address+"',
'"+nationality+"','"+name+"', '"+gender+"', '"+ph_no+"','"+passport_No+"', '"+fl_code+"')";
c.s.executeUpdate(str);
JOptionPane.showMessageDialog(null,"Customer Added");
setVisible(false);
} catch (Exception e) {
e.printStackTrace();
}
}
});
setSize(900,600);
setVisible(true);
setLocation(400,200);
JTextField textField;
JTable table;
JLabel Sector;
JLabel FlightCode, Capacity, Classcode, Classname, label;
public Payment_Details(){
initialize();
}
setVisible(true);
Show.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){
try {
String code = textField.getText();
ResultSet rs = c.s.executeQuery(str);
table.setModel(DbUtils.resultSetToTableModel(rs));
}catch(SQLException e) {
e.printStackTrace();
}
}
});
setSize(960,590);
setLocation(400,200);
setVisible(true);
}
}
Flight_Info.java: package
HOTEL.management.system;
public Flight_Info(){
getContentPane().setBackground(Color.WHITE);
getContentPane().setFont(new Font("Tahoma", Font.PLAIN, 13));
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
setSize(860,523);
setLayout(null);
setVisible(true);
btnShow.addActionListener(new ActionListener() {
public void actionPerformed(ActionEvent ae) {
try {
conn c = new conn();
String str = "select f_code,f_name,src,dst,capacity,class_code,class_name from flight
,sector where f_code = '"+code+"'";
ResultSet rs = c.s.executeQuery(str);
table.setModel(DbUtils.resultSetToTableModel(rs));
}catch(SQLException e){
e.printStackTrace();
}
}
});
setDefaultCloseOperation(JFrame.HIDE_ON_CLOSE);
setSize(900,650);
setVisible(true);
setLocation(400,200);
}
}
Practice.java: import
java.awt.EventQueue;
import javax.swing.ImageIcon;
import javax.swing.JButton;
import javax.swing.JTextField;
import java.awt.Color; public
class Practice {
PreparedStatement pst=null;
private JFrame frame; private
JTextField textField; private
JTextField textField_1; private
JTextField textField_2; private
JTextField textField_3; private
JTextField textField_4;
/**
* Launch the application.
*/
public static void main(String[] args) {
EventQueue.invokeLater(new Runnable()
{ public void run() { try {
Practice window = new Practice(); window.frame.setVisible(true);
} catch (Exception e) {
e.printStackTrace();
}
}
});
}
/**
* Create the application.
*/ public
Practice() {
initialize();
}
/**
* Initialize the contents of the frame.
*/
private void initialize() {
frame = new JFrame("CANCELLATION");
frame.getContentPane().setBackground(new Color(255, 153, 204)); frame.setBounds(100,
100, 801, 472);
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.getContentPane().setLayout(null);
btnCancel.addActionListener(new ActionListener()
{ public void actionPerformed(ActionEvent ae)
{
String passenger_no=(String)textField.getText();
String cancellation_no=(String)textField_1.getText();
String cancellation_date=(String)textField_2.getText();
String ticket_id=(String)textField_3.getText();
String flight_code=(String)textField_4.getText();
try {
Class.forName(driver);
con=DriverManager.getConnection(url+dbname,userName,password);
} catch (ClassNotFoundException | SQLException e1) { //
TODO Auto-generated catch block
e1.printStackTrace();
}
try {
pst=con.prepareStatement("INSERT INTO
`HOTEL`.`cancellation` (`pnr_no`, `cancellation_no`, `cancellation_date`, `ticket_id`,
`fli_code`)VALUES (?, ?, ?, ?, ?);"); pst.setString(1,passenger_no); pst.setString(2,
cancellation_no); pst.setString(3,cancellation_date); pst.setString(4,ticket_id);
pst.setString(5,flight_code);
pst.executeUpdate();
} catch (Exception e) {
// TODO Auto-generated catch
block e.printStackTrace(); }
}
});
frame.setSize(960,586);
frame.setVisible(true);
}
Cancel.java: package
HOTEL.management.system;
importjavax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
public Cancel() {
initialize();
}
ImageIcon i1 = new
ImageIcon(ClassLoader.getSystemResource("HOTEL/management/system/icon/cancel.png"));
Image i2 = i1.getImage().getScaledInstance(250, 250, Image.SCALE_DEFAULT);
ImageIcon i3 = new ImageIcon(i2);
JLabel NewLabel = new JLabel(i3);
NewLabel.setBounds(470, 100, 250, 250);
add(NewLabel);
Cancel.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent ae){
}catch (Exception e) {
e.printStackTrace();
}
}
});
setSize(860,500);
setVisible(true);
setLocation(400,200);
}
}
Java Core
Core Java is the part of Java programming language that is used for creating or developing a
generalpurpose application. It uses only one tier architecture that is why it is called as ‘stand alone’
application.Core java programming covers the swings, socket, awt, thread concept, collection object
and classess.
Swings
Swing is a GUI widget toolkit for Java. It is part of Oracle's Java Foundation Classes (JFC) – an API
for providing a graphical user interface (GUI) for Java prograMr.
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.
Backend Implementation
MYSQL
MySQL is an open-source relational database management system (RDBMS). A relational database
organizes data into one or more data tables in which data types may be related to each other; these
relations help structure the data. SQL is a language programmers use to create, modify and extract data
from the relational database, as well as control user access to the database. In addition to relational
databases and SQL, an RDBMS like MySQL works with an operating system to implement a relational
database in a computer's storage system, manages users, allows for network access and facilitates testing
database integrity and creation of backups.
Table cancellation:
create table cancellation(pnr_no varchar(10), cancellation_no varchar(10), cancellation_date DATE,
fli_code varchar(15));
Table flight:
create table flight(f_code varchar(10), f_name varchar(20), src varchar(30), dst varchar(30));
varchar(20));
Table passenger:
Table reservation:
create table reservation(pnr_no varchar(10), ticket_id varchar(10), f_code varchar(10), jny_date DATE,
jny_time varchar(10), src varchar(20), dst varchar(20));
Table sector:
Maintenance means restoring something to its original conditions. System maintenance confirms the system to
its original requirements and enhancement adds to system capability by incorporating new requirements.
Thus, maintenance changes the existing system, enhancement adds features to the existing system, and
development replaces the existing system. It is an important part of system development that includes the
activities which corrects errors in system design and implementation, updates the documents, and tests
the data.
Maintenance Types
System maintenance can be classified into three types −
• Corrective Maintenance − Enables user to carry out the repairing and correcting leftover
probleMr.
• Adaptive Maintenance − Enables user to replace the functions of the prograMr.
• Perfective Maintenance − Enables user to modify or enhance the programs according to the
users’ requirements and changing needs.
Managing Maintenance
• Number of people working in maintenance has surpassed number working in development
• Three possible organizational structures
Separate
Maintenance group consists of different personnel than development group
Combined
Developers also maintain systems
Functional
Maintenance personnel work within the functional business unit
SNAPSHOTS
Backend Records
Testing
Testing Techniques
System Testing
System testing is the stage, which is aimed at ensuring that the system works accurately &
efficiently before live operation commences. To assure the quality of the system, the following are to
be considered
Scope of Testing
Once the system has been developed the system has to be tested and if no Bugs found it is to
be implemented. A good test cannot solve a bad program and testing can never prove a program is right.
A good test case design that detects many errors is alarming Testing requires skill and knowledge.
Testing Platforms
Methods Used
1. Unit Testing
Unit tests are at program level where the programmer himself can test at the system for known
bugs. Unit testing are at involves the tests carried out on modules programs, which make up a system.
This is also called as Program Testing. The Units in the system are modules and the routines that are
assembled and integrated to perform a specific function. In a large System, many modules at different
levels are needed; unit testing focuses first on the modules, independently of one another, to locate
errors.
The Program to be tested for correctness of logic applied and should locate error in coding. For
example test cases are needed to determine how the system handles if an intruder try to enter the
application. User password will be encrypted and checks with the database. The Unauthorized user will
be warned with a message.
Valid and invalid data should be created and the programs should be made to the process this
data to catch errors. For example a student who has completed the course cannot access the lab resources
and he/she cannot appear for any other tests conducted by the institute.
2. Integration Testing
Integration testing begins with a software structure that has been defined using stubs (a dummy
module) that allows testing of super ordinate (calling Program) control and interface correctness. Stubs
are replaced by unit tested modules or builds integration testing proceeds. For Integration testing,
several factors should be considered:
Are routines to be integrated in a pure top-down manner or should build be developed to test
sub function first?
In what order should major software functions be incorporated?
Is the scheduling of modules code and test consistent with the order of integration?
Is special hardware required to test certain routines?
Developed a list of all modules. Associated with each module is its unit test completion date,
date of first integration, destination (e.g. build into which it will be incorporated or functional level)
and a reference to required test data/result for that module.
Another important consideration during integration test planning is the amount of test software
(e.g., drivers, test case generation) that must be developed to adequately test the required functionality.
3. System testing
The test plan is a product of software design. The test plan specifies the objectives of testing,
test completion criteria, system Integration Planed, methods to be used on modules and particular test
cases to be used.
Functional test – specify operation conditions, input values and expected results
Performance test –should be design to verify response time, throughput, primary and secondary
memory utilization and traffic rates on data channels and communication channels.
Stress test-is designed to overload a system in various ways.
Structural test- are concerned with examining the internal processing logic of a software
system.
Any software has to undergo robust test in each and every stage. Any shortcoming or bugs must
be rectified and tested. This software has undergone the tests thoroughly. A system is tested for online
responses, volume of transactions, stress, recovery from failure, and usability. Software testing is a
critical element of software quality assurance and represents the ultimate review of specification, design
and coding
System testing involves two types of testing, Integration testing and acceptance testing. In
integration testing all the modules are integrated the interfaces between the modules are tested. Bottom
up integration is the traditional strategy is to integrate the components of a software system into a
functioning whole. Top Down integration starts from the main module along one or two intermediate
subordinated routines in the system structure
Testing Strategies
Knowing the specified function that a product has been designed to perform, tests can be
conducted that demonstrate each function is fully operational.
Knowing the internal working of a product, tests can be conducted to ensure that the internal
components have been adequately exercised. The tests of this software were conducted on the following
fashion.
Database/data security:
After a user gains access to the application, the user is ability to perform certain actions is
restricted. For example, users are allowed to add new records but not delete existing ones. Users are
restricted to view the data online, but not produce printed reports of critical data. Thus, permission
checking enabled to check the user’s security profile to see whether that user has permission to perform
a particular task.
The next step in security added in the application is an audit trial that logs all the significant
actions taken by user within the application. This included logging in and out and executing any
“secured object” within the application, field change auditing, that is, changes made to data records on
a field-by-field basis.
The cost of a Project is estimated, keeping in account many factors like human efforts,
recourses required, security and reliability provisions, size in KLOC (Kilo Lines of Codes),
user interfaces, size of databases, integration, documentation and the types of reports or output
produced.
In our approach to cost estimation of the system, we followed Constructive Cost Model (COCOMO) to
estimate the total effort in terms of Programmers months or Persons-month. COCOMO model requires
sizing information as
Objects Points
Function Points
We used Objects Points to estimate the total effort required in our project. The Object Point is an indirect
Reports and
Each Object instance (e.g. a screen or report) is classified into one of three complexity levels, i.e.,
Simple, Medium or Difficult, based on the number and source of the client and server data tables that
are required to generate the screen or report and the number of views or report.
The software package “HOTEL Reservation System” provides convenient online uploading the
reportfrom executive and viewing that report by the managing director in an online fashion.
To input the data in a highly validated manner and generating the different reports, this involves
complex process that was being done on based manner.
This package is designed and developed in a compact manner, which is ready to meet the user’s
specification and to serve them in an effective as well as in an enhanced manner. The actual problem
has been observed with keen interest and it has been defined and analyzed in such a way that it never
causes choice to the user. More ever the limitation that has been prevailing in the existing system had
been overcome to suit the need of the user.
High precision and care has been taken to design the data base , input forms an output reports since they
should be given due importance which could otherwise to serious consequences thus affecting the whole
system . The system thus developed has been implemented successfully which has been performed to
scrutinized the validation of each data and errors were spotted out and then finally cleared in a
sophisticated manner.
The added feature of this system is that it has been provided with many provisions for future
enhancement in order to maintain the system in such a way that the future requirement of the user could
also be satisfied and upgrated.
Conclusion:
Bibliography
[1] https://developers.openshift.com/database/mysql.html
Software Metrics These are the quantitative measure of the degree to which a system
component or process possesses a given attribute. In other words software
metrics helps in assessing a process or product thereby checking in
validity, worthiness, risks, errors, and defects, work-flows or tasks etc.
The project is assessed while it is in development phase.
Feasibility Is the determination of weather or not a project is worth doing. The
process followed in making this documentation is called a feasibility
study.
Technical Feasibility Is defined as the availability of suitable technology to support the solution
and adequate expertise to develop the solution.
Economic Feasibility
System Testing
Is the stage, which is aimed at ensuring that the system works accurately
& efficiently before live operation commences.
Unit Tests
Are at program level where the programmer himself can test at the system
for known bugs. Unit testing are at involves the tests carried out on
modules programs, which make up a system. This is also called as
Program Testing.
Integration Testing It begins with a software structure that has been defined using stubs (a
dummy module) that allows testing of super ordinate (calling Program)
control and interface correctness.
Black Box Testing Knowing the specified function that a product has been designed to
perform, tests can be conducted that demonstrate each function is fully operational.
White Box Testing Knowing the internal working of a product, tests can be conducted to
ensure that the internal components have been adequately exercised.
Optimization
Portability
Schema
Control File A control file contains entries that specify the physical structure of the
database.