Compare commits
3 Commits
8ab0f3c181
...
master
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
df2e03acb4 | ||
| b7a587b7b6 | |||
| 479dd8de23 |
@@ -52,15 +52,17 @@
|
||||
}
|
||||
\begin{abstract}
|
||||
The Fenceless Grazing Collar system aims to reduce the amount of work
|
||||
needed by farmers to keep herds of grazing animals. Throughout the
|
||||
Fall term, our team has conducted research into the specifics of our
|
||||
project which culminated in a complete design detailing exactly how
|
||||
the project will be implemented. Work was spread out over the ten weeks,
|
||||
with the ultimate goal of completing the required plan prior to
|
||||
implementation. Throughout the term, our team completed progress reports
|
||||
in order to document our progress. This has been assembled into this
|
||||
one document, detailing our work throughout the Fall term.
|
||||
\end{abstract}
|
||||
needed by farmers to keep herds of grazing animals. During the fall
|
||||
term our team defined the problem that needs to be solved, drafted
|
||||
a document detailing the requirements of the project, and completed
|
||||
a design document and review with our client. Our client for this
|
||||
project has approved our design, setting us on the path of
|
||||
purchasing hardware. One of the largest issues we have encountered
|
||||
during the Fall term was a lack of funding, which will limit
|
||||
our ability to purchase hardware in the near future. Our team will
|
||||
solve this problem through constant communication with our TA and
|
||||
Dr. Winters.
|
||||
\end{abstract}
|
||||
\end{singlespace}
|
||||
\end{titlepage}
|
||||
|
||||
@@ -70,7 +72,6 @@
|
||||
\pagebreak
|
||||
|
||||
\section{Introduction}
|
||||
% TODO briefly recap the project purposes and goals
|
||||
This document describes the current state, problems, and future
|
||||
plans of the Fenceless Grazing Collars project. The FGC system's
|
||||
purpose is to reduce the amount of manual labor required for herding
|
||||
@@ -82,7 +83,6 @@ provide a reliable, cost-effective, and accessible replacement
|
||||
for manual farmer labor.
|
||||
|
||||
\section{Current Project State}
|
||||
% TODO describe where you are currently on the project
|
||||
At present, the initial design of the project is complete. The project's structure
|
||||
lends itself very well to division among the three group members, and all
|
||||
team members' responsibilities have been explicitly defined and agreed upon.
|
||||
@@ -129,9 +129,6 @@ others, we will peruse the online documents, modules, and extra links provided t
|
||||
that we are not asking questions that have already been answered.
|
||||
|
||||
\section{Weekly Progress}
|
||||
% TODO The document should include a detailed, week-by-week summary of activities,
|
||||
% problems, solutions, and the like (consider using your blogs to inform this report).
|
||||
% The report should not include more than a summary of any bigger documents you produced
|
||||
This section provides weekly summaries for every week of our Fall 2019 term for which the
|
||||
project was active.
|
||||
|
||||
@@ -249,10 +246,6 @@ responsibility for parts of each assignment.
|
||||
|
||||
\pagebreak
|
||||
\section{Retrospective}
|
||||
% TODO add retrospective
|
||||
% positives column: anything good that happened
|
||||
% deltas column: changes that need to be implemented
|
||||
% actions column: specific actions that will be implemented in order to create the necessary changes
|
||||
\setlength{\columnseprule}{0.4pt}
|
||||
\begin{parcolumns}[colwidths={1=0.3\textwidth}]{3}
|
||||
\colchunk{
|
||||
@@ -312,6 +305,14 @@ responsibility for parts of each assignment.
|
||||
The team must change the means of distributing tasks. The method used in this term,
|
||||
which was heavily based on individual initiative, led to an improper distribution of
|
||||
work and time.
|
||||
|
||||
Although one of the requirements for the project is the usage of the LoRa long range
|
||||
communication protocol, the team is not very familiar with the protocol's details.
|
||||
This has not been an issue for the documentation stage; the design document could
|
||||
be written with sufficient thoroughness. However, to proceed with the implementation
|
||||
of the LoRa gateway (device responsible for communicating with the collars), as well
|
||||
as the collars themselves, a more in-depth understanding of the LoRa protocol
|
||||
is required.
|
||||
}
|
||||
\colchunk{
|
||||
\subsection{Actions}
|
||||
@@ -330,6 +331,11 @@ responsibility for parts of each assignment.
|
||||
to assign and manage tasks. This way, a specific person will be responsible for
|
||||
assigning tasks, rather than relying on initiative like was done before. Assigning
|
||||
team members to individual tasks will serve the same purpose.
|
||||
|
||||
To address the lack of understanding of the LoRa protocol, all members of the team will spend
|
||||
the first week of the next term reading the LoRa documentation. Although only
|
||||
two members of the team must work in-depth with LoRa, an understanding of the protocol
|
||||
will be useful to every member.
|
||||
}
|
||||
\end{parcolumns}
|
||||
\end{document}
|
||||
|
||||
Reference in New Issue
Block a user