WanderSync employs several design patterns to ensure efficient and scalable architecture. The Model View ViewModel structure ensures efficient data binding between the UI and the underlying business logic.
Throughout the sprints, we implemented the Observer Pattern to update the UI in real-time when new data is added to the database. The dining reservation and travel community page both implement this pattern. The Singleton Pattern is used to manage the DatabaseManager, ensuring a single instance for consistent data handling.
| Domain Model |
The domain model represents the core entities and relationships in the Wanderly system. Introduces classes like Dining Reservation / Transportation . Supports collaborative trip planning. |
| Design Class Diagram |
A more technical Domain Model with attributes and methods. Shows relationships like aggregation, composition, and dependency. |
| Sequence Diagram: Login | Illustrates the user login process, including interactions for credential validation and navigation to the home screen. |
| Sequence Diagram: Dining |
Shows the flow of adding a dining reservation, from user input to storing details in the database. Includes error handling and confirmation of successful reservation creation. |
