blue / papers.hotmobile2015-maybe · Commits

Commit fc94039576cdf10ea5b8b2535aae01fdef42919f

Authored by Geoffrey Challen
1 parent 9867b498

New.

Inline Side-by-side
Showing 2 changed files with 10 additions and 10 deletions
certainty.tex
  View file @fc94039
... ... @@ -112,20 +112,20 @@ only change when the developer expects them to.
112 112 \subsubsection{Simulation or emulation}
113 113  
114 114 Pre-deployment simulation or emulation may provide a way to efficiently
115   -assess \texttt{maybe} statements without involving users. Building simulation
116   -environments that accurately reflect all of the uncertainties inherent to
117   -mobile systems programming, however, is difficult. To complicate matters,
118   -\texttt{maybe} alternatives may depend on details of user interaction that
119   -are difficult to know \textit{a priori}, particularly when new apps or
120   -functionalities are being investigated. So in most cases we believe
121   -post-deployment testing will be required.
  115 +evaluate \texttt{maybe} statements without involving users. Building
  116 +simulation environments that accurately reflect all of the uncertainties
  117 +inherent to mobile systems programming, however, is difficult. To complicate
  118 +matters, \texttt{maybe} alternatives may depend on details of user
  119 +interaction that are difficult to know \textit{a priori}, particularly when
  120 +new apps or functionalities are being investigated. So in most cases we
  121 +believe post-deployment testing will be required.
122 122  
123 123 However, pre-deployment testing may still be a valuable approach,
124 124 particularly when a large number of \texttt{maybe} statements are being used.
125 125 Since this can explode the adaptation space, simulations may be able to help
126 126 guide the developer's choices of which \texttt{maybe} statements may have a
127   -significant impact on performance and should be assessed first. Other
128   -\texttt{maybe} statements can be assessed later or eliminated.
  127 +significant impact on performance and should be evaluated first. Other
  128 +\texttt{maybe} statements can be evaluated later or eliminated.
129 129  
130 130 \subsubsection{Split testing}
131 131  
... ...
maybe.tex
  View file @fc94039
... ... @@ -66,7 +66,7 @@ Figure~\ref{fig-maybeexamples} shows several extensions of the \texttt{maybe}
66 66 statement providing syntactic sugar. \texttt{maybe} function annotations
67 67 allow uncertainty to be expressed at the function level, with the
68 68 alternatives consisting of multiple function definitions with identical
69   -signatures. Finally, \texttt{maybe} blocks that require custom evaluation
  69 +signatures. Finally, \texttt{maybe} statements that require custom evaluation
70 70 logic can include an \texttt{evaluate} block as shown in the final example.
71 71 \texttt{evaluate} blocks provide app-specific \textit{a posteriori} logic to
72 72 evaluate the selected alternative. The \texttt{evaluate} block must return a
... ...