\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Software Agent Reusability Mechanism at Application Level},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2013-01-15 (revised: 15 January 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-01-15}
\title{Software Agent Reusability Mechanism at Application Level}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Deepti  Aggarwal}

             \author[2]{Deepti  Aggarwal}

             \author[3]{Aarti  Singh}

             \affil[1]{  Maharishi Markendeshwar University, Mullana, Ambala, Haryana}

\renewcommand\Authands{ and }

\date{\small \em Received: 9 December 2012 Accepted: 4 January 2013 Published: 15 January 2013}

\maketitle


\begin{abstract}
        


The usage of already available software agents plays a vital role in the process of development of application specific software. This reuse also leads to software development cost benefits as well as may ensure the timely delivery. This paper  lay down an idea that for reusing reactive multi-agents systems two factors are to be considered i.e. (i) abstract description of agent in application independent way and (ii) reuse of such systems through adoption in specific domain[25]. For such a development main requirement is the effective reusable software abstractions. In present study the role of abstraction level and dependence level is analyzed for intelligent agents.

\end{abstract}


\keywords{software reuse, software agents, software abstraction.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
he reuse of software components refers to the process of using software artifacts for the development of new software. Since the evolution of computational systems, the reuse of software is in practice. Reuse of the already existing code to develop new software or developing the software that can be reused is one of the prominent areas of research. The present study mainly focuses on the intricacies involved in reuse of multi agent software systems.\par
A software agent is a computer program that symbolizes a user. It implies that an agent has the capacity to make the appropriate decisions.\par
Using software agents for Domain-oriented component design method is a newly proposed reuse approach in software engineering and it starts from the process of acquiring business knowledge within a common application domain. After having the knowledge of the application domain, a collection of business logic is mapped into components which can be reused in the future deign. This method increases the functional completeness of the software component and makes it reusable to a lower extent. Since the business requirements of different organizations are diverse and are changing, so a reusable knowledge base that can be adaptive and flexible are yet to be provided by current domain component design methods. In the following section the major design issues of the reusable software components are addressed.  
\section[{II.}]{II.} 
\section[{Design Issues}]{Design Issues} 
\section[{Software A bstractions}]{Software A bstractions}\par
The abstraction of software artifacts has to be used in every method of software reuse. A software abstraction is high-level, in the sense that attributes corresponding to one or more realizations of facts in more detailed level are represented. Some attributes describe what and how abstraction is done \hyperref[b18]{[19]}. For the clear understanding, comparison and selection of appropriate software artifacts, the small abstractions are needed and these abstractions can be used in reuse process. The clear understanding of user interface has to be there so that a set of software artifacts can be composed and this should be depicted in the abstraction specification. Every artifact plays an important role in application development and it may not be concluded that the final deliverable i.e. the software product satisfies the user requirements or not.\par
An abstraction is composed of a fixed, a variable and a hidden part. Only the fixed and variable part is visible in the abstraction specification. The fixed part represents the invariant features and the variable part symbolizes the variable features of the abstraction. The hidden part consists of the realization details.  
\section[{C}]{C}\par
The major issues to be considered in the development of agent-based software systems include \hyperref[b2]{[3]}, \hyperref[b10]{[11]}, \hyperref[b11]{[12]}.\par
required to transfer software system from one phase to another in terms of intellect. The goal of the reuse technique should be to minimize the cognitive distance between the abstraction and the final software product. To minimize this distance the abstraction specification should more specifically represent the abstractions which are used for application domain. Finally the mapping of the specifications should be made partially or fully automated \hyperref[b9]{[10]}. 
\section[{IV.}]{IV.}\par
Multigent A pplication E ngineering "Multi-Agent Application Engineering" is a domain oriented research towards reducing software complexity and increasing productivity. This can be accomplished via techniques and tools that aid software reuse in Multi-Agent Software Engineering.\par
In Application Engineering, the software abstractions that can be reused are created. Application Development is the process of developing domain specific applications using software abstractions that can be used again and again \hyperref[b11]{[12]}.\par
In the following section the model for developing agent based application specific software is presented. A set of activities and various tools and libraries that can be used is also discussed for developing high level software abstractions. 
\section[{a) Developing Multi-Agent Specific Applications}]{a) Developing Multi-Agent Specific Applications}\par
A multi-agent specific application is made using the constitution of a group/assortment of reusable agent frameworks available in the library of the development environment as shown in Figure 1. These frameworks are realizations of high-level software abstractions in the library. Particular requirements of a multi-agent specific application are used, to map the specification level of a domain model into a realization satisfying such needs. The realization should have associated a set of frameworks, which are agent-based solutions to those requirements. Requirement analysis in Agent-based Application Development should also consider particular preferences of users of the multi-agent specific application. Therefore, these user profiles are used to map the specification level of a user model into a realization satisfying these preferences or user needs. The realization should have associated a set of frameworks, which are agent-based solutions to those needs. The choice of mapping to select best frameworks depends on the fact that which particular style of agent architecture is to be used for the design. 
\section[{Realization of Composed of}]{Realization of Composed of} 
\section[{b) Developing High -Level Software Abstractions}]{b) Developing High -Level Software Abstractions}\par
The reusable agent-based software abstractions are illustrated and described considering their level of abstraction and their dependence level from the application or user domain: domain models, user models, agent-oriented architectural styles, agentoriented design patterns, agent-oriented frameworks and software agents.  
\section[{C}]{C}\par
Software Agent Reusability Mechanism at Application Level A conception of problem. The language represents the definitions necessary for elements, processes and their relationships in the system. The user model specifies the needs and requirements of the end user. 
\section[{d) Design of the Model}]{d) Design of the Model}\par
The outcome of the design phase is the reusable design attributes of Agent -Based Application Engineering. It consists of the agent based architectural styles, software patterns and the frameworks. Architectural style is the set of designing rules which will specify the type of elements and coupling which can be used to constitute the system and subsystems.\par
The software pattern identifies and specifies the problems can commonly occur at conceptual and architectural level. These problems generally originate from architectural styles being used, domain model and the user model. A software pattern has a set format so that it can be easily propagated. This format asserts the problems that have been depicted by the pattern and forces the action to be taken to resolve the problems. For making use of such pattern there should be a framework that validates the pattern and provides a probable solution to the problem. If it was previously used in some application, that has to be mentioned in the framework. Some agent based software patterns have already been proposed that can be used at architectural level or later stages in the agent design \hyperref[b1]{[2,}\hyperref[b16]{17]}. The basic design guidelines are provided by the architectural styles and the agent patterns so that agent oriented frameworks can be developed \hyperref[b2]{[3,}\hyperref[b4]{5,}\hyperref[b19]{20]}. The participating agents are chosen from the bank of agents which facilitates domain dependent or domain independent functionality. 
\section[{V.}]{V.} 
\section[{Conclusion}]{Conclusion}\par
A new horizon of reuse based software engineering using agent paradigm has been introduced. With the introduction of one more layer of abstraction at the software level, the present study may be used for the development of reusable software components across various platforms. Thus it proposed an effective model for agent based reuse. \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
    		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Krueger ()]{b15}\label{b15} 	 		\textit{},  		 			C W Krueger 		.  	 	 		\textit{Software Reuse. ACM Computing Surveys}  		1992. 24  (2) .  	 
\bibitem[Shankar and Thakare (2009)]{b10}\label{b10} 	 		‘A Road Map of Autonomous Software Agent Architectures’.  		 			Gopal Shankar 		,  		 			V M Thakare 		.  	 	 		\textit{Proceedings of 3 rd National Conference INDIA Com-2009, Computing for Nation Development},  				 (3 rd National Conference INDIA Com-2009, Computing for Nation Development)  		2009. Feb 26, 27 2009.  		 			BVICAM New Delhi 		 	 
\bibitem[Jennings ()]{b13}\label{b13} 	 		‘A Roadmap of Agent Research and Development’.  		 			N R Jennings 		.  	 	 		\textit{Autonomous Agents and Multi-Agent Systems}  		1998. 1  (1)  p. .  	 
\bibitem[Diniz and Girardi ()]{b5}\label{b5} 	 		\textit{ABARFI: An Agent-Based Software Architecture for Information Access and Filtering},  		 			A Diniz 			\mbox{}\\  				advisor 			 		,  		 			R Girardi 			\mbox{}\\  				advisor 			 		.  		2001.  	 
\bibitem[Aridor ()]{b1}\label{b1} 	 		‘Agent Design Patterns: Elements of Agent Application Design’.  		 			Y Aridor 		.  	 	 		\textit{Proceedings of Autonomous Agents 98},  				 (Autonomous Agents 98)  		1998.  	 
\bibitem[Lima Costa Ferreira and Girardi ()]{b16}\label{b16} 	 		‘Agent-based Software Architectures in Information Access Systems. Final Degree Dissertation’.  		 			S Lima Costa Ferreira 			\mbox{}\\  				advisor 			 		,  		 			R Girardi 			\mbox{}\\  				advisor 			 		.  	 	 		\textit{CGCC-UFMA}  		2002.  	 	 (In Portuguese) 
\bibitem[Ribeiro De Oliveira and Girardi ()]{b18}\label{b18} 	 		‘An Analysis of Software Patterns for Agentbased Development. Final degree dissertation’.  		 			I Ribeiro De Oliveira 			\mbox{}\\  				advisor 			 		,  		 			R Girardi 			\mbox{}\\  				advisor 			 		.  	 	 		\textit{CGCC-UFMA}  		2001.  	 	 (In Portuguese) 
\bibitem[Maamar ()]{b17}\label{b17} 	 		‘An Overview of Agent-based Framework’.  		 			Z Maamar 		.  	 	 		\textit{ACM Computing Surveys}  		2000. 32  (1) .  	 
\bibitem[Girardi (ed.) ()]{b9}\label{b9} 	 		\textit{Application Engineering: Putting Reuse to Work In: Object Frameworks},  		 			R Girardi 		.  		Dennis Tsichritzis (ed.)  		1992.  		 			University of Geneva 		 	 
\bibitem[Bradshaw ()]{b2}\label{b2} 	 		 			J M Bradshaw 		.  		\textit{Book on Software Agents. Published by The AAAI Press},  				1997. 1997.  	 
\bibitem[Burmeister ()]{b4}\label{b4} 	 		‘Models and Methodology for Agent-Oriented Analysis and Design’.  		 			B Burmeister 		.  	 	 		\textit{Proceedings of KI'96 Workshop on Agent-Oriented Programming and Distributed Systems},  				 (KI'96 Workshop on Agent-Oriented Programming and Distributed Systems)  		1996.  	 
\bibitem[Jennings ()]{b12}\label{b12} 	 		‘On Agent-based software engineering’.  		 			N R Jennings 		.  	 	 		\textit{Artificial Intelligence}  		2000. 117 p. .  	 
\bibitem[Kendall ()]{b14}\label{b14} 	 		‘Patterns of Intelligent and Mobile Agents’.  		 			E A Kendall 		.  	 	 		\textit{Proceedings of Autonomous Agents' 98},  				 (Autonomous Agents' 98)  		1998.  	 
\bibitem[Girardi]{b19}\label{b19} 	 		\textit{Reuse in Agent -Based Application Development},  		 			Rosario Girardi 		.  		 	 
\bibitem[Alves Da Silva Filho and Girardi ()]{b0}\label{b0} 	 		\textit{SIMCAP: A Multi-agent System for Filtering Scientific Publications from the Web},  		 			J H Alves Da Silva Filho 			\mbox{}\\  				advisor). 			 		,  		 			R Girardi 			\mbox{}\\  				advisor). 			 		.  		2001.  	 
\bibitem[Hyacinth ()]{b11}\label{b11} 	 		‘Software Agents: An Overview’.  		 			S N Hyacinth 		.  	 	 		\textit{Knowledge Engineering Review}  		1996. 11  (3)  p. .  	 
\bibitem[Shaw ()]{b20}\label{b20} 	 		\textit{Software Architecture: Perspectives on an Emerging Discipline},  		 			M Shaw 		.  		1996. Prentice-Hall.  	 
\bibitem[Girardi ()]{b7}\label{b7} 	 		‘Software Architectures to Improve the Effectiveness of Reuse Techniques’.  		 			R Girardi 		.  	 	 		\textit{8th WORKSHOP ON SOFTWARE REUSE (WISR8)},  				1997.  	 
\bibitem[Brugali ()]{b3}\label{b3} 	 		‘Towards Agent-oriented Application Frameworks’.  		 			D Brugali 		.  	 	 		\textit{ACM Computing Surveys}  		2000. 32  (1) .  	 
\bibitem[Girardi ()]{b8}\label{b8} 	 		\textit{Towards Effective Software Abstractions for Application Engineering. Position Paper, NASA Focus on Reuse Workshop},  		 			R Girardi 		.  		1996. Sept. 24-27, 1996. Fairfax, Virginia.  		 			George Mason University 		 	 
\bibitem[Fleming ()]{b6}\label{b6} 	 		‘User Modeling in the Design of Interactive Interface Agents’.  		 			M Fleming 		.  		 67-76.  	 	 		\textit{Proceedings of Seventh International Conference on User Modeling},  				 (Seventh International Conference on User ModelingNew York Inc. Secaucus NJ USA)  		1999. Springer -Verlag.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
