\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 Requirement Engineering Model during Reengineering},
 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-02-27 (revised: 27 February 2011)}
\def\TheID{\makeatother }
\def\TheDate{2011-02-27}
\title{Design of Requirement Engineering Model during Reengineering}
\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]{  VCE, rohtak, haryana, india}

\renewcommand\Authands{ and }

\date{\small \em Received: 17 January 2011 Accepted: 16 February 2011 Published: 27 February 2011}

\maketitle


\begin{abstract}
        


Requirement Engineering[1,2,3] is the most effective phase of software development. Its aims is to collect required requirement from stakeholders in the right way. It is very important of every organization to develop quality of software product, that can satisfy the users needs. It will focus number of viewpoints, roles, responsibility and objectives. Therefore it becomes necessary to apply requirement engineering in every phase of reengineering modules. Requirement engineering depends on customers request and planner knowledge. Requirement engineering model help in conceptual design and implementation design, also referred to as planning stage and implementation planning. Requirement engineering provides an incremental approach for reengineering. It concerned with the requirement elicitation, analysis, specification, validation and requirement management. Systematic requirements analysis is also known as requirements engineering. It is sometimes referred to loosely by names such as requirements gathering, requirements capture, or requirements specification.

\end{abstract}


\keywords{Reengineering, Requirement Engineering, Architectural Design, Review and Analysis}

\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
s we know that reengineering \hyperref[b3]{[4,}\hyperref[b4]{5,}\hyperref[b5]{6,}\hyperref[b6]{7]} is the revolution in software industry, it will reduces almost more than 60 percent cost as compared to maintenance of any software modules.\par
And we already know that maintenance is one of the critical activity of any software modules, but continue maintenance of software modules is not a good choice to increase the quality of the software. Because while continue maintenance takes place it will result increases the complexity of software modules.\par
Therefore, Reengineering is good choice than maintenance. The fundamental goal of reengineering was to minimize the impact of implementation expected system changes to the system. The purpose of this paper is to revisit the existing design methodology and develop a requirement engineering model, that will help to determine actual requirement of stakeholders before reengineering of software projects takes place. This data strongly suggests that, reengineering through new methodology significantly reduce full life cycle costs, schedules and risk. 
\section[{II.}]{II.} 
\section[{LITERATURE REVIEW}]{LITERATURE REVIEW}\par
The research is based on the process models found in \hyperref[b7]{[8,}\hyperref[b8]{9,}\hyperref[b9]{10,}\hyperref[b10]{11]} as these are the models that have been designed keeping in view the GSD context for streamlining the phase of RE. The process models given in sideline of any case study as in \hyperref[b11]{[12,}\hyperref[b12]{13]} are excluded because such processes are only for specific case study and situation. Moreover, the generic process models for RE that are not designed specifically for GSD(Global Software Deevelopment) context such as that proposed in \hyperref[b13]{[14]} have also been excluded because they are not suitable to this research In evolutionary model \hyperref[b7]{[8]} , requirements elicitation, requirements analysis and negotiation, requirements specification, and requirements validation are covered but this model addresses only few of the major GSD issues including a cultural issue which covers cultural diversity. Knowledge management issues cover knowledge sharing with users and knowledge acquisition techniques whereas technical issues over artifact sharing. Communication issues, time-zone difference, communication media and strategic issues are not covered in this model. Though this model is proposed to support the management of telecommunication network topologies but the reason for including this model is that it is documented process for DSD and is a good candidate for the GSD as well and can be applicable to other projects and domains as well.\par
In requirement traceability model \hyperref[b8]{[9]} , requirement traceability and requirements management are covered. Though this model does not cover all RE activities but the reason for including this model in this paper is that it can be very helpful in elicitation of correct requirements in GSD and the other reason for including this model is the level of importance attached to the requirements traceability and how this model can assist for better understanding of requirements in GSD A environment is also illustrated in this model. Requirement traceability helps in collecting rationale behind the requirements and this model also helps in indicating Value attached to the requirement. The GSD issues covered by this model are knowledge management, which includes knowledge sharing, and knowledge acquisition techniques. Technical issues (documentation sharing) and communication mode (asynchronous) are also covered. Other important issues like cultural issues, communication issues, strategic issues and time-zone difference are not addressed in this model.\par
In \hyperref[b9]{[10]} , though all activities of RE are not covered but major issues of GSD and three important activities of RE are covered. The other reason for including this process model is that it is documented process and it is in the context of GSD. The important RE activities which are covered by this model include requirements analysis and negotiation, requirements specification and requirements validation. This process model does not address the problems related to geographically distributed specification team. For example if some of the specification team members are in country A and some are in country B then, requirement speciation is quite a hectic tasks as team members at both sites need to validate SRS. This model address important GSD issues including cultural, technical, knowledge management and communication issues (poorly defined). 
\section[{'Requirement Engineering Model'}]{'Requirement Engineering Model'}\par
In the above model, there is four phase that play very crucial role during reengineering of software module before actual process takes place, because if we know each and every requirement of customers before actual process takes place then we can reduce overall complexity of module in later phase. The phases of requirement engineering model given below: 
\section[{Concept of formulation / Problem Understanding}]{Concept of formulation / Problem Understanding}\par
This phase generally proposed by people outside the system. E.g Senior manager in the organization, politician, chairman, or other member of the organization who want to get benefit directly or indirectly.\par
Here we will try to know, why reengineering takes place and the impact that the proposed concept is likely to have. This process should involves primarily domain experts rather than the system engineers. Although some system engineering input is essential. The above activity is iterative process\par
? all stakeholders involved are identified together with their goals (called win conditions); ? Conflicts between these goals are captured together with their associated risks and uncertainties; ? Goals are reconciled through negotiation to reach a mutually agreed set of goals, constraints, and alternatives for the next iteration. 
\section[{Requirement Engineering}]{Requirement Engineering}\par
Requirement engineering \hyperref[b0]{[1,}\hyperref[b1]{2,}\hyperref[b2]{3]} play very important role in identification of need:\par
? Identify need, want or desire  
\section[{Architectural Design}]{Architectural Design}\par
Evolve through a series of stages and each stages is evaluated, before proceeding to next stage Here one of very important activity takes place that to determine information need, determine different sources from where information will be obtained. 
\section[{Here two types of design takes place}]{Here two types of design takes place}\par
? Logical Design: is a more detail design, which includes all major components and entities plus their relationship. The data flow and connection are detailed in this stage ? Physical Design: has all major components and entities are identified within specific physical servers and location or specific software services, objects or solution, include all known detail such as OS, Ver. No. etc. 
\section[{Review and Analysis}]{Review and Analysis}\par
Review is one very important activity, in the requirement engineering model, it is essential to cross verification of functionality. Once anywhere requirement changes it is very important to review it according to change requirement.\par
Review and analysis is again a iterative process in the requirement engineering model, it help in  
\section[{Result \& Discussion}]{Result \& Discussion}\par
There is no doubt that requirement engineering is first activity of software development life cycle which play very important role in successes or failure of software projects, however there are some problem that we will face during requirement engineering during software development.\par
The purpose this paper is design requirement engineering model during reengineer that will solve the inconsistency of management for requirements engineering that will suffers these problems during software development:\par
? The specific kind of inconsistency being considered is not always clear. In fact, there is no common agreement on what a conflict between requirements does really mean. The lack of precise definition is a frequent source of confusion. Moreover, most techniques consider binary conflicts only, that is, conflicts among pairs of requirements. As we will see, there may be conflicts among three requirements, say, that are non conflicting pair wise.\par
? There is no systematic support for detecting conflicts among non operational specifications of goals or requirements-if one excepts theorem proving techniques for logically inconsistent specifications. Current conflict management techniques take it for granted that conflicts have been identified in some way or another. ? There is a lack of systematic techniques for resolving inconsistencies through goal/requirement transformations-one notable exception is \hyperref[b14]{[15]} , which proposes a set of operators for restructuring objects involved in conflicting goals. The above requirement engineering model solve above problem that we will face during software development, as well as it play important role during reengineering of module.\par
IV. 
\section[{Conclusion}]{Conclusion}\par
This model play very important role in reengineering, it not only reduces the risk to meet specification, but it also ensure to avoid immediately assuming you know what the problem and solution are, Going directly to try to solve the problem before thinking about it.\par
It provides systematic and organized approach that allows us to focus on achievable goal and to attain the best possible results from available resources. Therefore it will set the system objective, where reengineering takes place in the organization, so that management and employees agree to the objective and understand what they are in the organization.\par
This model play very important role in reengineering because it play very important part in testing of reengineered modules according to new requirement as well as existing functionality\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{figure2}}\end{figure}
 			\footnote{March 2011Design of Requirement Engineering Model during Reengineering ©2011 Global Journals Inc. (US)} 			\footnote{March 2011} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Robinson and Volkov (1997)]{b14}\label{b14} 	 		‘A Meta-Model for Restructuring Stakeholder Requirements’.  		 			W N Robinson 		,  		 			S Volkov 		.  	 	 		\textit{Proc. ICSE19-19th Int'l Conf. Software Eng},  				 (ICSE19-19th Int'l Conf. Software EngBoston)  		May 1997. p. .  	 
\bibitem[James and Markus ()]{b13}\label{b13} 	 		\textit{An operational model for structuring the requirements generation process},  		 			D A James 		,  		 			K G Markus 		.  		2004. Springer-Verlag London Limited. 10 p. .  	 
\bibitem[Hanish Jo et al. ()]{b11}\label{b11} 	 		‘Differentiating Local and Global Systems Requirements Gathering Processes in IS Software Development Projects’.  		 			C Hanish Jo 		,  		 			T Brian 		,  		 			Theerasak 		.  	 	 		PACIS Proceedings  		2005.  	 
\bibitem[Lopes et al. ()]{b9}\label{b9} 	 		‘Distributed Requirements Specification: Minimizing the Effect of Geographic Dispersion’.  		 			L Lopes 		,  		 			R Prikladnicki 		,  		 			J L N Audy 		,  		 			A Majdenbaum 		.  	 	 		\textit{Proc. ICEIS (3)},  				 (ICEIS (3))  		2004. p. .  	 
\bibitem[Maidantchik et al. ()]{b7}\label{b7} 	 		‘Learning organizational knowledge: an evolutionary proposal for requirements engineering’.  		 			C Maidantchik 		,  		 			M Montoni 		,  		 			G Santos 		.  	 	 		\textit{Proceedings of the 14th international conference on Software engineering and knowledge engineering},  				 (the 14th international conference on Software engineering and knowledge engineeringIschia, Italy)  		2002. p. .  	 
\bibitem[Davenport ()]{b6}\label{b6} 	 		‘Need radical innovation and continuous improvement? Integrate process reengineering and TQM’.  		 			T H Davenport 		.  	 	 		\textit{Planning Review}  		1993. 21  (3)  p. .  	 
\bibitem[Cook ()]{b4}\label{b4} 	 		\textit{Process Improvement: A Handbook for Managers},  		 			S Cook 		.  		1996. Hampshire, England: Gower Publishing.  	 
\bibitem[Damian and Zowghi ()]{b1}\label{b1} 	 		‘Requirements Engineering Challenges in Multi-Site Software Development Organizations’.  		 			D Damian 		,  		 			D Zowghi 		.  	 	 		\textit{Requirements Engineering Journal}  		2003. 8 p. .  	 
\bibitem[Jo and Brian (2007)]{b12}\label{b12} 	 		‘Requirements Engineering During Global Software Development: Some Impediments To The Requirement Engineering Process-A Case Study’.  		 			Hanisch Jo 		,  		 			C Brian 		.  	 	 		\textit{European Journal of Information Systems (ECIS)}  		Dec 2007. 16  (6)  p. .  	 
\bibitem[Damian ()]{b2}\label{b2} 	 		‘Requirements Engineering in Distributed Projects’.  		 			D Damian 		.  	 	 		\textit{International Conference on Global Software Engineering},  				2006.  	 
\bibitem[Heindl and Biffl ()]{b8}\label{b8} 	 		‘Risk Management with Enhanced Tracing of Requirements Rationale in Highly Distributed Projects’.  		 			M Heindl 		,  		 			S Biffl 		.  	 	 		\textit{International Conference on Software Engineering (ICSE)},  				 (Shanghai, China)  		2006. p. .  	 
\bibitem[Aranda et al. (2008)]{b10}\label{b10} 	 		‘Strategies to Minimize Problems in Global Requirements Elicitation’.  		 			G N Aranda 		,  		 			A Vizcaino 		,  		 			A Cechich 		,  		 			M Piattini 		.  	 	 		\textit{CLEI electronic journal}  		June 2008. 11  (1) .  	 
\bibitem[Espinosa and Carmel ()]{b0}\label{b0} 	 		‘The impact of time separation on coordination in global software teams: a conceptual foundation’.  		 			J A Espinosa 		,  		 			E Carmel 		.  	 	 		\textit{Software Process: Improvement and Practice},  				2003. Wiley InterScience. 8 p. .  	 
\bibitem[Davenport and Short ()]{b5}\label{b5} 	 		‘The New Industrial Engineering: Information Technology and Business Process Redesign’.  		 			H T Davenport 		,  		 			E J Short 		.  	 	 		\textit{Sloan Management Review}  		1990. 34  (4)  p. .  	 
\bibitem[Tenner and Detoro ()]{b3}\label{b3} 	 		\textit{The process redesign-the implementation guide for managers},  		 			A R Tenner 		,  		 			I J Detoro 		.  		1992. New Jersey: Prentice Hall.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
