% $Id: challenges.tex 12673 2008-05-06 18:50:38Z amoghk $



% Amogh, even the section heading needs to be generic enough
\section{Challenges in Maintaining Platform-specific QoS Mappings}
\label{sec:challenges}
Below we discuss challenges in developing and maintaining
platform-specific QoS mappings:
% Now explain the challenges first generally, then as applied to
% one or more platforms:

% rules duplication - A mapping may require change in each platform
% configuration - e.g., rules that hard code mechanisms/values of configurations
% must be changed across for each "commonality/generality"
% 
% rules maintainence - support for maintainance for each mapping..
% this is difficult because typically expressed as a set of rules..
% hard to maintain..as # of platforms increase..

% QoS mapping evolution - during development, if a configuration does not
% give confidence (through design-time techniques, or empirical
% validation), developer might want to change the way requirements
% get mapped..this is difficult..give example in terms of time reqd..
% %%%%NOTE: this also means that we have to clarify what tool we are using
% %%%%upfront - mention GME and GReAT somewhere in intro.
% give concrette example of ccm mapping..must be repeated several times.
\noindent\textbf{Duplication of Rules.}

\noindent\textbf{Maintainence of Rules.}

\noindent\textbf{Evolution of QoS Mapping Algorithms.}
% Amogh, make sure that you refer to the section(s) where these challenges are
% resolved.  If you think this section is too small, just move this to section 3
% with a subsection saying what challenges must be resolved by an approach like
% MTS. 
% Andy, this is what I am going to do - I dont think I have time to add challenges now
% so I have removed this file for the time being.
