\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={Representing Aspect Model as Graph Transformation},
 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{2011-12-15 (revised: 15 December 2011)}
\def\TheID{\makeatother }
\def\TheDate{2011-12-15}
\title{Representing Aspect Model as Graph Transformation}
\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]{Dr. Vishal  Verma}

             \affil[1]{  Kurukshetra University}

\renewcommand\Authands{ and }

\date{\small \em Received: 7 November 2011 Accepted: 2 December 2011 Published: 15 December 2011}

\maketitle


\begin{abstract}
        


In this paper we discussed a new method for representing aspect models. This method uses the basics of UML to devise a new way for specifying the model level aspects and transformations among them. The resultant model is effective from both expression and scaling point of view. The work in this paper is based on assumed transaction processing system in a bank.

\end{abstract}


\keywords{Aspect - Oriented, Graph Transformation, UML.}

\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
n most of the software development techniques identification and presentation of aspects is done only at some specific levels which pose constraints on the designer and developers to follow a predefined pattern/steps for development process. In this method we try to develop a technique which can be used for representing and composing aspect at any level of software development. With the advent of new techniques for software development it is quite common and natural, that aspect can occur during any of the development phase i.e. requirement \hyperref[b0]{[1]}, analysis \hyperref[b7]{[8]} and design \hyperref[b11]{[12]}. Aspect if modularized during software modeling can leads to a clear boundary among aspects and concerns and they become more maintainable, understandable and organize-able within the model. On the other hand if aspect modules are composed with the development of base module then it helps to fully understand and analyze the model with aspects, and any ambiguity, conflicts and omissions can be avoided. Hence, the mechanism used for specification of aspect at the modeling level must be complemented with mechanism used for composition, that weave the aspect model into base model. Lack of expression and scalability are the major problems faced by the researchers for development of mechanism like this. Composition at the modeling level can be extremely rich in nature \hyperref[b13]{[14]}. Existing models do not provide support for expressing the richness in compositions. However, increase in the degree of expressiveness can lead to the problem of scalability because a large effort is required by the developers to specify the composition. The method discussed in this paper is capable to handle the problem of scalability and expressiveness and the result of this paper is a practical technique that can be used for defining and composing aspect oriented model for best modeling purpose.\par
The method used in this model is based on two basic technology i.e. Role Based Meta Modeling language \hyperref[b1]{[2]} and graph transformation \hyperref[b2]{[3,}\hyperref[b4]{5]}. Role Based Meta Modeling language provides a precise, simple graphical means for specifying a model level aspect in a way that is consistent with UML \hyperref[b12]{[13]}. It is used for modeling the structural part of security aspects \hyperref[b5]{[6]} as well as model behavioral UML aspects \hyperref[b7]{[8]}. The base problem faced while using RBML is that they do not scale up to marks since a lot of effort is required to specify the cross cuts among the core modes. Our discussed method shows clearly the reduction in level of effort to be done for models. Transformations using graphs have been applied in a number of problems related to the software engineering and to the problem of merging of different systems together \hyperref[b8]{[9]}, but in none of the implementations it has been categorically addressed how to apply them, in general way, to handle the aspect at any level of UML modeling. The aim of this paper is to combine together the RBML and graph transformations to achieve a) General implementation of UML based aspect modeling and composition at any stage of abstraction. b) To implement the proper scalability of aspect composition.\par
This paper illustrates the approach with an assumed transaction execution system based closely on an existing application used by banks. 
\section[{II.}]{II.} 
\section[{MODEL LEVEL ASPECTS}]{MODEL LEVEL ASPECTS}\par
Aspect oriented models are models which represent the cross cut, points cut and concern in a well arranged manner along with aspects. From the view point of problem discussed in this paper it can be defined as a model that crosscuts other model at the same level of abstraction. Here the words "same level of abstraction " plays very important role i.e. a model is considered to be an aspect if it crosscut the other model of same interactions e.g. if requirement cut requirement model, requirement artifact cuts requirement artifact only then they are considered as aspects. In particular case a use case may not be aspect. Although a use case is suppose to always cut across multiple implantations module, it is only considered to be an aspect if it cuts across other use case.\par
Discussion in this paper is restricted to the definition of an aspect oriented model with a condition that a model is an aspect only if it crosscuts other model built with same perspective e.g. any model which is build for global interpretation of interaction cannot cut a model build with local interpretation of interaction and hence is not at same level of abstraction but they have different perspective-local and global. These types of models are not considered in this paper. 
\section[{a) Representation of Aspect in Role Based Modeling Language}]{a) Representation of Aspect in Role Based Modeling Language}\par
Role Based Modeling Language \hyperref[b1]{[2]} is used in this paper to represent the Aspect-Oriented Modules. This language is further complemented by France et al \hyperref[b9]{[10]}. RBML is considered as a special case of UML Meta model in which each element of RBML is treated as a role. It is also considered that a role is a constraint of a UML Meta class with a set of optional properties that any element must possess. Because RBML is considered as a special case of UML hence each UML diagram must have a corresponding RBML diagram in which model elements are roles e.g. state roles and transitions of RBML represents a generic state that can be made concrete by assigning it to a concrete role. Proper care is to be taken that only those model elements which satisfy the property of a role should be treated as a role. RBML model defines a generic model that can be instantiated in many ways by assigning elements to its entire role \hyperref[b13]{[14]}. Any UML model is said to conform to a RBML model if there is a valid argument of elements in the UML model to the roles of RBML model \hyperref[b13]{[14]}.\par
RBML model is used to formalize the design pattern \hyperref[b1]{[2]} and to represent model level aspect \hyperref[b3]{[4]}. This was extended to behavioral aspect in \hyperref[b7]{[8]} and \hyperref[b6]{[7]}. As per the original definition in \hyperref[b9]{[10]} all RBML model elements must be roles i.e. they are Meta -level elements. As per \hyperref[b7]{[8]} for representing aspects it is useful to allow objectlevel elements in RBML as well. The result is an extended RBML, represented by eRBML, in which an element may be Meta level or object level element \hyperref[b13]{[14]}. Fig.  {\ref 1} shows the sequence of aspect in eRBML. It clearly shows that whenever the user get ack of failed transaction the HOST itself record the status in STATUS file and at the same time shut down the USER side as well. Fig  {\ref 1} shows the combination of object level elements meta-level role together in one go. This type of combination is preferred since status like objects are remains unchanged and their relative updation dependent on the varying values of roles only.\par
i. Instantiation: it means to assign some concrete Fig.  {\ref 1} : Handling of Failed Transactions values to the elements or one -to -one mapping from role to model elements. In context of eRBML each aspect model must be instantiated before it can be composed with a base model. Instantiation is basically used to define what the aspect should like in context of a particular application i.e. the aspect is identified and specialized to a context. Fig.  {\ref 2} shows another example of how aspects cross cuts each other. Sequence diagram in Fig.  {\ref 2} is taken as base for further discussion and is part of our case study in coming sections. From fig.  {\ref 2} it is enough to conclude that there is a controller which keeps control of accessing request from user and sending it to the server for processing. Controlling all aspect of transaction is the sole responsibility of the Fig.  {\ref 2} : Base Sequence Diagram for user Transactions controller, it also provide the necessary GUI for processing. Failure handling is not considered as part of this discussion. Instantiation is used to propose the aspect for composition with the base. In the example discussed here following instantiations are specified by the modeler: | USER -> CONTROLLER| CONTROLLER-> SERVER and failure are not considered.  ii. Conformance A UML model is said to conform w.r.t. eRBML if their exist an instantiation of eRBML model in a way that all elements of instantiated eRBML are present in UML model along with existence of constraints. The constraints are suppose to include the message ordering, sequence diagram, transition ordering and additionally specified properties of eRBML roles with respect to an UML model there may exist any number of different eRBML models that conforms dependency upon the availability of additional transaction. There may be any number of additional transactions that exist in between starting and closing transaction i.e. intermediate transactions. Hence conformance should be considered as a type of refinement. Model level aspect can be specified in a well defined way in eRBML with respect to the aspects of UML diagram. As it is necessary to represent the model aspect in a modular fashion, composing the model aspect with base model is also important. Here we are comparing the composition approaches of France et al \hyperref[b10]{[11]} and Whittle \hyperref[b7]{[8]} to identify the limitations of existing method to model. Fist one out of these two approaches use templates to represent aspects. Instantiation of eRBML aspect before composition is mandatory in both of the approaches, though both of the approaches \hyperref[b10]{[11]} and \hyperref[b7]{[8]} have different way of implantation of composition.\par
We have discussed a single method for composition in Fig. \hyperref[fig_0]{3}. This figure though uses simple technique, yet there are many alternates by using which composition could be done. In fig. \hyperref[fig_0]{3} the intermediate transaction is introduced which can be placed at different level of execution and can produce different compositions accordingly. Although it is simple in nature, it may be not be suitable in many cases. Common limitations of this method is that it is not able to specify the fact that how the aspect messages should be interleaved with the base model, or to specify that the aspect messages define a sequence executed in parallel with the base model message. As an alternative there are many possible ways that composition could occur. Challenging part to find a way for specifying composition that admits a high degree of expressiveness, with minimum effort to be applied for modeling. To find the response on expressiveness and scalability below we compare the techniques discussed in \hyperref[b10]{[11]} and \hyperref[b7]{[8]}.\par
The method discussed in \hyperref[b10]{[11]} allows the modeler to describe the composition directive that finally tailors the tailor algorithm. These composition directives permit the user to specify the aspect message interleaved with base or as an alternative or to run in parallel of it. "Addition", "deletion", and "move", statements are supposed to be used as directives to make the composed model. To merge the base and instantiated model first of all their elements with the same name are merged together. On completion of merging of elements with same name in first go directives are tailored to drive the exact form of composition. This all method of tailoring demands a lot pressure on modeler. Manual composition in this way demands a composition to be implemented by first applying the directive in each and every model's element also in the base model. This type of procedure can't be scaled at all.\par
In contrast to this the method discussed in \hyperref[b7]{[8]} is at higher level of abstraction. In this method the composition operators are used instead of composition directives. Specifically AND, OR and IN operators are used. AND operator is used to interleave the base model with aspect model. OR can be used to provide the alternative sequence among base and aspect model. IN has some special use and it is used to insert the aspect message in any base sequence. Operators used in this approach offer a high level view of composing aspect models. This approach is more suitable and easy then the one discussed in \hyperref[b10]{[11]}   
\section[{NEW METHOD OF COMPOSITION}]{NEW METHOD OF COMPOSITION}\par
Techniques discussed in sec 2 have limitations with respect to scalability. In that technique it is the sole responsibility of modeler to specify a set of role instantiations for each aspect and for each base model that is cross cut by aspect. It is obvious that for large aspect more number of instantiations is required to be supplied. From fig. \hyperref[fig_0]{3} it is clear that all the instantiations are given in non graphical and in low level format that are time consuming to understand and ultimately make the maintenance of the model more difficult for the user. In comparison the method discussed in this paper provide a clean and clear way of separation of aspects and the base model. The newly discussed technique provides a new way of representing and composing model aspects in a way that maintains aspect modularity along with scalability. Basically graph transformation rules are used for representing composition and is represented by a rule (L -> R) bearing left hand side and right hand side. Left side is responsible for keeping points where the aspect should be applied and right side keeps the aspects in it. 
\section[{a) Aspect as Graph Transformation}]{a) Aspect as Graph Transformation}\par
A graph transformation discussed in \hyperref[b4]{[5]} is a rule represented by r and has L as left hand side and R as right hand side. Rule r is supposed to be applied on a graph G and the process of applying r finds a graph homomorphism, h, \hyperref[b4]{[5]} from L to G and replacing h (L) in G with h(R). To avoid any kind of unreferenced edges i.e. edges with missing resources or target node -L(R) is applied into G in such a way that all edges connected to a removed node in h(L) are reconnected to a replacement node in h(R).\par
UML diagram can be represented in the form of a graph because it is defined by the UML meta-model which is a graph where the nodes are Meta classes and the edges are meta-relationships \hyperref[b12]{[13]}. Hence it is possible to represent transformation over UML model as graph transformation.\par
Particularly we see composition of an aspect model with a base UML model as a graph transformation LHS and RHS both are eRBML models. As above L side specifies the points where the aspect should be applied and the R side specifies the crosscutting structure/behavior that should be inserted at those points. On applying composition it would become possible to deal with message for future that is inserted as an alternative sequence after all instances of send data/ack, a message sent from CONTROLLER to USER. The approach used here helps to define the expressiveness and scalability related to composition in an easy way. It becomes clear from fig. 4 that it become possible to keep a complete separation of the aspects and its composition strategy. It helps to reuse of the aspects and application of the same aspects with different purpose and different composition strategy. This technique is a fully expressive way of defining composition strategy -as one is shown in Fig. 4(it is one other alternative may be used). This strategy uses the number of instantiations required to design a model. In the example discussed in Fig . 4 only one instantiation is required to be provided by the modeler i.e. failure ack. Rest all roles can be instantiated by graph matching against a base mode, the left side of the graph transformation is required to be matched with base model instantiating USER, SERVER , send data/ack (only failure ack is required to be instantiated). In fig. 4 the UML 2.0 ref fragment is used to specify the placeholder for a sequence of messages in the base. This is an easy way to match against a message sequence whose position in the composed model can then be specified exactly on the R.H.S of the base definition must be modified. When matching against the Left side of the transformation rule r, it is mandatory to discuss the instantiation for the role elements. In this context the base definition is modified as the graph transformation applies to a UML model if and only if the Left side of transformation has a graph match i.e. module conformance exist there. The method in terms of scalability and expressiveness can be defined as: i. Scalability Main limitation of the scalability of all aspect approaches based on RBML is that the modeler must instantiate the role elements for each base model crosscut by the aspects. Use of graph transformations reduce this effort because instantiating the role elements become automated to some extent. Instantiation place a need to find a base model over which graph transformation can be applied-i.e. finding a match for left hand side of the transformation rule. As per above discussion we apply the module conformance while applying an aspect i.e. while working with the eRBML model, R (rule), match a UML model say U, modulo conformance if and only if there is an instantiation of the role element Ø, such that Ø(R) conforms to model U. as is clear from Fig. 4 it has modulo conformance with the base model and hence problem of scalability is managed well by graph transformations.\par
ii. Expressiveness As shown in Fig. 4 and sec 3.1 the Right side of the graph transformation rule, r, defines the manner in which the aspect cross cuts a base model. Since Right side is a model in itself, it completely reflects the expressiveness and how the cross cutting is defined.\par
Here the aspect messages can be defined as an alternative to a base message or messages, as interleaved with the base message, accessing in parallel with the base message or any other combination of above discussed alternatives. The composition operator discussed in sec 2.2.2 can be defined as special case but graph transformation allows any combination of these operators to be specified, or needed for new operators to be specified. The composition directive in sec 2.2.1 are subsumed by the graph transformation approach because there is no longer any need to tailor the aspect composition algorithm to add, delete or remove elements -these modifications are rather defined explicitly in the Right side of the transformation. 
\section[{IV.}]{IV.} 
\section[{CASE STUDY}]{CASE STUDY}\par
For the purpose of doing the case study of the expected system to be developed, we assume a system in general which is responsible for processing of transactions raised by user in terms of bank transactions. Every user of bank is supposed to execute a set of queries (may be predefined) for completion of desired tasks. We assume a system for study in which each user is required to first authenticate him/herself for executing other transactions. After authentication use is provided with a GUI by using which rest all requests can be processed. Some of the simplest form of query is deposit and withdraw of amount and to get a balance or mini statement from the bank. In all of this type of queries a proper integrity among user interface window and ATM machine is mandatory i.e. any transaction which affect the balance in the account must be effective at all place and do the final status change at some common location. These type of queries are expected to be executed form ATM machine, from online based banking system, mobile based banking system or from a window in a bank's office where a bank officer is supposed to execute desired on verification of credentials from user. Important among all these alternatives of query execution is that they must do final status change at common location which is accessed by all means of query execution and all the time latest updated value must be available at that location i.e. SERVER. Data integrity is clearly an important issue to be maintained in design of this type of systems. Any user who is permitted to use his account by a number of means is dependent on one central location i.e. SERVER for latest updated values. The design of this system is done by using the twophase commit protocol for maintaining serializability among the transactions to keep the commonly used values updated at all the time. The stress here is on the application implementation of protocol not on its practical details and is embedded in the working of CONTROLLER. Following we are showing the embedding of protocol in the CONTROLLER (core) functionality and how the protocol is implemented via aspects. This implementation is easily readable and hence any desired changes in integrity are easily implementable. The design is done in UML by keeping the dynamic nature of the design.\par
Importantly two situations demands the close look upon the updated data i.e. first when a user is accessing the account by bank window and at the same time accessing via the mobile banking services and second when transaction through ATM is under process and at the same time mobile banking transaction is executing. Both of the situations demand the very proper execution of two phase commit protocol. Fig. 5 and Fig. 6 shows the base sequence execution of transaction models corresponding to the execution of query's from WINDOW and MOBILE at a time and from ATM and MOBILE at a time. In second discussed scene the execution of query and updation in final value may be delayed for some time because updation done through ATM may take some time for final updation in the system. In fig. 6 we are introducing a new syntax (all) used for processing the number of transactions together finally at the common server execution. The intermediate results may get stored in CONTROLLER and are finally updated to the SERVER.\par
Here the two phase commit protocol is not modeled as part of the core functionality. Rather it is modeled separately for easy modification if needed. In Fig. 5 and Fig. 6 every time the trigger of transaction is initialized by initializing both the server as well as client by CONTROLLER. Then first of all data (initial) is updated at sever and first GUI is provided to the client. In steps proceeding further the ID and PWD is submitted from USER to the SEVER and on receiving the ACK (POSITIVE) further transactions are processed.\par
Two phase commit protocol is modeled and shown in Fig.  {\ref 7}. It is build by considering the aspectual view of transaction and keeping them in sequence in an eRBML. Aspects are used to define a general pattern of communication to be used by Interaction among the two is given in the form of message role so that it can be instantiated whenever required with any specific message names. Important implication of Fig.  {\ref 7} is that it commit any of the transaction only if both the USER as well as COMMIT SEVER agrees on the transaction. This all is modified and is shown in Fig.  {\ref 8} Representing Fig.  {\ref 9} and Fig.  {\ref 10} shows the left side and Right side of graph transformation for refined aspect discussed in Fig. 6. Important to note here is that the Left side says that we have to apply the aspect at the points at which prepare for commit will appear and the same should preceded by Initialize message. The enable is true for both of first and second scene. Here it is possible to process the step by step manner or to execute a separate algorithm for execution of transactions. Right side of graph is shown in Fig.  {\ref 10}. In this fig other messages are included to take into consideration all or any kind of transaction which not be used in general by all user but is expected to execute in some special case only. The messages are supposed to be executed only if the reply from the two phase commit protocol is true. Two phase commit protocol is able to reply true or false depending on the execution of transactions. The base and aspect model are composed in such a way that match for all other messages is done only after point of successful commitment. The use of existing method discussed in \hyperref[b10]{[11]} and \hyperref[b7]{[8]} are not able to specify the conditions. The method presented by \hyperref[b7]{[8]} may allow the weaving in the way which we want to describe. In method discussed in \hyperref[b10]{[11]} it is needed to specify a list of composition directives that give the instructions to composition algorithm where to placethe messages matching with other messages. Hence the messages Fig.  {\ref 8} : Updated Two Phase Commit Protocol discussed in \hyperref[b10]{[11]} and \hyperref[b7]{[8]} are not appropriate for presenting the directives in easy way and are time consuming and error-prone too. In comparison to these two methods the graph transformation is an easy graphical method to specify the directives. In the method suggested in this paper it is very easy to place any additional messages anywhere in the Right side of the graph transformation rule. Along with is also possible to specify a different composition way to simplify|modifying the Right side of the Rule. 
\section[{V. CONCLUSION AND RELATED WORK}]{V. CONCLUSION AND RELATED WORK}\par
All of the existing approaches used to identify, compose and represent aspect at various level of software development faces a number of limitations especially the problem of scalability. The approach discussed in this paper for representing aspect at any level of software development using the UML methodology based on role modeling language. Various level of hierarchy are used to structure aspects and their possible instances. The problem of scalability is sorted out in this method since graph transformation allow the matching at any level of development and it automatically compose aspects along with the problem of expressiveness is also sorted out as use of graphical method in terms of graph transformation expresses all implementations. The validity of approach is reflected through its use on bank's transactions. The approach discussed in this method is more close to syntactic implementations a lot of modifications can be done in terms of syntax related issues so that immediate implementations in programming language can be done. The modification to resolve the conflict among the aspects can also be done. The matching process discussed in this paper is also open to be modified. The modification in terms of forward and backward movements on matching at any level of transformation can be done. \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Fig. 3}\end{figure}
       \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.58796992481203\textwidth}P{0.22368421052631576\textwidth}P{0.038345864661654135\textwidth}}
USER\tabcellsep HOST\tabcellsep STATUS\\
Transaction Fwd\tabcellsep Save Status\tabcellsep \\
Failed Ack\tabcellsep \tabcellsep \\
Shut Down\tabcellsep \tabcellsep \\
2011\tabcellsep \tabcellsep \\
December\tabcellsep \tabcellsep \\
18\tabcellsep \tabcellsep \\
Enable\tabcellsep \multicolumn{2}{l}{Store Initial Status}\\
Store Initial Status\tabcellsep \tabcellsep \\
\multicolumn{2}{l}{Send Id \& Pwd}\tabcellsep \end{longtable} \par
  {\small\itshape [Note: © 2011 Global Journals Inc. (US)]} 
\caption{\label{tab_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.19302788844621513\textwidth}P{0.5147410358565737\textwidth}P{0.10159362549800798\textwidth}P{0.020318725099601594\textwidth}P{0.020318725099601594\textwidth}}
SCREEN\tabcellsep USER\tabcellsep CONTR\tabcellsep SERVER\tabcellsep STATUS\\
\tabcellsep \tabcellsep OLLER\tabcellsep \tabcellsep \\
Enable\tabcellsep \tabcellsep \multicolumn{2}{l}{Store Initial Status}\tabcellsep \\
\multicolumn{2}{l}{Store Initial Status}\tabcellsep \tabcellsep \tabcellsep \\
alt\tabcellsep \multicolumn{2}{l}{Send Id \& Pwd}\tabcellsep \tabcellsep \\
\tabcellsep \multicolumn{3}{l}{Acknowledge with Acceptance}\tabcellsep \\
\tabcellsep \multicolumn{2}{l}{Request for Transaction}\tabcellsep \tabcellsep \\
\tabcellsep \multicolumn{2}{l}{Reply with Latest Value}\tabcellsep \tabcellsep \\
\tabcellsep \multicolumn{2}{l}{Intermediate Request}\tabcellsep \tabcellsep \\
\tabcellsep \multicolumn{4}{l}{Update the final status after transaction}\\
\multicolumn{3}{l}{Activate for next User}\tabcellsep \tabcellsep \end{longtable} \par
  {\small\itshape [Note: manner. The only drawback of this approach is limited number of operators for performing all desired tasks. III.]} 
\caption{\label{tab_1}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.24363057324840762\textwidth}P{0.27070063694267515\textwidth}P{0.17866242038216562\textwidth}P{0.12452229299363056\textwidth}P{0.03248407643312102\textwidth}}
transformation w.r.t eRBML, the\tabcellsep USER\tabcellsep \tabcellsep CONTROLLER\\
\tabcellsep \multicolumn{2}{l}{Send data/ack}\tabcellsep \\
\tabcellsep ref\tabcellsep other\tabcellsep \\
2011\tabcellsep USER\tabcellsep \multicolumn{2}{l}{CONTROLLER}\tabcellsep STATUS\\
December\tabcellsep alt\tabcellsep Send data/ack\tabcellsep \multicolumn{2}{l}{Update Status}\\
20\tabcellsep \multicolumn{2}{l}{Failure ack}\tabcellsep \\
\tabcellsep \multicolumn{2}{l}{Shut Down}\tabcellsep \\
\tabcellsep ref\tabcellsep other\tabcellsep \end{longtable} \par
 
\caption{\label{tab_2}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.10152477763659466\textwidth}P{0.2667725540025413\textwidth}P{0.06912325285895807\textwidth}P{0.021601016518424394\textwidth}P{0.006480304955527319\textwidth}P{0.006480304955527319\textwidth}P{0.3574968233799238\textwidth}P{0.015120711562897076\textwidth}P{0.005400254129606099\textwidth}}
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep SCREEN\tabcellsep USER\tabcellsep CONTR\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep OLLER\\
\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep Enable\tabcellsep Initialize\\
\tabcellsep SCREEN\tabcellsep USER\tabcellsep CONTR\tabcellsep SERVER\tabcellsep STATUS\tabcellsep Initialize\\
\tabcellsep \tabcellsep \tabcellsep OLLER\tabcellsep \tabcellsep \\
\tabcellsep Enable\tabcellsep \tabcellsep \multicolumn{2}{l}{Initialize}\tabcellsep \tabcellsep Update Initial Status\\
2011\tabcellsep \tabcellsep \multicolumn{2}{l}{Initialize}\tabcellsep \tabcellsep \tabcellsep Send Id \& Pwd (Mobile Bank)\\
December\tabcellsep \tabcellsep \multicolumn{4}{l}{Update Initial Status Send Id \& Pwd (Mobile Bank)}\tabcellsep Acknowledge with Acceptance Request for Transaction\\
22\tabcellsep \multicolumn{3}{l}{Acknowledge with Acceptance}\tabcellsep \tabcellsep \tabcellsep Reply against Transaction\\
Global Journal of Computer Science and Technology Volume XI Issue XXII Version I\tabcellsep \multicolumn{4}{l}{Request for Transaction Reply against Transaction Latest Value Updated Credential Verify (Bank Window) Verify Ack Transaction Request Transaction Processed Latest Value Updated}\tabcellsep \tabcellsep Latest Value Updated Credential Verify (Bank Window) Verify Ack Transaction Request Update may pending Store to temp. Server (all) Transaction Processed (all) Latest Value Updated\\
\tabcellsep \multicolumn{2}{l}{© 2011 Global Journals Inc. (US)}\tabcellsep \tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_3}}\end{figure}
 			\footnote{© 2011 Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XI Issue XXII Version I 19 2011 December} 			\footnote{© 2011 Global Journals Inc. (US)} 			\footnote{© 2011 Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XI Issue XXII Version I 21 2011 December transformation. At the time of defining the graph location. Transfer of amount among the inter bank accounts processed in this way cause delayed} 			\footnote{© 2011 Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XI Issue XXII Version I 24} 		 		\backmatter   			  			  			  				\begin{bibitemlist}{1}
\bibitem[Kim ()]{b2}\label{b2} 	 		\textit{A Metamodeling Approach to Sepcifying Patterns},  		 			D-K. Kim 		.  		2004.  		 			Colorado State Univreisity 		 	 	 (PhD Thesis) 
\bibitem[Kim et al. ()]{b1}\label{b1} 	 		\textit{A Role-Based Metamodeling Approah to Sepecifying Design Patterns},  		 			Dae-Kyoo Kim 		,  		 			Robert France 		,  		 			Sudipto Ghosh 		,  		 			Eunjee Song 		.  		2003. 2003. Dallas, Texas.  	 
\bibitem[France et al. ()]{b9}\label{b9} 	 		‘A UML-Based Pattern Sepcification Technique’.  		 			R France 		,  		 			/D-K Kim 		,  		 			S Ghosh 		,  		 			Song 		.  	 	 		\textit{IEEE Transactions on Software Engineering}  		2004. 30  (3)  p. .  	 
\bibitem[Ray et al. (2004)]{b10}\label{b10} 	 		‘An Aspect-Oriented Approach to Design Modeling’.  		 			R 		,  		 			France I Ray 		,  		 			G Georg 		,  		 			S Ghosh 		.  	 	 		\textit{IEEE Proceedings Software}  		August 2004. 151  (4)  p. .  	 
\bibitem[Whittle et al. ()]{b13}\label{b13} 	 		‘Composing Aspect Models with Graph Transformations’.  		 			Whittle 		,  		 			Jon 		,  		 			Araujo 		,  		 			Joao 		,  		 			Moreira 		,  		 			Ana 		.  	 	 		\textit{EA 06},  				 (Shanghai, China)  		2006.  	 
\bibitem[Clarke and Walker ()]{b11}\label{b11} 	 		\textit{Composition Patterns : An Approach to Designing Reusable Aspects},  		 			S Clarke 		,  		 			R J Walker 		.  		2001. 2001. Toronto, Canada: IEEE CS Press. p. .  	 
\bibitem[Rozenberg ()]{b4}\label{b4} 	 		‘Handbook of Graph Grammers and Computing by Graph Transformation’.  		 			G Rozenberg 		.  	 	 		\textit{Foundations." World Scientific}  		1997. 1.  	 
\bibitem[Araujo and Whittle ()]{b6}\label{b6} 	 		\textit{Modeling and Computing Scenario-Based Requirements with Aspects},  		 			J Araujo 		,  		 			J Whittle 		,  		 			DK 		,  		 			Kim 		.  		2004. 2004. Kyoto, Japan: IEEE CS Press.  	 
\bibitem[Rashid et al. (2003)]{b0}\label{b0} 	 		‘Modularisation and Composition of Aspectual Requirements’.  		 			A Rashid 		,  		 			A Moreira 		,  		 			J Araujo 		.  	 	 		\textit{AOSD}  		2003. 2003. March 2003. ACM Press. p. .  	 
\bibitem[Whittle and Araujo ()]{b7}\label{b7} 	 		‘Scenario Modeling with Aspects’.  		 			J Whittle 		,  		 			J Araujo 		.  	 	 		\textit{IEEE Proceedings Software}  		2004. 151  (4)  p. .  	 
\bibitem[Georg and France (2002)]{b3}\label{b3} 	 		‘UML Aspect Specification using Role Modles’.  		 			G Georg 		,  		 			R France 		.  	 	 		Lecture Notes in Computer Science  		September 2002. Springer. 2425 p. .  	 
\bibitem[UML version 2.0 Available from the Object Management Group ()]{b12}\label{b12} 	 		\textit{UML version 2.0 Available from the Object Management Group},  		 \url{http://www.omg.org}  		2005.  	 
\bibitem[Ray et al. ()]{b5}\label{b5} 	 		‘Using UML to Visualize Role-based Access Control Constraints’.  		 			I Ray 		,  		 			N Li 		,  		 			R B France 		,  		 			D-K. Kim 		.  	 	 		\textit{SACMAT}  		2004. p. .  	 
\bibitem[Goedicke et al. ()]{b8}\label{b8} 	 		‘ViewPoint-Oriented Software Development : Tool Support for Integrating Mutiple Prespective by Distributed Graph Transformation’.  		 			M Goedicke 		,  		 			B Enders 		,  		 			T Meyer 		,  		 			G Taentzer 		.  	 	 		\textit{TACAS}  		2000. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
