% by Mirella M. Moro; version: September/03/2010 @ 6:04pm 
% -- 09/03/2010: bib file with names for proceedings and journals; cls with shrinked {received}
% -- 08/27/2010: appendix, table example, more explanation within comments, editors' data

\documentclass[jidm,a4paper,dvipdfm]{jidm} % NOTE: JIDM is published on A4 paper
\usepackage{graphicx,url}  % for using figures and url format
\usepackage{graphicx}
\usepackage[T1]{fontenc}   % avoids warnings such as "LaTeX Font Warning: Font shape 'OMS/cmtt/m/n' undefined"
\usepackage{fancyhdr}
\usepackage[usenames]{color}
\usepackage{pifont} 		% pacote para símbolos matemáticos
\usepackage{makeidx}  	% allows for indexgeneration
\usepackage{varioref} 
\usepackage{amssymb}            % pacote para símbolos matemáticos
%\usepackage{wasysym}            % pacote para símbolo DiamondBlack, ajusta toda a fonte matemática


%\usepackage{makeidx}  % allows for indexgeneration
%\usepackage{amsfonts}           % pacote para fontes
%\usepackage{wrapfig}  % Figura ao lado do texto
%\usepackage[latin1]{inputenc}	% pacote para acentuação TIRAR
\usepackage{wasysym} % pacote para símbolos matemáticos
%\usepackage{latexsym} % pacote para símbolos matemáticos
%\usepackage{ifsym} 
%\hyphenpenalty=2000 \tolerance=400  % preserva a hifenização de grandes palavras e evita q as pqnas se quebrem
%\usepackage{algorithm}
%\usepackage{algorithmic}



%\usepackage{cite} % NOTE: do **not** include this package because it conflicts with jidm.bst

% Standard definitions
\newtheorem{problem}{Problem}
\newtheorem{theorem}{Theorem}[section]
\newtheorem{conjecture}[theorem]{Conjecture}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{lemma}[theorem]{Lemma}
\newdef{definition}[theorem]{Definition}
\newdef{remark}[theorem]{Remark}
\newenvironment{latexcode}
{\vspace{0.1in}\setlength{\parindent}{18pt}}
{\vspace{0.1in}}

\def\mt#1{\textcolor{blue}{#1}}
\def\pb#1{\textcolor{red}{#1}}
% ALL FIELDS DOWN TO BEGIN{document} ARE MANDATORY

% The following data (volume, number and page) are given by the editors prior to publishing your paper
\jidmVolume{1}
\jidmNumber{1}
\jidmYear{11}
\jidmMonth{Oct}
\setcounter{page}{1}


% Includes headers with simplified name of the authors and paper title
\markboth{M. Teixeira, P. Sabadin}
{Planning Databases Service Level Agreements through Stochastic Petri Nets}
%  -> \markboth{}{}
%         takes 2 arguments
%         ex: \markboth{M. M. Moro}{Any paper title}


% Title of the paper
\title{Planning Databases Service Level Agreements\\ through Stochastic Petri Nets
}


% List of authors
%IF THERE ARE TWO or more institutions, please use:
\author{Marcelo Teixeira\inst{1}, Pablo Sabadin Chaves\inst{2}}
%\author{Marcelo Teixeira}


%Affiliation and email
\institute{Universidade Federal de Santa Catarina \\ 
\email{mt@das.ufsc.br}
% IF THERE IS ANOTHER INSTITUTION:
\and Dueto Tecnologia Ltda\\
\email{pablo@duetotecnologia.com.br}
}


% Paper abstract - it should be from 100 to 300 words
\begin{abstract}
The Service Oriented Architecture (SOA) has become a pattern for managing business transactions through distributed services, usually supported by third-party providers. 
In the SOA world, Service Level Agreements (SLA) are used to establish the requirements between customers and providers. 
Among the clauses agreed in SLA are those related with databases execution time, which have direct relationship with the overall web services performance. 
However, the high variability, typical of the SOA environments, makes difficult the negotiation of an appropriate SLA that could be guaranteed in practice. 
Thus, efforts to predict the quality of SOA-based transactions are justified by anticipate possible problems that tend to arise at run-time, disturbing the SLA clauses. 
In this paper we propose a simulation modeling approach, based on stochastic Petri nets, for performance evaluation of databases requests in data-intensive business applications. 
Through our proposal it is possible to predict the resources consumption and performance degradation of databases, upon the variation of the workload levels, both at design-time and run-time.
A case study was conducted in order to illustrate our contributions.
\end{abstract}


% ACM Computing Classification System categories
%\category{H. Information Systems}{H.m. Miscellaneous}{Databases}
%\category{H.3.4}{Information Systems}{Systems and Software}[Performance evaluation] 
\category{D.4.8}{Software}{Performance}[Modeling and prediction] 
% Categories and Descriptors are available at the 1998 ACM Computing Classification System
% http://www.acm.org/about/class/1998/
%  -> \category{}{}{}
%         takes 3 arguments for the Computing Reviews Classification Scheme.
%         ex: \category{D.3.3}{Programming Languages}{Language Constructs and Features}
%                   [data types and structures]
%                   the last argument, in square brackets, is optional.

% Paper keywords
\keywords{Databases, GSPN, Performance Evaluation, SLA compliance}
%  -> \keywords{} (in alphabetical order \keywords{document processing, sequences,
%                      string searching, subsequences, substrings})


% THE PAPER BEGINS
\begin{document}
\maketitle

%\input{Sections/Planning}
\input{Sections/Introduction}
\input{Sections/RelatedWorks}
\input{Sections/BasicConcepts}
\input{Sections/DB_PerformanceModel}
\input{Sections/CaseStudy}
\input{Sections/Conclusions}


	
% INCLUDE BIBLIOGRAPHY WHICH MUST FOLLOW jidm.bst TEMPLATE
\bibliographystyle{jidm}
\bibliography{Ref/jidmb}
% For information on how to write bibliography entries, 
% see file jidmb.bib

\begin{received}
\end{received}

\end{document}
