How shifaabarham/event-planner-system works
Project type and purpose
• This is a standalone Java “Event-planner-system” console application (not a web app).
• It implements user authentication, event creation/editing/deletion/search, booking/payment, and notification delivery.
• Persistence is file-based (UserFile.txt, EventFile.txt) with simple repositories.
File structure
Top-level
• pom.xml → Maven build & dependencies
• cases/ → Cucumber feature files (Gherkin) covering authentication, event planning, notifications
• src/main/java/
– components/ → service-layer classes (UserComponent, EventComponent, Checker, ImageUploader, SendMail)
– repositories/ → data access classes (UserRepository, EventRepository)
– special/event/ → domain model + orchestration (Event, User, Place, Notification, BookingSystem, Main)
• src/main/resources/ → file storage (EventFile.txt, UserFile.txt) + images
• src/test/java/ → acceptance & unit tests against the domain
Deployment & CI
• .github/workflows/main.yml → GitHub Actions pipeline
• target/ → Maven build output
(minimal) README
• Confirms the project name but has no additional architectural guidance.
Elements
e.g., Main → BookingSystem → UserComponent → UserRepository → UserFile.txt
→ Checker for validation → SendMail → SMTP Service
• Presentation (light blue)
• Service components (green)
• Domain model (yellow)
• Repositories/persistence (orange)
• External systems (gray)