How foxriver-2005/dekutvote-digital-electronic-voting-system- works
Main Components
• Mobile Presentation Layer: This includes the Android Activities, Fragments, and XML layout files (found under app/src/main/res/layout). Key screens include Login, Registration, Dashboard, Admin Approval, Election/Poll management, user vote screens, and other related UI screens.
• Business Logic Components: The Java classes located in app/src/main/java under the package “com.lelei.dekutvote” and its sub-packages (Adapters, models, etc.) represent the core application logic. Here, classes like Login.java, CreateElection.java, AdminApproval.java, and various Adapters encapsulate the interactions, role-based operations, and data binding.
• Data Models: The classes in the “model” package (e.g., AdminApprovalList, UserList, VotingReceiptsList) structurally define data used for elections, polls, user management, and logs.
• External Services/Integration: The presence of google-services.json indicates integration with Google/Firebase services for analytics, push notifications, authentication, or database storage. Although backend endpoints are not directly present in the file tree, these integrations function as out-of-app services.
• Utility/Support Components: Additional resources such as animations, drawables, and XML configuration files add to UI effects and standard Android behavior.
Relationships and Interactions
• The UI Layer (Activities and Layouts) interacts with the business logic components through various controllers (and corresponding event handlers) to process user inputs.
• Adapters serve as connectors between data models and various list or grid UI components, managing the display of dynamic information (e.g., election lists, poll selections, logs).
• Business logic classes use the data models to retrieve and update vote data, manage user roles (voter, admin, faculty), handle registration and verification, and log user activities.
• External services (Firebase) are called from within these logic components to authenticate users, push notifications (e.g., verification emails), and possibly store or retrieve election data.
• A clear interaction flow exists between user actions (e.g., registration, casting a vote), business logic processing (validation, role-based decision making), and updates to the user interface.
Architectural Patterns and Design Principles
• MVC/MVVM-like Separation: Although not explicitly described, the project’s structure separates the UI (Activities/Layouts), the business logic (Adapters, Activities, and utility classes), and the data (models).
• Integration with Cloud Services: The google-services.json file points to external integrations (e.g., Firebase), which should be illustrated as separate external components interacting with the mobile app.
Relevant Technologies and Libraries
• Android SDK components (Activities, XML-based layouts, resource directories)
• Firebase/Google Services (for authentication, cloud messaging, and possibly database storage)
• Java-based adapters and models specific to the app’s voting process, logging, and user management functionalities