ONLINE EVENT MANAGEMENT SYSTEM

1. INTRODUCTION
1.1 Objective and Introduction:

Online Event Management is web application software being designed and developed to meet
the needs of customers’ who want to book for required services. Using this web application,
the customers will be able to avail services for their events after registering with us through
our web site. Our web application facilitates clients to choose services according to their
budget and also the online payments. This will improve the customers satisfaction and saves
time.

Major Modules:

 Admin
 Customer
Functionalities of Modules:

Admin can perform the following operations:

 Approval of new members

 Updating service charges details
 Adding/Updating events and scenarios
 Preparation of reports

Customers have the following privileges:

 Obtaining membership
 Booking services for events
 Making transactions – Online Payments
 Preparation of service booking summary
 Viewing status
 Changing password

VI BCA 1
 ONLINE EVENT MANAGEMENT SYSTEM

1.2 OUTLINE AND BRIEF DESCRIPTION OF THE ISSUES INVOLVED

The administrator has the full privilege in this web application. The user
with admin login can add new service details as when introduced in the
market. The financial scenarios of clients are obtained and service
booking plans and services are given. Also, on regular basis admin keeps
checking the market trends and updates the service for the customers and
generate the report.

The customers will have to register to do business through our web

application. Only the authentic customers can make transactions and get
their service status. The authenticithy of customers are maintained
through user name and password. Customers are facilitated with
password change, they can register new password if their password is
compromised. The Customers have options to view the new services and
charges details and choose the services accordingly for their events.

VI BCA 2
 ONLINE EVENT MANAGEMENT SYSTEM

2. SOFTWARE REQUIREMENT ANALYSIS

System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Analysis begins when a developer begins a
study of the program using existing system. During analysis, data are collected on the various
files, decision points and transactions handled by the present system. The commonly used
tools in the system are Data Flow Diagram, interviews, etc. Training, experience and
common sense are required for collection of relevant information needed for the development
of the system. The success of the system depends largely on how clearly the problem is
defined, thoroughly investigated and properly carried out through the choice of solution. A
good analysis model should provide not only the mechanisms of problem understanding but
also the frame work of the solution. Thus it should be studied thoroughly by collecting data
about the system. Then the proposed system should be analyzed thoroughly in accordance
with the needs.

2.1 PRESENT SYSTEM

The existing system is functionally compatible with the process logic, but lacking in certain
operations such as booking summary and alteration that customers should be able to do in the
system for the changing needs. The booking and status tracking are not automated. Usually
the e-commerce websites does not provide with the status tracking. The customers will have
to register for the same with customer support team and make phone calls to know the status
of requested service. In this type of status tracking the customers face lots of hardships in
getting connected and to talk to the executive for knowing the status. Also, the savings,
expenses and various types of earnings related operations in finance maintenance require the
automation.

2.2 PROPOSED SYSTEM

In the proposed system, the drawbacks of existing system are overcome. The customer
support for status tracking is done through one of the web module, so that customers can
track the booking status through the web pages. The numerous phone calls and endless
waiting is eliminated. All other operations are typical web commerce oriented, so system
functionality is well understood. The development and usage of this application is really
interesting one.

VI BCA 3
 ONLINE EVENT MANAGEMENT SYSTEM

3. SOFTWARE REQUIREMENT SPECIFICATION

A software requirements specification (SRS) is a comprehensive description of the intended

purpose and environment for software under development. The SRS fully describes what the
software will do and how it will be expected to perform.

An SRS minimizes the time and effort required by developers to achieve desired goals and
also minimizes the development cost. A good SRS defines how an application will interact
with system hardware, other programs and human users in a wide variety of real-world
situations. Parameters such as operating speed, response time, availability, portability,
maintainability, footprint, security and speed of recovery from adverse events are evaluated.

The requirements of this web application (ems) developed by us is very well understood and
documented initially when the process started.Accordingly the hardware and software
requirements are chosen. The same can be referred in the next section of this report. This web
application runs in the Apache Tomcat Server, which can be accessed by web clients through
the Internet from anywhere in the world. The SRS parameters are adopted in this system,
with the detailed feasibility study. While developing, this system tested as the localhost,
through the Mozilla firefox browser. Also, few other popular web browsers are tested.

VI BCA 4
 ONLINE EVENT MANAGEMENT SYSTEM

4. SOFTWARE AND HARDWARE CONFIGURATION

VI BCA 5
 ONLINE EVENT MANAGEMENT SYSTEM

5. SOFTWARE PROFILE

5.1 ABOUT HTML/XHTML

HTML (Hyper Text Markup Language) :

HARDWARE HTML
Processor Intel Core i3 was
RAM 2GB created by

HDD 500GB Tim

Berners-
SOFTWARE
Lee at
CLIENT SIDE TECHNOLOGIES XHTML, CSS, JAVASCRIPT
European
SERVER SIDE TECHNOLOGIES SERVLET, JSP, BEANS, JDBC

WEB SERVER APACHE TOMCAT 7.0

PROGRAMMING LANGUAGE JAVA

DATABASE ORACLE 10g

IDE NETBEANS 7.0.1

TEST TOOL JUnit

BUILD TOOL ANT

WEB AUTHORING TOOLS PHOTOSHOP, FLASH

Laboratory for Particle Physics (CERN) in late 1980’s. Developed by the World Wide
Web Consortium; HTML or the Hyper Text Markup Language, as its name suggests,
is a markup language for Web pages. Today, the most important component of any
web page is the text-based information that it contains. The markup tags of HTML
define the structure of the text-based information of a web page. HTML tags are used
to denote various text-based information of a webpage as paragraphs, headings, links,
bullet points etc. Various HTML tags can also be used to supplement the text with
images, forms and other objects. HTML tags are for browsing; they are meant for
interactions between humans and computers.

Hardware Interface:
Client side:
 Processor: Intel Core i3.
 RAM: 2GB.

VI BCA 6
 ONLINE EVENT MANAGEMENT SYSTEM

 Network Interface.
Server Side:
 Processor: Intel Core i3.
 RAM: 2GB.
 Disk space: 2GB.

Software Interface
Client side:
 Windows XP/ Vista/ Win 7.
 Internet Explorer 6.0 or above
 Network Interface.
Server Side:
 Apache Tomcat Web Server 7.0.1.
 Oracle 10g Database as Back End.
 J2EE Framework.

VI BCA 7
 ONLINE EVENT MANAGEMENT SYSTEM

HTML draft version timeline

October 1991

HTML Tags an informal CERN document listing eighteen HTML tags, was first
mentioned in public.

June 1992

First informal draft of the HTML DTD with seven subsequent revisions (July 15,
August 6, August 18, November 17, November 19, November 20, November 22)

November 1992

HTML DTD 1.1 (the first with a version number, based on RCS revisions, which start
with 1.1 rather than 1.0), an informal draft.

June 1993

Hypertext Markup Language was published by the IETF IIIR Working Group as an
Internet-Draft (a rough proposal for a standard). It was replaced by a second version
one month later, followed by six further drafts published by IETF itself that finally
led to HTML 2.0 in RFC1866

November 1993

HTML+ was published by the IETF as an Internet-Draft and was a competing

proposal to the Hypertext Markup Language draft. It expired in May 1994.

April 1995 (authored March 1995)

HTML 3.0 was proposed as a standard to the IETF, but the proposal expired five
months later without further action. It included many of the capabilities that were in
Raggett's HTML+ proposal, such as support for tables, text flow around figures and
the display of

January 2008

HTML5 was published as a Working Draft by the W3C.

VI BCA 8
 ONLINE EVENT MANAGEMENT SYSTEM

Although its syntax closely resembles that of SGML, HTML5 has abandoned any
attempt to be an SGML application and has explicitly defined its own "html"
serialization, in addition to an alternative XML-based XHTML5 serialization.

Characteristics: -

 It is the language which can be easily understood and can be modified.

 Effective presentations can be made with the HTML with the help of its all
formatting tags.
 It provides the more flexible way to deign web pages along with the text.
 Links can also be added to the web pages so it helps the readers to browse the
information of their interest.
 You can display HTML documents on any platforms such as Macintosh,
Windows and Linux etc.
 Graphics,videos and sounds can also be added to the web pages which give an
extra attractive look to your web pages. Allows database integration with wide
variety of applications.
 Additional internet capabilities.

XHTML Versions: -

XHTML is a separate language that began as a reformulation of HTML 4.01 using

XML 1.0. It continues to be developed:

 XHTML 1.0, published January 26, 2000, as a W3C Recommendation, later revised
and republished August 1, 2002. It offers the same three variations as HTML 4.0 and
4.01, reformulated in XML, with minor restrictions.
 XHTML 1.1 published May 31, 2001, as a W3C Recommendation. It is based on
XHTML 1.0 Strict, but includes minor changes, can be customized, is reformulated
using modules from Modularization of XHTML, which was published April 10, 2001,
as a W3C Recommendation.
 XHTML 2.0 There is no XHTML 2.0 standard. XHTML 2.0 is only a draft document
and it is inappropriate to cite this document as other than work in progress. XHTML

VI BCA 9
 ONLINE EVENT MANAGEMENT SYSTEM

2.0 is incompatible with XHTML 1.x and, therefore, would be more accurately
characterized as an XHTML-inspired new language than an update to XHTML 1.x.
 XHTML5, which is an update to XHTML 1.x, is being defined alongside HTML5 in
the HTML5 draft.

VI BCA 10
 ONLINE EVENT MANAGEMENT SYSTEM

5.2 JAVA SERVER PAGES (JSP)

Released in 1999 by Sun Microsystems, JavaServer Pages (JSP) is similar to ASP

and PHP, but it uses the Java programming language. JavaServer Pages (JSP) is a
technology that helps software developers serve dynamically generated web pages
based on HTML, XML, or other document types.

JSP allows Java code and certain pre-defined actions to be interleaved with static web
markup content, with the resulting page being compiled and executed on the server to
deliver an HTML or XML document. The compiled pages and any dependent Java
libraries use Java bytecode rather than a native software format, and must therefore be
executed within a Java virtual machine (JVM) that integrates with the host operating
system to provide an abstract platform-neutral environment.

JSP syntax is a fluid mix of two basic content forms: scriptlet elements and markup.
Markup is typically standard HTML or XML, while scriptlet elements are delimited
blocks of Java code which may be intermixed with the markup. When the page is
requested the Java code is executed and its output is added, in situ, with the
surrounding markup to create the final page. JSPs must be compiled to Java bytecode
classes before they can be executed, but such compilation is needed only when a
change to the source JSP file has occurred.

VI BCA 11
 ONLINE EVENT MANAGEMENT SYSTEM

Characteristics of Java Server Pages

 The Power of Server-Side Java

 Easy and Rapid Web Development, Deployment and Maintenance
 Emphasizing Reusable Components
 Separating Content Generation from Presentation
 Open Development and Widespread Industry Support
 Platform Independence

VI BCA 12
 ONLINE EVENT MANAGEMENT SYSTEM

5.3 SERVLET

A Servlet is a Java programming language class that is used to extend the capabilities
of servers that host applications access via a request-response programming model.
Although servlets can respond to any type of request, they are commonly used to
extend the applications hosted by web servers. For such applications, Java Servlet is a
Java class in Java EE that conforms to the Java Servlet API, a protocol by which a
Java class may respond to requests. They are not tied to a specific client-server
protocol, but are most often used with the HTTP protocol. Therefore, the word
"Servlet" is often used in the meaning of "HTTP Servlet".[2] Thus, a software
developer may use a servlet to add dynamic content to a Web server using the Java
platform. The generated content is commonly HTML, but may be other data such as
XML. Servlets are the Java counterpart to non-Java dynamic Web content
technologies such as CGI and ASP.NET. Servlets can maintain state in session
variables across many server transactions by using HTTP cookies, or URL rewriting.

Characteristics Of Java Servlet

 Servlets are efficient

 Servlets are robust

 Servl ets are portable.

 Servlets are persistence.

VI BCA 13
 ONLINE EVENT MANAGEMENT SYSTEM

5.4 APACHE TOMCAT

Apache Tomcat is an open source software implementation of the Java Servlet and
JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications
are developed under the Java Community Process.

Apache Tomcat is developed in an open and participatory environment and released

under the Apache License Version 2. Apache Tomcat is intended to be a collaboration
of the best-of-breed developers from around the world. Apache Tomcat powers
numerous large-scale, mission-critical web applications across a diverse range of
industries and organizations. Apache Tomcat, Tomcat, Apache, the Apache feather,
and the Apache Tomcat project logo are trademarks of the Apache Software
Foundation.

Apache Tomcat (or simply Tomcat, formerly also Jakarta Tomcat) is an open source
web server which means that it is free and is managed by a large team of volunteers, a
process that efficiently and effectively maintains the system and servlet container
developed by the Apache Software Foundation (ASF).

Tomcat implements the Java Servlet and the JavaServer Pages (JSP)
Specifications from Oracle Corporation, and provides a "pure Java"
HTTP web server environment for Java code to run.

Apache is available for a range of operating systemS including UNIX,

LINUX, WINDOWS, SOLARIS, NOVELL NETWARE, MAC OS X.

VI BCA 14
 ONLINE EVENT MANAGEMENT SYSTEM

5.5 ORACLE

The Oracle Database (commonly referred to as Oracle RDBMS or simply as Oracle)

is an object-relational database management system (ORDBMS)] produced and
marketed by Oracle Corporation. The original version of Oracle was developed by
Software Development Laboratories (SDL) in 1977.

An Oracle database system is identified by an alphanumeric system identifier or SID,

which comprises of at least one instance of the application, along with data storage.
The Oracle DBMS can store and execute stored procedures and functions within it.

Storage: -

The Oracle RDBMS stores data logically in the form of tablespaces and physically in
the form of data files. Tablespaces can contain various types of memory segments,
such as Data Segments, Index Segments, etc. Segments in turn comprise one or more
extents. Extents comprise groups of contiguous data blocks. These data blocks form
the basic units of data storage. There are also partitioning feature available on newer
versions of the database, which allows tables to be partitioned based on different set
of keys.

Oracle database management tracks its computer data storage with the help of
information stored in the SYSTEM tablespace. The SYSTEM tablespace contains the
data dictionary and often indexes and clusters. A data dictionary contains of a special
collection of tables that contains information about all user-objects in the database.
Since version 8i, the Oracle RDBMS also supports “locally managed” tablespaces

VI BCA 15
 ONLINE EVENT MANAGEMENT SYSTEM

which can store space management information in bitmaps in their own headers rather
than in the SYSTEM tablespace. Version 10g and later introduced the SYSAUX
tablespace which contains some of the tables formerly in the SYSTEM tablespace.

Database Schema: -

Oracle database conventions refer to defined groups of object ownership (generally

associated with a "username") as schemas. Most Oracle database installations
traditionally come with a default schema called SCOTT. After the installation process
has set up the sample tables, the user can log into the database with the username scott
and the password tiger. The name of the SCOTT schema originated from Bruce Scott,
one of the first employees at Oracle (then Software Development Laboratories), who
had a cat named Tiger. Oracle Corporation has de-emphasized the use of the SCOTT
schema, as it uses few of the features of the more recent releases of Oracle. Most
recent examples supplied by Oracle Corporation reference the default HR or OE
schemas. Other default schemas include SYS, SYSTEM, OUTLN, BI, IX, HR, OE,
PM, and SH.

VI BCA 16
 ONLINE EVENT MANAGEMENT SYSTEM

5.6 DATABASE MANAGEMENT SYSTEM

A database management system (DBMS) is a collection of programs that enables

users to create and maintain a database. This is a software system that allows access to
the data contained in the database. The primary goal of a DBMS is to provide an
environment that is both convenient and efficient to use in storing and retrieving
database information.

Functions of DBMS:-

DBMS is a general purpose software system that performs the following functions:-

 Defining a database.

 Constructing the database.

 Manipulating the database.

 Sharing database among various users.

 Protecting the database.

 Maintaining a database.

VI BCA 17
 ONLINE EVENT MANAGEMENT SYSTEM

DBMS Architecture:-

DBMS architecture consists of three levels known as Three Schema Architecture. It is

convenient tool with which the user can visualize the schema levels in a database
system. It contains of the following three schemas:-

1. The Internal level: - This contains of an internal schema, which describes the
physical storage structure of the database. It is the lowest level of abstraction. It does
not hide the storage details. It contains the definition of the stored record, the method
of representing the data fields and the access aids used. This internal schema uses a
physical data model and describes the complete details of data storage and access
paths for the database. It is also called the physical schema.

2. The Conceptual level: - This has a conceptual schema, which describes the structures
of a database for a group of users. This schema hides the storage details from the user
and it includes description of entities, data types, relationships, user operations and
constraints. The description of data at this level is in a format independent of its
physical representation.

3. The External level: - This has a number of external schemas or user views. Each
external schema describes the part of the database that a particular user group is
interested in and hides all the other details from this group. This is at a highest level of
database absorption.

VI BCA 18
 ONLINE EVENT MANAGEMENT SYSTEM

Fig: - Three schema DBMS architecture

Client-Server Architecture: -

The client/server architecture was developed to deal with computing environments in

which a large number of PCs, workstations, file servers, printers, database servers,
Web servers and other equipment are connected via a network. There are two
client/server architecture:-

 Two-tier

 Three-tier

 N-tier

Two-Tier Client/Server Architecture: -

In two tier architecture, the software components are distributed over two systems: the
client and the server. This architecture has two forms as: logical two-tier and physical
two-tier.

VI BCA 19
 ONLINE EVENT MANAGEMENT SYSTEM

Fig: - Logical two-tier client/server architecture

Fig: - Physical two-tier client/server architecture

The above figure shows the physical client/server architecture. Some machines like
diskless workstations, or workstations/PCs with disks that have only client software
installed would be only client sites. Other machines would be dedicated servers. Some
other machines would have both client and server functionality. In relational DBMS,
user interface and application programs can run at client side. The query and
transactions functionality are included on the server side. A client program can send
query and transaction requests using the ODBC API which are then processed at the
server site. The query results are sending back to the client program which can
process or display the results needed.

VI BCA 20
 ONLINE EVENT MANAGEMENT SYSTEM

Three-Tier Client/Server Architecture: -

With the emergence of World Wide Web, many web applications use the three-tier
architecture. There is an intermediate layer between the client and the database server
called the application server or the web server. The web server plays the intermediary
role by storing business rules that are used to access data from the database server. It
checks the client’s credentials before forwarding a request to the database server. The
intermediate server accepts requests from the client, process the request and sends
database commands to the database server, and then acts as a conduit for passing
processed data from the database server to the clients, where it may be processed
further.

Fig: - Logical three-tier client/server architecture

N-Tier Architecture: -

In N-Tier architecture, the middle tier is allowed to have multiple application objects
rather than a single application. Each of these application objects must have a well-
defined interface which allows them to contact and communication with one another.
An interface actually brings an idea of contract. That is, each object states through its
interface that it will accept certain parameters and return a specific set of results.

Application objects use their interfaces to do business processing. With and N-Tier
architecture, one can have multiple applications using a common set of business
objects across an organization. This promotes the standardization of business
practices by creating a single set of business functions for the entire organization to

VI BCA 21
 ONLINE EVENT MANAGEMENT SYSTEM

access. If a particular business rule changes, then changes have to be made to only the
business object and if need, to its interface also.

Normalization: -

Normalization is a process during which unsatisfactory relation schemas are

decomposed by breaking up their attributes into smaller relation schemas that possess
desirable properties.

Normalization of data can be looked upon as a process of analyzing the given relation
schemas based on their functional dependencies and primary keys to achieve the
desirable properties of minimizing redundancy, insertion, deletion and update
anomalies.

The different Normal Forms present in DBMS are: -

 First Normal Form: - It states that the domains of attributes must include only atomic
values and that the value of any attribute in a tuple must be single value from the
domain of that attribute. It disallows a set of values, a tuple of values, or a
combination of both as an attribute value for a single tuple.

 Second Normal Form: - A relation is said to be in Second Normal Form if it is in

1NF and non-key attributes are fully functionally dependent on the key attribute(s). If
the key has more than one attribute (composite key) then no non-key attributes should
be functionally dependent upon a part of the key attributes.

 Third Normal Form: - A relation is said to be in Third Normal Form if it is in 2NF

and no non-prime attributes of relation R is transitively dependent on the primary key.

 Fourth Normal Form: - Under this, a record type should not contain two or more
independent multi-valued facts about an entity. In addition, the record must satisfy
third normal form.

 Fifth Normal Form: - It also deals with multi-valued facts. Here, the record must
satisfy the fourth normal form.

VI BCA 22
 ONLINE EVENT MANAGEMENT SYSTEM

 Boyce Codd Normal Form: - It a normal form used in database normalization. It is a

slightly stronger version of the third normal form (3NF). A table is in Boyce–Codd
normal form if and only if for every one of its nontrivial dependencies X → Y, X is a
super key—that is, X is either a candidate key or a superset thereof

VI BCA 23
 ONLINE EVENT MANAGEMENT SYSTEM

5.7 CASCADING STYLE SHEET

Cascading Style Sheets (CSS) is a style sheet language used to describe the
presentation semantics (the look and formatting) of a document written in a markup
language. It’s most common application is to style web pages written in HTML and
XHTML, but the language can also be applied to any kind of XML document,
including plain XML, SVG and XUL.

CSS defines HOW HTML elements are to be displayed. Styles are normally saved in
external .css files. External style sheets enable you to change the appearance and
layout of all the pages in a Web site, just by editing one single file! The CSS files
referenced in the HTML page.

A CSS rule has two main parts: a selector, and one or more declarations:

VI BCA 24
 ONLINE EVENT MANAGEMENT SYSTEM

The selector is normally the HTML element you want to style. Each declaration
consists of a property and a value. The property is the style attribute you want to
change. Each property has a value.
Following example formats a paragraph in an HTML document
p
{
color:red;
text-align:center;
}

VI BCA 25
 ONLINE EVENT MANAGEMENT SYSTEM

5.8 JAVASCRIPT

JavaScript was originally developed by Brendan Eich of Netscape under the name
Mocha, which was later renamed to LiveScript, and finally to JavaScript.

JavaScript is a prototype-based, object-oriented Scripting Language that is dynamic,

weakly typed and has first-class functions. It is also considered a functional
programming language because it has closures and supports higher-order functions.
JavaScript is primarily used in the form of client-side JavaScript, implemented as part
of a web browser in order to provide enhanced user interfaces and dynamic websites.

The primary use of JavaScript is to write functions that are embedded in or included
from HTML pages and that interact with the Document Object Model (DOM) of the
page. Some simple examples of this usage are:
i) Opening or popping up a new window with programmatic control over the
size, position, and attributes of the new window (e.g. whether the menus,
toolbars, etc. are visible).
ii) Validating input values of a web form to make sure that they are acceptable
before being submitted to the server.
iii) Changing images as the mouse cursor moves over them: This effect is often
used to draw the user's attention to important links displayed as graphical
elements.

EXAMPLE:
a) A simple recursive function:
function factorial(n)
{
if (n === 0)
{
return 1;
}
return n * factorial(n - 1);
}

VI BCA 26
 ONLINE EVENT MANAGEMENT SYSTEM

6. SYSTEM DESIGN

6.1 DATABASE SCHEMA DESIGN:

create table emslogin(
username varchar2(20) constraint sspuseridpk primary key,
password varchar2(30),
usertype varchar2(20)
);

create table emsemployee

(
empid varchar(12) constraint sspempidpk primary key,
empname varchar2(20) ,
empgender varchar2(6),
empaddress varchar2(50),
empphone varchar2(11),
empemail varchar2(20),
empsalary number(7,2),
empjobcategory varchar2(20),
empstatus varchar2(20)
);

create table emsservicemaster

(
serviceid varchar2(12) constraint sspserviceidpk primary key,
servicetype varchar(20)
);

create table emsclients

(
clientid varchar2(12) constraint sspclientidpk primary key,
clientname varchar2(20),
email varchar2(20),

VI BCA 27
 ONLINE EVENT MANAGEMENT SYSTEM

phone varchar2(11),
address varchar2(50),
companyname varchar2(20),
balanceamt number(10,2)
);

create table emscaterservicemast

(
caterserviceid varchar2(12) constraint sspcatserserviceidpk primary key,
caterservicetype varchar2(20),
serviceid varchar2(12) references emsservicemaster(serviceid)
);

create table caterservicedetails

(
caterserviceid varchar2(12) references emscaterservicemast(caterserviceid),
menuitemname varchar2(20),
price number(7,2)
);

create table emsbkgmaster

(
bkgid varchar2(12) constraint sspbkgidpk primary key,
bkgdate varchar2(20),
bkgclientid varchar2(10) references emsclients(clientid),
servicedate varchar2(20),
bkgeventaddr varchar2(50),
bkgnumdays number(10),
bkgamt number(10,2),
bkgstatus varchar2(20)
);

VI BCA 28
 ONLINE EVENT MANAGEMENT SYSTEM

create table emseventservicedetails

(
servicedetid varchar2(12) constraint sspservicedetidpk primary key,
serviceid varchar2(12) references emsservicemaster(serviceid),
servicename varchar2(20),
servicecharge number(8),
availableserviceqty number(8)
);

create table emsservicebkgdet

(
servicedetid varchar2(12) references emseventservicedetails(servicedetid),
bkgid varchar2(12) references emsbkgmaster (bkgid),
serviceqty number(8),
serviceamt number(10,2)
);

create table emscaterbkgdet

(
caterserviceid varchar2(12) references emscaterservicemast (caterserviceid),
bkgid varchar2(12) references emsbkgmaster(bkgid),
serviceqty number(6),
serviceamt number(10,2)
);

create table emsservicedespatch

(
emsservicedespid varchar2(12) constraint sspemsservicedespidpk primary key,
bkgid varchar2(12) references emsbkgmaster (bkgid)
);

VI BCA 29
 ONLINE EVENT MANAGEMENT SYSTEM

create table emsservicedespatchdetails

(
emsservicedespid varchar2(12) references emsservicedespatch (emsservicedespid),
empid varchar2(12) references emsemployee(empid)
);

VI BCA 30
 ONLINE EVENT MANAGEMENT SYSTEM

6.2 DATA DICTIONARY

-----------------------------------------------------------------------------------------------------------

Sequences Used

-----------------------------------------------------------------------------------------------------------

create sequence sspempidseq increment by 1 start with 101 nocycle;

create sequence sspserviceidseq increment by 1 start with 101 nocycle;

create sequence sspclientidseq increment by 1 start with 101 nocycle;

create sequence sspcaterserviceidseq increment by 1 start with 101 nocycle;

create sequence sspbkgidseq increment by 1 start with 101 nocycle;

create sequence sspservicedetidseq increment by 1 start with 101 nocycle;

create sequence sspemsservicedespidseq increment by 1 start with 101 nocycle;

VI BCA 31
 ONLINE EVENT MANAGEMENT SYSTEM

6.3 DATA FLOW DIAGRAM

VI BCA 32
 ONLINE EVENT MANAGEMENT SYSTEM

6.4 ER DIAGRAM

VI BCA 33
 ONLINE EVENT MANAGEMENT SYSTEM

7. TESTING

7.1 CODING , TESTING AND IMPLEMENTATION

The main interfaces are:

 Web server and application server interface.
 Application server and Database server interface.
Check if all the interactions between these servers are executed properly. Errors are
handled properly. If database or web server returns any error message for any query by
application server then application server should catch and display these error messages
appropriately to users. Check what happens if user interrupts any transaction in-between?
Check what happens if connection to web server is reset in between?

7.2 TESTING AND ERRORS

Compatibility of our web site is very important testing aspect. See which compatibility
test to be executed:
 Browser compatibility
 Operating system compatibility
 Mobile browsing
 Printing options
Browser compatibility:
Some applications are very dependent on browsers. Different browsers have different
configurations and settings that your web page should be compatible with. Your web site
coding should be cross browser platform compatible. If you are using java scripts or
AJAX calls for UI functionality, performing security checks or validations then give more
stress on browser compatibility testing of your web application. Test web application on
different browsers like Internet explorer, Firefox, Netscape navigator, AOL, Safari,
Opera, Chrome browsers with different versions.

OS compatibility:
Some functionality in your web application is may not be compatible with all operating
systems. All new technologies used in web development like graphics designs, interface
calls like different API’s may not be available in all Operating Systems.
Test your web application on different operating systems like Windows, Unix, MAC,
Linux, Solaris with different OS flavors.

VI BCA 34
 ONLINE EVENT MANAGEMENT SYSTEM

7.3 SAMPLE TEST CASES DONE

Sl.No
Test Case Done Action taken
.
1 Invalid user credentials Redirected to error page.
entered Customer of Admin main
page not shown.
2 Incomplete form entry in the Users are prompted to
registration and few other complete the page to proceed
pages. next.
3 Illegal data entry. E.g., amount All such errors are captured
entered in negative values. and prompted accordingly so
Phone numbers out of range, that users will provide only
etc., the legal input to the system.
4 Invalid credit card number Captured and prompted the
entry. user to enter only the valid
credit card number.
5 Incorrect ClientID entry Error message notified to the
Client ID.

VI BCA 35
 ONLINE EVENT MANAGEMENT SYSTEM

8. SCREENS

VI BCA 36
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 37
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 38
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 39
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 40
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 41
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 42
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 43
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 44
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 45
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 46
 ONLINE EVENT MANAGEMENT SYSTEM

VI BCA 47
 ONLINE EVENT MANAGEMENT SYSTEM

9. SAMPLE CODES

REGISTRATION.HTML

<html>
<head>
<title></title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

<script type="text/javascript">
function checkForEmpty(form)
{
cn = document.regform.mname.value;

caddr = document.regform.maddress.value;
phno = document.regform.mphone.value;

em = document.regform.memail.value;

if(cn.length == 0 || cper.length == 0 || caddr.length == 0 || phno.length == 0 || pin.length ==

0 || em.length == 0 || faxnum.length == 0)
{
alert("Please fill all the fields");
return false;
}
else
return true;
}
function checkNum1(form)
{
str = document.regform.mname.value;
var i, x ;
for(i=0; i< str.length; i++)
{

VI BCA 48
 ONLINE EVENT MANAGEMENT SYSTEM

x = charAt(i);
if(x >= 0 && x <= 9)
{
alert("please enter only alphabet");
document.regform.mname.value= "";
//return false;
}
}
// return true;
}
function checkPhno()
{
var retval = true;
var pno = document.regform.mphone.value;
var stripped = pno.replace(/[\(\)\.\-\ ]/g, '');
//strip out acceptable non-numeric characters
if (isNaN(parseInt(stripped))) {
alert("The phone number contains illegal characters.");
document.regform.mphone.value="";
retval = false;
}
if(pno.length != 10)
{
alert("Illegal length");
document.regform.mphone.value="";
retval = false;
}
return retval;
}

function emailValid()
{
var aemail = document.regform.memail.value;

VI BCA 49
 ONLINE EVENT MANAGEMENT SYSTEM

//if email field is empty - warning displays and return false

if(aemail=="")
{
alert ("This field is required. Please enter email [email protected]")
return false
}
//get email string length
len = aemail.length
//check position of @ character.
//it may be anywhere but not in the beginning or at the end of string.
if((aemail.charAt(1)=='@')||(aemail.charAt(1)=='.'))
{
alert ("Invalid email. Please enter email like [email protected]");
document.regform.memail.value="";
return false;

}
if((aemail.charAt(len-2)=='@')||(aemail.charAt(len-2)=='.'))
{
alert ("Invalid email. Please enter email like [email protected]");
document.regform.memail.value="";
return false

}
//count number of @ occurrences and number of dot occurrences
count=0
dotcount=0
for (i=0; i< aemail.length; i++)
{
if(aemail.charAt(i)=='@')
count++
if(aemail.charAt(i)=='.')
dotcount++

VI BCA 50
 ONLINE EVENT MANAGEMENT SYSTEM

}
//if @ or dot occurs not once display warning and return false
if((count !=1)||(dotcount !=1))
{
alert ("Invalid email. Please enter email like [email protected]");
document.regform.memail.value="";
return false
}
return true
}

function isAlpha(parm,num)
{
//var parm = document.f1.T1.value;
var lwr = 'abcdefghijklmnopqrstuvwxyz .';
var upr = 'ABCDEFGHIJKLMNOPQRSTUVWXYZ';
return isValid(parm,num,lwr+upr);
}
function isValid(parm,num,val) {
if (parm == "")
{
alert("Please enter text");
return false;
}
for (i=0; i<parm.length; i++) {
if (val.indexOf(parm.charAt(i),0) == -1)
{
alert("please enter only alphabet");
if(num==1)
document.regform.mname.value="";

return false;
}

VI BCA 51
 ONLINE EVENT MANAGEMENT SYSTEM

}
return true;
}
function checkfill()
{
var ele;
var flag=true;
var ecount=document.regform.elements.length;
for(i=0;i<ecount;i++)
{
ele=document.regform.elements[i].value;
if(ele.length==0)
{
window.alert("Please fill all fields");
flag=false;
break;
}
}
return flag;
}
</script>
<style type="text/css">
td,a,h1
{
color: white;
}
a:hover
{
color: yellow;
}
</style>
</head>
<body background="rbg8.jpg">

VI BCA 52
 ONLINE EVENT MANAGEMENT SYSTEM

<center><h1>REGISTRATION FORM</h1>
<hr/>
<form name="regform" action="regprocess.jsp" method="post" onsubmit="return
checkfill();">
<table width="60%" >
<tr>
<td >
<table>
<tr><td>
<img src="join.png" />
</td>
</tr>
</table></td>
<td>
<table>
<tr> <td>Name</td>
<td><input type="text" name="mname" value="" onblur="checkNum1()"/>
</td></tr>
<tr> <td>Address</td>
<td><input type="text" name="maddress" value=""/>
</td></tr>
<tr> <td>Email</td>
<td><input type="text" name="memail" value="" onblur="emailValid()"/>
</td></tr>
<tr> <td>Phone</td>
<td><input type="text" name="mphone" value="" onblur="checkPhno()" />
</td></tr>
<tr> <td>Company Details</td>
<td><input type="text" name="mcompanydetails" value=""/>
</td></tr>
<tr><td><input type="submit" name="s1" value="Register"/>
</td><td><input type="reset" name="r1" value="clear"/>
</td>

VI BCA 53
 ONLINE EVENT MANAGEMENT SYSTEM

</tr>
</table>
</tr>
</table>
</form>
</center>
</body>
</html>

REGISTRATION.JSP
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<jsp:useBean class="emspack.PasswordBean" id="pb" scope="request"></jsp:useBean>
<%@page import="java.sql.*" %>
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<%
String un = request.getParameter("mname");
String uadr = request.getParameter("maddress");
String uem = request.getParameter("memail");
String uph = request.getParameter("mphone");
String ucomdet = request.getParameter("mcompanydetails");
String pwd = pb.genPwd();
String uid = "emsuser";

Connection c = null;
Statement s = null;
ResultSet r = null;

VI BCA 54
 ONLINE EVENT MANAGEMENT SYSTEM

try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
c = DriverManager.getConnection("jdbc:odbc:sspemsdsn","scott","tiger");
s = c.createStatement();
r = s.executeQuery("select userseq.nextval from dual");
while(r.next())
{
uid += r.getInt(1);
}
s = c.createStatement();
s.executeUpdate("insert into emsclients values('" + uid + "','" + un + "','" + uem +
"','" + uph + "','" + uadr + "','" + ucomdet + "',0)");
s = c.createStatement();
s.executeUpdate("insert into emslogin values('" + uid + "','" + pwd + "','client')");
%>
<h1>Your registration is confirmed. Welcome to EMS</h1>
<hr />
<h2>Your user name is <%= uid %></h2>
<h2>Your password is <%= pwd %></h2>
<h3><a href="login.html">CLICK HERE TO LOGIN</a></h3>
<% }
catch(Exception e)
{
%>
<h1><%= e %> </h1>
<% }
%>

</body>
</html>

VI BCA 55
 ONLINE EVENT MANAGEMENT SYSTEM

REGISTRATION SERVLET
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/

import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import emspack.UserCreation;
/**
*
* @author admin
*/
public class UserCreServ extends HttpServlet {

/**
* Processes requests for both HTTP <code>GET</code> and <code>POST</code>
methods.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
response.setContentType("text/html;charset=UTF-8");
PrintWriter out = response.getWriter();
try {
/* TODO output your page here

VI BCA 56
 ONLINE EVENT MANAGEMENT SYSTEM

out.println("<html>");
out.println("<head>");
out.println("<title>Servlet UserCreServ</title>");
out.println("</head>");
out.println("<body>");
out.println("<h1>Servlet UserCreServ at " + request.getContextPath () + "</h1>");
out.println("</body>");
out.println("</html>");
*/
} finally {
out.close();
}
}

// <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the + sign on

the left to edit the code.">
/**
* Handles the HTTP <code>GET</code> method.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
//processRequest(request, response);
PrintWriter out = response.getWriter();
String s1=request.getParameter("T1");
String s2=request.getParameter("T2");
String s3=request.getParameter("T3");
String s4=request.getParameter("T4");
String s5=request.getParameter("T5");

VI BCA 57
 ONLINE EVENT MANAGEMENT SYSTEM

double s6=Double.parseDouble(request.getParameter("T6"));
String s7=request.getParameter("T7");
UserCreation ua=new UserCreation();
ua.userCreation(s1, s2, s3, s4, s5,s6,s7);
String eid=ua.getEmpId();
out.println("<html>");
out.println("<head>");
out.println("<title>Servlet UserCreServ</title>");
out.println("</head>");
out.println("<body>");
out.println("<h1>EMPLOYEE ID: " + eid + "</h1><br>");
out.println("</body>");
out.println("</html>");

/**
* Handles the HTTP <code>POST</code> method.
* @param request servlet request
* @param response servlet response
* @throws ServletException if a servlet-specific error occurs
* @throws IOException if an I/O error occurs
*/
@Override
protected void doPost(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

/**
* Returns a short description of the servlet.
* @return a String containing servlet description
*/

VI BCA 58
 ONLINE EVENT MANAGEMENT SYSTEM

@Override
public String getServletInfo() {
return "Short description";
}// </editor-fold>
}
REGISTRATION BEAN
package emspack;
import java.sql.*;
/**
*
* @author admin
*/
public class UserCreation {
Connection con = null;
Statement st = null;
Statement st1 = null;
ResultSet rs = null;
int id=0;
String eid = "";
public void userCreation(String name, String gender, String email, String addr,String
phno , double sal, String jobcat)
{

try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection("jdbc:odbc:sspemsdsn","scott","tiger");
st = con.createStatement();
rs=st.executeQuery("select sspempidseq.nextval from dual");
while(rs.next())
{
id=Integer.parseInt(rs.getString(1));
}

VI BCA 59
 ONLINE EVENT MANAGEMENT SYSTEM

eid = "SSPEMP" + id;

st1 = con.createStatement();
st1.executeUpdate("insert into emsemployee values('" + eid + "','" + name + "','"
+ gender + "','" + email + "','" + addr + "','" + phno + "'," + sal + ",'" + jobcat +
"','AVAILABLE')");

}
catch(Exception e)
{
System.out.println(e);
}
}
public String getEmpId()
{
return(eid);
}
}

VI BCA 60
 ONLINE EVENT MANAGEMENT SYSTEM

PASSWORD BEAN
package emspack;
import java.util.Random;
/**
*
* @author admin
*/
public class PasswordBean {
public String genPwd()
{
String
alphanumerals="ABCDEFGHIJKLMNOPQRSTRUVWXYZabcdefghijklmnopqrstuvwxyz0
123456789";

Random r=new Random();

String pwd="";
for(int i=0;i<8;i++)
{
pwd+=alphanumerals.charAt(r.nextInt(61));
}
return(pwd);
}
}
EVENT CART BEAN
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package emspack;
import java.util.Hashtable;
import java.util.Enumeration;

/**

VI BCA 61
 ONLINE EVENT MANAGEMENT SYSTEM

*
* @author admin
*/
public class EventCart {
protected Hashtable decoration = new Hashtable();
protected Hashtable music = new Hashtable();
protected Hashtable photo = new Hashtable();
protected Hashtable makeup = new Hashtable();
protected Hashtable funiture = new Hashtable();
protected Hashtable catering = new Hashtable();

//HASHTABLE FOR CARTERING

public void addItemCatering( String itemname, int rate,int numunits) {

if(numunits > 0){
String[] item = {itemname, Integer.toString(rate),Integer.toString(numunits)};
catering.put(itemname, item);
}
}

public void removeItemCatering(String itemId) {

if (catering.containsKey(itemId))
{
catering.remove(itemId);
}
}
public void deductItemCatering(String itemname, int qty)
{
Enumeration e = catering.elements();
String[] tmpItem;
String id="";
String name="";

VI BCA 62
 ONLINE EVENT MANAGEMENT SYSTEM

int price=0;
int units = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
if(itemname.equals(tmpItem[0]))
{
units = Integer.parseInt(tmpItem[2]);
if(qty >= units)
removeItemCatering(itemname);
else
{
//id = tmpItem[0];
name=tmpItem[0];
price=Integer.parseInt(tmpItem[1]);
units = units - qty;

removeItemCatering(itemname);
addItemCatering(name,price,units);
}

break;
}
}
}
public void updateQuantityCatering(String itemId, int quantity) {
if (catering.contains(itemId)) {
String[] tmpItem = (String[])catering.get(itemId);
tmpItem[3] = Integer.toString(quantity);
}
}

public Enumeration getEnumerationCatering() {

VI BCA 63
 ONLINE EVENT MANAGEMENT SYSTEM

return catering.elements();
}

public float getCostCatering() {

Enumeration e = catering.elements();
String[] tmpItem;
int totalCost = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
totalCost += Integer.parseInt(tmpItem[1]) * Integer.parseInt(tmpItem[2]);
}
return totalCost;
}

public int getNumOfItemsCatering() {

Enumeration e = catering.elements();

int num = 0;

while (e.hasMoreElements()) {
num++;
}

return num;
}

//HASHTABLE FOR FURNITURE CART

public void addItemFurniture(String itemid, String itemname, int rate,int numunits) {

if(numunits > 0){

VI BCA 64
 ONLINE EVENT MANAGEMENT SYSTEM

String[] item = {itemid,itemname, Integer.toString(rate),Integer.toString(numunits)};

funiture.put(itemid, item);
}
}

public void removeItemFurniture(String itemId) {

if (funiture.containsKey(itemId))
{

funiture.remove(itemId);
}
}
public void deductItemFurniture(String itemid, int qty)
{
Enumeration e = funiture.elements();
String[] tmpItem;
String id="";
String name="";

int price=0;
int units = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
if(itemid.equals(tmpItem[0]))
{
units = Integer.parseInt(tmpItem[3]);
if(qty >= units)
removeItemFurniture(itemid);
else
{
id = tmpItem[0];
name=tmpItem[1];

VI BCA 65
 ONLINE EVENT MANAGEMENT SYSTEM

price=Integer.parseInt(tmpItem[2]);
units = units - qty;

removeItemFurniture(itemid);
addItemFurniture(id,name,price,units);
}

break;
}
}
}
public void updateQuantityFruniture(String itemId, int quantity) {
if (funiture.contains(itemId)) {
String[] tmpItem = (String[])funiture.get(itemId);
tmpItem[3] = Integer.toString(quantity);
}
}

public Enumeration getEnumerationFurniture() {

return funiture.elements();
}

public float getCostFurniture() {

Enumeration e = funiture.elements();
String[] tmpItem;
int totalCostf = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
totalCostf += Integer.parseInt(tmpItem[1]) * Integer.parseInt(tmpItem[2]);
}
return totalCostf;

VI BCA 66
 ONLINE EVENT MANAGEMENT SYSTEM

public int getNumOfItemsFurniture() {

Enumeration e = funiture.elements();
//String[] tmpItem;
int numf = 0;

while (e.hasMoreElements()) {
numf++;
}

return numf;
}

//HASHTABLE FOR PHOTO/VIDEO CART

public void addItemPhoto( String itemname, int rate,int numunits) {

if(numunits > 0){
String[] item = {itemname, Integer.toString(rate),Integer.toString(numunits)};
photo.put(itemname, item);
}
}

public void removeItemPhoto(String itemname) {

if (photo.containsKey(itemname))
{

photo.remove(itemname);
}
}
public void deductItemPhoto(String itemname, int qty)

VI BCA 67
 ONLINE EVENT MANAGEMENT SYSTEM

{
Enumeration e = photo.elements();
String[] tmpItem;
String id="";
String name="";
int price=0;
int units = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
if(itemname.equals(tmpItem[0]))
{
units = Integer.parseInt(tmpItem[2]);
if(qty >= units)
removeItemPhoto(itemname);
else
{
name=tmpItem[0];
price=Integer.parseInt(tmpItem[1]);
units = units - qty;

removeItemPhoto(itemname);
addItemPhoto(name,price,units);
}

break;
}
}
}
public void updateQuantityPhoto(String itemId, int quantity) {
if (photo.contains(itemId)) {
String[] tmpItem = (String[])photo.get(itemId);
tmpItem[3] = Integer.toString(quantity);

VI BCA 68
 ONLINE EVENT MANAGEMENT SYSTEM

}
}

public Enumeration getEnumerationPhoto() {

return photo.elements();
}

public float getCostPhoto() {

Enumeration e = photo.elements();
String[] tmpItem;
int totalCostp = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
totalCostp += Integer.parseInt(tmpItem[1]) * Integer.parseInt(tmpItem[2]);
}
return totalCostp;
}

public int getNumOfItemsPhoto() {

Enumeration e = photo.elements();

int nump = 0;

while (e.hasMoreElements()) {
nump++;
}

return nump;
}

VI BCA 69
 ONLINE EVENT MANAGEMENT SYSTEM

//HASHTABLE FOR DECORATION CART

public void addItemDecoration(String itemtype, String itemname, int rate, int qty) {

String[] item = {itemtype,itemname, Integer.toString(rate),Integer.toString(qty)};

decoration.put(itemtype, item);

public void removeItemDecoration(String itemname)

{
if (decoration.containsKey(itemname))
{
decoration.remove(itemname);
}

}
/*public void deductItemDecoration(String itemname, int qty)
{
Enumeration e = decoration.elements();
String[] tmpItem;
String id="";
String name="";
int price=0;
int units = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
if(itemname.equals(tmpItem[0]))
{
units = Integer.parseInt(tmpItem[2]);
if(qty >= units)
removeItemDecoration(itemname);

VI BCA 70
 ONLINE EVENT MANAGEMENT SYSTEM

else
{
name=tmpItem[0];
price=Integer.parseInt(tmpItem[1]);
units = units - qty;

removeItemDecoration(itemname);
addItemDecoration(name,price,units);
}

break;
}
}
}*/
/*public void updateQuantityDecoration(String itemId, int quantity) {
if (decoration.contains(itemId)) {
String[] tmpItem = (String[])decoration.get(itemId);
tmpItem[3] = Integer.toString(quantity);
}
}*/

public Enumeration getEnumerationDecoration() {

return decoration.elements();
}

public float getCostDecoration() {

Enumeration e = decoration.elements();
String[] tmpItem;
int totalCostd = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();

VI BCA 71
 ONLINE EVENT MANAGEMENT SYSTEM

totalCostd += (Integer.parseInt(tmpItem[2]) * Integer.parseInt(tmpItem[3]));

}
return totalCostd;
}

public int getNumOfItemsDecoration() {

Enumeration e = decoration.elements();

int numd = 0;

while (e.hasMoreElements()) {
numd++;
}

return numd;
}

//HASHTABLE FOR MUSIC CART

public void addItemMusic(String itemname, int rate) {

String[] item = {itemname, Integer.toString(rate)};

music.put(itemname, item);

public void removeItemMusic(String itemname) {

Enumeration e = music.elements();
while (e.hasMoreElements())
{
if (music.containsKey(itemname))

VI BCA 72
 ONLINE EVENT MANAGEMENT SYSTEM

{
music.remove(itemname);
break;
}
}
}
/*public void deductItemDecoration(String itemname, int qty)
{
Enumeration e = decoration.elements();
String[] tmpItem;
String id="";
String name="";
int price=0;
int units = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
if(itemname.equals(tmpItem[0]))
{
units = Integer.parseInt(tmpItem[2]);
if(qty >= units)
removeItemDecoration(itemname);
else
{
name=tmpItem[0];
price=Integer.parseInt(tmpItem[1]);
units = units - qty;

removeItemDecoration(itemname);
addItemDecoration(name,price,units);
}

break;

VI BCA 73
 ONLINE EVENT MANAGEMENT SYSTEM

}
}
}*/
/*public void updateQuantityDecoration(String itemId, int quantity) {
if (decoration.contains(itemId)) {
String[] tmpItem = (String[])decoration.get(itemId);
tmpItem[3] = Integer.toString(quantity);
}
}*/

public Enumeration getEnumerationMusic() {

return music.elements();
}

public float getCostMusic() {

Enumeration e = music.elements();
String[] tmpItem;
int totalCostm = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
totalCostm += Integer.parseInt(tmpItem[1]);
}
return totalCostm;
}

public int getNumOfItemsMusic() {

Enumeration e = music.elements();

int numm = 0;

VI BCA 74
 ONLINE EVENT MANAGEMENT SYSTEM

while (e.hasMoreElements()) {
numm++;
}

return numm;
}

//HASHTABLE FOR MAKE-UP CART

public void addItemMakeup(String itemname, int qty, int rate) {

if(qty > 0){
String[] item = {itemname, Integer.toString(qty), Integer.toString(rate)};
makeup.put(itemname, item);
}
}

public void removeItemMakeup(String itemname) {

if (makeup.containsKey(itemname))
{
makeup.remove(itemname);

}
public void deductItemMakeup(String itemname, int qty)
{
Enumeration e = makeup.elements();
String[] tmpItem;
String id="";
String name="";
int price=0;

VI BCA 75
 ONLINE EVENT MANAGEMENT SYSTEM

int units = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
if(itemname.equals(tmpItem[0]))
{
units = Integer.parseInt(tmpItem[1]);
if(qty >= units)
removeItemMakeup(itemname);
else
{
name=tmpItem[0];
price=Integer.parseInt(tmpItem[2]);
units = units - qty;

removeItemMakeup(itemname);
addItemMakeup(name, units, price);
}

break;
}
}
}
/*public void updateQuantityDecoration(String itemId, int quantity) {
if (decoration.contains(itemId)) {
String[] tmpItem = (String[])decoration.get(itemId);
tmpItem[3] = Integer.toString(quantity);
}
}*/

public Enumeration getEnumerationMakeup() {

return makeup.elements();
}

VI BCA 76
 ONLINE EVENT MANAGEMENT SYSTEM

public float getCostMakeup() {

Enumeration e = makeup.elements();
String[] tmpItem;
int totalCostma = 0;
while (e.hasMoreElements())
{
tmpItem = (String[])e.nextElement();
totalCostma += Integer.parseInt(tmpItem[1]) * Integer.parseInt(tmpItem[2]);
}
return totalCostma;
}

public int getNumOfItemsMakeup() {

Enumeration e = makeup.elements();

int numma = 0;

while (e.hasMoreElements()) {
numma++;
}

return numma;
}

VI BCA 77
 ONLINE EVENT MANAGEMENT SYSTEM

10. CONCLUSION AND FUTURE ENHANCEMENTS

CONCLUSION:

This web application is easy to use and user-friendly software. End-users are
expected to have some experience in using windows applications and browsing
the Internet. Event booking can be done through web is a very useful module in
this application. Clients can get appropriate information with less efforts and
time.

FUTURE ENHANCEMENTS:

 Booking can be made through mobile phones.

 Auditors can be involved for advising corporates.
 User involvement can be increased.
Etc.,

VI BCA 78
 ONLINE EVENT MANAGEMENT SYSTEM

11. BIBLIOGRAPHY

1) Books Referred:

 Software Engineering by Roger Pressman

 Beginning JSP – Wrox Publication
 Database Systems by Abraham Silberschatz
 Oracle 10g by Gary Cornell and Horstman.

2) Websites referred:

 www.w3schools.com/html
 www.htmlcodetutorial.com/
 http://en.wikipedia.org

VI BCA 79