...
User Classes and Characteristics
For this product, we'll realise realize two types of users. Firstly, there's the crewmembers, who are our main scope. A crewmember can view a race and retrieve all of its real-time and past data. Second, there's the viewers, who can only view the race with a restricted set of data that is updated real time. Viewers can not select what kind of data they wish to see, all data that is visible for them will be visible at all time whilst watching the race.
...
Our web-application's back-end will be built in Java 17 and Maven and our front-end will be built in Angular 14.0 and Bootstrap 5.0. The application will run in Wildfly 25.0.0, which allows us to run the website locally. We will use Java Database Connection (JDBC) to establish a connection between our database and our web-application. We'll also use a Broker to establish a connection between the racecar's sensors and our application, which allows us to receive a constant stream of data. The broker will also send data to the database, so that past data can be seen aswellas well.
Design and Implementation Constraints
The product owner has not given a lot of constraints for this project. There are still a few technical limitations that limit our options. The car's data is being sent to the database twenty times per second. Because Regterschot Racing wants a constant stream of data to the application, it is required to use TCP as a communication protocol. This data has to be converted into charts and in order to do this fast and reliable, we graphs because a clear overview of all data is demanded. We will have to use Google Charts . because Google Charts runs in a web-application and can update the data twenty times per second (Lijden & Kooy, 2022).
...