...
User Classes and Characteristics
This product will be used by the Regterschot Racing team. In the future, users that are not part of the team, may be able to login to the website to view the race. The racing team are able to see the statistics of the car during and after the race.
...
For this product, we'll realise 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.
These users can both log in into our web-application. A crewmember can see more options when logged in, as they can view back races and watch live races, whereas a viewer can only watch live races.
Operating Environment
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 recieve a constant stream of data
<Identify the various user classes (actors) that you anticipate will use this product. User classes may be differentiated based on the subset of product functions used. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. >
Operating Environment
The software will operate on Java 17 and will use maven. The program will run in jboss/wildfly 25.0.0.final. The connection to the database and the execution of queries are done with JDBC. The data can be seen using a TCP connection since the program needs a constant stream of data. On top of that, we'll use Angular as our front-end framework.
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. For constant streaming of data to the application, it is required to use TCP as a communication protocol.<Describe any items or issues that will limit the options available to the developers. These might include: hardware (e.g. specific mobile platforms), specific technologies, tools, and databases to be used; interfaces to other applications; programming language required; or communications protocols>
Product Functions
The product must present data from the sensors of the racecar. The user is able to login to the site and choose how the data is presented. The product stores all the data from the sensor for future purposes.<Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary is needed here. In most cases, this section will primarily contain a use case diagram and brief use case descriptions >