From d08ea85a93b2e55f417820c70281d2390e03caf1 Mon Sep 17 00:00:00 2001 From: Scott Haseley Date: Fri, 15 Apr 2016 16:15:27 -0400 Subject: [PATCH] Fix paragraph break, add abstract. --- abstract.tex | 10 +++++++++- introduction.tex | 1 + 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/abstract.tex b/abstract.tex index 7ee2bc0..826688f 100644 --- a/abstract.tex +++ b/abstract.tex @@ -1,5 +1,13 @@ \begin{abstract} -Write an abstract here. +Current operating systems are already proficient at managing certain system +resources, such as the CPU, memory, and disk. But on interactive mobile devices, +users care more about resources such as time, battery life, and money, that are +unmanaged or poorly managed by today's smartphone platforms. It is the degree +to which mobile devices effectively manage these human-facing resources that +determines a user's \textit{quality of experience} (QoE), and it is QoE which +should drive not just policy, but decisions on mobile devices. To meet +smartphone users' expectations, it is necessary to design systems that can +accurately measure and understand QoE, and make decisions based on QoE. \end{abstract} diff --git a/introduction.tex b/introduction.tex index d3b4079..0caf1e6 100644 --- a/introduction.tex +++ b/introduction.tex @@ -37,6 +37,7 @@ frequency, such as for time-insensitive background tasks or when the performance increase would not be perceivable, negative QoE may manifest itself through poor battery life. +\newpage In terms of QoE, static policies can lead to resource allocation decisions that are less than optimal. To remedy this, we propose designing QoE-centric mobile operating systems that use QoE as input to drive resource allocation -- libgit2 0.22.2