How sonykar/usn.-android-group-project works
Key Components
• User Interface Layer: Represented by the various Activities (e.g., LoginActivity, SignUpActivity, CourseListActivity, etc.) and the supporting layouts (XML files under res/layout) and navigation components (MenuDrawer). This layer handles user interactions.
• Business Logic and Controllers: Shown as the controllers such as CourseController, CourseFilter, CourseSort, and the PictureController. These handle the main processing logic and mediate between the UI and data layers.
• Data Models: Include all model classes (e.g., Course, User, Category, Comment, etc.) located under the models package. These define the objects being manipulated across the system.
• Data Persistence/Database Layer: Indicated by the various database classes (e.g., CategoryDatabase, CourseDatabase, CommentDatabase, etc.) which interact with the underlying storage (likely backed by cloud services or local storage).
• External Services and Notifications: Include components related to notifications (FirebaseMessagingService, NotificationSender, APIService, etc.) and integration with Google services (google-services.json), showing how external events are managed.
• Utility and Miscellaneous: This covers adapters (that populate UI components like lists), constants, validations, and testing files (androidTest and test directories) used to ensure functionality and maintain code integrity.
Relationships and Interactions
• Notification & External Services: Outline how notifications are sent and received (Firebase services, API calls) and indicate integration with Google services.
• Utilities like Adapters: Show utility classes (adapters) as supporting the UI layer by binding data models to views.
Architectural Patterns to Highlight
• MVC-like Structure: Although Android architecture sometimes follows MVVM or MVP, here the separation between Activities (view), Controllers (logic), and Data classes (model) implies an MVC-like design.
• Testing Layer: Separate a unit/instrumentation testing section to indicate quality assurance supports.
Relevant Technologies and Frameworks
• Android SDK: All activities, layouts, and Android resource files imply the use of the Android framework.
• Firebase/Google Services: Presence of google-services.json and Firebase messaging classes suggest integration with Firebase or Google APIs.
• Gradle Build System: Shown through the build.gradle and settings.gradle files.
• Standard Java (or Kotlin) for business logic: Organize the code into packages for models, controllers, and utilities.