Event Visualizer

Project Statement

Problem:
On a broader scale, the ethos of DIY culture is rooted in limited or no access to the resources and tools needed to achieve a goal. Small-scale event planners (with a focus on music events) embody this philosophy, turning challenges like lack of industry experience, location, and commercialism—common barriers to entry—into opportunities for innovation. Rather than seeing these limitations as setbacks, DIYers view them as a silver lining, using them as fuel to adapt creatively and bring their visions to life. In contrast, larger operations with commercial backing or established names follow proven strategies and rules to ensure success, but it’s the resourcefulness of the DIY community that drives their unique approach to achieving goals.\ \ However, many current event planning tools, such as Eventbrite—the most popular platform—are designed with larger commercial entities in mind. While Eventbrite facilitates event planning, its emphasis on client-side interaction, ticket sales, reporting analytics (like sales and customer reach/retention), and marketing campaigns does not address the primary concerns of DIYers. DIY event planners need tools that help them organize their unique ideas and customize the planning process to fit their specific needs, rather than focusing on ticket sales and revenue tracking.

View of Eventbrite's event builder page


View of Eventbrite's event builder page

Solution:
DIY Event Visualizer is a resource designed for the resourceful. It offers a flexible, customizable blueprint tailored specifically for DIY event planners. Unlike platforms like Eventbrite that prioritize sales and analytics, the DIY Event Visualizer focuses on creative freedom and adaptability, giving DIYers a place to house their ideas and customize the planning process. By covering the basics of event planning and allowing for personalization, it empowers DIY planners to turn their creative visions into reality, while overcoming the unique challenges they face without relying on traditional, sales-focused tools.

Applied Technologies & Techniques

IDE

• Intellij

Build Configuration

• Maven (dependency management)
• POM.xml (project dependencies)
• WAR file (project packaging build tool)

ORM

• Hibernate v 6.4.3 final

Version Control

• GitHub

Logging

• Log4j2

Database

• MySQL v 8.1.0

Application Server

• Servlet/JSP Container
• Apache Tomcat 8.5 (WAR file deployment)

Programming Languages

• Java
  • Back-end/server-side technology
• Javascript
  • Front-end/client-side scripting

Runtime Environment

• JDK v 11.0.20

Web Service

• RESTful API
  • Handles client/server interactions
  • HTTP methods GET,POST,PUT,DELETE (CRUD)
• Jackson
  • Java/JSON serialization/deserialization
• Jersey
  • Handles HTTP requests/response between client

Web Application

• Presentation Layer
  • JSP
• JSTL tag library
• Markup languages
  • HTML/CSS

Client-Side Scripting

• JavaScript

Client-Server Communication

• AJAX

Unit Testing

• Junit (Jupiter) v 4.13.1

CSS

• Bootstrap v 5.3.0

Project Documentation

• Markdown

Supplementary Files

Project Plan • User Stories • Screen Design • Reflection Journal