Add headers for final report

reports/final.lyx

@@ -1754,433 +1754,19 @@ The battery life on modern smartphones rarely exceeds 24 hours of typical
 \end_layout
 
 \begin_layout Part
-Specification
+Accelerometer classification
 \end_layout
 
-\begin_layout Section
-Experimentation
-\begin_inset CommandInset label
-LatexCommand label
-name "sec:Experimentation"
-
-\end_inset
-
-
-\end_layout
-
-\begin_layout Subsection
-Battery use
-\end_layout
-
-\begin_layout Standard
-The average lifetime of a typical Android mobile telephone will need to
- be ascertained, taking into consideration typical day-to-day use of the
- device and any additional battery drain caused by that.
- The impact of sensor use on the battery lifetime needs to be calculated
- or experimentally determined, and the effect of the algorithms described
- in section 
-\begin_inset CommandInset ref
-LatexCommand ref
-reference "sec:Power-management"
-
-\end_inset
-
- needs to be quantified.
-\end_layout
-
-\begin_layout Standard
-Once this is complete, a selection of algorithms and suitable parameters
- should be made for use in the classifier application (section 
-\begin_inset CommandInset ref
-LatexCommand ref
-reference "sub:Classifier-application"
-
-\end_inset
-
-).
- The aim of the selection should be to ensure the best activity detection
- whilst not severely reducing the device's battery life.
-\end_layout
-
-\begin_layout Subsection
-Location analysis
-\begin_inset CommandInset label
-LatexCommand label
-name "sub:Location-analysis"
-
-\end_inset
-
-
-\end_layout
-
-\begin_layout Standard
-As discussed in section 
-\begin_inset CommandInset ref
-LatexCommand ref
-reference "sec:Location-analysis"
-
-\end_inset
-
-, existing algorithms to detect interesting places rely on GPS signals not
- being obtainable indoors, which is no longer true with current generation
- GPS chipsets.
- It may be possible to adapt these algorithms to work instead using the
- GSM signal strength or number of locked GPS satellites.
- The variance of these when inside and outside a building need to be investigate
-d to determine if this is a feasible approach, or whether an alternate algorithm
- needs to be used.
-\end_layout
-
-\begin_layout Standard
-A suitable algorithm should be implemented which allows the user's activity
- to be annotated with location-based context.
- This would ideally take the form of a source and destination for mobile
- activities, or location for static activities.
- The goal is to be able to differentiate between 
-\begin_inset Quotes eld
-\end_inset
-
-walking to work
-\begin_inset Quotes erd
-\end_inset
-
- and 
-\begin_inset Quotes eld
-\end_inset
-
-walking to the shop
-\begin_inset Quotes erd
-\end_inset
-
-, although the labeling of places may be left to future work.
- Unlabeled places (i.e., something akin to 
-\begin_inset Quotes eld
-\end_inset
-
-walking to place2
-\begin_inset Quotes erd
-\end_inset
-
- and 
-\begin_inset Quotes eld
-\end_inset
-
-walking to place7
-\begin_inset Quotes erd
-\end_inset
-
- instead of the previous examples) still allow for applications to tailor
- their behaviour based on the user's previous activities at or when walking
- to that place, so will be sufficient for an initial version.
-\end_layout
-
-\begin_layout Subsection
-Bluetooth usage
-\begin_inset CommandInset label
-LatexCommand label
-name "sub:Bluetooth-usage"
-
-\end_inset
-
-
-\end_layout
-
-\begin_layout Standard
-The algorithm for classifying familiar, unfamiliar, and 
-\begin_inset Quotes eld
-\end_inset
-
-familiar stranger
-\begin_inset Quotes erd
-\end_inset
-
- Bluetooth devices (section 
-\begin_inset CommandInset ref
-LatexCommand ref
-reference "sec:Bluetooth"
-
-\end_inset
-
-) should be implemented.
- An experiment should then be conducted to determine whether or not the
- data provides useful clues as to the user's context.
- This will depend on the number of other people with Bluetooth discoverable
- devices in the vicinity of the user.
-\end_layout
-
-\begin_layout Standard
-If there are a sufficient number of discoverable devices, then the algorithms
- should be included in the classifier application to provide additional
- context.
-\end_layout
-
-\begin_layout Section
-Deliverables
-\begin_inset CommandInset label
-LatexCommand label
-name "sec:Deliverables"
-
-\end_inset
-
-
-\end_layout
-
-\begin_layout Standard
-The following items should be delivered:
-\end_layout
-
-\begin_layout Subsection
-Context-aware Framework
-\begin_inset CommandInset label
-LatexCommand label
-name "sub:Classifier-application"
-
-\end_inset
-
-
-\end_layout
-
-\begin_layout Standard
-An Android application which:
-\end_layout
-
-\begin_layout Itemize
-monitors raw sensor data and extracts features from the device's:
-\end_layout
-
-\begin_deeper
-\begin_layout Itemize
-accelerometer sensors
-\end_layout
-
-\begin_layout Itemize
-magnetic field sensors
-\end_layout
-
-\begin_layout Itemize
-camera
-\end_layout
-
-\begin_layout Itemize
-microphone
-\end_layout
-
-\end_deeper
-\begin_layout Itemize
-monitors relevant data and extracts features concerning:
-\end_layout
-
-\begin_deeper
-\begin_layout Itemize
-visible Bluetooth devices in proximity to the device
-\end_layout
-
-\begin_layout Itemize
-the current location of the device
-\end_layout
-
-\begin_layout Itemize
-the current GSM signal strength and cell ID
-\end_layout
-
-\end_deeper
-\begin_layout Itemize
-presents the user with a method of optionally annotating this data with
- their current activity
-\end_layout
-
-\begin_layout Itemize
-classifies the user's current activity using the extracted features and
- a K-Nearest Neighbour algorithm
-\end_layout
-
-\begin_layout Itemize
-enhances the classification with extra contextual data inferred from location
- or Bluetooth service:
-\end_layout
-
-\begin_deeper
-\begin_layout Itemize
-the user's probable source and destination, if traveling
-\end_layout
-
-\begin_layout Itemize
-the user's current location, if stationary
-\end_layout
-
-\begin_layout Itemize
-the user's company, if detected
-\end_layout
-
-\end_deeper
-\begin_layout Itemize
-attempts to conserve battery life by intelligent management and timing of
- sensor activity
-\end_layout
-
-\begin_layout Subsubsection
-Interface
-\end_layout
-
-\begin_layout Standard
-The application should provide two different interfaces to retrieve the
- user's context.
- The first should be an implementation of the Android ContentProvider interface.
- This allows third party applications to query and retrieve data (in this
- case, the user's probable activities and context) as and when they need
- it.
-\end_layout
-
-\begin_layout Standard
-The ContentProvider interface exposes data as a table.
- The classifier application should therefore supply a unique ID for each
- possible activity, the name of the activity (if labeled), the time the
- activity was started, and the estimated uncertainty in the classification.
- It should also expose relevant details of any context information, such
- as related places (s
-\begin_inset CommandInset ref
-LatexCommand ref
-reference "sub:Location-analysis"
-
-\end_inset
-
-) or other participants (s
-\begin_inset CommandInset ref
-LatexCommand ref
-reference "sub:Bluetooth-usage"
-
-\end_inset
-
-).
-\end_layout
-
-\begin_layout Standard
-The second interface should use Android broadcast Intents to notify any
- interested application whenever the user's activity changes.
- This will allow applications to be notified whenever the activity or context
- of the user changes.
- The Intent should contain a URI which corresponds to an entry in the table
- returned by the ContentProvider, so applications can retrieve information
- about the user's activity directly.
-\end_layout
-
-\begin_layout Standard
-Whenever activities, places or participants are exposed in the interface,
- they should be assigned an ID which remains consistent for the specified
- activity, place or participant.
- Applications can use this ID regardless of any annotations the user supplies.
- For example, the first time an interesting place is detected it may be
- assigned ID 42 and label 
-\begin_inset Quotes eld
-\end_inset
-
-place42
-\begin_inset Quotes erd
-\end_inset
-
-, the user may then annotate this place as 
-\begin_inset Quotes eld
-\end_inset
-
-home
-\begin_inset Quotes erd
-\end_inset
-
-, and some time later replace it with 
-\begin_inset Quotes eld
-\end_inset
-
-old house
-\begin_inset Quotes erd
-\end_inset
-
-; the ID will be consistent across all of these labels, so any application
- using this information will continue to function.
-\end_layout
-
-\begin_layout Subsection
-Activity condition for Locale
-\end_layout
-
-\begin_layout Standard
-As a proof-of-concept, an application should be developed which provides
- Locale
-\begin_inset CommandInset citation
-LatexCommand cite
-key "TwoFortyFourAm2010"
-
-\end_inset
-
-, a popular Android application used to alter device settings and perform
- actions based on certain conditions, with a new condition representing
- the user's activity.
-\end_layout
-
-\begin_layout Standard
-This will allow users to change their device settings based on their current
- activity by creating rules within Locale.
- Locale also allows users to post updates to popular social networking sites
- such as Twitter and Facebook, so it will be possible for users to broadcast
- their activities to their friends.
-\end_layout
-
-\begin_layout Subsection
-Context-aware home screen
-\end_layout
-
-\begin_layout Standard
-To demonstrate the utility of applications being context-aware, an application
- will be developed that replaces the standard Android home screen.
- It should dynamically adapt its layout and contents according to the user's
- activity and other context information made available by the classifier
- application.
-\end_layout
-
-\begin_layout Standard
-The replacement home screen needs to allow users to browse and launch applicatio
-ns, and should expose relevant (context-sensitive) notifications to the
- user, including notifications of e-mails, missed calls, text messages and
- upcoming appointments.
-\end_layout
-
-\begin_layout Subsection
-User and developer guides
-\end_layout
-
-\begin_layout Itemize
-A user guide for the classifier
-\noun on
- 
-\noun default
-application
-\end_layout
-
-\begin_layout Itemize
-A user guide for the Locale condition provider
-\end_layout
-
-\begin_layout Itemize
-A user guide for the Context-aware home screen
-\end_layout
-
-\begin_layout Itemize
-A developer's guide for using the information exposed by the 
-\noun on
-classifier
-\noun default
- application
+\begin_layout Part
+Microphone, camera and Bluetooth
 \end_layout
 
-\begin_layout Subsection
-Website
+\begin_layout Part
+Places
 \end_layout
 
-\begin_layout Standard
-A website should be created containing an overview of the applications,
- instructions for both users and developers, and links to download the applicati
-ons.
- The website should explain the basic ideas behind activity and context
- aware applications, and the specific techniques used in this project.
+\begin_layout Part
+The Context Analyser
 \end_layout
 
 \begin_layout Standard
@@ -2339,6 +1925,17 @@ Finally, the applications should be evaluated based on their resource usage.
  users to change their normal charging behaviour, and memory usage should
  not be so high as to cause other applications to become sluggish or be
  closed by the operating system.
+\end_layout
+
+\begin_layout Standard
+\begin_inset Newpage pagebreak
+\end_inset
+
+
+\end_layout
+
+\begin_layout Part
+Conclusion
 \begin_inset Newpage pagebreak
 \end_inset