Flesh out requirements so more
This commit is contained in:
parent
17c2356486
commit
dca41013a0
|
@ -8,6 +8,8 @@
|
|||
\author{Danila Fedorin \and Matthew Sessions \and Ryan Alder}
|
||||
|
||||
\maketitle
|
||||
\tableofcontents
|
||||
\pagebreak
|
||||
|
||||
% From: ISO/IEC/IEEE 29148:2011, page 44
|
||||
% 1. Introduction
|
||||
|
@ -154,18 +156,94 @@ if necessary, the Android application \emph{should} assume domain specific knowl
|
|||
in the area of agriculture, since its intended audience is from this field.
|
||||
|
||||
\subsubsection{Servicability of Collars}
|
||||
Because the collars are intended to be battery-based, they will need to be serviced,
|
||||
with the minimum goal of replacing or recharging the on-board batteries. This
|
||||
must be possible to people with no prior technical experience, as the presence
|
||||
of such experience is not guaranteed the expected client base. Other common
|
||||
servicing goals, such as cleaning the device, should also be easy to accomplish
|
||||
without an understanding of the architecture or implementation of the FGC system.
|
||||
|
||||
\subsection{Performance requirements}
|
||||
\subsubsection{Battery Efficiency}
|
||||
Since the FGC device is battery powered and will require maintenance upon
|
||||
reaching low battery levels, it's important that the device is able to
|
||||
maintain an operational level of charge for long periods of time. That
|
||||
is, the number and duration of servicing actions should be low, in alignment
|
||||
with the original goal of reducing human labor. At minimum, the device
|
||||
should remain operational for 7 days (1 week).
|
||||
|
||||
\subsubsection{Support for Multiple Collars}
|
||||
As mentioned above, the goal for hte FGC system is to support large herds of animals,
|
||||
which normally require significant portions of time to be dedicated by humans.
|
||||
In order to properly support large herds, it must be possible for the system
|
||||
to support as many as 100 concurrently active collars without issue. This
|
||||
requirement applies to the collars themselves and the Android application:
|
||||
\begin{itemize}
|
||||
\item The collars themselves should not experience difficulties when concentrated
|
||||
in large groups (farm animals instinctively tend towards proximity).
|
||||
\item The Android application, given hardware that is not greatly outdated,
|
||||
should be able to display and manage this number of collars without
|
||||
additional delays.
|
||||
\end{itemize}
|
||||
|
||||
\subsection{System interface}
|
||||
\subsubsection{LoRa}
|
||||
@ryan \todo{write this}
|
||||
|
||||
\subsection{System operations}
|
||||
\subsection{System modes and states}
|
||||
Besides the "standard" operational mode for the collar, it
|
||||
is useful to envision other modes that help in troubleshooting
|
||||
and setting up the FGC system. We define the following modes:
|
||||
|
||||
\subsubsection{Standard}
|
||||
In this mode, the device uses the defined
|
||||
"out of bounds" area to determine whether or not to emit a negative
|
||||
stimulus. The produced negative stimuli are as defined in the
|
||||
sounds and electrical shock section of the functional requirements.
|
||||
|
||||
\subsubsection{Electric Shock Test}
|
||||
In this mode, the device operates identically to the standard mode
|
||||
described above, with the exception of not generating electrical
|
||||
shocks. Instead, the device should emit a different sound (or
|
||||
a visual signal) to indicate when the shock would have been delivered.
|
||||
This allows for safe testing of the device's behavior around area boundaries.
|
||||
|
||||
\subsection{Physical characteristics}
|
||||
\subsubsection{Weight}
|
||||
It's necessary for the device to be physically bearable by livestock for indefinite
|
||||
periods of time. If the resulting collar is a constant and noticable weight on the
|
||||
farm animal, it would serve as an unnecessary and permanent source of stress. Besides
|
||||
the ethical considerations of subjecting an animal to a constant level of stress through
|
||||
unnecessary physical labor (i.e. carrying a collar that is too heavy), this goes against
|
||||
the purpose of the project, since it will likely reduce the quality of the resulting animal
|
||||
management below the level that can be provided by humans.
|
||||
|
||||
\subsubsection{Form Factor}
|
||||
In order to be able to effectively use the collar, it must fit comfortably on target farm
|
||||
animals. In our initial prototype, these animals will be cows, and thus, a requirement
|
||||
for the project is that the collar can be put onto, and stay on a farm cow.
|
||||
|
||||
\subsection{Environmental conditions}
|
||||
\subsubsection{Water Resistance}
|
||||
The product will be tested in collaboration with Oregon State University's College of Animal
|
||||
Science, and therefore, will be tested in Oregon's climate. Since rain is very common
|
||||
during the winter months in Western Oregon, the device must be readily able to withstand
|
||||
such conditions, without sustaining any damage.
|
||||
|
||||
\todo{Anything else?}
|
||||
|
||||
\subsection{System security}
|
||||
\todo{Do we need this?}
|
||||
\subsection{Information management}
|
||||
\todo{Do we need this?}
|
||||
\subsection{Policies and regulations}
|
||||
\todo{Do we need this?}
|
||||
\subsection{System life cycle sustainment}
|
||||
\todo{Do we need this?}
|
||||
\subsection{Packaging, handling, shipping and transportation}
|
||||
\todo{Do we need this?}
|
||||
\section{Verification}
|
||||
\todo{Someone else please}
|
||||
|
||||
\end{document}
|
||||
|
|
Loading…
Reference in New Issue
Block a user