How fionaverzivolli/eventhiveuoft works
Main Components
• Frontend / Presentation Layer:
– Represented by the "view" package and parts of the interface_adapter (e.g., LoginView, CreateEventView, DisplayEventView, etc.). This layer is responsible for handling user interaction through the various UI screens (including the interactive campus map using JXMapViewer) and routing display output.
• Application/Use Case Layer:
– Located under the "use_case" packages. This is where the business logic resides. For each feature (such as event creation, modification, RSVP handling, login, registration, etc.), there are corresponding interactors and associated input/output boundary interfaces.
• Data Access Layer:
– Found within packages like "data_access" as well as parts handling Firebase configuration and Email sending. This layer interfaces with external dependencies such as Firebase for persistent storage and email notifications.
• Domain/Entity Layer:
– The "entity" package holds core business entities (e.g., Event, User) and their factories, encapsulating essential business rules.
• Testing:
– Although not directly part of runtime architecture, the "src/test" directory confirms the use of unit testing across components.
Relationships and Data Flow
– Interface Adapters (Controllers, Presenters, View Models)
– Use Cases / Interactors (each feature’s core driver, for example, CreateEventInteractor, LoginInteractor, RSVPEventInteractor)
– Gateway / Data Access components (FirebaseService, EmailSender, DAOs)
– Domain Entities (Event, User)
– User actions in the Presentation Layer → Requests routed to Controllers → Passed to Interactors (Use Case Layer)
– Interactors call Data Access interfaces (via Firebase or Email services) and send processed data back through Presenters → then update the Views.
• External services like Firebase (for storage, authentication, and real-time updates) and the email infrastructure (via EmailSender).
Architectural Patterns
• Clean Architecture / Hexagonal Architecture:
– Emphasize the separation where the outer layers (interface_adapter and data_access) depend on inner use cases and domain, not vice versa.
• MVC-like Separation:
– Although a strict MVC isn’t used, the separation of controllers (handling input logic), presenters (processing data for the views), and view classes is critical.
• Dependency Inversion:
– The use of interfaces (e.g., data access interfaces in use cases) shows the inversion of dependencies, allowing for better testing and flexibility.
Relevant Technologies/Frameworks
• Java with Spring Boot (as indicated by Maven’s pom.xml and Spring Boot’s typical dependencies).
• Firebase (for storage, authentication, and real-time database, managed through FirebaseConfig and FirebaseService).
• JXMapViewer library for the interactive map.
• Maven as the build tool.
• Testing frameworks integrated into the src/test suite (JUnit, etc.).
Additional Details
• Asynchronous or real-time elements (especially for email notifications and live event updates via Firebase).