Skip to main content

Sprint 6: Improve Final System

Sprint Goal​

Make the system better and more complete by adding important features, accessibility support, and ensuring foundational performance and data persistence.

Sprint Planning​

During this sprint, the focus shifts towards improving user experience, personalization, and system robustness. We aim to add accessibility features (colorblind mode, multiple language support), introduce user personalization (login), integrate a persistent database, handle the Traffic Use Case, and conduct baseline performance tests.

Tasks​

  • Traffic UC
  • Implement login system
  • Colorblind accessibility mode
  • Multiple Languages Support
  • Database Integration
  • Performance Tests

Progress​

  • Traffic Use Case is now fully implemented: the Traffic Jam detector aggregates vehicle density and speed along a road segment and pushes congestion alerts to the frontend.
  • A complete login/authentication system was added on top of the DT4MOB authentication service, making LoginActivity the app's launcher and enabling per-user preferences.
  • Accessibility was expanded with a colorblind mode (adjusted alert colors and contrast) and multi-language support, allowing the UI to adapt to the driver's preferred language.
  • A persistent database (Preference Database) was integrated through the Database Manager service, so user settings and preference filters survive across sessions.

Challenges​

  1. Wiring the login flow into an Automotive OS launch sequence while keeping every screen distraction-optimized.
  2. Keeping colorblind palettes and translated strings consistent across all alert types and UI components.
  3. Designing the preference schema so the database integration did not add noticeable latency to the real-time event flow.

Sprint Review​

A good sprint for system maturity and inclusivity. Our app now supports personalized accounts, persistent preferences, accessibility options, and an additional safety use case (traffic congestion).