Permalink
Browse files

ordered requirements

  • Loading branch information...
1 parent 404a46d commit 0339a28fd79672c17ba3977625afee6aff2b11b3 @roffelsaurus roffelsaurus committed Mar 7, 2012
Showing with 26 additions and 29 deletions.
  1. +26 −29 documentation/report/files/requirements.tex
@@ -1,68 +1,65 @@
%Functional Requirements
\section{Functional Requirements}
+Requirements are ordered by importance.
+
\begin{itemize}
-\item{Wireless connectivity}\newline
+\item{F1 Communication Library}\newline
+The Android should use the Communication Library to connect wirelessly
+to an Arduino module and establish duplex communication.
+
+\item{F2 Social Library}\newline
+Android applications should be able to retrieve social data from any
+supported social network through the use of the Social Library. General
+concepts applicable in any social network such as Person, Group, Message, etc.
+should be extracted and devised into a model interface that is easy for the application
+developer to use.
+
+\item{F3 Wireless connectivity}\newline
Since the product will target a user-base with no technical background,
the customer required all connections between devices to be wireless,
so that connecting the User Interface to the Android mobile will be
as easy as possible for the end-users. For this reason, the technical
details of the connection should be hidden to the end-user so that
the product can be easily operated.
-\item{Prototype}\newline
-Develop three prototypes, one more complex prototype showcasing the
+\item{F4 Prototype}\newline
+To show that the concept of Tangible User Interfaces for Android applications
+(including social networks) using Arduino is not only possible, but
+also a feasible market product, the customer is interested in a working
+prototype. Develop three prototypes, one more complex prototype showcasing the
functionality of both the Communication Library and Social Library. The other
two prototypes should be much simpler in complexity and their purpose is just to
prove that the libraries can be successfully used for different prototypes.
-
-\item{Communication Library}\newline
-The Android should use the Communication Library to connect wirelessly
-to an Arduino module and establish duplex communication.
-
-\item{Social Library}\newline
-Android applications should be able to retrieve social data from any
-supported social network through the use of the Social Library. General
-concepts applicable in any social network such as Person, Group, Message, etc.
-should be extracted and devised into a model interface that is easy for the application
-developer to use.
\end{itemize}
%Non functional Requirements
\section{Non-functional Requirements}
\begin{itemize}
-\item{Flexible software architecture}\newline
+\item{NF1 Flexible software architecture}\newline
The software that will be developed for this project will serve as
a proof-of-concept and possibily as a starting point for other research
projects. For this reason a flexible, modular software architecture
is an important requirement for our customer. The code shall be developed
in independent, thus reusable modules so that adding new functionality
will be fairly easy for new developers.
-\item{Software licenses}\newline
+\item{NF2 Software licenses}\newline
The customer made clear that the software developed needs to be released
under a permissive, Apache compatible software license. This implies
that pre-existing software that will eventually be adopted and incorporated
in the project must have a compatible license.
-\item{Target platforms}\newline
-The product has to target the Android platform and Arduino.
-This will place restrictions on the software and on the programming languages that will be adopted.
-
-\item{Working prototype}\newline
-To show that the concept of Tangible User Interfaces for Android applications
-(including social networks) using Arduino is not only possible, but
-also a feasible market product, the customer is interested in a working
-prototype. As the project evolves, together with our customer we
-gradually decided the specifications for the prototype that will
-be produced at the end of the project.
-
-\item{API Documentation and Javadoc}\newline
+\item{NF3 API Documentation and Javadoc}\newline
Since the product is going to be further developed by other people and is
mainly designed for easier application development then proper research and usage
documentation is important. Proper documentation or tutorials should describe how
the end-user can easily use the libraries without any technical knowledge of how
the library works.
+
+\item{NF4 Target platforms}\newline
+The product has to target the Android platform and Arduino.
+This will place restrictions on the software and on the programming languages that will be adopted.
\end{itemize}

0 comments on commit 0339a28

Please sign in to comment.