Download Java booking system - School of Computing

Abstract
With the increasing popularity of the Internet many organisations are now looking
to create Web based applications capable of collating, processing and distributing
information central to the organisations needs. Applications that not only provide
services to the organisations staff, but also to their customers via the Web. To
meet the needs of such applications, new standards and design models have
evolved. This project takes a sample application that allows both customers and
staff access to a central store of data via the Web. A new component oriented
server side architecture; the
Java 2 Enterprise Edition has been used to
implement a layered architecture. The sample application was developed in
association with a small chain of restaurants and is allows both staff and
customers to book tables, based on information updated in real-time. Since the
trade levels can be determined in real-time, special offers can be displayed to
customers at quiet times, attempting to provide a form of supply and demand
based advertising. The application is fully functional. The new Enterprise Java
Beans component model that forms part of the Java 2 Enterprise Edition has been
used to implement the core application, providing a highly modifiable, portable
and extensible software package. One of the Projects main aims was to present an
application sufficiently well designed and implemented that it could be used as a
model for other similar systems. The careful implementation of a pure layered
architecture using servlets, JavaServerPages and Enterprise JavaBeans has been
used to accomplish this aim. It is the implementation of the layered architecture
that has been one of the major accomplishments of this project. Course grained
software components have been used to implement a core application that is
capable of supporting not only the browser clients used for the sample
application, but standalone applications. In addition, the use of the new Container
Managed Persistence features of the J2EE specification mean that the sample
application has been implemented in a way that is database independent.
Persistence requirements are not hard-coded into the application, only specified in
the deployment descriptor files. Thus achieving complete independence from the
underlying database used by the application.
2