How aclab-hcmut/thesis_mdt260_application_motion_detection works
This project is a full-stack application that combines a Flutter frontend with a Node.js–based backend. The purpose is to serve as a starting point for a Flutter application (as indicated by the README) with an accompanying backend API server that supports various functions like user management, activities, real-time communications through sockets, and more.
Main components
• Frontend: A Flutter application intended to run on multiple platforms (Android, iOS, web, Linux, macOS, and Windows). The Flutter codebase is structured under the “frontend” directory, featuring components, screens, models, services, and localization support.
• Backend: A Node.js–based server located in the “backend” directory. It follows an MVC-inspired structure with directories for controllers, routes (in different API versions v1 and v2), models, middlewares, validations, sockets (for real-time features), configuration files, utility functions, and providers.
• Database/External Services: Although not explicitly detailed, the “backend/src/config/mongodb.js” file suggests that MongoDB is used as the datastore.
• (Optional) Socket Server: Under “backend/src/sockets”, the inclusion of a sample socket file indicates support for real-time communications which can be diagrammed as an additional component interacting with the backend.
Component relationships and interactions
• The Backend handles requests via route files, passes them to controllers, and interacts with the database to process data. This flow should be shown in a step-wise or layered manner. For example:
• API Request → Route → Middleware (authentication, error handling, etc.) → Controller → Database/Model interaction → Response back to Frontend.
Architectural patterns and design principles
• The backend design seems to follow the Modular/Layered architecture with clear separations for configurations, routes, controllers, models, middlewares, and validations.
• The frontend leverages Flutter’s standard project architecture with separation of UI components, screens, services, and models.
• Separation of concerns between client-side UI handling and server-side business logic.
Relevant technologies/frameworks
• For the frontend, note Flutter and Dart as the programming language/environment along with support for multi-platform deployment (Android, iOS, web, etc.).
• For the backend, note Node.js alongside configuration files for Babel, ESLint, and environment configurations, as well as MongoDB for database operations.
• Mention additional functionalities like WebSocket support for real-time communications.
Final checklist
• Components are clearly labeled.
• Be as detailed as possible by separating the components into their submodules (routes, controllers, middlewares, etc.) to capture the maximum granularity of the system’s architecture.
• Notes on any potential extensibility points, such as the WebSocket service and the provider modules, to give a clear picture of how the system can evolve.