## 3 Prototype Description and Implementation
### Prototyping of Hardware Components  
As far as hardware components are concerned, the UAV that has been built as a livestock monitoring tool has two fundamental subsystems. The first of the subsystems is a Command Ground Station (CGS) that, for convenience in receiving information and sending commands, must be located next to the flight operator. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Requirement Number** & **Description** & **Purpose** \\ \hline Functional Requirement 1 & The UAV will FLY over cattle & Basic functionality expected \\ (FR1) & with as little disturbance as & for cattle monitoring. \\ Functional Requirement 2 & The UAV will HOVER over cattle with as little disturbance & Basic functionality expected \\ (FR2) & as possible. & for cattle monitoring. \\ Functional Requirement 3 & The UAV will perform & Asility to monitor cattle as the \\ (FR3) & missions in a GUIDED & main task. \\  & manner. & \\ Functional Requirement 4 & The UAV will perform & Ability to ease the farmer from \\ (FR4) & AUTONOMOUS manner. & constant monitoring tasks. \\ Functional Requirement 5 & The UAV will transmit & Instant information about \\ (FR5) & information as & livestock movement and \\  & REAL-TIME DATA. & location can be obtained. \\ Functional Requirement 6 & The UAV will STORE DATA & Ability to have data saved for \\ (FR6) & as part of the & future processing and/or \\  & information collected. & knowledge inference \\ Functional Requirement 7 & Data will be SHARED among & Ability to share information \\ (FR7) & relevant parties participating & among different entities in a \\  & in the system & reliable, trustless manner \\ \hline \hline \end{tabular}
\end{table} 
Table 4: List of the UAV functional requirements. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Requirement Number** & **Description** & **Purpose** \\ \hline Non-Functional Requirement & Security measures must be & The UAV must not be hijacked \\ (NFR1) & present in the UAV hardware. & or tampered with in any way. \\ Non-Functional Requirement & Security measures must be & The data collected from the \\ (NFR2) & present in the software. & UAV must not be tampered with in any way. \\ Non-Functional Requirement & Communications range must be of at least & The UAV must be able to fly \\ (NFR3) & 5 milometers long. & through the countryside with \\ Non-Functional Requirement & Mission length must be of at & no restraint for monitoring. \\
4 & least 15 min. & The UAV must have enough \\ Non-Functional Requirement & UAV must have components & The UAV must be repaired \\
5 & that can be repaired in situ. & without significant aid from \\ (NFR5) & UAV and missions must be & the UAV deployment and \\
6 & compliant with & data gathering must respect \\ (NFR6) & current legislation. & existing legislation. \\ Non-Functional Requirement & Data must be shareable & Information will be provided \\
7 (NFR7) & among interested parties in a & in a transparent way to any \\  & reliable manner & partly providing perks \\ Non-Functional Requirement & Data must be transferred in a & Hardware and software \\  & secure manner through & components used will provide \\
8 (NFR8) & the system & security measures \\ \hline \hline \end{tabular}
\end{table} 
Table 5: List of the UAV non-functional requirements, as obtained from studied literature and questions formulated to farmers. The CGS can be built with a computer capable of running a mission planner software [27] and a display connected to a 5.8 GHz analog video receiver. Through this base station, the operator will have detailed telemetry of the aircraft, without requiring a too steep learning curve. Telemetry information will display data to help the operator with any decision making during the flight in case the flight is guided (so the operator is effectively maneuvering the UAV). Some of these data are (a) the position of the aircraft, (b) its altitude or (c) the State of Charge (SOC) of the battery.