## 3 Prototype Description and Implementation
### Prototyping of Hardware Components
It has been estimated that, considering the other parts of the UAV, this battery would have a duration of about twenty-one minutes. Due to the feedback received by the farm workers where tests took place, it has been regarded as enough for the in a circular to perform reconnaissance and herd-gathering missions. Considering that the UAV can travel at an average speed of 30 km per hour, during the battery life duration it could travel up to about 10 km without the risk of running out of energy. Based on the data shown, it can be concluded that the chosen battery satisfies the requirements of the project. * As for the Radio Control System of the aircraft, it offers the possibility of PPM or SBUS protocol and has 14 fully configurable PWM channels for the implementation of different modules. In addition, it has other ports and a high-sensitivity barometer that allows the UAV to be positioned with high accuracy. With all the features considered for the hardware parts of the proposed system, it can be claimed that the components integrated in this prototype are contributing to the fulfillment of the functional and non-functional requirements that were formulated in the previous section in Tables 4 and 5. Table 6 shows how this is done. Note that there are several not applicable requirements, as they are more software oriented. Nevertheless, they will be satisfied by the software components of the system. The components used for hardware prototyping can also be seen in Figure 2. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Requirement Number** & **Description** & **Fulfillment** \\ \hline Functional Requirement 1 & The UAV will FLY over cattle & Frame, Controller, Motors, RC \\ (FR1) & with as little disturbance as possible. & components, ESCs, Battery \\ Functional Requirement 2 & The UAV will HOVER over cattle with as little disturbance as possible. & Frame, Controller, Motors, RC \\ (FR2) & The UAV will perform missions & components, ESCs, Battery \\ Functional Requirement 3 & The UAV will perform missions in a GUIDED manner. & Frame, Controller, Motors, RC \\ Functional Requirement 4 & The UAV will perform missions & Frame, Controller, Motors, RC \\ (FR4) & in an AUTONMOUS manner. & components, Radio Control \\ Functional Requirement 5 & The UAV will transmit information as & components, SECs, Finder, Battery \\ (FR5) & REAL-TIME DATA. & Frames, Controller, Motors, RC \\ Functional Requirement 6 & The UAV will STORE DATA as part of the information collected. & Not Applicable. Fulfilled by IPFS and blockchain nodes \\ Non-Functional Requirement 1 & Security measures must be present in the UAV hardware. & Controller, RC components, Video Transmission System, \\ Non-Functional Requirement 2 & Security measures must be present in the software. & Radio Control Systems \\ (NFR2) & Security measures must be present in the software. & Not Applicable. Fulfilled by IPFS and blockchain nodes \\ Non-Functional Requirement 3 & Communications range must be of at least 5 milometers long. & Transmission System, Radio \\ Non-Functional Requirement 4 & Mission length must be of at least 15 min. & Battery \\ Non-Functional Requirement 5 & UAV must have components that can be repaired in situ. & Frame, Controller, Motors, RC \\ (NFR5) & UAV and missions must be compliant with & Frame, Controller, Motors, RC \\ (NFR6) & current legislation. & Systems, ESCs, Battery \\ \hline \hline \end{tabular}
\end{table} 
Table 6: Fulfillment of some functional and non-functional requirements with the UAV. It must be noted that the components represented in Figure 2 are placed in the same order as described in the manuscript: (a) Frame F450, (b) Navio2 controller, (c) FPV camera from the video transmission subsystem, (d) Video Transmisor AKK from the radio control subsystem, (e) Antenna RHCP 5, 8 GHz, (f) FPV Goggles Eachine EV800D, (g) RC System, (h) rotor MN2212, (i) ESC, (j) Finder JHE42B S and (k) battery.