\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={Design of Quality Model during Reengineering of Legacy 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{2011-04-22 (revised: 22 April 2011)}
\def\TheID{\makeatother }
\def\TheDate{2011-04-22}
\title{Design of Quality Model during Reengineering of Legacy 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. Anil  Kumar}

             \affil[1]{  Vaish College of Engineering}

\renewcommand\Authands{ and }

\date{\small \em Received: 15 March 2011 Accepted: 7 April 2011 Published: 22 April 2011}

\maketitle


\begin{abstract}
        


The purpose of this paper is design such kind of model that will improve the quality of system during reengineering[1] of legacy system that why this model is known as Quality Model. During reengineering of object oriented system[2,3], the methodology is design in such a way that will create a link/bridge between problem detection and problem correction in the legacy system, as well as simultaneously improvement in object oriented design, that can be used during later reengineering and also reduces the complexity as compared to object oriented design[4,5,6]. The further design of legacy system in such a way to specifying, how branches can be selected, how behavior is preserved and how code transformation applied. Quality of model, depends upon two factor favor and disfavor, attach to each branches, software quality is directly proportional to maintenance cost. Quality model is used for two purpose sketch and blueprint. Sketch is used a thinking tool, which help developer communicates, some aspects of a system and alternative about, what are about to be done. Blueprint intends to be comprehensive and definitive. It is used for guiding the implementation.

\end{abstract}


\keywords{Reengineering, obj ect oriented design, Q uality model, Problem detection, Re-factoring.}

\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[{Design of Quality Model during Reengineering of Legacy System}]{Design of Quality Model during Reengineering of Legacy System}\par
Dr Ashok Kumar ? , Anil Kumar ? Abstract-The purpose of this paper is design such kind of model that will improve the quality of system during reengineering [1] of legacy system that why this model is known as Quality Model.\par
During reengineering of object oriented system [2,3], the methodology is design in such a way that will create a link/bridge between problem detection and problem correction in the legacy system, as well as simultaneously improvement in object oriented design, that can be used during later reengineering and also reduces the complexity as compared to object oriented design [4,5,6].\par
The further design of legacy system in such a way to specifying, how branches can be selected, how behavior is preserved and how code transformation applied. Quality of model, depends upon two factor favor and disfavor, attach to each branches, software quality is directly proportional to maintenance cost. Quality model is used for two purpose sketch and blueprint. Sketch is used a thinking tool, which help developer communicates, some aspects of a system and alternative about, what are about to be done. Blueprint intends to be comprehensive and definitive. It is used for guiding the implementation.\par
Keywords: Reengineering, object oriented design, quality model, Problem detection, Re-factoring.\par
I. 
\section[{Problem Statement}]{Problem Statement}\par
here is no doubt, that OO design [4,5,6] is one of the best choice of designer, to design any software modules, however, is universal truth, that while we restructure [7] any system it is always acceptable, it will improve its efficiency, productivity, scalability and reduces the complexity as well as reduces the resources that are required during development of development of software modules.\par
Therefore, restructure is part of reengineering of OO design, that help transformation of a software system, without modifying its behavior that will improve its structure of the system. A common path during reengineering of OO design is to identify fragments in the subject system's design that violet principle of good design and then try to restructure the system in such a way, that minimizes these violations. Currently there is no. of approaches that can help developer and designer to identify design flows on one side and that can perform various code transformation safely on other side. While reengineering takes place on legacy system, where OO approaches are used to build a system, developer obtain a list of design flows together with their location in the system, but the necessary transformation that remove them are left to their own judgment and experience. The mapping between a specific design flow and the code transformation to remove it, together with the consequence of choosing one set of transformation over the other, is missing. Still, there is no satisfactory approach that links between the two, guiding the developer from problem detection to code transformation, that can remove the identified problem. Therefore, improvement of OO design are required. 
\section[{II.}]{II.} 
\section[{Introduction}]{Introduction}\par
The life of software products extends far beyond the development of first release. After being developed to the customer, a software product enter the most extended stage of its life: evolution. Software maintenance [8] is concerned with the changes, that need to be made on an existing product: defect are removed. As we know that, software evolution is a reality with various reason and consequence. As software system evolve, their structure degrades a phenomena know as software decay.\par
Developer who makes the changes are not same as the one who developed the initial system. For a large system it is difficult to understand the concept of initial designer had in mind, so changes are made that changes the initial concept.\par
Future changes are need to take into account, the new concept and execution introduced by previous changes. This leads to system very difficult to update and understand, the changes introduces more bugs and documentation became increasingly inaccurate. Maintaining these system become nightmare and the maintenance cost increase very much. Therefore, reengineering is the best choice for this purpose. During reengineering process certain phases can be identified. The one that bears restructure of OO system, where subject system is modified in order to improve its structure without affecting its functionality.\par
In other words, restructure process aims to improve the quality of existing system, in order to T 
\section[{Global Journal of Computer Science and Technology}]{Global Journal of Computer Science and Technology}\par
Volume XI Issue VIII Version I 2011 facilitate the later reengineering task. Restructuring is often used as a form of preventive maintenance to improve the physical state of the subject system with respect to certain standard. The steps that will be followed by restructuring of OO system are:\par
? Do a survey of existing work on problem detection and re-factoring and attempts to provide a link between two. ? Select a no. of design flow that are the subject of further investigation ? Describe the way to remove such design flows from OO system ? Define methodologies for the design improvement using correction strategies\par
? Implement an infrastructure that allows the easy implementation of correction strategies. The quality model is based on design pattern \hyperref[b8]{[9]} , that will improve the legacy system, during design phase, rather than code. This model is help to determining:\par
? Language independence: approach should operate at design level, rather than programming language level. This way, it should be applicable to the system written in any programming language, that should support OO paradigm \hyperref[b9]{[10]} ? Behavior preservation: any approach should give a minimum degree of confidence that the modified system will behave the same as before ? Automation: most legacy system are very large as well as very complex. Therefore, this approach should allow for large degree of automation and should minimizes human intervention during the process ? Quality estimation ? Extensibility easy to accommodate, new knowledge\par
? Causality: this approach should directly detect any risk at design flows. Reengineering life cycle \hyperref[b10]{[11,}\hyperref[b11]{12,}\hyperref[b12]{13]} contain problem detection phase, when design flows are modified. Each pattern describe a problem, which occurs over and over again in one environment and the describe the core of the solution to that problem, in such a way that you can use this solution a million of times over, without ever doing it, the same way twice. Design pattern, is the description of communicating objects and classes, that are customized to solve a general design problem in a particular context. Here, we do not inspect all area of reengineering, but focus on two phases that aim to link: problem detection and re-factoring. 
\section[{III.}]{III.} 
\section[{Problem Detection}]{Problem Detection}\par
Problem detection is a specific phase in the reengineering lifecycle. Its process aims to identify design flows in the analyzed system. It has a series of steps -first formalization, which takes OO design heuristics, rules, principle and turns them into precise rules and that can be used to identify design flows. The source code is parsed and a model of the system is obtained. It will support the assessment and improvement of the quality in OO system . the problem detection strategies on the model's entities that is packages, classes, methods, attributes, local variables, global variables and parameters. 
\section[{Re-Factoring}]{Re-Factoring}\par
Re-factoring \hyperref[b13]{[14]} is the process of changing a software system, in such a way that it does not alter its external behaviors, but still improves its internal structure. The framework are reusable architecture , they are the result of many iterations and no. of way limited to OO framework \hyperref[b14]{[15,}\hyperref[b15]{16,}\hyperref[b16]{17,}\hyperref[b17]{18]} and more recent software development process, suggest, refactoring should be part of development cycle. Re-factoring OO System \hyperref[b9]{[10]} :\par
? Defining an abstract super class of one or more existing classes The further design of legacy system, in such a way to specifying, how branches can be selected, how behaviors is preserved and how code transformation applied. Here, problem detection model, are used to choose the appropriate branches in each decision node and safely applying code transformation. By applying this, finding a path through graph strategies. Depending on the system and reengineering goals, different path can be chosen for the same design flow.\par
Reengineering process, start with requirement analysis, which establish the overall reengineering goals. Reengineering goal provides the focus of all activities carried out, during the process of reengineering. These goal can be expressed in terms of quality factors, that need improvement: flexibility, portability, efficiency etc.. At each decision node, the available branches can be selected according to their impact on each of the considered quality factors. 
\section[{System}]{System}\par
Packages Class 
\section[{Methods Attributes}]{Methods Attributes}\par
Statements\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}q}\end{figure}
 			\footnote{May©2011 Global Journals Inc. (US)} 			\footnote{May©2011 Global Journals Inc. (US)} 			\footnote{May©2011 Global Journals Inc. (US)} 			\footnote{May©2011 Global Journals Inc. (US)} 			\footnote{May©2011 Global Journals Inc. (US)} 			\footnote{May©2011 Global Journals Inc. (US)} 		 		\backmatter  			 
\subsection[{Conciseness}]{Conciseness} 
\subsection[{Structured Ness}]{Structured Ness}\par
Device Independence Legibility Self Description Completeness			 			  				\begin{bibitemlist}{1}
\bibitem[ Object Modeling and Design Strategies by Sanjiv Gossain, Ian S. Graham -SIGS Books & Multimedia]{b9}\label{b9} 	 		\textit{},  	 	 		\textit{Object Modeling and Design Strategies by Sanjiv Gossain, Ian S. Graham -SIGS Books \& Multimedia}  		ISBN p. 052164822X.  	 
\bibitem[A Theory of Object-Oriented Design: The building-blocks of OOD and notations for representing them]{b3}\label{b3} 	 		\textit{A Theory of Object-Oriented Design: The building-blocks of OOD and notations for representing them},  		 	 	 (with focus on design patterns) 
\bibitem[Fowler ()]{b4}\label{b4} 	 		\textit{Analysis Patterns: Reusable Object Models},  		 			Martin Fowler 		.  		1997. Addison-Wesley.  	 	 (An introduction to object-oriented analysis with conceptual models) 
\bibitem[Booch ()]{b1}\label{b1} 	 		 			Grady Booch 		.  		 \url{http://www.informit.com/store/product.aspx?isbn=020189551X}  		\textit{Object-oriented Analysis and Design with Applications},  				2007. Addison-Wesley.  	 	 (3rd edition) 
\bibitem[Muthu et al. (1999)]{b0}\label{b0} 	 		‘Business process reengineering: a consolidated methodology’.  		 			S Muthu 		,  		 			L Whitman 		,  		 			H S Cheraghi 		.  	 	 		\textit{Proceedings of the 4th Annual International Conference on Industrial Engineering Theory, Applications and Practice},  				 (the 4th Annual International Conference on Industrial Engineering Theory, Applications and Practice)  		1999. Retrieved October 19, 2007.  	 
\bibitem[Tonella (2001)]{b6}\label{b6} 	 		‘Concept Analysis for Module Restructuring’.  		 			Paolo Tonella 		.  	 	 		\textit{IEEE Transactions on Software Engineering}  		April 2001. 27  (4)  p. .  	 
\bibitem[Davenport ()]{b11}\label{b11} 	 		 			Thomas Davenport 		.  		\textit{Process Innovation: Reengineering work through information technology},  				 (ess Innovation: Reengineering work through information technologyBoston)  		1993. Harvard Business School Press.  	 
\bibitem[Bosch (ed.) ()]{b15}\label{b15} 	 		\textit{Design of an object-oriented framework for measurement systems. Object-Oriented Application Frameworks},  		 			J Bosch 		.  		Fayad ME, Schmidt DC, Johnson RE (ed.)  		1999. Wiley \& Sons.  	 
\bibitem[Wirfs-Brock et al. ()]{b2}\label{b2} 	 		\textit{Designing Object Oriented Software},  		 			Rebecca Wirfs-Brock 		,  		 			Brian Wilkerson 		,  		 			Lauren Wiener 		.  		1990. Prentice Hall.  	 
\bibitem[Mattsson and Bosch (1997)]{b16}\label{b16} 	 		‘Framework composition problems, causes and solutions’.  		 			M Mattsson 		,  		 			J Bosch 		.  	 	 		\textit{Proceedings Technology of Object-Oriented Languages and Systems},  				 (Technology of Object-Oriented Languages and SystemsU.S.A.)  		August 1997.  	 
\bibitem[Wilde and Huitt (1992)]{b7}\label{b7} 	 		‘Maintenance Support for Object-Oriented Programs’.  		 			Norman Wilde 		,  		 			Ross Huitt 		.  		 SE- 18.  	 	 		\textit{IEEE Transactions on Software Engineering}  		December 1992.  (12)  p. .  	 
\bibitem[Tonella and Antoniol (1999)]{b8}\label{b8} 	 		‘Object Oriented Design Pattern Inference’.  		 			Paolo Tonella 		,  		 			Giuliano Antoniol 		.  	 	 		\textit{Proceedings of ICSM '99 (International Conference on Software Maintenance)},  				 (ICSM '99 (International Conference on Software Maintenance))  		October 1999. IEEE Computer Society Press. p. .  	 
\bibitem[Bosch et al. (ed.)]{b14}\label{b14} 	 		\textit{Object oriented frameworks-problems and experiences. Building Application Frameworks},  		 			J Bosch 		,  		 			P Molin 		,  		 			M Mattson 		,  		 			P Bengtsson 		.  		Fayad ME, Schmidt DC, Johnson RE (ed.)  		 	 
\bibitem[Mattsson ()]{b17}\label{b17} 	 		\textit{Object-oriented frameworks survey of methodological issues},  		 			M Mattsson 		.  		1996.  		 			Department of Computer Science, Lund University 		 	 	 (Licentiate Thesis) 
\bibitem[Meyer ()]{b5}\label{b5} 	 		\textit{Object-oriented software construction},  		 			Bertrand Meyer 		.  		1997. Prentice Hall.  	 
\bibitem[Davenport (1995)]{b12}\label{b12} 	 		\textit{Reengineering -The Fad That Forgot People, Fast Company},  		 			Thomas Davenport 		.  		1995. November 1995.  	 
\bibitem[Fowler ()]{b13}\label{b13} 	 		\textit{Refactoring: Improving the Design of Existing Code},  		 			Martin Fowler 		.  		1999. Addison Wesley.  	 
\bibitem[Davenport and Short ()]{b10}\label{b10} 	 		\textit{The New Industrial Engineering: Information Technology and Business Process Redesign},  		 			Thomas \& Davenport 		,  		 			J Short 		.  		1990. 1990. Summer: Sloan Management Review. p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
