EVENT MANAGEMENT SYSTEM

Undertaken at

“Sri Guru Tegh Bahadur Institute of Management & Information Technology”

Submitted in the partial fulfillment of the requirements for the award of the degree of

BACHELOR OF COMPUTER APPLICATIONS

Of

GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY, DELHI

Under Supervision of: Submitted by:

Ms. Ashmeet Kaur Gauravneet Singh

(Asst. Prof. S.G.T.B.I.M. & I.T.) 35690202015

Session 2015- 2018

SRI GURU TEGH BAHADUR INSTITUTE OF MANAGEMENT

&INFORMATION TECHNOLOGY
Affiliated to Guru Gobind Singh Indraprastha University, Delhi
 DECLARATION

I, Gauravneet Singh of BCA course in Sri Guru Tegh Bahadur Institute of

Management and Information Technology, hereby declares that the project report
entitled “ Event management system” is an original work and the same has not been
submitted to any other institute for award of any other degree or diploma.

Date: Gauravneet Singh

35690202015

2
 CERTIFICATE

This is to certify that Gauravneet Singh University Enrollment Number –

35690202015 has worked under my supervision to prepare this project report of
“Event management system”. This work embodied in this report is original & is of
the standard expected of B.C.A. Student & has not been submitted in part or full to
this or any university for the award of any degree or diploma he has completed all
requirements of guidelines for research project & the work is fit for evaluation.

Date:

Signature of HOD:
Dr. Harshita Tuli

Signature of Guide:
Ms. Ashmeet Kaur

3
 ACKNOWLEDGEMENT
It is nearly impossible for an individual to entirely complete a project work herself.
Help in some form or other is needed by everyone from others. I am really fortunate
enough to get support from my friends and faculties.

I am whole-heartedly thankful to my HOD(IT) Dr. Harshita Tuli for providing me a

great opportunity to work in a great learning atmosphere & for their esteem guidance,
persistent encouragement and deep involvement in important discussion throughout
my project work.

I sincerely thank my mentor Ms. Ashmeet Kaur who is always my inspiration and a
pleasant guru. It is from him I discovered the ‘art of thinking’, technically anything
and everything. I aspire, his achievements to be my strong and certain long-term
goals.I wish to express my thanks to my entire Event management system team for
their ever present helping hand and nice company which made me enjoy my work
more. I am also grateful to all those friends who helped me during the progress of this
project. Without their help this research would not have been completed. I am really
very thankful to them for giving me their precious time and relevant information and
experiences I required; without which this project would have been a different story.

I would also like to express my gratitude to entire B.C.A. Department and my team
members.

Gauravneet Singh
35690202015

4
 ABSTRACT
This project on Event management system uses java advance at front end and
MYSQL at back end. Event management system is a Website that can be accessed by
any person who is interested in sharing about the music events, gigs for the music,
and can contact anyone for their band, for solo music and many more.

This website saves the valuable time of the users and the users can easily interact with
the website in few steps.

This report describes my implementation of a Event management system I have

created the database using MYSQL and populated it with some sample data.
 TABLE OF CONTENT
Chapter Topic Page
No. No.
1 INTRODUCTION 11
1.1 About the organization 12
1.2 Problem statement 13
1.3 Propose solution 14
2 REQUIREMENTS AND ANALYSIS 16
2.1 Hardware requirement 17
2.2 Software requirement 18
2.3 Introduction 20
2.4 Technology required 20
2.5 Software development lifecycle 20

2.6 Feasible study 22

2.7 Technical feasibility 22

2.8 Economical feasibility 23

2.9 Cost 23

2.10 Operational feasibility 24

3 SOFTWARE DESIGN 26

3.1 Dataflow Diagram 28

3.2.1 Context Diagram 29
4 DATABASE DESIGN 33
4.1 Entity Relation Diagram 35
4.2 Introduction 36
5 TEST REPORT 39
5.1 Introduction 40
5.2 Unit testing 41
5.3 Integration testing 42
5.4 System Testing 43
6 ROLES & RESPONSIBILITY 46

6
7 CONCLUSION 48
8. BIBLOGRAPHY 50
9. Appendices 51

7
 LIST OF FIGURES
S.no Figure Page
No.
1 Figure 2.1 : The Waterfall Model 21

2 Figure 2.2 :Use Case 25

3 Figure 3.2.1 : Context Flow Diagram 29

4 Figure 3.2.2 : Data Flow Diagram Level-1 30

5 Figure 3.2.3 : Data Flow Diagram Level-2 31

6 Figure 4.1: E-R Diagram 35

8
 List of Tables

S.No Figures Page no.

1 Table 4.1candidate masters 36

2 Table 4.2 event masters 37

3 Table 4.3 login 37

4 Table 4.4 venue masters 38

5 Table 4.5 registration masters 38

9
 TABLE OF SCREENSHORTS

S.N0 Figures Page no.

1 Table Home Page 69

2 Table about us 70

3 Table user view 71

4 Table create user 72

5 Table view data 73

10
 CHAPTER: 1
INTRODUCTION

11
1.1 ABOUT THE ORGANISATION

ICL is a leading global Technology and IT Enterprise with annual revenues of US$ 4.9 billion.
The ICL Enterprise comprises two companies listed in India, ICL Technologies and ICL Info
systems. The 3 decade old enterprise, founded in 1976, is one of India's original IT garage
startups. Its range of offerings span R&D and Technology Services, Enterprise and Applications
Consulting, Remote Infrastructure Management, BPO services, IT Hardware, Systems
Integration and Distribution of Technology and Telecom products in India. The ICL team
comprises 55,000 professionals of diverse nationalities, operating across 18 countries including
360 points of presence in India. ICL has global partnerships with several leading Fortune 1000
,includings everal IT and Technology majors.

Products & Services

Product Engineering & Technology Development
The Engineering and R & D services department runs the largest outsourced engineering center
outside the US which is a testimony to the 30 year product engineering experience. The company
offers a comprehensive range of R&D and Engineering services to component vendors, OEMs,
ODMs and ISVs across multiple industry segments and domains.

Career Development Centre (CDC)

As the training arm of ICL Infosystems, ICL Career Development Centre (CDC) carries forth a
legacy of excellence spanning across more than three decades. ICL CDC is an initiative that
enables individuals and organizations to benefit from ICL's deep expertise in the IT space.
Among the fastest growing IT education brands in India, ICL CDC offers a complete spectrum
of quality training programs on software, hardware, networking as well as global certifications in
association with leading IT organizations worldwide.

BPO
Business Processing Outsourcing is heading towards a maturity level where a new form of BPO,
called Transformational BPO, is evolving that constitutes Full Process Outsourcing and Multiple
Process Outsourcing .

IT Hardware
ICL Infosystems portfolio of products covers the entire spectrum of the information technology
needs of its customers. By virtue of the immense diversity of markets and customers that it
address, ICL Infosystems products offerings include everything from high end enterprise level
servers for mission critical applications to multimedia home computers.

12
1.2 PROBLEM STATEMENT

Online event Management System is the software project that gives us the information about
which Events are going to be organized by ICL Infosystems and at which venue in our country.
Event Management is a process of researching, planning, marketing, executing, and evaluating
an event. So, Event Management is the application of the management practice of project
management to the creation and development of festivals and events.

The industry now includes events of all sizes from the advertising down to a breakfast meeting
for ten business people. Every industry, charity, society and group will hold events of some
type/size in order to market themselves, build business relationships, raise money or celebrate.

This system consists of the modules like candidate registration, login forms, add/update event,
add/update venue, add/update venue, view company information, view venue info, view events
info.

Manually keeping record for each and every event that are going to held in company is not
possible today. We requires a simple but powerful mean of keeping the information about all the
events that are going to held in such a way that we can receive output in effective and efficient
manner.

13
1.3 PROPOSED SOLUTION

The projects aims at creation of an Online Event Management System for the organization to
manage its events effectively and efficiently. This Software is accessible to all the user that are
registered by the administrator. Administrator can obtain the registration fees from the different
user according to the role and functionalities provided to the user. This solutions aims that the
organization is responsible for organizing their own events and does not provide any support for
the events of other organization.
There are following groups of user in an organization

 Administrator: Administrator is responsible for registering new users and managing all
the events that are going to held in the organization. There is no another way for
registering the new user they can be only registered by the administrator after the user
pays the amount that he is eligible for. Other than, the user registration administrator also
responsible for selecting the venues according to the facilities provided by these venues.
Administrator also responsible for managing the complete events.
 User: User are registered by the administrator. After the registration they get a unique
User Id i.e Registration Number and password. After the first login the user can change
his password but he cannot change his user id. With the use of his user id he can register
himself with the events that are going to held in the organization.

The OMS provide the different facalities for user and administrator of the organization which he
can access after the valid login.

Functionality provided to Administrator:

 Registration for Candidate.
 Inclusion of new venues
 View details of all candidates, events, venues, companies, branches.
 User friendly forms to add, update and show the details of candidates, events, venues,
companies, branches.
 Administrator is capable of adding the new events, updating the venue, time and other
details about the events.
 Administrator is also capable of modifying the new events, updating the venue, time and
other details about the events.
 Administrator can also make use of search option to search the events, user, venues etc.
 Administrator is able to print the daily, weekly, monthly or yearly reports for number of
user who attends the events.

14
Functionalities provided for user
 Login facility is provided for user to view their home screen.
 Users have to register themselves by filling the online forms, with the unique Userid and
register themselves for the events.
 There are two types of Events- Cultural Events and Vocational (carrier oriented) events
or seminars.
 User can also make use of search option to search the events, user, venues etc.

15
 CHAPTER - 2
Requirement & Analysis

16
2.1 HARDWARE REQUIREMENTS

Hardware Requirements for server:

Component Specification
Processor Pentium 4 Class processor
Memory 512 MB RAM or Higher
Hard Drive(HDD) 80 GB or Higher
Floppy Drive 1.44 MB
Modem 56 KBPS
Monitor 17’’Samsung Color Monitor
Keyboard Samsung Pleomax Qwerty Standard Keyboard
Mouse Optical
Power Supply 600 VA Luminous
CD/DVD Writer 52X LG
MotherBoard Intel 915 G
Cabinet P4 ATX
Printer HP Laserjet

Hardware Requirements for Clients:

Component Specification
Processor Pentium 4 Class processor
Memory 256 MB RAM or Higher
Hard Drive(HDD) 40 GB or Higher
Floppy Drive 1.44 MB
Modem 56 KBPS
Monitor 15’’Samsung Color Monitor
Keyboard Samsung Pleomax Qwerty Standard Keyboard
Mouse Optical
Power Supply 600 VA Luminous
CD/DVD Writer 52X LG
MotherBoard Intel 915 G
Cabinet P4 ATX
Printer HP Laserjet

17
2.2 SOFTWARE REQUIREMENTS
Software Requirements:

Operating System Linux, Windows XP professional or Higher

Front End Java, Servlet, JSP, JDBC, HTML, Java Script

Back End MYSQL

Application Server Web-Logic

Browser Mozilla Firefox, Internet Explorer,

Documentation Tool Microsoft Office 2007

18
2.2.1 SOFTWARE REQUIREMENTS SPECIFICATION

Introduction
Purpose
The main objective of this document is to illustrate the requirements of the project ONLINE
EVENT MANAGEMENT SYSTEM. The document gives the detailed description of the both
functional and non-functional requirements proposed by the client. The document is developed
after a number of considerations with client and considering the complete requirement
specifications of the given project. The final product of the team will be meeting the
requirements of this document.

Document Conventions
The following are the list of conventions and acronyms used in this document and project as
well:
 Administrator: A login id, role and Branch Id representing a user with user
administration privileges to the software ONLINE EVENT MANAGEMENT
SYSTEM.
 User: A general login id and role assigned to most users that are customers of the system.
 Client: Is the company for which the system is developed.
 SQL: Structured Query Language, used to retrieve information from Database.
 HTML: Hyper text markup Language used to format a Web page on server and delivered
to browser.
 User Interface Layer: The section of assignment referring to what the user of ONLINE
EVENT MANAGEMENT SYSTEM interacts with directly.
 Data Storage Layer: The section of this assignment referring to where all data is
recorded.
 Data Flow Diagram: It shows the dataflow between the entities.
 Use Case: A broad level diagram of project showing a basic overview.
 Interface: something used to communicate across different medium.
 Primary key: Used to differentiate entities in a database.

19
2.3 Introduction
Requirement analysis is done to analyze, refine and scrutinize requirements to make
consistent and unambiguous requirements.

Steps in Requirement Analysis

Draw the
context
diagram

Develop
Prototype
(Optional)
Model the
Requirements

Finalize the
Requirements

Figure 2.1 Requirement Analysis

Requirement Analysis Steps

2.4 Technologies Required

Following is a tabular representation of the technology to be used for the developmentof the
proposed solution:
System Requirements
Operating System Windows/Linux
Frontend Designing PHP
Data Base MySQL

2.5 Software Development Life Cycle

20
 The software development life cycle (SDLC) is the process based standard practice to
develop any kind of software product. These processes are categories as phases in SDLC and
related to different activities. Different models are described in software engineering text books,
but none is fully satisfied all the need of a software companies. Some SDLC models are Water
Fall Model, Spiral Model, and Prototype Model etc.

OUR PROJECT IS BASED ON WATERFALL MODEL

Requirement
Analysis and
specification

Design

Implementation and
Unit Testing

Integration and
System Testing

Operation and
Figure 2.2: The Waterfall Model maintenance

Figure 2.2 waterfall model

The different phases of a typical SDLC are as:

Request for Project (RFP)

The first stage is the RFP wherein a request to start a project is made. The request can be
made either by the tip management or end users.
Detailed requirement Gathering
As the PRF is signed off /approved, requirement gathering starts.
Business Analysts gather the requirements from the user and prepare a SRS document. This
document then needs to be signed off by the user to approve that the requirements mentioned in
SRS have been rightly comprehended.
Design
After the SRS sign off, design phase starts, wherein the software development starts at
the vendors end. Here also, two types of documents are prepared.
 High Level design Documents

21
 These documents contain Data Flow diagrams, Process Flow Charts etc. This document
some time called Architecture Design Document, because it described the architecture view of
the proposed software product.

 Low Level Design Documents

These contain the database level design information i.e. the details about the fields etc.
This document described the pseudo code for the various algorithms or logic used to build the
software. This documents contained module level design of the software.
Development
Post finalization of the software design, development team uses the design document to
develop individual software units.
Post completion of development, the development team does the unit testing and initiates System
Integration Testing (SIT).
On successful completion of testing, the software is released for UAT (User Acceptance
Testing).
Testing
Before software is deployed it is tested to check if it meets all the requirement criteria. For this, a
System Test Plan with System Test Cases is prepared.
Implementation After the User signs off the developed software, a pilot is implemented.
Maintenance It is the post implementation maintenance, wherein the performance of the
software is monitored.

2.6 FEASIBILITY STUDY

When complex problems and opportunities are to be defined, it is generally desirable to conduct
a preliminary investigation called FEASIBILITY STUDY. A feasibility study is conducted to
obtain an overview of the problem and to roughly assess whether the feasible solutions exist
prior to committing substantial resources to an information systems development project.
Feasibility study involves investigating the information needs of the prospective end users and
the objectives, constraints, basic resource requirements, costs, benefits and feasibility of a
proposed project.
By intent, the feasibility study is very rough analysis of the viability of the project. It is,
however, a highly desirable checkpoint that should be completed before committing more
resources.
The outcome of the feasibility study is very clear. So, depending upon the aspect on which
feasibility is being done is categorized into following classes: -
 Technical feasibility
 Economical Feasibility
 Operational Feasibility

2.7 Technical Feasibility

In technical Feasibility, the following issues are taken into consideration:
 Whether the required technology is available or nor?
 Whether the required resources are available –
Manpower-programmers, testers and debuggers
Software/Hardware

22
Therefore, it is mainly concerned with the satisfying equipment i.e. hardware and software that
will successfully satisfy the user requirements. The technical needs of the system may vary, but
might include:
 The facility to produce outputs in a given time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to a distant location
After examining the technical feasibility, we give more importance to the configuration of the
system than the actual make of the hardware. The configuration gives the complete and true
picture of the system’s requirements. The proposed system can be operated on a two PC. The PC
will have its own color monitor, keyboard and mouse. And it will also require a peripheral device
i.e. a printer. The computer system should have enough speeds of input and output to achieve a
good quality printout. The software, which has been used in the proposed system, is Microsoft
Visual Basic and Microsoft Access. These software’s are very popular and easily available in the
market. The system can be upgraded from time to time when new versions of software are
available from either the Internet or in the market. If by any chance our operating system doesn’t
support a particular type of hardware then we can install the hardware equipment again using its
device driver. And if we don’t have the device driver available then we can download that
particular device driver using the Internet to suit to our requirements.
The main problem of running after the programmer who developed the system or generated the
system as now any software engineer will be able to solve the problem, which may occur in the
future. It is also important to consider the monetary factors also. Since it might happen that
developing a particular system may be technically possible but it may require huge investments
and benefits may be less. For evaluating this, economic feasibility of the proposed system is
carried out.

2.8 Economical Feasibility

It is the most frequently used method for evaluating the effectiveness of the system. The
procedure is to determine the benefits and savings that are expected from the system in
comparison with the cost involved. If the benefits outweigh the cost, then the system is said to be
economically feasible. Economic analysis is the most frequently used technique for evaluating
the effectiveness of a proposed system. It is more commonly known as COST/BENEFIT
ANALYSIS.

2.9 Cost/Benefit analysis of the proposed system

 Cost Analysis
In case of computerization, the cost involvement is not that high as it was 5-7 years back. For
this project to run successfully, the office initially requires a Desktop computer, a printer and a
UPS to maintain continuous supply of electricity.
Cost of stationary (ink cartridges, printing paper) involves approximately Rs.1000. The cost of
electricity is incurred at Rs.1, 000 per year.
One person has to be hired who have the knowledge about the operation of computers.
Miscellaneous expenditure will be around Rs.2000 per annum.
 Benefit Analysis
As it is necessary to do cost analysis of the developed project, it is also very essential to
do benefit analysis along with it. The analysis of the benefit arising from the use of the
23
 software named “Issue Management System” has been done in a very efficient manner.
The points that have been kept in mind while performing the task of benefit analysis of
the software are as follows:
 Stationary cost
The cost of purchasing stationary is also very high. It includes the cost of record registers to
maintain records of the Employees, Projects running and the issues given to the Employees,
pens, cost of photocopying daily. But, after the implementation of the proposed software, all the
record maintenance has become fully computerized; this step would save a big amount of
money, which was previously used for purchasing the stationary. Now, all the work for which a
large amount of stationary was required before can now be done using a computer.

2.10 Operational Feasibility

It is mainly related to human organizational and political aspects. For operational feasibility
study we appointed a small group of people, which included the office employees. This group
worked with the new system and found that the system was very user friendly, and very efficient.
It was found that no special training was required to operate the system. The burden of the
project manager who wants to give the issue to other employees and other staff members was
reduced. It takes about 5 minutes to enter the issue details as compared to the 30-40 minutes of
the manual system. And the employees found that they can prepare the statistical reports with
more speed, accuracy and in very less time.

24
USE CASE DIAGRAM

25
 ```

Login

View Events

Administrator

User
Add Events

USER
ADMIN Add Venue

User Registration

Search

Reports

Event Registration

Edit Events

Use-Case Diagram
Logout

FeedbackF

Figure 2.3 Usecase diagram

26
 Chapter-3
Software Design

Data Flow Diagrams (DFDs)

As information moves through software, it is modified by a series of transformation. A data flow
diagram is a graphical representation that depicts Information flow and the transforms that are
applied as data move from input to output. . The data flow diagram may be used to represent a

27
system or software at any level of abstraction. In fact, DFDs may be partitioned into levels that
represent increasing Information flow and functional detail. Therefore, the DFD provides a
mechanism for functional modeling as well as information flow modeling. Data Flow
Diagramming is a means of representing a system at any level of detail with a graphic network of
symbols showing data flows, data stores, data processes, and data sources/destination. The data
flow diagram is analogous to a road map. It is a network model of all possibilities with different
detail shown on different hierarchical levels. This processes of representing different details level
is called “leveling” or “partitioning” by some data flow diagram advocates. Like a road map,
there is no starting point or stop point, no time or timing, or steps to get somewhere. We just
know that the data path must exist because at some point it will be needed. A road map shows all
existing or planned roads because the road is needed. Details that is not shown on the different
levels of the data flow diagram such as volumes, timing, frequency, etc. is shown on
supplementary diagrams or in the data dictionary. For example, data store contents may be
shown in the data dictionary.
A data flow diagram shows the logical flow of the system. For a system it describes the input
(source), output (destination), database (data stores) and procedures (data flows) all in a format
that meets the user’s requirement. When analysis prepares the logical system design, they specify
the user needs at a level of detail that virtually determines the information flow into an out of the
system and the required data resources. The logical design also specifies input forms and screen
layouts. The activities following logical design are the procedure followed in the physical design
e.g. producing programs, software, file and a working system. Design specifications instruct the
user about what the system should do

28
3.1.1 Context Diagram
A level 0 DFD is called fundamental system model or context model represents entire software
element as a single bubble with input and output data indicating by incoming & outgoing arrows.

Login
USER EVENT Create event
MANAGEMENT View event
ADMIN
SYSTEM Venue
f

Event create Venue

Figure 3.2.1

29
 REGISTRATION
REGISTRATIO
N

LOGIN

REGISTRATION

VENUE
VENUE
UPDTAE
ADMIN DETAIL VENUE

CREATE
EVENT
CREAT
EVENT EVENT
USER E

USER

CREAT CRETA ADD

CREATE
E CREATE
E USER
USER
ID
DETAIL
ADD
EVENT
EVENT VENUE
VENUE DETAILS ID

EVENT VENUE USER

LEVEL 1.DFD

30
ADMIN

LOGIN

2.1
UPDATE
EVENT
2.
MANAGE
EVENT
2.2
CREATE
EVENT
EVENT

2.3
DELETE
EVENT

2.4
VIEW
EVENT

3.1

3. UPDATE
USER

MANAGE
USER
USER
3.2

DELETE
USER

3.3

CREATE
USER

LEVEL 2ND DFD

31
USER

LOGIN LOGIN

VIEW
EVENT
DETAILS EVENT

CREATE
EVENT

UPDATE
EVENT

EDIT
PERSONAL USER
DETAILS

LEVEL 2ND DFD

32
CHAPTER-4
DATABASE
DESIGN

33
4.1 Entity Relationship Diagram
An entity- relationship (ER) diagram is a specialized graphic that illustrates the relationship
between entities in a database ER diagrams often use symbols to represent three different types of
information. Boxes are commonly used to represent entities. Diamonds are normally used to
represent relationships and ovals are used to represent attributes.
Symbols that used for ER Diagram are:

Symbol Function

Flow of information

Entity – something that can be recognized

separately

Relationship among entities

Attributes – properties that identify an entity

34
 ER DIAGRAM

Figure 4.1 ER DIAGRAM

35
4.2 Introduction
Database design is the process of producing a detailed data model of a database. This logical data model
contains all the needed logical and physical design choices and physical storage parameters needed to
generate a design in a data definition language, which can then be used to create a database. A fully
attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different parts of the design of an overall database
system. Principally, and most correctly, it can be thought of as the logical design of the base data
structures used to store the data. In the relational model these are the tables and views. In an object
database the entities and relationships map directly to object classes and named relationships. However,
the term database design could also be used to apply to the overall process of designing, not just the base
data structures, but also the forms and queries used as part of the overall database application within the
database management system (DBMS)
Table Structure:

Following are the different tables that are used in ONLINE EVENT MANAGEMENT SYSTEM.
Figure 4.1

1.) USER

36
Figure 4.2

Table 1.2 Event

Figure 4.3

Table 1.3 Login

Figure 4.4

Table 1.4 Venue

37
Figure 4.5

Table 1.5 Registration

38
CHAPTER – 5
TESTING

39
Software Testing is any activity aimed at evaluating an attribute or capability of a program or
system and determining that it meets its required results. Testing is very important but an
expensive activity. It is more than just running a program with the intention of finding faults.
Every project is a new project with different parameters. So, No Single yardstick may be
applicable in all circumstances.

First Step in testing is to prepare a Test Plan. A Test Plan of the product entails the following
activities.

1.) Prepare a Test Plan- The plan made for the product consist of the following

 Outputs expected from the System. The outputs from the system include:

a.) Validation of each and every field.

b.) Low Load
c.) High Usability
d.) High Performance

 Volume of Test Data is Prepared

 Procedure of using the Test Data is written.

2.) Test Data is prepared for program Testing.

1.) Test Data is prepared for Transaction Path Testing.

Software Testing is an important phase of Software Development Life Cycle (SDLC). We

execute the program with given inputs and note down the observed outputs. These are then
compared with the expected outputs. If there is match between observed and expected outputs
then the program is said to be as per user’s specifications, else there is something wrong
somewhere in the program.

40
5.1 Unit Testing

Methodology Used:

Unit Testing is the process of taking a module and running it in an isolation from the rest of the
software product by using prepared test cases and comparing the actual results with the results
predicted by the specification and design module.

Tools Used:

For the Unit Testing a URL tool is used name QaTest. Following URL is used
www.qatest.co.in/rail.

41
5.2 Integration Testing

A system is composed of multiple components or modules that comprise hardware and software.
Integration is defined as the set of the interactions among components. Testing the interaction
between the modules and interaction with other systems externally is called as integration
testing.

Methodology Used:

Big Bang Strategy is used for integration testing of Online Event Management System.
Instead of integrating component by component and testing, this approach waits till all
components arrive and one round of integration testing is done. This is known as ‘Big Bang’
Integration Testing. It reduces testing effort and removes duplication in testing for the multi step
component integrations. Big Bang integration is deal for a product where the interfaces are stable
with less number of defects.

Tool Used:

Doit- A simple Web Application Testing. Doit is a scripting tool and language for testing Web
Applications that use forms. Doit can generate random or sequenced form fill-in information,
report results(into a database), filter HTML results, and compare results to previous results,
without having to manually use a web browser. It uses a console based Web Client Tool to send
and receive HTTP requests and responses respectively.

DreamWeaver: This is the tool which checks for the broken links. This is the automated tool for
creating both design and code for the WebPages. Dreamweaver is a web development
application program and it is available for both Mac and Window Operating System.

Firebug: The firebug plugin for Mozilla Firefox enables on the fly debugging, editing, and
monitoring of a web site’s CSS, HTML, DOM and Java Script, though these edits aren’t saved
on the fly. Firebug also provides other web-development tools such as HTTP header monitoring,
the download time, Image Download and so on.

Test Cases:

The integration testing test Cases include:

GUI interaction Checking I.e Link Checking, Load Checking among Modules, Performance
checking among Modules.

42
5.3 System Testing:
System Testing focuses on a complete, integrated System to evaluate compliance with specified
requirements. Tests are made on characteristics that are only present when the entire system is
run.

System Testing can be of Functional Testing or Non-Functional Testing. Where the functional
testing is considered with testing the functionalities of the product but Non functional testing is
considered with testing the quality factors.

Functional Testing:

Methodology Used: The methodology used is testing the product from module to whole
application taking the application as the full unit.

Tools Used:

Firebug: Open Source add-on tool for Firefox – allows editing, debugging, and monitoring of
CSS, HTML, and Java Script live in any Web Page. Monitor network activity, visualize CSS
metrics, information about errors in the JavaScript, CSS, and XML. Includes DOM explorer;
execute Java Script on the fly.

Test Cases:

1.) Functionality Testing- In Testing the functionality of the websites the following are tested:
 Links
 Internal Links
 External Links
 Mail Links
 Broken Links

 Forms
 Field Validations
 Error Messages for wrong Input
 Optional and mandatory fields

 Database Testing will be done on the database to ensure the Database Integerity.

43
Non-Functional Testing:

Methodology Used:

The methodology used is testing the product from module to whole application taking the whole
application as the full unit.

Tools Used:

Stress Tester- Enterprise Load and performance testing tool for web applications from Reflective
Solutions Ltd. Advanced user Journey modeling, scalable load, System resources monitors and
results analysis. No Scripting required. Suitable for any Web application, JMS, IP or SQL
Application.

Load Storm- A Web based load testing tool/services as a distributed application that leverages
the power of Amazon Web Services to scale on demand with processing power users, LoadStorm
automatically adds machines from Amazon’s Server farm to handle the processing. Tests can be
built using the tool in such a way as to simulate a large number of different users with unique
logins and different tasks.

Test Cases:

Performance Testing- It is done to understand the website’s scalability.

 Connection Speed- Connection Speed is tested over various networks like Dial
up, ISDN etc.

 Load- Load is tested here as

 What are the numbers of users per time.
 Checking the peak load time and how system behaves at this time.
 Large Amount of Data accessed by User.

 Stress-
 Continuous Load
 Performance of Memory, CPU, Database etc.

 Usability Testing- It is the process by which the human-to-Computer Interaction

characteristics of a system are measured, and weakness are identified for connection.
 Ease of Learning
 Navigation
 Subjective user satisfaction
 General Appearance

 Server Side Interface- This testing to verify that communication is done properly.
Compatibility of server with software, Hardware, Network and Database is tested.

44
  Client Side Compatibility- The Client side Compatibility is tested along various
platforms using various browsers and resolutions.`

Acceptance Testing

In this phase after system testing that is done by the customers. The customers define a set of test
cases that will be executed to qualify and accept the product. These Test cases are executed by
the customers that are small in number. They are not written with the intention of finding defects.
Testing in detail is already over in the component, integration and system testing phase prior
product delivery to the customer. Acceptance test cases are developed by the both customer and
product organization. Acceptance test cases are black box type of tests cases. They are written to
execute near real life scenarios.

A user Acceptance Test are

 A chance to complete test software.
 A chance to completely test business process.
 A condensed version of a system.
 A comparison of actual results against expected results.

45
 CHAPTER - 6
Role & Responsibility

46
6.1.Project Roles and Responsibilities

6.1.1 ROLE

 Work as a developer, designer, tester of the application.

6.1.2 RESPONSIBILITIES

 Work on definition of development requirements and priorities.

 Data migration.
 Interfaces with other systems.
 Reporting configuration and deployment.
 Set up and maintence of security rights and access permission.
 Contributing to technical strategy,policy and procedure.
 Development and operation of technical testing programmes.
 Production of technical documentation to agreed quality standards.
 Reporting on progress/issues to management and users.

47
CHAPTER – 7
CONCLUSION

48
Conclusion: Online Event Management System is a project that is created to solve the real life
problems related to organizing the events and maintaining the registration for the events by the
user. With the help of this software now the Event Manager for an organization does not need to
go to each user with the different forms for registration in respective events. Each user who is
eligible for participating / registering in the Events can go online and register themselves for the
particular events. This will really reduce the amount of paperwork that is previously needed for
successfully organizing the events.

This project has represented as challenging task to our team but in addition it has been a great
learning experience for us. Not only we have improved our java skills but we have been able to
explore alternatives in creating Client/ Server applications. Above all this, The project has laid a
strong foundation for being a improved system that can be used in real world.

49
Bibliography

 The complete Reference Java 2 :Herbert Schildt

 Java 2 Programming Bible :Walsh and Cough

 Head First Java : Kathy Sierra and Bert Bates-

 www.sun.java.com

50
Appendices

51
 LOGIN

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Event Management System....All What You need!!!!</title>
<meta name="keywords" content="" />
<meta name="description" content="" />
<link href="styles.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="bg_top">
<div id="bg_bot">

<div id="bg_bot_g">
<div id="bg_top_g">

<div id="main">
<!-- header begins -->
<div id="header">
<div id="logo"> <a href="www.hcl.com">ICL Event Management
Sytem</a>
<h2><a href="www.hcl.com">All what you need....</a></h2>
</div>
</div>
<!-- header ends -->
<div id="buttons">
<a href="index.jsp" class="but" title="">Home</a><div
class="but_razd"></div>
<a href="about_us.jsp" class="but" title="">About Us</a><div
class="but_razd"></div>
<a href="gallery.jsp" class="but" title="">Gallery</a><div
class="but_razd"></div>
<a href="license.jsp" class="but" title="">License</a><div
class="but_razd"></div>
<a href="contact_us.jsp" class="but" title="">Contact us</a>
</div>
<div style="height:10px"></div>
<!-- content begins -->
<div class="png_top"></div>
<div class="png">
<div class="cont_top"></div>
<div id="content">

52
 <div style="height:
18px;"></div>
<div id="content_razd">
<div id="left">
<!-- Java Server page coding-->

<!--SESSION MANAGEMENT-->

<%@ page import="java.sql.*" language="java" %>

<%@ page errorPage="error.jsp" %>
<%
Connection con;
ResultSet rs;
PreparedStatement pst;
String query="Select * from login where userid=? And password=? and role=? and
branchid=?";
//int ra=0;

String uid=request.getParameter("uid");
String pwd=request.getParameter("paswd");
String role=request.getParameter("role");
String bid=request.getParameter("bid");

try{
Class.forName("com.mysql.jdbc.Driver");

con=DriverManager.getConnection("jdbc:mysql://localhost/ems?"+"user=root&password=ro
ot");
pst=con.prepareStatement(query);
pst.setString(1,uid);
pst.setString(2,pwd);
pst.setString(3,role);
pst.setString(4,bid);
rs=pst.executeQuery();

if(rs.next())
{

out.println("<h1>Welcome to ICL Event Management System.</h1>");

out.println("<div style=height: 15px></div>");
out.println("<p><b>All what you need...</b> <br />");

53
 if(role.equalsIgnoreCase("Administrator"))
{
session.setAttribute("LoggedIn",new String("true"));

session.setAttribute("user_id",uid);
session.setMaxInactiveInterval(300);

response.sendRedirect("browse_events.jsp");
}
else if(role.equalsIgnoreCase("User"))
{
session.setAttribute("LoggedIn",new String("true_user"));

session.setAttribute("user_id",uid);
session.setMaxInactiveInterval(300);

response.sendRedirect("user_browse_events.jsp");
}
}
else{
out.println("<h1> Login fails</h1><br><b>Try again to Login in Home page</b>");
}

}//try block
catch(Exception e){e.printStackTrace();}

%>
<div style="clear: both; height: 12px;"></div>
</div>
<div class="cont_bot"></div>
<!-- content ends -->

<div style="height: 15px;"></div>

<!-- bottom begin -->
<div class="cont_top"></div>
<div id="bottom">

<div class="b_col1">

<h2>Contact Information</h2>
<div class="bottom_text">
<div style="height:15px"></div>
NEW DELHI<br />
Phone: +919899992586<br />
<br />

54
 E-mail:
<b>brand@info.com<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;varun2208@gmail.com</b>
</div>
</div>
<div class="b_col2">
<h2>Follow Us</h2>

<div class="bottom_text">
<div style="height:15px"></div>
<ul>
<li><img src="images/fu_i2.gif" class=" fu_i" alt="" /><a
href="#">Facebook</a></li>
<li><img src="images/fu_i3.gif" class=" fu_i" alt="" /><a href="#">Linked
in</a></li>
<li><img src="images/fu_i4.gif" class=" fu_i" alt="" /><a
href="#">twitter</a></li>
</ul>
</div>
</div>
<div class="b_col3">

<h2>Group Sites</h2>
<div class="bottom_text">
<div style="height:15px"></div>
<ul>

<li><a href="http://www.hcl-axon.com/">ICL AXON</a></li>

<li><a href="http://www.hcl-axon.com/"><strong>ICL
Technologies</strong></a></li>

<li><a href="http://www.hclinfosystems.in/"><strong>ICL
InfoSystems</strong></a></li>

<li><a href="http://www.hclbpo.com/"><strong>ICL BPO</strong></a></li>

<li><a href="http://www.hclcdc.in/"><strong>ICL CDC</strong></a></li>

</ul>
</div>
</div>

<div style="clear: both; height:1px;"></div>

</div>

55
 <div class="cont_bot"></div>
</div>
<div class="png_bot"></div>

<!-- bottom end -->

<!-- footer begins -->
<div id="footer">
Copyright 2011. Designed by <a href="http://www.metamorphozis.com/" title="Flash
Templates">Flash Templates</a><br />
<a href="#">Privacy Policy</a> | <a href="#">Terms of Use</a> | <a
href="http://validator.w3.org/check/referer" title="This page validates as XHTML 1.0
Transitional"><abbr title="eXtensible HyperText Markup Language">XHTML</abbr></a> |
<a href="http://jigsaw.w3.org/css-validator/check/referer" title="This page validates as
CSS"><abbr title="Cascading Style Sheets">CSS</abbr></a></div>
<!-- footer ends -->
</div>

</div>

<div style="text-align: center; font-size: 0.75em;">Design and Coded by Varun and

Ankur</div>

</body>
</html>

56
 LOGOUT

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Event Management System....All What You need!!!!</title>
<meta name="keywords" content="" />
<meta name="description" content="" />
<link href="styles.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="bg_top">
<div id="bg_bot">

<div id="bg_bot_g">
<div id="bg_top_g">

<div id="main">
<!-- header begins -->
<div id="header">

<div id="logo"> <a href="www.hcl.com">ICL

Event Management Sytem</a>
<h2><a href="www.hcl.com">All what you need....</a></h2>
</div>

<p align=right><font color=black size=4><u><a Style="color: White"

href="#">Search</a>&nbsp;|&nbsp;<a Style="color:White"
href="http://localhost:7001/EMS/logout.jsp">Logout</a></right>
</u></font></p>
</div>
<!-- header ends -->
<div id="buttons">
<a href="browse_events.jsp" class="but" title="">Upcoming Events</a><div
class="but_razd"></div>
<a href="build_event.jsp" class="but" title="">Build Events</a><div
class="but_razd"></div>
<a href="venue.jsp" class="but" title="">Venues</a><div
class="but_razd"></div>
<a href="browse_user.jsp" class="but" title="">Users</a><div
class="but_razd"></div>
<a href="Reports.jsp" class="but" title="">Reports</a><div
class="but_razd"></div>
</div>
<div style="height:10px"></div>
57
 <!-- content begins -->
<div class="png_top"></div>
<div class="png">
<div class="cont_top"></div>
<div id="content">
<div style="height:
18px;"></div>
<div id="content_razd">
<div id="left">

<h1>Welcome!! to Event Management System.</h1>

<!-- Java Server Pages code.-->

<%
String
LoggedIn=(String)session.getAttribute("LoggedIn");
if(LoggedIn==null)

response.sendRedirect("index.jsp");
else
{
if(!LoggedIn.equals("true"))

response.sendRedirect("index.jsp");
else
{

session.removeAttribute("LoggedIn");

session.removeAttribute("uid");

response.sendRedirect("index.jsp");
}
}

%>
</div>
<div id="right">
<h1>Talk to us..</h1>
<div style="height: 15px;"></div>
<img src="images/contactus.gif" width="230" height="228" alt="" />
<div class="razd_v"></div>
<div class=" cont_text">
<h1>Our Head Office Address</h1>

58
 <div style="height: 10px;"></div>
<b> ICL Infosystems Ltd.<br />
E-4,5 &amp; 6, Sector 11,<br />
NOIDA 201 301, UP<br />
India</b>
<p>Tel: 2526518/19, 2520977<br />
</p>
<b>E-mail: brand@info.com</b> </div>
</div>
<div style="clear: both; height:
12px;"></div>
</div>
<div style="height: 18px;"></div>
</div>
<div class="cont_bot"></div>
<!-- content ends -->

<div style="height: 15px;"></div>

<!-- bottom begin -->
<div class="cont_top"></div>
<div id="bottom">

<div class="b_col1">

<h2>Contact Information</h2>
<div class="bottom_text">
<div style="height:15px"></div>
NEW DELHI<br />
Phone: +919899992586<br />
E-mail:
<b>brand@info.com<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;varun2208@gmail.com</b>
</div>
</div>
<div class="b_col2">
<h2>Follow Us</h2>

<div class="bottom_text">
<div style="height:15px"></div>
<ul>
<li><img src="images/fu_i2.gif" class=" fu_i" alt="" /><a
href="#">Facebook</a></li>
<li><img src="images/fu_i3.gif" class=" fu_i" alt="" /><a href="#">Linked
in</a></li>

59
 <li><img src="images/fu_i4.gif" class=" fu_i" alt="" /><a
href="#">twitter</a></li>
</ul>
</div>
</div>
<div class="b_col3">

<h2>Group Sites</h2>
<div class="bottom_text">
<div style="height:15px"></div>
<ul>

<li><a href="http://www.hcl-axon.com/">ICL AXON</a></li>

<li><a href="http://www.hcl-axon.com/"><strong>ICL
Technologies</strong></a></li>

<li><a href="http://www.hclinfosystems.in/"><strong>ICL
InfoSystems</strong></a></li>

<li><a href="http://www.hclbpo.com/"><strong>ICL BPO</strong></a></li>

<li><a href="http://www.hclcdc.in/"><strong>ICL CDC</strong></a></li>

</ul>
</div>
</div>

<div style="clear: both; height:1px;"></div>

</div>
<div class="cont_bot"></div>
</div>
<div class="png_bot"></div>

<!-- bottom end -->

<!-- footer begins -->
<div id="footer">
<a href="#">Privacy Policy</a> | <a href="#">Terms of Use</a> | <a
href="http://validator.w3.org/check/referer" title="This page validates as XHTML 1.0
Transitional"><abbr title="eXtensible HyperText Markup Language">XHTML</abbr></a> |
<a href="http://jigsaw.w3.org/css-validator/check/referer" title="This page validates as
CSS"><abbr title="Cascading Style Sheets">CSS</abbr></a></div>
<!-- footer ends -->
</div>

60
</div>
</div>

</div>
</div>

<div style="text-align: center; font-size: 0.75em;">Design and Coded by Varun and Ankur
</div></body>
</html>

61
 UPDATE

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Event Management System....All What You need!!!!</title>
<meta name="keywords" content="" />
<meta name="description" content="" />
<link href="styles.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="bg_top">
<div id="bg_bot">

<div id="bg_bot_g">
<div id="bg_top_g">

<div id="main">
<!-- header begins -->
<div id="header">

<div id="logo"> <a href="www.hcl.com">ICL

Event Management Sytem</a>
<h2><a href="www.hcl.com">All what you need....</a></h2>
</div>

<p align=right><font color=black size=4><u><a Style="color: White"

href="#">Search</a>&nbsp;|&nbsp;<a Style="color:White"
href="http://localhost:7001/EMS/logout.jsp">Logout</a></right>
</u></font></p>
</div>
<!-- header ends -->
<div id="buttons">
<a href="browse_events.jsp" class="but" title="">Upcoming Events</a><div
class="but_razd"></div>
<a href="build_event.jsp" class="but" title="">Build Events</a><div
class="but_razd"></div>
<a href="venue.jsp" class="but" title="">Venues</a><div
class="but_razd"></div>
<a href="browse_user.jsp" class="but" title="">Users</a><div
class="but_razd"></div>
<a href="Reports.jsp" class="but" title="">Reports</a><div
class="but_razd"></div>
</div>
<div style="height:10px"></div>
62
 <!-- content begins -->
<div class="png_top"></div>
<div class="png">
<div class="cont_top"></div>
<div id="content">
<div style="height:
18px;"></div>
<div id="content_razd">
<div id="left">

<h1>Update Events.</h1>

<!-- Java Server Pages code.-->

<%@ page import="java.sql.*" language="java" %>
<%
Connection con;
PreparedStatement st;
ResultSet rs;
String query="update event_master set
Event_Title=?,Description=?,Start_Date=?,Start_Time=?,End_Time=?,End_Date=?,Contact
_Person=?,Mobile_No=?,Venue_Id=?,Venue_Name=? where Event_Id=?";
int ra=0;

String
LoggedIn=(String)session.getAttribute("LoggedIn");
if(LoggedIn==null)

response.sendRedirect("index.jsp");
else
{
if(!LoggedIn.equals("true"))

response.sendRedirect("index.jsp");
}
//Valid Session

int eid=Integer.parseInt(request.getParameter("eid"));
String etitle=request.getParameter("etitle");
String
desc=request.getParameter("desc");
//start Date
String
sdate_dd=request.getParameter("sdate_dd");

63
 String
sdate_mm=request.getParameter("sdate_mm");
String sdate_yy=request.getParameter("sdate_yy");
String sdate=sdate_dd+"-
"+sdate_mm+"-"+sdate_yy;
//start Time
String
stime_hh=request.getParameter("stime_hh");
String stime_mm=request.getParameter("stime_mm");
String
stime_am=request.getParameter("stime_am");
String
stime=stime_hh+":"+stime_mm+":"+stime_am;
//End Time
String
etime_hh=request.getParameter("etime_hh");
String etime_mm=request.getParameter("etime_mm");
String
etime_am=request.getParameter("etime_am");
String
etime=etime_hh+":"+etime_mm+":"+etime_am;
//End Date
String
edate_dd=request.getParameter("edate_dd");
String
edate_mm=request.getParameter("edate_mm");
String edate_yy=request.getParameter("edate_yy");
String edate=edate_dd+"-
"+edate_mm+"-"+edate_yy;

String
cperson=request.getParameter("cperson");
String
mno=request.getParameter("mno");
String
vid=request.getParameter("vid");
String
vname=request.getParameter("vname");

try{

Class.forName("com.mysql.jdbc.Driver");

64
con=DriverManager.getConnection("jdbc:mysql://localhost/ems?"+"user=root&password=ro
ot");

st=con.prepareStatement(query);

st.setString(1,etitle);
st.setString(2,desc);
st.setString(3,sdate);
st.setString(4,stime);
st.setString(5,etime);
st.setString(6,edate);
st.setString(7,cperson);
st.setString(8,mno);
st.setString(9,vid);
st.setString(10,vname);
st.setInt(11,eid);

ra=st.executeUpdate();

if(ra>0)
{
out.println("<B><br>Record Updated Successfully</center>");
}
else{
out.println("<center><b>Record is Not Updated</center>");
}
out.println("<form action='http://localhost:7001/EMS/browse_events.jsp'>");
out.println("<br><br><b> Please Click the Button to go Back ");
out.println("<input class='submit2' name='Back' type='submit' value='Back'>");
out.println("</form>");
}
catch(Exception
e){e.printStackTrace();}
%>

</div>
<div id="right">
<h1>Talk to us..</h1>
<div style="height: 15px;"></div>
<img src="images/contactus.gif" width="230" height="228" alt="" />
<div class="razd_v"></div>
<div class=" cont_text">
<h1>Our Head Office Address</h1>
<div style="height: 10px;"></div>

65
 <b> ICL Infosystems Ltd.<br />
E-4,5 &amp; 6, Sector 11,<br />
NOIDA 201 301, UP<br />
India</b>
<p>Tel: 2526518/19, 2520977<br />
</p>
<b>E-mail: brand@info.com</b> </div>
</div>
<div style="clear: both; height:
12px;"></div>
</div>
<div style="height: 18px;"></div>
</div>
<div class="cont_bot"></div>
<!-- content ends -->

<div style="height: 15px;"></div>

<!-- bottom begin -->
<div class="cont_top"></div>
<div id="bottom">

<div class="b_col1">

<h2>Contact Information</h2>
<div class="bottom_text">
<div style="height:15px"></div>
NEW DELHI<br />
Phone: +919899992586<br />
E-mail:
<b>brand@info.com<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;varun2208@gmail.com</b>
</div>
</div>
<div class="b_col2">
<h2>Follow Us</h2>

<div class="bottom_text">
<div style="height:15px"></div>
<ul>
<li><img src="images/fu_i2.gif" class=" fu_i" alt="" /><a
href="#">Facebook</a></li>
<li><img src="images/fu_i3.gif" class=" fu_i" alt="" /><a href="#">Linked
in</a></li>
<li><img src="images/fu_i4.gif" class=" fu_i" alt="" /><a
href="#">twitter</a></li>

66
 </ul>
</div>
</div>
<div class="b_col3">

<h2>Group Sites</h2>
<div class="bottom_text">
<div style="height:15px"></div>
<ul>

<li><a href="http://www.hcl-axon.com/">ICL AXON</a></li>

<li><a href="http://www.hcl-axon.com/"><strong>ICL
Technologies</strong></a></li>

<li><a href="http://www.hclinfosystems.in/"><strong>ICL
InfoSystems</strong></a></li>

<li><a href="http://www.hclbpo.com/"><strong>ICL BPO</strong></a></li>

<li><a href="http://www.hclcdc.in/"><strong>ICL CDC</strong></a></li>

</ul>
</div>
</div>

<div style="clear: both; height:1px;"></div>

</div>
<div class="cont_bot"></div>
</div>
<div class="png_bot"></div>

<!-- bottom end -->

<!-- footer begins -->
<div id="footer">
<a href="#">Privacy Policy</a> | <a href="#">Terms of Use</a> | <a
href="http://validator.w3.org/check/referer" title="This page validates as XHTML 1.0
Transitional"><abbr title="eXtensible HyperText Markup Language">XHTML</abbr></a> |
<a href="http://jigsaw.w3.org/css-validator/check/referer" title="This page validates as
CSS"><abbr title="Cascading Style Sheets">CSS</abbr></a></div>
<!-- footer ends -->
</div>

</div>

67
</div>

</div>
</div>

<div style="text-align: center; font-size: 0.75em;">Design and Coded by Varun and Ankur
</div></body>
</html>

68
 SCREENSHORTS

HOME PAGE

69
ABOUT US

70
USER VIEW

71
CREATE USER

72
73