assignment1 update

assignment1/latexsource/assignment1.aux

@@ -1,8 +1,8 @@
 \relax 
-\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces 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}}{4}}
-\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces A story map is used to organize requirements in order of priority and to illustrate how user interacts with app}}{5}}
-\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces A variety of design approaches for the recording screen}}{6}}
-\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Extended sketches for other parts of the apps UI screens}}{7}}
-\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces The recording screen responding to user input}}{8}}
-\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Initial exchange of emails to get the project started}}{9}}
-\@writefile{lof}{\contentsline {figure}{\numberline {7}{\ignorespaces Setting up a stand up meeting with Dr. Donev as a group}}{10}}
+\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces 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}}{5}}
+\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces A story map is used to organize requirements in order of priority and to illustrate how user interacts with app}}{6}}
+\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces A variety of design approaches for the recording screen}}{7}}
+\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Extended sketches for other parts of the apps UI screens}}{8}}
+\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces The recording screen responding to user input}}{9}}
+\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Initial exchange of emails to get the project started}}{11}}
+\@writefile{lof}{\contentsline {figure}{\numberline {7}{\ignorespaces Setting up a stand up meeting with Dr. Donev as a group}}{12}}

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)  26 MAY 2018 19:55
+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
 entering extended mode
  restricted \write18 enabled.
  %&-line parsing enabled.
@@ -238,84 +238,101 @@ File: umsb.fd 2013/01/14 v3.01 AMS symbols B
 ) [1
 
 {/usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}] [2] [3]
-<storycard1.png, id=16, 474.77374pt x 253.94875pt>
+ [4]
+<storycard1.png, id=19, 472.76625pt x 241.90375pt>
 File: storycard1.png Graphic file (type png)
 <use storycard1.png>
-Package pdftex.def Info: storycard1.png  used on input line 106.
-(pdftex.def)             Requested size: 251.9989pt x 134.78981pt.
- [4 <./storycard1.png>]
-<storymap.png, id=22, 1717.41624pt x 1322.9425pt>
+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>
 File: storymap.png Graphic file (type png)
 <use storymap.png>
-Package pdftex.def Info: storymap.png  used on input line 121.
-(pdftex.def)             Requested size: 576.0022pt x 443.6982pt.
+Package pdftex.def Info: storymap.png  used on input line 131.
+(pdftex.def)             Requested size: 720.0pt x 464.43375pt.
+
+Overfull \hbox (112.40671pt too wide) in paragraph at lines 130--132
+ []|  [] 
+ []
 
 
-LaTeX Warning: Float too large for page by 109.42737pt on input line 124.
+LaTeX Warning: Float too large for page by 73.25742pt on input line 134.
 
 
 LaTeX Warning: `h' float specifier changed to `ht'.
 
-[5 <./storymap.png>]
-<overviewsketches.png, id=27, 989.6975pt x 1069.9975pt>
+[6 <./storymap.png>]
+<overviewsketches.png, id=30, 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 132.
-(pdftex.def)             Requested size: 396.0022pt x 428.12202pt.
+Package pdftex.def Info: overviewsketches.png  used on input line 142.
+(pdftex.def)             Requested size: 396.0022pt x 427.79274pt.
 
-Overfull \hbox (36.0022pt too wide) in paragraph at lines 132--133
+Overfull \hbox (36.0022pt too wide) in paragraph at lines 142--143
  [][] 
  []
 
-[6
+[7
 
 
  <./overviewsketches.png>]
-<elaboratingsketches.png, id=32, 2216.28pt x 2160.07pt>
+<elaboratingsketches.png, id=36, 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 142.
-(pdftex.def)             Requested size: 431.9989pt x 421.03069pt.
+Package pdftex.def Info: elaboratingsketches.png  used on input line 159.
+(pdftex.def)             Requested size: 302.39868pt x 289.16641pt.
+ [8 <./elaboratingsketches.png>]
+<storyboard.png, id=42, 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.
+(pdftex.def)             Requested size: 413.9978pt x 511.1319pt.
 
-Overfull \hbox (71.9989pt too wide) in paragraph at lines 142--143
- [][] 
+Overfull \hbox (42.20477pt too wide) in paragraph at lines 169--171
+ []|  [] 
  []
 
-[7 <./elaboratingsketches.png>]
-<storyboard.png, id=38, 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 151.
-(pdftex.def)             Requested size: 352.79846pt x 435.57407pt.
-<1.png, id=39, 808.52063pt x 538.51187pt>
+[9 <./storyboard.png>] [10]
+<1.png, id=50, 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 162.
-(pdftex.def)             Requested size: 288.0011pt x 191.8263pt.
- [8 <./storyboard.png>] [9 <./1.png>]
-<3.png, id=48, 806.01125pt x 492.84125pt>
+Package pdftex.def Info: 1.png  used on input line 185.
+(pdftex.def)             Requested size: 396.0022pt x 263.75807pt.
+
+Overfull \hbox (36.0022pt too wide) in paragraph at lines 185--186
+ [][] 
+ []
+
+[11 <./1.png>]
+<3.png, id=55, 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 173.
-(pdftex.def)             Requested size: 288.0011pt x 176.09915pt.
- [10 <./3.png>] (./assignment1.aux) ) 
+Package pdftex.def Info: 3.png  used on input line 196.
+(pdftex.def)             Requested size: 396.0022pt x 242.14105pt.
+
+Overfull \hbox (36.0022pt too wide) in paragraph at lines 196--197
+ [][] 
+ []
+
+[12 <./3.png>] (./assignment1.aux) ) 
 Here is how much of TeX's memory you used:
- 2488 strings out of 492649
- 33814 string characters out of 6129622
+ 2490 strings out of 492649
+ 33838 string characters out of 6129622
  97985 words of memory out of 5000000
- 6319 multiletter control sequences out of 15000+600000
- 9796 words of font info for 37 fonts, out of 8000000 for 9000
+ 6320 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,712b,251s stack positions out of 5000i,500n,10000p,200000b,80000s
-</usr/local/texlive/2018/texmf-dist/fonts/
-type1/public/amsfonts/cm/cmbx12.pfb></usr/local/texlive/2018/texmf-dist/fonts/t
-ype1/public/amsfonts/cm/cmr10.pfb></usr/local/texlive/2018/texmf-dist/fonts/typ
-e1/public/amsfonts/cm/cmr12.pfb></usr/local/texlive/2018/texmf-dist/fonts/type1
-/public/amsfonts/cm/cmr17.pfb>
-Output written on assignment1.pdf (10 pages, 1248044 bytes).
+ 41i,6n,25p,959b,253s stack positions out of 5000i,500n,10000p,200000b,80000s
+</usr/local/texlive/2018/texmf-dist/fonts/t
+ype1/public/amsfonts/cm/cmbx10.pfb></usr/local/texlive/2018/texmf-dist/fonts/ty
+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).
 PDF statistics:
- 68 PDF objects out of 1000 (max. 8388607)
- 37 compressed objects within 1 object stream
+ 78 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)
 

assignment1/latexsource/assignment1.tex

@@ -11,7 +11,8 @@
 \author{Celina Ma, John Ngo, Omar Qureshi}
 \begin{document}
 \maketitle
-
+\def\textfraction{.01}
+\def\topfraction{.99}
 \section*{Deliverable \#1}
 
 Generally, the software development model is chosen in response to the circumstances of the software’s development. Our client is a real-world client – Professor Jason Donev, who is an individual and understandably has a busy schedule. He can meet up with us around once a week, but it would be difficult and unreasonable to remain in constant communication. There are difficulties for us as well as students going to classes on a set schedule, thus any method which requires constant client input and interaction on every aspect of development appears unsuitable. This difficulty eliminates the Scrum model, due to it being an agile model which requires such constant communication.
@@ -51,7 +52,7 @@ \subsection*{2-1: Functional Requrements (FRs)}
 \vskip 6mm
 4. "The app must be able to record the averaged  'get readings' in a table." 
 
-Upon pressing the 'get reading' button, the value is averaged and stored into a table that is accessible in another part/menu of the application.
+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."
@@ -63,25 +64,25 @@ \subsection*{2-2: Non Functional Requirements (NFRs)}
 
 1. "The app should present the readings with two significant digits."
 
-This allows the user to experience a non cluttered UI, removing unnecessary information This NFR would fall under the usability. 
+This allows the user to experience a non cluttered UI, removing unnecessary information. This NFR would fall under the usability. 
 
-\vskip 6mm
+\vskip 4mm
 
 2. "The app should record the readings by making a smooth visual animation."
 
-A transition animation is often desired to express the information in a clearer way. This NFR would fall under the usability category. 
+A transition animation is often desired to express user action in a clearer way. This NFR would fall under the usability category. 
 
-\vskip 6mm
+\vskip 4mm
 
 3. "The app should record the readings within 0.5s after pressing the 'get reading' button."
 
-This ensures the user doesn't have to wait an unusually long amount of time to get the reading. It also stops the user from getting frustrated and pressing the button again needlessly. This NFR would fall under the response time category. 
-\vskip 6mm
+This ensures the user doesn't have to wait an unusually large amount of time to get the reading. It also stops the user from getting frustrated and pressing the button again needlessly. This NFR would fall under the response time category. 
+\vskip 4mm
 4. "The app should emit a feedback sound when the user presses the ‘get reading button’" 
 
 Giving the user direct confirmation of their action being applied is helpful and again stops user from pressing the button unnecessarily. This NFR would fall under the usability category.
 
-\vskip 6mm
+\vskip 4mm
 5. "The app should present a message if the muon detector is connected or not."
 
 This makes sure that a precondition of using the app is met, which is having the miniUSB cable plugged into the phone and detector. This NFR would fall under the learnability/usability category. 
@@ -91,14 +92,23 @@ \subsection*{2-2: Non Functional Requirements (NFRs)}
 
 \section*{Deliverable \#3}
 
-\subsection*{3-1: Choosing User Stories/Map}
+\subsection*{3-1: Choosing User Stories Vs Use Cases}
+
+After considering both use cases and user stories, we conclude that the user stories method is a better way to represent the systems requirements for our project. Just as with the selection of our software process model, this comes from consideration of our circumstances compared to the strengths and weaknesses of each model.
+
+The largest, most important draw of the user stories model is that it is extremely simple and to the point. Its structure, where a given user wants to do something for a given reason, is very, very close to how our client expresses what he wants out of the software, and as such is extremely attractive. Along with the emphasis on action and reason, user stories allow for the communication of overarching requirements goals as opposed to more nitty-gritty details, which fits with the iterative model of development we have chosen, since iterative models work towards a general end goal but don’t care about details at each stage.
+
+The largest, most important draw of the use cases model is that done correctly, it can map out the structure of the very application needed, at least on some level. However, this backbone given and its greater emphasis on specific details compared to user stories does not lend it quite as well to an iterative model; and furthermore, it is more technically designed than user stories, which are closer to natural language. As such, while not a terrible alternative, it just doesn’t provide nearly as many advantages as with user stories.
+
+Therefore, we have selected user stories to represent our system requirements.
 
-The reason why we chose user stories over use cases is...
 
 \subsection*{3-2: User Stories}
 
 The three core functional requirements that the user (in our case Professor Donev) needs to accomplish are as follows: connect muon detector to phone, view muon detector data and save data from muon detector to a log. As such, three corresponding story cards are created; 
 
+\newpage
+
 
 \begin{figure}[h]
   \centering
@@ -117,8 +127,8 @@ \subsection*{3-3: Story Map}
 \begin{landscape}
 \begin{figure}[h]
   \centering
-
-      \includegraphics[width=1.6\textwidth]{storymap.png}
+  \vspace*{-2cm} \hspace*{-0.5cm}
+      \includegraphics[width=2.0\textwidth]{storymap.png}
       \caption{A story map is used to organize requirements in order of priority and to illustrate how user interacts with app}
 
 \end{figure}
@@ -134,49 +144,62 @@ \subsection*{4-1: Overview Sketches}
 \end{figure}
 
 \newpage
-\subsection*{4-2: Elaborating Sketches}
+\subsubsection*{Why We Chose Sketch A}
+
+We chose sketch A to elaborate on due to its clarity and emphasis on the most important aspects of this screen. The main buttons the user would interact with (Record, Mode and Data Log) are large and displayed clearly. Compared to sketches B and C, which have smaller icons that the user may accidentally mis-press, the interface of A is more focused on what is important to the user. This is key to enhancing the intuitiveness of the app. Sketch D emphasizes similar points to sketch A, but the mode selection button is somewhat less obvious in this design. Although sketch E shows more information about Previous Readings than the other sketches, it is too cluttered; additionally, that information is repeated in the Data Log screen in more detail, so it is not needed for the Data Collection screen. Thus, our main reason for choosing sketch A was its relative simplicity and correctly emphasized functions compared to the other designs.
 
+\subsection*{4-2: Elaborating Sketches}
+\def\textfraction{.01}
+\def\topfraction{.99}
 \bigskip
-\begin{figure}[h]
+\begin{figure}[b!]
   \centering
-      \includegraphics[width=1.2\textwidth]{elaboratingsketches.png}
+  \hspace*{-1cm}
+  \renewcommand{\textfraction}{0.05} 
+      \includegraphics[width=0.84\textwidth]{elaboratingsketches.png}
   \caption{Extended sketches for other parts of the apps UI screens}
 \end{figure}
+
 \newpage
 \subsection*{4-3: Storyboard Sketches}
 
 \bigskip
 \begin{figure}[h]
   \centering
-      \includegraphics[width=0.98\textwidth]{storyboard.png}
+  \hspace*{-0.5cm}
+      \includegraphics[width=1.15\textwidth]{storyboard.png}
   \caption{The recording screen responding to user input}
 \end{figure}
-\subsection*{4-3: Wizard of Oz Demo Video}
-\subsection*{4-4: Requirements Change}
+
+\newpage
+\subsection*{4-4: Wizard of Oz Demo Video}
+\subsection*{4-5: Requirements Change}
+
+\newpage
 \section*{Deliverable \#5}
 
-Our project first began with John consulting us about a program an external client, Dr. Donev,  might need. We agreed and this led to John emailing Dr. Donev  for confirming the project. The following emails show the first steps in the project; 
+Our project first began with John consulting us about a program an external client, Dr. Donev, might need. We agreed and this led to John emailing Dr. Donev to confirm the project. The following emails show the first steps in the project; 
 \bigskip
 \begin{figure}[h]
   \centering
-      \includegraphics[width=0.8\textwidth]{1.png}
+      \includegraphics[width=1.1\textwidth]{1.png}
   \caption{Initial exchange of emails to get the project started}
 \end{figure}
 
 \newpage
-Once the project was confirmed, Dr. Donev and John chatted briefly on the phone to go over some project specifications very briefly. John told us a little about the app requirements such as it needing to communicate with an external piece of hardware. After some discussions of our own, we then met with Dr. Donev as a group after confirming a time;
+Once the project was confirmed, Dr. Donev and John chatted on the phone to go over some project specifications very briefly. John told us a little about the app requirements such as it needing to communicate with an external piece of hardware. After some discussions of our own, we then met with Dr. Donev as a group after confirming a time;
 
 
 \bigskip
 \begin{figure}[h]
   \centering
-      \includegraphics[width=0.8\textwidth]{3.png}
+      \includegraphics[width=1.1\textwidth]{3.png}
 
   \caption{Setting up a stand up meeting with Dr. Donev as a group}
 \end{figure}
 
 
-During this meeting we focused solely on requirements and what was the applications intended purpose. Some of the major requirements that were deduced were displaying a reading of the muons and being able to record that reading for data processing.
+During this stand up meeting, we focused solely on requirements and what was the applications intended purpose. Some of the major requirements that were deduced were displaying a reading of the muons and being able to record that reading for data processing.
 
 Approximately two weeks after the initial consult, we met with Dr. Donev again with a low fidelity prototype. This was the meeting where we recorded our Wizard of Oz style demo.