## 5 Director's Dashboard
### Use Case Analysis  
Figure 2 shows the use case breakdown of the Dashboard. The roles involved in the process include both human actors and machine system components (shown, respectively, as man icons and gray rectangles in Figure 2). The director is responsible for defining, leading, and coordinating the editorial shooting missions. The role of the cameramen is to operate the cameras on board the drones, thus replacing their autonomous operation when necessary due to production requirements. The editorial staff deals with the data entry of events, possibly organizing them hierarchically in \begin{table}
\begin{tabular}{l l l} \hline \hline  & & SHOOTING ROLE \\ \hline
**Field Name** & **Data Type** & **Comment** \\ \hline Shooting type & Discrete value & Lateral, chase, static, orbit, fly-through, etc. \\ \hline Framing type & Discrete value & Long shot, medium shot, close up, etc. \\ \hline Shooting & & e.g., distance to the target in a lateral, angular velocity in an orbit, etc. \\ parameters & Set of parameters & e.g., distance to the target in a lateral, angular velocity in an orbit, etc. \\ \hline Shooting target & Natural number & Identifies the shooting target to film \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Structure for the data type SHOOTING ROLE. \begin{table}
\begin{tabular}{l l l} \hline \hline  & & DRONE ACTION \\ \hline
**Field Name** & **Data Type** & **Comment** \\ \hline Action type & Discrete value & Takeoff, land, go-to-waypoint or shooting \\ \hline Action ID & String & Identifies the corresponding shooting action \\ \hline Start event & String & Identifies the event that triggers this drone action \\ \hline Shooting action & SHOOTING ACTION & The shooting action if type is “shooting” \\ \hline Path & List of waypoints & List of waypoints to follow if type is “go to waypoint” \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Structure for the data type DRONE ACTION. sub-events. The system administrator is responsible for effective provisioning, configuration, operation, and maintenance of the Dashboard. The Mission Controller is the autonomous module in charge of controlling the mission production workflow. It generates signals upon the occurrence of leaf events in to trigger associated shooting actions on board the drones. Some leaf events may be manually triggered by the director, e.g., to start a race. Others may be generated automatically, e.g., after detecting the appearance of a point of interest. The Mission Controller is also in charge of managing semantic maps, i.e., Keyhole Markup Language (KML) files [20] representing a set of geolocalized features such as landing/take-off spots, no-fly zones, or points of interest. These maps are first created offline during the pre-production phase and displayed on the Dashboard. Then, during mission execution, they might be automatically updated if new features were detected, e.g., obstacle or crowd regions detected by the drone cameras. The human and machine actors defined above interact with each other in order to create and manage an editorial shooting mission (see Figure 2). There is a higher-level process preceding any shooting mission, which is that of event management, i.e., the process by which events are organized hierarchically, and by which specific events are associated with missions planned to be executed in reaction to them. The process of mission production is split into mission planning and mission execution. Mission planning is the process in which all aspects related to each mission are defined. These include, e.g., expected starting time and duration, shot types, shooting targets like the leader of a race or a geographic points of interest within the race route, etc. The mission planning process can be further broken down into a mission configuration process, optionally supported by a mission simulation process, which depends on the former.