- Cloud computing
- IoT
- A decision on the technical stack
- Architecture engineering
- UI/UX design
- Front-end/back-end development
- QA
- Product management
- SaaS deployment
- Technical consulting
- Requirements elaboration
- PostgreSQL
- HTML/CSS
- JavaScript
- Google Maps
- Java
- Angular
- DDD
- AWS
- AWS SQS
- AWS API Gateway
- AWS Fargate
- AWS RDS
- AWS Cloudfront
- AWS CloudFormation
- AWS CodePipeline / CodeBuild / CodeDeploy
Challenge
Navigating the maze of telematics testing and driver behavior monitoring challenges
The idea was to install video recording devices that record the environments both inside and outside the car. The devices have various sensors, including GPS, crash sensors, etc. The data collected by the device will serve as an actionable insight for the company to act on.
The task of the Euristiq team was to design a Cloud system that would process the data from the devices and collect information on the driver’s behavior on the road (driving skills, car condition, etc.).
After the assessment of the project, we identified key testing goals. In this case, we had hardware represented by the camera. We connected it to the vehicle and performed real-world testing to ensure it worked as the client intended. We aimed to check the following:
- How the camera generates data and whether it is accurate
- How the data is logged
- How the data is processed and visualized for the user
To perform such testing, the skills of driving license and the experience of working with data logs and databases.
Solution
Power of IoT testing techniques for telematics app and driver behavior monitoring
In the testing process, we found some critical bugs in the functionality of the selected hardware. To be specific, the data logging and accuracy issues.
The other challenge we encountered was related to the described manufacturer’s capabilities of the camera, which appeared to be unavailable. After contacting the producer, we established that some settings are on paper but not working efficiently in practice, and the manufacturer won’t be able to fix them. Hence, it should be treated as a limitation caused by the hardware. For example, the camera was supposed to react to change in acceleration. As per the manual, acceleration was categorized into three types low, medium, and high. However, they were not defined, so it was unknown what the camera considers a medium-acceleration.
Finally, the camera uses third parties, and it was essential for us to understand the cost of it. In our case, the video from two cameras was recorded to a flash drive and sent to the cloud using mobile Internet. The file size was the least favorable, leading to a high Internet bill. However, we managed to identify this issue early, to inform the client about the potential expenses.








