How 2729stormrobotics/scoutingradar2023 works
Main Components
• Mobile Application UI & Navigation:
• MainActivity with different fragments such as ConfigureScoutingFragment, PermissionsFragment, SettingsFragment, MatchRecordFragment, and scouting/fragments for Objective, Subjective, and Pit scouting.
• Navigation components (see /res/navigation/nav_graph.xml) that manage transitions between screens.
• Data Management Layer:
• AppDatabase along with DAO classes for various data types (objective, subjective, and pit scouting data).
• Data utilities like CSVCreator, DataUtils, and StringDecoder that handle data formatting and processing.
• Communication Modules:
• Bluetooth Handling: Classes like BluetoothReader and BluetoothServer indicate that data transfer via Bluetooth is supported.
• Data Import/Export Fragments and associated ViewModels (ExportDataFragment/ExportViewModel, ImportDataFragment/ImportViewModel) are used for consolidating and transferring collected data via CSV or QR codes.
• Configuration and Analytics:
• The configuration system relying on an external configuration file (uploadable into the app for setting up scouting modes) as described in the README.
• An analytics part exists outside the Android module (in the analytics directory) which includes Python scripts used to process and analyze time-based data (especially for objective scouting).
Out Relationships and Data Flow
• Data Management services (showing how user interactions trigger database operations through Repositories and DAOs).
• Communication modules (Bluetooth components) to illustrate data exchange between devices.
• UI triggers → ViewModels → Repositories/DAO → AppDatabase.
• Bluetooth server/client interactions to reflect two-way data transfers.
• Data export/import via designated fragments.
Architectural Patterns and Design Principles
• The structure suggests an MVVM or a Fragment-based architecture common in Android apps—with clear separation between UI (fragments/activities), business logic (ViewModels), and the data layer (Room or SQLite based database with DAOs).
• The use of separate modules for objectives versus subjective versus pit scouting shows a clear modular breakdown of functionality.
• Communication (Bluetooth) and configurability enhance the extensibility and separation of concerns within the app.
Technologies, Frameworks, and Tools
• Android SDK with specific layouts, fragments, and activities managed through Android Studio.
• Gradle build system (multiple build.gradle files).
• Likely a database framework (such as Room) given the structure of AppDatabase and DAOs.
• For data analysis, external Python scripts (Tableau Prep Builder flow integration indicated in README) and CSV exporting (use of CSVCreator).
• Bluetooth APIs for data transfer.
Elements
• Labels for every major component such as UI Components, Data Management Layer, Communication Modules, and Analytics/Configuration.
• The UI and the business logic (ViewModels and Repositories).
• The business logic with the Database and external transfer modules.
• External configuration and analytics processes.
• User interface elements (activities, fragments)
• Data storage elements (database and DAO components)
• Transfer mechanisms (Bluetooth and QR Code exchange modules)
• External artifacts (analytics scripts and configuration files).