\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={Diligence of Domain Engineering in Accounting Management System},
 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{2012-01-15 (revised: 15 January 2012)}
\def\TheID{\makeatother }
\def\TheDate{2012-01-15}
\title{Diligence of Domain Engineering in Accounting Management System}
\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. Mukesh  Kumar}

             \author[2]{Pro. (Dr.) Parveen  Kumar}

             \author[3]{  Seema}

             \affil[1]{  Nims University , Jaipur (Rajshthan) India.}

\renewcommand\Authands{ and }

\date{\small \em Received: 14 December 2011 Accepted: 31 December 2011 Published: 15 January 2012}

\maketitle


\begin{abstract}
        


This paper presents on domain feature modeling, domain architecture design and domain implementation in an enterprise. This paper demonstrates the accounting management feature modeling based on the extended (Feature-Oriented Domain Analysis) FODA method and system architecture of accounting management domain, integrates Aspect Object Oriented Programming technology with domain implementation, and designs a whippersnapper AOP framework based on the object proxy pattern to separates crosscutting concerns in the domain implementation phrase.Research result shows this method can effectively seal insulate and abstract variability in requirements of accounting management domain, instruct the designing and implementation of accounting management components, get the requirement of software reuse, resource sharing and collaboration in accounting management domain.

\end{abstract}


\keywords{Feature-Oriented Domain Analysis, Aspect Object Oriented Programming, whippersnapper.}

\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
omain engineering is a reusable approach that focus on a selected application domain as like inventory control, finance management, word processing etc. The motto of domain engineering is find, catalog, construct and broadcast set of software artifacts that could apply for future software in specialized application domain. In domain engineering, we perform domain analysis and capture domain knowledge in the form of reusable software assets. By reusing the domain assets, an organization will be able to deliver a new product in the domain in a shorter time and at a lower cost. In industry, domain engineering forms a basis for software product line practices. Domain engineering is most often divided into three phases: domain analysis, domain design, and domain implementation. At present, from the point of domain engineering, little research has been carried on the accounting management domain. Based on the real project, this paper introduces domain engineering method into the development of accounting management system. In the domain analysis phrase, we use the FODA method to analyze the accounting management domain, expand its feature-oriented modeling method, establish the feature model of accounting management domain; in the domain design phrase, we design multi-tier system architecture of accounting management domain; In the domain implementation phrase, We combine AOP technology with OOP technology, separate crosscutting multi modules concerns in software, reduce the dependence between components effectively. Practice has proved the systems developed by this method have a better performance of maintainability, extendibility and reusability. 
\section[{II.}]{II.} 
\section[{Analysis of Account Management Domain a) Feature Oriented Domain Analysis}]{Analysis of Account Management Domain a) Feature Oriented Domain Analysis}\par
A method specifically designed for DA is the Feature Oriented Domain Analysis (FODA) method developed at the SEI. This process is for domain analysis which supports the discovery, analysis, and documentation of commonality and differences within a domain. The feature oriented concept emphasis on findings the capabilities that are normally expected in applications in a given domain. The FODA domain model captures the similarities and differences among domain assets in terms of a set of related features. A feature is a distinctive aspect, quality, or characteristic of the domain asset. The features identified by the FODA method can be used to parameterize the system product line and Implementations of the domain assets. The features differentiating domain entities arise from differences in capabilities, operating environments, domain technology, implementation techniques, etc., i.e., a range of possible implementations within the domain. A specific implementation consists of a consistent set of feature values describing its capabilities. The feature diagram depicts the decomposition of features into sub-features in a hierarchical way. For each sub-feature below a certain feature it can be specified if it is compulsory, secondstringer or optional. The graphical notations introduced in are used here. We first briefly describe the representations used in illustrated in Figure \hyperref[fig_0]{1}. The compulsory feature is represented by being attached to an edge ending with a filled circle. So the feature F consists of both K1 and K2 in this case, and the feature instances here are \{F, K1, K2\}. The optional feature is( D D D D )\par
C represented by being attached to an edge ending with an unfilled circle. So the feature F may or may not contain K1. The optional feature instances here are \{F, K2\} and \{F, K1, K2\}. The second-stringer feature is represented by connecting edges with an arch. So the feature F consists of exactly one of its child features. The second-stringer feature instances here are \{F, K1\} and \{F, K2\}. Note that if K1 is optional while K2 is compulsory, then the second-stringer feature instances here are \{F\}, \{F, K1\} and \{F, K2\}, because the child feature instances derived from the K1 side contain an empty feature. The OR feature is represented by connecting edges with a filled arch. The OR feature instances here are \{F, K1\}, \{F, K2\} and \{F, K1, K2\}. If there is an optional child feature, then the OR representation is actually equivalent to the situation that all the child features are optional, i.e., the OR feature instances will be \{F\}, \{F, K1\}, \{F, K2\} and \{F, K1, K2\}. Through domain analysis, we find common and variant features of different account management systems, from different requirements: business requirement, user requirement, and functional requirement. Business requirement depicts business ability that the software system should have. User requirement depicts the interaction process between user and system, and this process may reflect the generally accepted business process in this domain. Functional requirement depicts functions that software system must have in order to realize the specific business requirements. Through domain analysis, we divide the service of account management domain into the following types: Account Drafting, Account Auditing, Account Implementation, Account Adjustment, Account Analysis, Account assessment. Among them, account assessment is optional features.\par
The second analysis is to identify functional features which the service has, analyze the specific functions which systems must have in order to complete special service. Taking account implementation control service as example, its functional layer includes compulsory features and optional features. And as   Optional features include data import. Compulsory features, namely common features, exist in each member system of the special domain, but optional features are one type of representation style of variant features, and only exist in parts of member system of the special domain. Optional features represents the variability which is relative to whole features, its introduction enables the feature model to respond the different system's diversity of domain, and makes the feature model to have better tailorability and expansibility.\par
The third Behavior characteristics layer analysis. The task of behavior characteristics layer analysis is to identify behavior characteristics what the function should be there, analyze behavior features of the early stages of functional implementation, such as preconditions of functional implementation, preparatory works; analyze the principal behavior characteristics of function part, find its outstanding features and its possible variability; analyze behavior features of the later period of function implementation, such as the postposition condition of functional implementation and the domination shift after the functional implementation. 
\section[{III. Account Management Domain with Architectural Design}]{III. Account Management Domain with Architectural Design}\par
Domain designing is the core architecture for a family of applications according to domain analysis model, namely a Domain-Specific Software Architecture (DSSA), and based on the DSSA, We can identify, develop and organize the reusable components. According to the requirements defined in the domain analysis stage, considering the actual development environment (such as operating system, database, communication mechanism, middleware, and so on, this paper designs Account Management domain architecture, This architecture uses the hierarchical architecture style. The hierarchical architecture style can avoid system component's coupling, protect and divide system function, improve maintainability, reusability and extendibility of software.\par
This domain architecture has five components: foundation component layer, atomic business component layer, foundation business component layer, general business component layer, industry application component layer.\par
(1) Industry application component:-This component is designed to satisfy special industry business requirements. It can be encapsulated by one or more atomic business components, or by one or more foundation business components, and even also can be combined by atomic business components, foundation business components and general business components.\par
(2) General business component: -This component is a subsystem level application component which is formed by encapsulates foundation business components or atomic business components, such as revenue budget components, investment budget components, capital budget components, cash flow budget components.  
\section[{General Business Component}]{General Business Component} 
\section[{Income budget}]{Income budget}\par
Capital budget Expense budget  
\section[{Cash flow budget}]{Cash flow budget} 
\section[{Foundation Business Component}]{Foundation Business Component} 
\section[{Sales revenue target element}]{Sales revenue target element} 
\section[{Period expense target Element}]{Period expense target Element} 
\section[{Business Component}]{Business Component} 
\section[{Accounts receivable target element}]{Accounts receivable target element} 
\section[{Atomic Business Component}]{Atomic Business Component} 
\section[{Implementation of Budget Management Domain}]{Implementation of Budget Management Domain}\par
In the part of domain design, we have putted required and harder structural DSSA and assigned the stable parts to the budget management domain system architecture and the variable parts to components. In the process of component implementation, we normally use OOP Object-Oriented Programming) for the simplifying the things and encapsulating the class. Aspect-oriented Programming (AOP) is a new programming technology which compensates the weakness of Object-Oriented Programming (OOP) for applying common behavior that spans multiple related object models. AOP introduces Aspect, it packages the behavior which impacts multiple classes into a reusable model, it allows programmers to model crosscutting concerns and eliminates the code tangling and scattering caused by OOP, the code is more readable and easier to maintain. The key to achieve AOP is to intercept normal method call. In order to complete some extra requirements, we will need to add extra features transparent "weaving" to these methods. Generally speaking, the weaving method includes two major types: Static weaving method and Dynamic weaving method. Static weaving method usually need to extend compiler's function, directly weave codes into the appropriate weaving point by modifying byte codes(Java) or IL code(.Net). Or, we need to add new syntax structure for original language to support AOP. As for dynamic weaving method, there are many specific implementation methods. In the Java platform, we can use Proxy pattern, or custom Class Loader to implement AOP features. Generally, at the .Net platform, the following methods can be used to achieve the dynamic weaving method: 1. Use Context Attribute and Context Bound Object to intercept the object methods. 2. Use Emit technology in the run-time to build new class which codes are woven into. 3. Use Proxy pattern V. 
\section[{Conclusion}]{Conclusion}\par
In this paper it is depicts the application of domain engineering in account management system development. Domain analysis method of FODA this paper has extended its feature oriented modeling method and design multi-layer framework according to the domain analysis result. At the domain implementation segment we applied a lightweight AOP framework with the name of SJAOP. This technology with the help of OOP separates crosscutting multi modules concerns in software, reduces the dependence between components effectively, and implements the system with a better performance of maintainability, extendibility and reusability.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
     		 		\backmatter  			 \par
Picture 2 : Architecture of Account Management System based on Component (3) Foundation business component: -On the basis of atomic business component, these components are able to complete certain business functions through aggregation of some atomic components. This type of component faces to application directly, such as sales revenue target components, period expense target components, business interface components.\par
(4) Atomic business component: -According to the decomposition business object, this is made by			 			  				\begin{bibitemlist}{1}
\bibitem[Qian-Xiang et al. ()]{b2}\label{b2} 	 		‘An Object-Oriented Method for Domain Engineering’.  		 			Wang Qian-Xiang 		,  		 			Wu Qiong 		,  		 			Li Ke-Qin 		,  		 			Yang Fuqing 		.  	 	 		\textit{Journal of Software}  		2002. 13  (10)  p. .  	 
\bibitem[Ke-Qin et al. ()]{b3}\label{b3} 	 		‘An outline of Domain Engineering’.  		 			Li Ke-Qin 		,  		 			Chen Zhao-Liang 		,  		 			Mei Hong 		,  		 			Yang Fuqing 		.  	 	 		\textit{Computer Science}  		1996. 26  (5)  p. .  	 
\bibitem[Kelly and Tolvanen ()]{b1}\label{b1} 	 		\textit{Domain-Specific Modeling : Enabling Full Code Generation},  		 			Steven Kelly 		,  		 			Juha-Pekka Tolvanen 		.  		2008. Wiley-Interscience.  	 
\bibitem[Fan et al. ()]{b4}\label{b4} 	 		‘Feature Modeling Method Oriented to Traffic Domain Component’.  		 			Wang Fan 		,  		 			Tan Guo-Zhen 		,  		 			Wang Hao 		.  	 	 		\textit{Computer Engineering}  		2009. 35  (1)  p. .  	 	 (He Qinlai) 
\bibitem[Hess et al. ()]{b0}\label{b0} 	 		\textit{Feature-Oriented Domain Analysis (FODA) Feasibility Study},  		 			James A Hess 		,  		 			William E Novak 		,  		 			A Spencer Peterson 		.  		2000.  		 			Carnegie Mellon Software Engineering Institute (SEI), USA 		 	 
\bibitem[Liu ()]{b5}\label{b5} 	 		‘Research on Enterprise Budget Management System Based On Domain Engineering’.  		 			Zhengmin Liu 		.  	 	 		\textit{International Journal of Digital Content Technology and its Applications}  		2011. 5  (9)  p. .  	 
\bibitem[Chen et al. ()]{b6}\label{b6} 	 		‘Towards a semantic anchoring infrastructure for domain-specific modeling languages’.  		 			Kai Chen 		,  		 			Janos Sztipanovits 		,  		 			Sandeep Neema 		.  	 	 		\textit{International Conference on Embedded Software},  				2005. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
