https://github.com/rickbarretto/events

Event Management System written in Java - PBL II - Algorithms & Programming II
https://github.com/rickbarretto/events

clean-architecture ddd learning oop pbl problem-based-learning

Last synced: 8 days ago
JSON representation

Event Management System written in Java - PBL II - Algorithms & Programming II

• Host: GitHub
• URL: https://github.com/rickbarretto/events
• Owner: RickBarretto
• Created: 2024-09-21T19:29:22.000Z (about 2 months ago)
• Default Branch: main
• Last Pushed: 2024-10-21T11:38:31.000Z (25 days ago)
• Last Synced: 2024-10-21T15:18:34.540Z (24 days ago)
• Topics: clean-architecture, ddd, learning, oop, pbl, problem-based-learning
• Language: Java
• Homepage:
• Size: 3.77 MB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Events Management

This project is a PBL (Project-Based Learning) initiative for my university's Programming and Algorithms II course. 

It focuses on applying OOP principles in Java through practical, real-world scenarios.

The requirements are:

- Must be written in Java

- Must follow some project requirements

- Must not use database, but store data into Json files

## Features

- **Event Creation:** Administrators can create new events. 

- **User Management:** The system manages administrators and regular users.

- **Ticket Sales:** Includes a ticketing system where users can buy tickets for events.

- **Event Listings:** Users can browse through a list of available events.

- **Event Evaluation:** After attending events, users can evaluate them.

- **Refund Management:** The project also supports ticket refunds.

- **Database Integration:** All the event and user data is stored in a Json database.

## Project's Structure

This project uses Clean Architecture and Domain-Driven Design (DDD) for learning purposes. 

The choosen Architecture ensures modularity and testability by separating the code into layers. 

With this in mind, the project's structure aligns perfectly with this approach. 

Here's a look at the src/main structure:

- `domain`: The business logic

    - `context`: Provides all context needed for the user's stories

    - `exceptions`: Contains all domain-specific exceptions

    - `models`: Includes all models (entities and value objects)

- `infra`: The infrastructure code

    Handles database interactions and external services

- `roles`: All interfaces that define the logic

    Ensures flexibility between the infra and domain layers

## Workspace's Structure

The workspace contains three main folders:

- `docs`: the documentation generated from Javadocs 

- `lib`: the necessary `.jar` dependencies

- `src/main`: the source code

- `src/test`: the test files

## Documentation

* [Online Page](https://rickbarretto.github.io/events)

* [Online Documentation](https://rickbarretto.github.io/events/docs)

* [Local Documentation](./docs/index.html)

## Java Version

```

java 22.0.2 2024-07-16

Java(TM) SE Runtime Environment (build 22.0.2+9-70)

Java HotSpot(TM) 64-Bit Server VM (build 22.0.2+9-70, mixed mode, sharing)

```

## Used VsCode Extensions

### Extension Pack for Java

* Id: vscjava.vscode-java-pack

* Description: Popular extensions for Java development that provides Java IntelliSense, debugging, testing, Maven/Gradle support, project management and more

* Version: 0.29.2024091906

* Publisher: Microsoft

* VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack

### GitHub Theme

* Id: GitHub.github-vscode-theme

* Description: GitHub theme for VS Code

* Version: 6.3.5

* Publisher: GitHub

* VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=GitHub.github-vscode-theme