Sprint 7: Technical and Risk Assessment
Sprint Goal
Evaluate the legal, privacy, and security implications of the system, and develop the proximity filter to refine data relevance.
Sprint Planning
This sprint is dedicated to ensuring our application complies with relevant laws and protects user privacy, especially given the sensitive nature of real-time location and telemetry data. Additionally, we will develop a Proximity Filter to optimize data transmission and system performance, alongside conducting a comprehensive security validation of our architecture.
Tasks
- Legal Requirements
- Privacy and Data Protection
- Security validation
- Proximity Filter Development
Progress
- Documented the legal requirements applicable to the system, including a PESTEL analysis, SWOT/TOWS matrices, terms of use, and a risk assessment, all published to the microsite.
- Reviewed privacy and data protection obligations around real-time location and telemetry data, defining how user data is handled, minimized, and protected.
- Security Validation almost complete: encrypted communication between components and authentication on the message flow
- Developed the Proximity Filter, a microservice that discards irrelevant data before it reaches the detectors, reducing load on the pipeline
Challenges
- Mapping the legal and privacy framework onto a system that continuously processes sensitive location and telemetry data.
- Validating security without a dedicated security team, relying on architectural review and encrypted, authenticated channels.
- Tuning the Proximity Filter radius to drop noise without ever filtering out an event the driver actually needed to see.
Sprint Review
This sprint shifted the focus from features to compliance and robustness. The legal, privacy, and security work gives the project a solid non-functional foundation, and the Proximity Filter measurably improved the relevance of the data flowing through the detectors and the overall efficiency of the system.