PROJECT REPORT

on

EVENT SPHERE
From

ANALYZE INFOTECH

Towards partial fulfilment of the requirements for

the award of degree of

Master of Computer Applications

from

Babu Banarasi Das University Lucknow

Academic Session 2023 - 24

School of Computer Applications

I Floor, EC-Block, BBDU, BBD City, Faizabad Road, Lucknow (U. P.) INDIA 226028
PHONE: HEAD: 0522-3911127, 3911321 Dept. Adm. & Exam Cell: 0522-3911326 Dept. T&P Cell: 0522-3911128; E-Mail: [email protected]

w w w . b b d u . a c. in
 PROJECT REPORT
on

EVENT SPHERE
from

ANALYZE INFOTECH

Towards partial fulfilment of the requirements for

the award of degree of

Master of Computer Applications

from

Babu Banarasi Das University

Lucknow

Developed and Submitted by Under Guidance of

Kopal Nigam Dr. Nupur Soni
12202121058 Assistant Professor

Academic Session 2023 – 24

School of Computer Applications
I Floor, EC-Block, BBDU, BBD City, Faizabad Road, Lucknow (U. P.) INDIA 226028
 www .bbdu.ac.in

UNDER TAKING
This is to certify that Project Report entitled

EVENT SPHERE
being submitted by

Kopal Nigam
Towards the partial fulfillment of the requirements for the

award of the degree of

Master of Computer Applications

from

Babu Banarasi Das University

Lucknow

Academic Year 2023-24

is a record of the student’s own work carried out at

Analyze InfoTech

and to the best of our knowledge the work reported herein does not form a
part of any other thesis or work on the basis of which degree or award was
conferred on an earlier occasion to this or any other candidate.

Authorized Signatory Student’s Signature

Analyze InfoTech Name: Kopal Nigam
Roll No: 12202121058

DECLARATION
This is to certify that the dissertation entitled EVENT SPHERE is being submitted to the
School of Computer Application, Babu Banarasi Das University, BBD City, Faizabad
Road, Lucknow Uttar Pradesh - 226 028 India, in partial fulfillment of the requirements for
the award of the degree of Master of Computer Applications, is a record of bonafide work
carried out by me under the supervision of Pankaj Mishra.

The matter embodied in the dissertation has not been submitted in part or full to any
University or Institution for the award of any other degree or diploma.

Student Name: Kopal Nigam

University Roll No: 1220212058
School of Computer Application,
Babu Banarasi Das University
1
 ACKNOWLEDGEMENT
The feeling of acknowledge and expressing it in words are two things apart. It is weakness,
but we honestly admit when we truly wish to express our warm gratitude and indebtedness
towards somebody, we are always at loss of word.

The project could not have completed without support extends to us by Pankaj Mishra, he
guided us in preparation of the project and every time when we reached with difficulties, he
welcomed them which helped us to successfully complete the project. We express our
heartfelt gratitude with great pleasure and a sense of obligation to Dr. Syed Anas Ansar, our
project in charge for her timely support and supervision. And also, we would like to thanks
our T&P CoOrdinator’s for their support and guide. We would also like to thank Dr.
Prabhash Chandra Pathak, our Head of department. He was always there with his support
and those wonderful insights whenever eagerly needed.

We would also like to thank Dr. Reena Srivastava Honorable Dean of our Department whose
continued cooperation and support top the School of Computer Application was pivotal force
in making this project a success. And, finally a word of gratitude to our family and friends
who were always there with their support and encouragement.

2
3
 INDEX

S. NO. TOPICS PAGE NO.

1. INTRODUCTION 1

2. IDENTIFICATION OF NEED 2

3. PROBLEM STATEMENT 3

4. PRELIMINARY INVESTIGATION 4-5

5. SYSTEM ANALYSIS 6-10

6. TOOL & PLATEFORM 11-12

7. PROJECT PLANNING 13

8. SOFTWARE REQUIREMENT SPECIFICATION(SRS) 14

9. MODULE 15

10. SYSTEM DESIGN 16-17

11. TESTING 18

12. HIGH LEVEL DESIGN 19-20

13. LOW LEVEL DESIGN 21-22

14. CODE 23-44

15. SCREENSHOT 45-53

16. CONCLUSION 54

17. LIMITATION & FUTURE SCOPE 55-56

18. BIBLIOGRAPHY 57

4
 1. INTRODUCTION
The "Event Sphere" has been developed to override the problems prevailing in the practicing
manual system. This software is supported to eliminate and, in some cases, reduce the hardships
faced by this existing system. Moreover, this system is designed for the particular need of the
company to carry out operations in a smooth and effective manner. The application is reduced as
much as possible to avoid errors while entering the data. It also provides error message while
entering invalid data. No formal knowledge is needed for the user to use this system. Thus, by
this all it proves it is user-friendly. Event Sphere, as described above, can lead to error free,
secure, reliable and fast management system. It can assist the user to concentrate on their other
activities rather to concentrate on the record keeping.
Thus, it will help organization in better utilization of resources.

Every organization, whether big or small, has challenges to overcome and managing the
information’s of Booking, Event, Employee, Package, Enquiry. Every Event Sphere has different
Event needs; therefore, we design exclusive employee management systems that are adapted to
your managerial requirements. This is designed to assist in strategic re, and will help you ensure
that your organization is equipped with the right level of information and details for your future
goals. Also, for those busy executive who are always on the go, our systems come with remote
access features, which will allow you to manage your workforce anytime, at all times. These
systems will ultimately allow you to better manage resources.

2. IDENTIFICATION OF NEEDS
The old manual system was suffering from a series of drawbacks. Since whole of the system was
to be maintained with hands the process of keeping, maintaining and retrieving the information
was very tedious and lengthy. The records were never used to be in a systematic order. there used
to be lots of difficulties in associating any particular transaction with a particular context. If any
information was to be found it was required to go through the different registers, documents
there would never exist anything like report generation. There would always be unnecessary
consumption of time while entering records and retrieving records. One more problem was that it
was very difficult to find errors while entering the records. Once the records were entered it was
very difficult to update these records.

5
The reason behind it is that there is lot of information to be maintained and have to be kept in
mind while running the business. For this reason, we have provided features Present system is
partially automated (computerized), actually existing system is quite laborious as one has to enter
same information at three different places

3. PROBLEM STATEMENT
"In today's dynamic business environment, organizations of all sizes face numerous challenges in
effectively managing their events, bookings, employees, packages, and inquiries. The reliance on
manual systems exacerbates these challenges, resulting in inefficiencies, inaccuracies, and
missed opportunities. Manual processes for event management often involve cumbersome
paperwork, disjointed communication channels, and a lack of centralized data storage, leading to
delays, errors, and customer dissatisfaction. Booking and managing events manually are labor-
intensive tasks that consume valuable time and resources. Coordinating schedules, tracking
reservations, and managing payments manually are prone to errors, resulting in double bookings,
missed opportunities, and revenue loss. Additionally, manual systems for employee management
lack scalability and flexibility, making it difficult to adapt to changing organizational needs and
growth.

Furthermore, manual record-keeping processes for packages and inquiries are susceptible to data
entry errors, data loss, and security breaches. Without a centralized system for storing and
retrieving information, organizations struggle to maintain accurate records, resulting in customer
dissatisfaction and reputational damage. Moreover, the lack of remote access to critical
information hampers the ability of busy executives to make informed decisions on the go.
Without real-time access to event details, employee schedules, and customer inquiries,
organizations risk falling behind competitors and missing out on business opportunities. In
summary, the prevailing manual systems for event, booking, employee, package, and inquiry
management present significant challenges for organizations, including inefficiencies,
inaccuracies, scalability limitations, and a lack of flexibility. There is an urgent need for a
comprehensive software solution that streamlines these processes, enhances data accuracy,
improves resource utilization, and provides remote access capabilities, thereby enabling
organizations to achieve greater efficiency, effectiveness, and competitiveness in their operations.

6
"This detailed problem statement outlines the specific pain points and challenges associated with
manual systems for event management and emphasizes the need for the development and
implementation of Event Sphere to address these issues effectively.

4. PRELIMINARY INVESTIGATION
Current System Analysis:

• Evaluate the existing manual systems for event management, booking, employee
management, package handling, and inquiry management within organizations.

• Identify the key pain points, inefficiencies, and limitations of these manual systems.

• Gather data on the frequency and impact of errors, delays, and resource wastage resulting
from manual processes.

Stakeholder Interviews:

• Conduct interviews with stakeholders involved in event management, including event

planners, booking agents, employees, and customers.

• Gather insights into their experiences, challenges, and frustrations with the current manual
systems.

• Identify specific user requirements, preferences, and pain points that need to be addressed
by the new software solution.

Market Research:

• Research existing software solutions available in the market for event management,
booking, employee scheduling, package handling, and inquiry management.

• Evaluate their features, functionalities, pricing, and user reviews.

• Identify gaps in the market and opportunities for differentiation and innovation with the
Event Sphere software.

7
Data Analysis:

• Analyze historical data on event management, booking, employee scheduling, package

handling, and inquiries within the organization.

• Identify trends, patterns, and areas for improvement based on data insights.

• Quantify the potential benefits of transitioning from manual systems to the Event Sphere
software in terms of cost savings, efficiency gains, and customer satisfaction
improvements.

Risk Assessment:

• Assess the potential risks and challenges associated with implementing the new software
solution.

• Identify technical, operational, and organizational risks that may impact the success of the
project.

• Develop risk mitigation strategies to address and minimize potential threats to the
project's success.

Cost-Benefit Analysis:

• Estimate the costs associated with developing, implementing, and maintaining the Event
Sphere software.

• Quantify the anticipated benefits in terms of time savings, resource utilization

improvements, revenue generation, and customer satisfaction enhancements.

• Conduct a cost-benefit analysis to determine the return on investment (ROI) and the
viability of the project.

Recommendations:

• Based on the findings of your investigation, provide recommendations for the

development and implementation of the Event Sphere software.

8
• Outline the key features, functionalities, and design considerations that should be
incorporated into the software to address the identified challenges and meet user needs.

• Present a roadmap for the project, including timelines, milestones, and resource
requirements.

5. SYSTEM ANALYSIS
Requirements and objectives of a software system before its development begins. It involves
a systematic examination of the existing processes, user needs, and organizational goals to
identify opportunities for improvement and innovation. During system analysis, the scope and
objectives of the software are clearly defined to ensure alignment with the organization's
strategic priorities and user expectations. This involves gathering input from stakeholders
through interviews, surveys, and workshops to understand their needs, preferences, and pain
points. By involving stakeholders early in the process, system analysts can ensure that the
resulting software solution meets their requirements and delivers tangible benefits. One of the
key activities in system analysis is modeling the existing processes within the organization.
This involves documenting the steps involved in tasks such as event management, booking,
employee scheduling, and inquiry handling using techniques like flowcharts or swim lane
diagrams. By visualizing these processes, system analysts can identify inefficiencies,
bottlenecks, and areas for improvement that can be addressed through the development of the
new software system.

System analysis also involves proposing the architecture of the software system, including its
components, modules, and interfaces. This requires careful consideration of factors such as
technology choices, scalability requirements, and integration with existing systems. By
defining the architecture upfront, system analysts lay the groundwork for a scalable, flexible,

9
and maintainable software solution that can adapt to changing organizational needs. In
addition to defining the functional requirements of the software, system analysis also
addresses nonfunctional requirements related to performance, security, usability, and
reliability. These requirements ensure that the software not only meets the functional needs of
users but also delivers a high-quality user experience and complies with industry standards
and best practices.

Business Need: The business need for the Event Sphere project arises from the pressing
challenges and limitations faced by organizations in managing events, bookings, employees,
packages, and inquiries using manual systems. Manual processes are labor-intensive, error-
prone, and time-consuming, leading to inefficiencies, inaccuracies, and missed opportunities.
Organizations struggle to maintain accurate records, coordinate schedules, track reservations,
and manage inquiries effectively, resulting in delays, errors, and customer dissatisfaction.
Moreover, the lack of remote access to critical information hampers the ability of busy
executives to make informed decisions on the go, hindering organizational agility and
responsiveness. Recognizing these challenges, there is a clear need for a comprehensive
software solution like Event Sphere that streamlines event management processes, improves
data accuracy, enhances resource utilization, and provides remote access capabilities. By
addressing these needs, Event Sphere will empower organizations to achieve greater
efficiency, effectiveness, and competitiveness in their operations, ultimately driving business
growth and success.

Objective: The objective of the Event Sphere project is to develop and implement a
comprehensive software solution that addresses the challenges inherent in manual event
management systems while meeting the diverse needs of users and stakeholders. The
primary goal is to streamline event management processes, improve data accuracy, enhance
resource utilization, and provide remote access capabilities, thereby enabling organizations
to achieve greater efficiency, effectiveness, and competitiveness in their operations.
Specifically, the software aims to facilitate the efficient creation, management, and tracking
of events, simplify the booking process for events, services, and facilities, optimize
employee scheduling and task assignment, enable customization of event packages to meet
client requirements, and enhance communication with clients, customers, and stakeholders
through effective inquiry tracking and management. By delivering a user-friendly interface

10
with built-in error handling mechanisms, Event Sphere seeks to streamline event
management processes, improve organizational efficiency, and drive business growth and
success.

Proposed System: The proposed system, Event Sphere, is a comprehensive software

solution designed to revolutionize event management processes and enhance organizational
efficiency. At its core, Event Sphere will offer a user-friendly interface and a suite of
powerful features tailored to meet the diverse needs of event planners, booking agents,
employees, and customers.

Key components of the proposed system include:

• Event Management Module: Event Sphere will streamline event creation,

management, and tracking processes, allowing users to schedule events, select
venues, manage attendees, and allocate resources seamlessly. The module will
provide intuitive tools for event customization, enabling users to tailor event details
to meet specific client requirements.

• Booking Management System: The software will include a robust booking

management system to simplify the booking process for events, services, and
facilities. Users will be able to check availability, make reservations, process
payments, and generate invoices efficiently within the system.

• Employee Management Module: Event Sphere will feature an employee

management module to facilitate scheduling, task assignment, and performance
tracking for staff involved in event planning and execution. Managers will have tools
to create employee schedules, assign tasks, track attendance, and monitor
performance metrics effectively.

• Package Customization: The system will support the creation and customization
of event packages tailored to meet the diverse needs of clients and customers. Users
will have the flexibility to select from predefined packages or customize packages
based on specific requirements, preferences, and budget constraints.

11
 • Inquiry Tracking and Management: Event Sphere will include a system for
tracking and managing inquiries from clients, customers, and stakeholders regarding
events, bookings, and services. Users will be able to log inquiries, track their status,
respond to inquiries, and generate reports to analyze inquiry trends and patterns.

• Remote Access and Mobility Features: The software will offer remote access
capabilities, allowing users to access and manage event-related information from
anywhere, at any time, using desktop or mobile devices. This feature will enhance
productivity and responsiveness, particularly for busy executives and staff members
on the go.

Benefits: Implementation of Event Sphere promises numerous benefits that span across
various aspects of organizational operations. Firstly, by streamlining event management
processes and providing a centralized platform for scheduling, venue selection, attendee
management, and resource allocation, Event Sphere significantly reduces the time and effort
required to plan and execute events. This efficiency translates into cost savings and allows
organizations to allocate resources more effectively. Additionally, the robust booking
management system simplifies the booking process for events, services, and facilities,
leading to faster turnaround times, improved customer satisfaction, and increased revenue
opportunities. Moreover, the employee management module enhances workforce
productivity by facilitating scheduling, task assignment, and performance tracking, enabling
managers to optimize staffing levels and ensure seamless coordination during events.
Furthermore, the customization capabilities of Event Sphere enable organizations to tailor
event packages to meet specific client requirements, fostering stronger client relationships
and driving customer loyalty. The system's inquiry tracking and management features
streamline communication with clients, customers, and stakeholders, enhancing
responsiveness and ensuring inquiries are addressed promptly and efficiently. Lastly, the
remote access and mobility features of Event Sphere empower users to access and manage
event-related information from anywhere, at any time, enhancing flexibility, collaboration,
and decisionmaking. Overall, the adoption of Event Sphere promises to enhance
organizational efficiency, improve customer satisfaction, and drive business growth and
success.

12
Feasibility Study: A feasibility study for the Event Sphere project would assess the
viability and potential success of the proposed software solution. Here's an overview of what
a feasibility study for Event Sphere might entail:

▪ Technical Feasibility: Technical feasibility assesses the organization's capability to

develop and implement the proposed software solution, Event Sphere. It evaluates
the availability of necessary technical resources, such as hardware, software, and
development tools, as well as the compatibility of Event Sphere with existing
systems and infrastructure. This analysis determines if the proposed features and
functionalities of Event Sphere can be technically implemented within the desired
timeframe and budget constraints.

▪ Financial Feasibility: Financial feasibility examines the economic viability of

developing and implementing Event Sphere. It involves conducting a cost-benefit
analysis to estimate the initial development costs, ongoing operational expenses, and
potential returns on investment (ROI) from implementing Event Sphere. This
analysis considers factors such as increased efficiency, revenue generation, and cost
savings over time to determine the affordability and financial sustainability of Event
Sphere for the organization.

▪ Operational Feasibility: Operational feasibility evaluates the impact of Event

Sphere on existing business processes and operations within the organization. It
assesses the readiness of employees and stakeholders to adopt and use Event Sphere
effectively, as well as any potential barriers or challenges to successful
implementation. This analysis helps identify strategies to mitigate risks and ensure a
smooth transition to Event Sphere, including change management initiatives and user
training programs.

▪ Legal and Regulatory Feasibility: Legal and regulatory feasibility ensures that Event
Sphere complies with all relevant laws, regulations, and industry standards. It
involves identifying legal and regulatory requirements that may impact the
development and implementation of Event Sphere, such as data privacy laws or
intellectual property rights. This analysis helps mitigate potential risks and liabilities

13
 associated with Event Sphere, such as data security breaches or legal disputes, by
ensuring compliance with applicable legal and regulatory requirements.

▪ Schedule Feasibility: Schedule feasibility involves developing a realistic project

timeline and schedule for the development and implementation of Event Sphere. It
assesses the feasibility of meeting project deadlines, considering factors such as
resource availability, dependencies, and project milestones. This analysis helps
identify potential risks or delays that may impact the project schedule and develop
contingency plans to mitigate them, ensuring the timely delivery of Event Sphere
within the organization's objectives and timeframe.

6. TOOLS AND PLATFORM

▪ Web Platform: Web-based software is software you use over the internet with a web
browser.

▪ Java EE: You don’t have to install anything, download any software, or worry about
upgrades.
If you use an online bank or web-based email program like Email, Hot-mail, or Yahoo
Mail, you’re already using web-based software. Java Platform, Enterprise Edition (Java

14
 EE) is the standard in community-driven enterprise software. Java EE is developed using
the Java Community Process, with contributions from industry experts, commercial and
open-source organizations, Java User Groups, and countless individuals. Each release
integrates new features that align with industry needs, improves application portability,
and increases developer productivity.

▪ MySQL: MySQL is the most popular Open-Source Relational SQL Database

Management
System. MySQL is one of the best RDBMS being used for developing various web-based
software applications.

▪ Jitsi Technology: Jitsi is a set of open-source projects that allows you to easily build and
deploy secure video conferencing solutions. Jitsi Video-bridge passes everyone’s video
and audio to all participants, rather than mixing them first. Better quality, lower latency
and if we are running your own service, a much more scalable and inexpensive solution.

▪ Apache Tomcat Server: The Apache Tomcat® software is an open source

implementation of the Java Servlet, Java Server Pages, Java Expression Language and
Java Web-socket technologies. The Java Servlet, Java Server Pages, Java Expression
Language and Java Websocket specifications are developed under the Java Community
Process. Apache Tomcat is a Java Servlet container, or web container, that provides the
extended functionality to interact with Java Servlets.

Resources (Hardware & Software):

• Hardware Requirements:
Client Side:
Processor : Dual Core or above

15
 RAM : 4 GB
HDD : 500 GB
Display : High Resolution
screen
Others : Internet Connection

Developer Side:

Processor : Core i3 or above

RAM : 4 GB
HDD : 500 GB
Display : High Resolution screen
Others : Internet Connection

• Software Requirements: Client Side

Web Browser : Any updated browser

Developer Side
Browser : Any updated browser
IDE : Eclipse IDE
Software : jdk17
Database : MySQL
OS : Windows

16
 7. PROJECT PLANNING
Project planning is part of project management, which relates to the use of schedules such as
Gantt charts to plan and subsequently report progress within the project environment. Project
planning can be done manually or by the use of project management software.

Project Schedule Plan:

• Gantt Chart: A Gantt chart, commonly used in project management, is one of the most
popular and useful ways of showing activities (tasks or events) displayed against time. On
the left of the chart is a list of the activities and along the top is a suitable time scale. Each
activity is represented by a bar; the position and length of the bar reflects the start date,
duration and end date of the activity.

8. SOFTWARE REQUIREMENT SPECIFICATION(SRS)

The Software Requirements Specification is produced at the culmination of the analysis task. The
function and performance allocated to software as part of system engineering are refined by

17
establishing a complete information description, a detailed functional and behavioral description,
an indication of performance requirements and design constraints, appropriate validation criteria,
and other data pertinent to requirements.

The proposed system has the following requirements:

• System needs store information about new entry of Event.

• System needs to help the internal staff to keep information of Booking and find them as
various queries.

• System needs to maintain quantity record.

• System needs to keep the record of Customer.

• System needs to update and delete the record.

• System also needs a search area.

• It also needs a security system to prevent data.

9. MODULES
• Event Management Module: Used for managing the Event details.

18
 • Enquiry Module: Used for managing the details of Enquiry.

• Package Module: Used for managing the details of Package.

• Booking Management Module: Used for managing the information and details of the
Booking.

• Customer Module: Used for managing the Customer details.

• Employee Module: Used for managing the Employee information.

• Login Module: Used for managing the login details.

• Users Module: Used for managing the users of the system.

10. SYSTEM DESIGN

Software Process Model (Agile Development Model)

19
"Agile process model" refers to a software development approach based on iterative
development.

• Agile methods break tasks into smaller iterations, or parts do not directly involve long
term planning.

• The project scope and requirements are laid down at the beginning of the development
process.

• Plans regarding the number of iterations, the duration and the scope of each iteration are
clearly defined in advance.

• Each iteration is considered as a short time "frame" in the Agile process model, which
typically lasts from one to four weeks.

• The division of the entire project into smaller parts helps to minimize the project risk and
to reduce the overall project delivery time requirements.

• Each iteration involves a team working through a full software development life cycle
including planning, requirements analysis, design, coding, and testing before a working
product is demonstrated to the client.

20
 11. TESTING
We will continuously test our project to ensure that it is fully functional. In order to perform
testing test cases are designed with the intent of finding the errors in the project and help in
removing those errors. Testing begins at the module level and is conducted systematically. It
is generally conducted by independent test groups or third party.

Testing is done in our project remote controlling PC with help of black box testing that
exercise all the functional requirement of the project test cases are designed using these
approaches by providing set of input conditions to get the expected output.
Test Cases for Client:

21
 TEST CASE ID INPUT EXPECTED ACTUAL OUTPUT
OUTPUT
1 Password and key Start Operation started
combination

2 No Input Alert Message Select a valid

configuration setting

Test Cases for Server:

TEST CASE ID INPUT EXPECTED ACTUAL OUTPUT

OUTPUT
1 127.0.0.1 Connection establishes Client Connected

2 Get Status Alert Box If no client selected

“alert box” is
displayed

12. HIGH LEVEL DESIGN

DFD (Data Flow Diagram): DFD stands for Data Flow Diagram. It's a graphical representation
that depicts the flow of data within a system, showing how data moves through different
processes and data stores. Here's a basic explanation of its components:

• External Entities: These are sources or destinations of data outside the system you're
modeling. They could be users, other systems, or even physical devices. In a DFD, they're
represented by rectangles.

• Processes: Processes represent transformations or manipulations of data within the

system. Each process takes input data, does something with it, and produces output data.

22
 In a DFD, processes are typically represented by circles or rectangles with rounded
corners.

• Data Stores: Data stores are places where data is held within the system. They can be
databases, files, or any other storage medium. In a DFD, data stores are represented by
openended rectangles.

• Data Flows: Data flows represent the movement of data between external entities,
processes, and data stores. They show the path that data takes through the system. In a
DFD, data flows are represented by arrows.

By using these components and connecting them appropriately, a DFD provides a high-level
overview of how data moves through a system, helping analysts and stakeholders understand the
system's functionality and structure.

Tools/Platform, Hardware and Software

Requirement specifications:

Software

Requirements:
ER Diagram:

23
 13. LOW LEVEL DESIGN
Database Table:

24
25
26
 14. CODING
/*

* To change this license header, choose License Headers in Project Properties.

* To change this template file, choose Tools | Templates * and open the template in the

editor.

*/ package

Event;

import DB.DBConnection; import

java.awt.Image; import

java.awt.event.KeyEvent; import java.io.File;

import java.io.FileInputStream; import

java.text.SimpleDateFormat; import

java.util.Vector; import javax.imageio.ImageIO;

import javax.swing.ImageIcon; import

javax.swing.JFileChooser; import

javax.swing.JOptionPane; import

javax.swing.table.DefaultTableModel;

/**

* @author Inshu

27
*/ public class Admin extends javax.swing.JFrame

/**

* Creates new form Admin

*/ public Admin()

{ initComponents();

setExtendedState(MAXIMIZED_BOTH);

public Admin(String u) { initComponents();

setExtendedState(MAXIMIZED_BOTH);

/**

* This method is called from within the constructor to initialize the form. * WARNING: Do NOT modify

this code. The content of this method is always * regenerated by the Form Editor.

*/

@SuppressWarnings("unchecked")

// <editor-fold defaultstate="collapsed" desc="Generated Code"> private

void initComponents() {

28
 jPanel1 = new javax.swing.JPanel(); jPanel2 = new

javax.swing.JPanel(); jLabel3 = new javax.swing.JLabel();

jDesktopPane1 = new javax.swing.JDesktopPane(); addven = new

javax.swing.JInternalFrame(); jPanel3 = new javax.swing.JPanel();

jLabel14 = new javax.swing.JLabel(); jLabel15 = new

javax.swing.JLabel(); jLabel16 = new javax.swing.JLabel();

jLabel17 = new javax.swing.JLabel(); jLabel18 = new

javax.swing.JLabel(); jTextField2 = new javax.swing.JTextField();

jFormattedTextField1 = new javax.swing.JFormattedTextField();

jLabel19 = new javax.swing.JLabel(); jTextField3 = new

javax.swing.JTextField(); jFormattedTextField2 = new

javax.swing.JFormattedTextField(); jLabel20 = new

javax.swing.JLabel(); jLabel21 = new javax.swing.JLabel();

jFormattedTextField3 = new javax.swing.JFormattedTextField();

jLabel22 = new javax.swing.JLabel(); jLabel23 = new

javax.swing.JLabel(); jLabel10 = new javax.swing.JLabel();

jComboBox1 = new javax.swing.JComboBox<String>(); newbook

= new javax.swing.JInternalFrame(); jPanel4 = new

javax.swing.JPanel(); jLabel24 = new javax.swing.JLabel();

jLabel27 = new javax.swing.JLabel(); jTextField4 = new

javax.swing.JTextField(); jTextField5 = new

29
javax.swing.JTextField(); jLabel32 = new javax.swing.JLabel();

jLabel33 = new javax.swing.JLabel(); jLabel34 = new

javax.swing.JLabel(); jComboBox3 = new

javax.swing.JComboBox<String>(); jLabel35 = new

javax.swing.JLabel(); jScrollPane1 = new

javax.swing.JScrollPane(); jTable1 = new javax.swing.JTable();

bookhis = new javax.swing.JInternalFrame(); jPanel5 = new

javax.swing.JPanel(); jLabel25 = new javax.swing.JLabel();

jScrollPane2 = new javax.swing.JScrollPane(); jTable2 = new

javax.swing.JTable(); viewven = new javax.swing.JInternalFrame();

jPanel6 = new javax.swing.JPanel(); jLabel26 = new

javax.swing.JLabel(); jLabel41 = new javax.swing.JLabel();

jLabel42 = new javax.swing.JLabel(); jComboBox5 = new

javax.swing.JComboBox<String>(); jScrollPane3 = new

javax.swing.JScrollPane(); jTable3 = new javax.swing.JTable();

addemp = new javax.swing.JInternalFrame(); jPanel32 = new

javax.swing.JPanel(); jLabel124 = new

javax.swing.JLabel(); jLabel125 = new javax.swing.JLabel();

jLabel126 = new javax.swing.JLabel(); jLabel127 = new

javax.swing.JLabel(); jLabel128 = new javax.swing.JLabel();

jLabel129 = new javax.swing.JLabel(); jLabel130 = new

javax.swing.JLabel(); jLabel132 = new javax.swing.JLabel();

30
jLabel133 = new javax.swing.JLabel(); jPanel33 = new

javax.swing.JPanel(); jLabel134 = new javax.swing.JLabel();

jTextField46 = new javax.swing.JTextField(); jFormattedTextField8 =

new javax.swing.JFormattedTextField(); jRadioButton5 = new

javax.swing.JRadioButton(); jRadioButton6 = new

javax.swing.JRadioButton(); jTextField47 = new

javax.swing.JTextField(); jTextField48 = new

javax.swing.JTextField(); jTextField50 = new

javax.swing.JTextField(); jLabel135 = new javax.swing.JLabel();

jLabel136 = new javax.swing.JLabel(); jLabel137 = new

javax.swing.JLabel(); jFormattedTextField22 = new

javax.swing.JFormattedTextField(); jPasswordField1 = new

javax.swing.JPasswordField(); jDateChooser1 = new

com.toedter.calendar.JDateChooser(); viewemp = new

javax.swing.JInternalFrame(); jPanel34 = new

javax.swing.JPanel(); jLabel139 = new javax.swing.JLabel();

jLabel140 = new javax.swing.JLabel(); jLabel141 = new

javax.swing.JLabel(); jLabel142 = new javax.swing.JLabel();

jLabel143 = new javax.swing.JLabel(); jLabel144 = new

javax.swing.JLabel(); jLabel145 = new javax.swing.JLabel(); jPanel35

= new javax.swing.JPanel(); jLabel147 = new javax.swing.JLabel();

jTextField52 = new javax.swing.JTextField();

31
jFormattedTextField19 = new javax.swing.JFormattedTextField();

jRadioButton7 = new javax.swing.JRadioButton();

jRadioButton8 = new javax.swing.JRadioButton();

jFormattedTextField23 = new javax.swing.JFormattedTextField();

jTextField53 = new javax.swing.JTextField(); jTextField54 = new

javax.swing.JTextField(); jTextField55 = new

javax.swing.JTextField(); jLabel148 = new javax.swing.JLabel();

jLabel149 = new javax.swing.JLabel(); jLabel150 = new

javax.swing.JLabel(); jFormattedTextField24 = new

javax.swing.JFormattedTextField(); jScrollPane9 = new

javax.swing.JScrollPane(); jTable9 = new javax.swing.JTable();

jLabel151 = new javax.swing.JLabel(); jTextField57 = new

javax.swing.JTextField(); jLabel29 = new javax.swing.JLabel();

jLabel28 = new javax.swing.JLabel(); jLabel36 = new

javax.swing.JLabel(); jLabel31 = new javax.swing.JLabel(); jLabel37 =

new javax.swing.JLabel(); jLabel30 = new javax.swing.JLabel();

jLabel12 = new javax.swing.JLabel(); jLabel13 = new

javax.swing.JLabel(); jLabel4 = new javax.swing.JLabel();

jLabel5 = new javax.swing.JLabel(); jLabel6 = new

javax.swing.JLabel(); jLabel7 = new javax.swing.JLabel();

jLabel8 = new javax.swing.JLabel(); jLabel9 = new

javax.swing.JLabel(); jLabel11 = new javax.swing.JLabel();

32
jLabel2 = new javax.swing.JLabel(); jLabel1 = new

javax.swing.JLabel();

setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);

setMinimumSize(new java.awt.Dimension(1366, 768));

jPanel1.setBackground(new java.awt.Color(0, 0, 0));

jPanel1.setMaximumSize(new java.awt.Dimension(1366, 768));

jPanel1.setMinimumSize(new java.awt.Dimension(1366, 768));

jPanel1.setPreferredSize(new java.awt.Dimension(1366, 768));

jPanel1.setLayout(new

org.netbeans.lib.awtextra.AbsoluteLayout());

jPanel2.setBackground(new java.awt.Color(0, 0, 0));

jPanel2.setLayout(new

org.netbeans.lib.awtextra.AbsoluteLayout());

jLabel3.setFont(new java.awt.Font("Century Gothic", 1, 24)); // NOI18N

jLabel3.setForeground(new java.awt.Color(255, 255, 255));

jLabel3.setHorizontalAlignment(javax.swing.SwingConstants.CENTER); jLabel3.setText("Admin

Module"); jPanel2.add(jLabel3, new org.netbeans.lib.awtextra.AbsoluteConstraints(0, 10,

245, 60));

33
 jPanel1.add(jPanel2, new org.netbeans.lib.awtextra.AbsoluteConstraints(0, 0, 1370, 80));

jDesktopPane1.setLayout(new org.netbeans.lib.awtextra.AbsoluteLayout());

addven.setClosable(true);

addven.setDefaultCloseOperation(javax.swing.WindowConstants.HIDE_ON_CLOSE);

addven.setTitle("Add Venue"); addven.setVisible(false);

jPanel3.setBackground(new java.awt.Color(255, 255, 255)); jPanel3.setLayout(new

org.netbeans.lib.awtextra.AbsoluteLayout()); jLabel14.setFont(new

java.awt.Font("Century Gothic", 1, 24)); // NOI18N

jLabel14.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel14.setText("Add Venue"); jPanel3.add(jLabel14, new

org.netbeans.lib.awtextra.AbsoluteConstraints(460, 40, -1, -1));

jLabel15.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel15.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel15.setText("Rupees :"); jPanel3.add(jLabel15, new

org.netbeans.lib.awtextra.AbsoluteConstraints(160, 450, -1, -1));

jLabel16.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel16.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

34
jLabel16.setText("Image Upload :"); jPanel3.add(jLabel16, new

org.netbeans.lib.awtextra.AbsoluteConstraints(720, 130, -1, 20));

jLabel17.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel17.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel17.setText("Venue Address :"); jPanel3.add(jLabel17, new

org.netbeans.lib.awtextra.AbsoluteConstraints(160, 190, -1, -1));

jLabel18.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel18.setHorizontalAlignment(javax.swing.SwingConstants.CENTER); jLabel18.setText("Venue Phone

No.:"); jPanel3.add(jLabel18, new org.netbeans.lib.awtextra.AbsoluteConstraints(160, 260, -1, -1));

jTextField2.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N

jTextField2.setBorder(javax.swing.BorderFactory.createMatteBorder(0, 1, 2, 1, new java.awt.Color(0,

0, 0))); jTextField2.addActionListener(new java.awt.event.ActionListener()

{ public void actionPerformed(java.awt.event.ActionEvent evt) {

jTextField2ActionPerformed(evt);

});

jPanel3.add(jTextField2, new org.netbeans.lib.awtextra.AbsoluteConstraints(340, 130, 280, -1));

jFormattedTextField1.setBorder(javax.swing.BorderFactory.createMatteBorder(0, 1, 2, 1, new

java.awt.Color(0, 0, 0)));

35
jFormattedTextField1.setHorizontalAlignment(javax.swing.JTextField.CENTER);

jPanel3.add(jFormattedTextField1, new org.netbeans.lib.awtextra.AbsoluteConstraints(340, 450, 280,

20));

jLabel19.setFont(new java.awt.Font("Century Gothic", 1, 18)); // NOI18N

jLabel19.setHorizontalAlignment(javax.swing.SwingConstants.CENTER); jLabel19.setText("Click

here"); jLabel19.setBorder(javax.swing.BorderFactory.createLineBorder(new java.awt.Color(0, 0, 0)));

jLabel19.addMouseListener(new java.awt.event.MouseAdapter() { public void

mouseClicked(java.awt.event.MouseEvent evt) { jLabel19MouseClicked(evt);

});

jPanel3.add(jLabel19, new org.netbeans.lib.awtextra.AbsoluteConstraints(860, 120, 120, 40));

jTextField3.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N

jTextField3.setBorder(javax.swing.BorderFactory.createMatteBorder(0, 1, 2, 1, new java.awt.Color(0,

0, 0))); jPanel3.add(jTextField3, new org.netbeans.lib.awtextra.AbsoluteConstraints(340, 190, 280,

-1));

jFormattedTextField2.setBorder(javax.swing.BorderFactory.createMatteBorder(0, 1, 2, 1, new

java.awt.Color(0, 0, 0)));

36
jFormattedTextField2.setHorizontalAlignment(javax.swing.JTextField.CENTER);

jPanel3.add(jFormattedTextField2, new org.netbeans.lib.awtextra.AbsoluteConstraints(340, 260, 280,

20));

jLabel20.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel20.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel20.setText(" Capacity :");

jPanel3.add(jLabel20, new org.netbeans.lib.awtextra.AbsoluteConstraints(160, 330, -1, -1));

jLabel21.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel21.setHorizontalAlignment(javax.swing.SwingConstants.CENTER); jLabel21.setText(" Preferred For

:"); jPanel3.add(jLabel21, new org.netbeans.lib.awtextra.AbsoluteConstraints(160, 390, -1, -1));

jFormattedTextField3.setBorder(javax.swing.BorderFactory.createMatteBorder(0, 1, 2, 1, new

java.awt.Color(0, 0, 0)));

jFormattedTextField3.setHorizontalAlignment(javax.swing.JTextField.CENTER);

jPanel3.add(jFormattedTextField3, new org.netbeans.lib.awtextra.AbsoluteConstraints(340, 330, 280,

20));

jLabel22.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel22.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel22.setText("Venue Name :"); jPanel3.add(jLabel22, new

37
org.netbeans.lib.awtextra.AbsoluteConstraints(160, 130, -1, 20));

jLabel23.setFont(new java.awt.Font("Century Gothic", 1, 18)); // NOI18N

jLabel23.setHorizontalAlignment(javax.swing.SwingConstants.CENTER); jLabel23.setText("Submit");

jLabel23.setBorder(javax.swing.BorderFactory.createLineBorder(new java.awt.Color(0, 0, 0)));

jLabel23.addMouseListener(new java.awt.event.MouseAdapter() { public void

mouseClicked(java.awt.event.MouseEvent evt) { jLabel23MouseClicked(evt);

});

jPanel3.add(jLabel23, new org.netbeans.lib.awtextra.AbsoluteConstraints(460, 490, 120, 40));

jLabel10.setBorder(javax.swing.BorderFactory.createLineBorder(new java.awt.Color(0, 0, 0)));

jPanel3.add(jLabel10, new org.netbeans.lib.awtextra.AbsoluteConstraints(690, 190, 330, 280));

jComboBox1.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N

jComboBox1.setModel(new javax.swing.DefaultComboBoxModel(new String[] { "Select-----", "Marriage",

"Meeting", "Auction", "Birthday", "Ring Ceremony", "Kitty Party" }));

jComboBox1.setPreferredSize(new java.awt.Dimension(56, 30)); jPanel3.add(jComboBox1, new

org.netbeans.lib.awtextra.AbsoluteConstraints(340, 390, 280, -1));

javax.swing.GroupLayout addvenLayout = new javax.swing.GroupLayout(addven.getContentPane());

addven.getContentPane().setLayout(addvenLayout);

38
addvenLayout.setHorizontalGroup( addvenLayout.createParallelGroup(javax.swing.GroupLayout.A

lignment.LEADING)

.addComponent(jPanel3, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)

);

addvenLayout.setVerticalGroup( addvenLayout.createParallelGroup(javax.swing.GroupLayout.Alig

nment.LEADING)

.addComponent(jPanel3, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)

);

jDesktopPane1.add(addven, new org.netbeans.lib.awtextra.AbsoluteConstraints(480, 120, 1060,

700));

newbook.setClosable(true);

newbook.setDefaultCloseOperation(javax.swing.WindowConstants.HIDE_ON_CLOSE);

newbook.setTitle("New Booking"); newbook.setVisible(false);

jPanel4.setBackground(new java.awt.Color(255, 255, 255)); jPanel4.setLayout(new

org.netbeans.lib.awtextra.AbsoluteLayout());

39
 jLabel24.setFont(new java.awt.Font("Century Gothic", 1, 24)); // NOI18N

jLabel24.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel24.setText("New Booking"); jPanel4.add(jLabel24, new

org.netbeans.lib.awtextra.AbsoluteConstraints(460, 30, -1, -1)); jLabel27.setFont(new

java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel27.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel27.setText("Status :");

jPanel4.add(jLabel27, new org.netbeans.lib.awtextra.AbsoluteConstraints(350, 460, -1, -1));

jTextField4.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N

jTextField4.setBorder(javax.swing.BorderFactory.createMatteBorder(0, 1, 2, 1, new java.awt.Color(0, 0, 0)));

jPanel4.add(jTextField4, new org.netbeans.lib.awtextra.AbsoluteConstraints(530, 410, 280, -1));

jTextField5.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N

jTextField5.setBorder(javax.swing.BorderFactory.createMatteBorder(0, 1, 2, 1, new java.awt.Color(0,

0, 0))); jPanel4.add(jTextField5, new org.netbeans.lib.awtextra.AbsoluteConstraints(530, 460, 280,

-1));

jLabel32.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel32.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel32.setText("Booking ID :"); jPanel4.add(jLabel32, new

org.netbeans.lib.awtextra.AbsoluteConstraints(350, 410, -1, 20));

40
 jLabel33.setFont(new java.awt.Font("Century Gothic", 1, 18)); // NOI18N

jLabel33.setHorizontalAlignment(javax.swing.SwingConstants.CENTER); jLabel33.setText("Search");

jLabel33.setBorder(javax.swing.BorderFactory.createLineBorder(new java.awt.Color(0, 0, 0)));

jLabel33.addMouseListener(new java.awt.event.MouseAdapter() { public void

mouseClicked(java.awt.event.MouseEvent evt) { jLabel33MouseClicked(evt);

});

jPanel4.add(jLabel33, new org.netbeans.lib.awtextra.AbsoluteConstraints(840, 400, 120, 30));

jLabel34.setFont(new java.awt.Font("Century Gothic", 0, 16)); // NOI18N

jLabel34.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel34.setText("Change :"); jPanel4.add(jLabel34, new

org.netbeans.lib.awtextra.AbsoluteConstraints(350, 510, -1, -1));

jComboBox3.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N

jComboBox3.setModel(new javax.swing.DefaultComboBoxModel(new String[] { "Select-----", "Seen",

"Approved" })); jComboBox3.setPreferredSize(new java.awt.Dimension(56, 30));

jPanel4.add(jComboBox3, new org.netbeans.lib.awtextra.AbsoluteConstraints(530, 510, 280, -1));

jLabel35.setFont(new java.awt.Font("Century Gothic", 1, 18)); // NOI18N

jLabel35.setHorizontalAlignment(javax.swing.SwingConstants.CENTER); jLabel35.setText("Submit");

jLabel35.setBorder(javax.swing.BorderFactory.createLineBorder(new java.awt.Color(0, 0, 0)));

41
jLabel35.addMouseListener(new java.awt.event.MouseAdapter() { public void

mouseClicked(java.awt.event.MouseEvent evt) { jLabel35MouseClicked(evt);

});

jPanel4.add(jLabel35, new org.netbeans.lib.awtextra.AbsoluteConstraints(560, 560, 120, 40));

jScrollPane1.setBorder(null);

jTable1.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N jTable1.setModel(new

javax.swing.table.DefaultTableModel(

new Object [][] {

{null, null, null, null},

{null, null, null, null},

{null, null, null, null},

{null, null, null, null}

},

new String [] {

"Title 1", "Title 2", "Title 3", "Title 4"

));

jTable1.setRowHeight(22);

jTable1.setShowHorizontalLines(false);

42
jTable1.setShowVerticalLines(false); jTable1.addMouseListener(new

java.awt.event.MouseAdapter() { public void

mouseClicked(java.awt.event.MouseEvent evt)

{ jTable1MouseClicked(evt);

});

jScrollPane1.setViewportView(jTable1);

jPanel4.add(jScrollPane1, new org.netbeans.lib.awtextra.AbsoluteConstraints(30, 70, 980, 310));

javax.swing.GroupLayout newbookLayout = new

javax.swing.GroupLayout(newbook.getContentPane());

newbook.getContentPane().setLayout(newbookLayout); newbookLayout.setHorizontalGroup(

newbookLayout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)

.addComponent(jPanel4, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)

);

newbookLayout.setVerticalGroup( newbookLayout.createParallelGroup(javax.swing.GroupLay

out.Alignment.LEADING)

.addComponent(jPanel4, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)

);

43
 jDesktopPane1.add(newbook, new org.netbeans.lib.awtextra.AbsoluteConstraints(500, 130, 1060,
700));

bookhis.setClosable(true);

bookhis.setDefaultCloseOperation(javax.swing.WindowConstants.HIDE_ON_CLOSE);

bookhis.setTitle("Booking History"); bookhis.setVisible(false); jPanel5.setBackground(new

java.awt.Color(255, 255, 255)); jPanel5.setLayout(new org.netbeans.lib.awtextra.AbsoluteLayout());

jLabel25.setFont(new java.awt.Font("Century Gothic", 1, 24)); // NOI18N

jLabel25.setHorizontalAlignment(javax.swing.SwingConstants.CENTER);

jLabel25.setText("Bookings"); jPanel5.add(jLabel25, new

org.netbeans.lib.awtextra.AbsoluteConstraints(460, 30, -1, -1)); jScrollPane2.setBorder(null);

jTable2.setFont(new java.awt.Font("Century Gothic", 0, 14)); // NOI18N jTable2.setModel(new

javax.swing.table.DefaultTableModel(

new Object [][] {

{null, null, null, null},

{null, null, null, null},

{null, null, null, null},

{null, null, null, null}

},

44
 new String [] {

"Title 1", "Title 2", "Title 3", "Title 4"

));

jTable2.setRowHeight(22); jTable2.setShowHorizontalLines(false);

jTable2.setShowVerticalLines(false);

jScrollPane2.setViewportView(jTable2);

jPanel5.add(jScrollPane2, new org.netbeans.lib.awtextra.AbsoluteConstraints(30, 70, 980, 470));

javax.swing.GroupLayout bookhisLayout = new javax.swing.GroupLayout(bookhis.getContentPane());

bookhis.getContentPane().setLayout(bookhisLayout);

bookhisLayout.setHorizontalGroup( bookhisLayout.createParallelGroup(javax.swing.GroupLayout.Alignm

ent.LEADING)

.addComponent(jPanel5, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)

);

bookhisLayout.setVerticalGroup( bookhisLayout.createParallelGroup(javax.swing.GroupLayout.Alig

nment.LEADING)

45
 .addComponent(jPanel5, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)

);

jDesktopPane1.add(bookhis, new org.netbeans.lib.awtextra.AbsoluteConstraints(140, 0, 1060, 700));

viewven.setClosable(true);

viewven.setDefaultCloseOperation(javax.swing.WindowConstants.HIDE_ON_CLOSE);

viewven.setTitle("New Booking"); viewven.setVisible(false);

jPanel6.setBackground(new java.awt.Color(255, 255, 255)); jPanel6.setLayout(new

org.netbeans.lib.awtextra.AbsoluteLayout());

15. SCREEN SHOTS

46
47
48
49
50
51
52
53
54
 16. CONCLUSION
Our project is only a humble venture to satisfy the needs to manage their project work. Several user
friendly coding have also adopted. This package shall prove to be a powerful package in satisfying

55
all the requirements of the school. The objective of software planning is to provide a frame work
that enables the manger to make reasonable estimates made within a limited time frame at the
beginning of the software project and should be updated regularly as the project progresses.

• A description of the background and context of the project and its relation to work
already done in the area.

• Made statement of the aims and objectives of the project.

• The description of Purpose, Scope, and applicability.

• We define the problem on which we are working in the project.

• We describe the requirement Specifications of the system and the actions that can
be done on these things.

• We understand the problem domain and produce a model of the system, which
describes operations that can be performed on the system.

• We included features and operations in detail, including screen layouts.

• We designed user interface and security issues related to system.

• Finally, the system is implemented and tested according to test cases.

17. FUTURE SCOPE & LIMITATION

Scope: The scope of the Event Sphere project encompasses a comprehensive set of
functionalities and features aimed at addressing the challenges inherent in manual event
management systems while meeting the diverse needs of users and stakeholders. At its core, the
software will facilitate the efficient creation, management, and tracking of events, streamlining

56
processes such as scheduling, venue selection, attendee management, and resource allocation.
Additionally, a robust booking management system will be implemented to simplify the booking
process for events, services, and facilities, enabling users to check availability, make
reservations, process payments, and generate invoices seamlessly. The software will also include
an employee management module to facilitate scheduling, task assignment, and performance
tracking for staff involved in event planning and execution. Customization options will be
available to tailor event packages to meet specific client requirements, while a system for
tracking and managing inquiries will ensure prompt and effective communication with clients,
customers, and stakeholders. Remote access capabilities will enable users to access and manage
eventrelated information from anywhere, at any time, enhancing productivity and responsiveness.
Overall, the Event Sphere software will provide a user-friendly interface with built-in error
handling mechanisms to ensure data accuracy and integrity, thereby streamlining event
management processes and improving organizational efficiency.

• Further enhancements to this project will be to create a module for video upload
and download.

• Another enhancement would be allowing video conferencing.

• We will use payment gateway for online transaction.

• Other enhancement would be to allow multiple choice questions and subjective

questions. This would allow many varieties of questions to be added. The tutorials
can be made available in flash format and other animated formats.

Limitation: Although I have put my best efforts to make the software flexible, easy to operate
but limitations cannot be ruled out even by me. Though the software presents a broad range of
options to its users some intricate options could not be covered into it; partly because of logistic
and partly due to lack of sophistication. Paucity of time was also major constraint; thus it was not
possible to make the software foolproof and dynamic. Lack of time also compelled me to ignore
some part such as storing old result of the candidate etc.

Considerable efforts have made the software easy to operate even for the people not related to the
field of computers but it is acknowledged that a layman may find it a bit problematic at the first
instance. The user is provided help at each step for his convenience in working with the software.

57
 • Excel export has not been developed for Event, Booking due to some criticality.

• The transactions are executed in off-line mode, hence on-line data for Customer,
Employee capture and modification is not possible.

• Off-line reports of Event, Enquiry, Customer cannot be generated due to batch

mode execution.

BIBLIOGRAPHY

• Google for problem-solving

• http://www.javaworld.com/javaworld/jw-01-1998/jw-01-Credentialreview.html

58
• Database Programming with JDBC and Java by O'Reilly

• Head First Java 2nd Edition

• http://www.jdbc-tutorial.com/

• Java and Software Design Concepts by Apress

• https://www.tutorialspoint.com/java/

• http://www.javatpoint.com/java-tutorial • http://www.tutorialspoint.com/mysql/

59