...
The use-case diagram for Regterschotracing looks like this, with the viewer and crewmember that were mentioned in the domain model now acting as actors that interact with our system. A view viewer can watch a race and enjoy the enticing race from the comfort of their own couch. A crewmember has to analyse the data from the racecar in graphs that are placed in tabs whilst watching a race, so there's two distinct user-actions that solely crewmembers can perform. Furthermore, the graphs that are used by a crewmember connect to an external actor, the broker. This is a servie that can send a long stream of data to our application without requiring constant requests for fetching said data.
...