update assignment1

assignment1/latexsource/assignment1.log

@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex 2018.4.16)  27 MAY 2018 21:07
+This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex 2018.4.16)  29 MAY 2018 20:44
 entering extended mode
  restricted \write18 enabled.
  %&-line parsing enabled.
@@ -239,87 +239,97 @@ File: umsb.fd 2013/01/14 v3.01 AMS symbols B
 
 {/usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2] [3]
  [4]
-<storycard1.png, id=19, 472.76625pt x 241.90375pt>
+<storycard1.png, id=19, 344.28625pt x 174.6525pt>
 File: storycard1.png Graphic file (type png)
 <use storycard1.png>
 Package pdftex.def Info: storycard1.png  used on input line 116.
-(pdftex.def)             Requested size: 251.9989pt x 128.9429pt.
- [5 <./storycard1.png>]
-<storymap.png, id=25, 1702.36pt x 1098.1025pt>
+(pdftex.def)             Requested size: 251.9989pt x 127.83638pt.
+<storycard2.png, id=21, 344.28625pt x 173.64874pt>
+File: storycard2.png Graphic file (type png)
+<use storycard2.png>
+Package pdftex.def Info: storycard2.png  used on input line 123.
+(pdftex.def)             Requested size: 251.9989pt x 127.10168pt.
+<storycard3.png, id=22, 353.32pt x 181.67876pt>
+File: storycard3.png Graphic file (type png)
+<use storycard3.png>
+Package pdftex.def Info: storycard3.png  used on input line 131.
+(pdftex.def)             Requested size: 251.9989pt x 129.5805pt.
+ [5 <./storycard1.png> <./storycard2.png> <./storycard3.png>]
+<storymap.png, id=29, 1245.65375pt x 868.24374pt>
 File: storymap.png Graphic file (type png)
 <use storymap.png>
-Package pdftex.def Info: storymap.png  used on input line 131.
-(pdftex.def)             Requested size: 720.0pt x 464.43375pt.
+Package pdftex.def Info: storymap.png  used on input line 146.
+(pdftex.def)             Requested size: 720.0pt x 501.85944pt.
 
-Overfull \hbox (112.40671pt too wide) in paragraph at lines 130--132
+Overfull \hbox (112.40671pt too wide) in paragraph at lines 145--147
  []|  [] 
  []
 
 
-LaTeX Warning: Float too large for page by 73.25742pt on input line 134.
+LaTeX Warning: Float too large for page by 110.6831pt on input line 149.
 
 
 LaTeX Warning: `h' float specifier changed to `ht'.
 
 [6 <./storymap.png>]
-<overviewsketches.png, id=30, 1650.165pt x 1782.66pt>
+<overviewsketches.png, id=34, 1650.165pt x 1782.66pt>
 File: overviewsketches.png Graphic file (type png)
 <use overviewsketches.png>
-Package pdftex.def Info: overviewsketches.png  used on input line 142.
+Package pdftex.def Info: overviewsketches.png  used on input line 157.
 (pdftex.def)             Requested size: 396.0022pt x 427.79274pt.
 
-Overfull \hbox (36.0022pt too wide) in paragraph at lines 142--143
+Overfull \hbox (36.0022pt too wide) in paragraph at lines 157--158
  [][] 
  []
 
 [7
 
 
  <./overviewsketches.png>]
-<elaboratingsketches.png, id=36, 1883.035pt x 1800.7275pt>
+<elaboratingsketches.png, id=40, 1883.035pt x 1800.7275pt>
 File: elaboratingsketches.png Graphic file (type png)
 <use elaboratingsketches.png>
-Package pdftex.def Info: elaboratingsketches.png  used on input line 159.
+Package pdftex.def Info: elaboratingsketches.png  used on input line 174.
 (pdftex.def)             Requested size: 302.39868pt x 289.16641pt.
  [8 <./elaboratingsketches.png>]
-<storyboard.png, id=42, 979.66pt x 1209.51875pt>
+<storyboard.png, id=46, 979.66pt x 1209.51875pt>
 File: storyboard.png Graphic file (type png)
 <use storyboard.png>
-Package pdftex.def Info: storyboard.png  used on input line 170.
+Package pdftex.def Info: storyboard.png  used on input line 185.
 (pdftex.def)             Requested size: 413.9978pt x 511.1319pt.
 
-Overfull \hbox (42.20477pt too wide) in paragraph at lines 169--171
+Overfull \hbox (42.20477pt too wide) in paragraph at lines 184--186
  []|  [] 
  []
 
 [9 <./storyboard.png>] [10]
-<1.png, id=50, 808.52063pt x 538.51187pt>
+<1.png, id=54, 808.52063pt x 538.51187pt>
 File: 1.png Graphic file (type png)
 <use 1.png>
-Package pdftex.def Info: 1.png  used on input line 185.
+Package pdftex.def Info: 1.png  used on input line 212.
 (pdftex.def)             Requested size: 396.0022pt x 263.75807pt.
 
-Overfull \hbox (36.0022pt too wide) in paragraph at lines 185--186
+Overfull \hbox (36.0022pt too wide) in paragraph at lines 212--213
  [][] 
  []
 
 [11 <./1.png>]
-<3.png, id=55, 806.01125pt x 492.84125pt>
+<3.png, id=59, 806.01125pt x 492.84125pt>
 File: 3.png Graphic file (type png)
 <use 3.png>
-Package pdftex.def Info: 3.png  used on input line 196.
+Package pdftex.def Info: 3.png  used on input line 223.
 (pdftex.def)             Requested size: 396.0022pt x 242.14105pt.
 
-Overfull \hbox (36.0022pt too wide) in paragraph at lines 196--197
+Overfull \hbox (36.0022pt too wide) in paragraph at lines 223--224
  [][] 
  []
 
 [12 <./3.png>] (./assignment1.aux) ) 
 Here is how much of TeX's memory you used:
- 2490 strings out of 492649
- 33838 string characters out of 6129622
+ 2500 strings out of 492649
+ 34016 string characters out of 6129622
  97985 words of memory out of 5000000
- 6320 multiletter control sequences out of 15000+600000
+ 6328 multiletter control sequences out of 15000+600000
  10104 words of font info for 38 fonts, out of 8000000 for 9000
  1141 hyphenation exceptions out of 8191
  41i,6n,25p,959b,253s stack positions out of 5000i,500n,10000p,200000b,80000s
@@ -329,10 +339,10 @@ pe1/public/amsfonts/cm/cmbx12.pfb></usr/local/texlive/2018/texmf-dist/fonts/typ
 e1/public/amsfonts/cm/cmr10.pfb></usr/local/texlive/2018/texmf-dist/fonts/type1
 /public/amsfonts/cm/cmr12.pfb></usr/local/texlive/2018/texmf-dist/fonts/type1/p
 ublic/amsfonts/cm/cmr17.pfb>
-Output written on assignment1.pdf (12 pages, 1429151 bytes).
+Output written on assignment1.pdf (12 pages, 1539070 bytes).
 PDF statistics:
- 78 PDF objects out of 1000 (max. 8388607)
+ 82 PDF objects out of 1000 (max. 8388607)
  44 compressed objects within 1 object stream
  0 named destinations out of 1000 (max. 500000)
- 36 words of extra memory for PDF output out of 10000 (max. 10000000)
+ 46 words of extra memory for PDF output out of 10000 (max. 10000000)
 

assignment1/latexsource/assignment1.tex

@@ -55,9 +55,9 @@ \subsection*{2-1: Functional Requrements (FRs)}
 After pressing the 'get reading' button, the value is averaged and stored into a table that is accessible in another part/menu of the application.
 
 \vskip 6mm
-5. "The app and all of its relevant code must be open source to further future academic endeavours."
+5. "The app must be able to export out the saved data to a computer so that further data interpretation and processing can be performed."
 
-The client has specified that the code must be accessible to the public. This would progress the learning experiences of future students who want to extend on the work (ie make an iOS version).  
+The client has specified that the readings once in tabled format must be able to export (via .csv for example) to another computer. This would progress the learning experiences of future students who want to work with the data more comfortably once it has been collected via the phone.  
 
 
 \subsection*{2-2: Non Functional Requirements (NFRs)}
@@ -114,14 +114,29 @@ \subsection*{3-2: User Stories}
   \centering
 
       \includegraphics[width=0.7\textwidth]{storycard1.png}
+
+\end{figure}
+
+\begin{figure}[h]
+  \centering
+
+      \includegraphics[width=0.7\textwidth]{storycard2.png}
+
+
+\end{figure}
+
+\begin{figure}[h]
+  \centering
+
+      \includegraphics[width=0.7\textwidth]{storycard3.png}
       \caption{Individual story cards are first created to document core requirements, upon which further cards will be used to document how a user goes about accomplishing those tasks}
 
 \end{figure}
 
 
 \subsection*{3-3: Story Map}
 
-With the use of the user story cards above, a collage/story map can be created that details further on how a user can interact with the app to accomplish their requirements. The story map can be viewed on the next landscape page. 
+With the use of the user story cards above, a collage/story map can be created that details further on how a user can interact with the app to accomplish their requirements. The story map can be viewed on the next landscape page;
 
 \newpage
 \begin{landscape}
@@ -173,8 +188,20 @@ \subsection*{4-3: Storyboard Sketches}
 
 \newpage
 \subsection*{4-4: Wizard of Oz Demo Video}
+
+Demo videos can be viewed at the following links:
+
+
 \subsection*{4-5: Requirements Change}
 
+When generating overview sketches for part 4-1, we had to consider what aspects of the Data Collection screen were most important for satisfying our initial requirements. All the sketches have similarities, such as having the live reading be the focus of the screen (FR \#2). However, they emphasized some different points, and we had to choose which design seemed most intuitive to use. For example, we considered if a settings button allowing the user to turn feedback sounds on/off (NFR \#4) was necessary on this screen, or if it was better suited for the main menu. As for the elaborating sketches, they were mainly based on our functional requirements (FR \#1 Collection Prompt; FR \#4 Data Log).  Deciding how the reading screen should be connected to other parts of the app was helpful for planning user navigation.
+
+When storyboarding, we again focused on improving usability of the app. Along with playing a sound when the user presses the "get reading" button (NFR \#4), we added visual cues to indicate a successful recording. In this case, we changed the colour of the button and placed a checkmark symbol on the Data Log. So, the storyboarding process was helpful for generating more visual feedback to the user. This step was also useful for estimating how convenient it is to perform a key task in our interface (recording a value to the log).
+
+The most helpful prototyping technique for adjusting our requirements was the Wizard of Oz video. Allowing Dr. Donev to directly interact with our paper prototype resulted in a great amount of feedback. We realized the discrepancies between our current design and what our client considered important. For example, we emphasized a constant, live stream of data (FR \#2), but Dr. Donev explained that we should only begin displaying data after pressing the record button. Rather than averaging readings (FR \#3), the application should function more like a counter over some time interval. He also introduced other requirements that we had not thought about before, like having the user indicate if they are indoors or outdoors when taking measurements. By discussing requirements and revising them with our client, we gained a much clearer image of how our application should work.
+
+
+
 \newpage
 \section*{Deliverable \#5}