\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={Requirement Elicitation Model (REM) in the Context of Global Software Development},
 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{2018 2018-01-15 (revised: 37 Year 2018 15 January 2018)}
\def\TheID{\makeatother }
\def\TheDate{2018 2018-01-15}
\title{Requirement Elicitation Model (REM) in the Context of Global Software Development}
\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]{Muhammad  Yaseen}

             \author[2]{Umar  Farooq}

             \affil[1]{  }

\renewcommand\Authands{ and }

\date{\small \em Received: 15 December 2017 Accepted: 5 January 2018 Published: 15 January 2018}

\maketitle


\begin{abstract}
        


Contxext:  Requirement elicitation is difficult and critical phase of requirement engineering and the case is worst in global software development (GSD). The study is about requirement elicitation in the context of GSD.  Objective:  Development of requirement elicitation model (REM) which can address the factors that have positive impact and the factors that have negative impact during elicitation in GSD. The propose model will  give solutions and practices to the challenges during elicitation.  Method:  Systematic literature review (SLR) and empirical research study will be used for achieving the goals and objectives.  Expected Outcomes:  The expected results of this study will be REM that will help vendor organizations for better elicitation during GSD

\end{abstract}


\keywords{systematic literature review, requirement engineering, global software development, requirement elicitation model.}

\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
equirement engineering (RE) is the systematic and discipline way of collecting user requirements for a software system and to manage it \hyperref[b0]{[1,}\hyperref[b2]{2]}. The purpose of RE process is satisfaction of user needs and what customer wants from a software product \hyperref[b2]{[2]}\hyperref[b3]{[3]}\hyperref[b4]{[4]}\hyperref[b5]{[5]}.Requirement elicitation is the first phase of RE during software development life cycle \hyperref[b6]{[6]}. During elicitation phase we do direct communication with users or customers and gather requirements by applying various elicitation techniques. The quality of software system is more depended on the quality of how better the requirements are gathered \hyperref[b0]{[1,}\hyperref[b7]{7]}. RE is very difficult when we do it locally but the case very difficult when the development is done globally where clients and vendors are separated by distance and face challenges like culture issues, time zone difference and difference in languages and terminologies. Due to extra challenges in GSD proper elicitation process is affected \hyperref[b8]{[8,}\hyperref[b9]{9]}. 
\section[{II.}]{II.} 
\section[{Motivation and Related Work}]{Motivation and Related Work}\par
Miguel Romero \hyperref[b10]{[10]}discuss that culture and time differences are big challenges in GSD. For reducing the effect of challenges it is necessary for people to share knowledge about requirements and have a proper knowledge management system. The author describes relevant skills for elicitation in GSD are; English language skills, understanding of cultures of others, computer mediated communication skills, use of proper communication protocols, ability to resolve conflicts and teamwork skills are needed for effective elicitation.\par
Nosheen Sabahat \hyperref[b6]{[6]} after doing survey and interviews explains the effectiveness of elicitation techniques. She concluded that in GSD the most effective elicitation techniques are prototyping, scenarios and interview. The prototype is considered to be the best technique in GSD because prototypes represents product earlier and customers are more satisfied. Scenarios are best in case where prototypes are difficult to make. Questionnaires and other traditional techniques are not suitable in GSD. The author propose iterative model where elicitation and analysis works iteratively at same time.\par
Bin Wen \hyperref[b11]{[11]} discuss that traditional elicitation techniques are not enough to apply in GSD during collecting of requirements, collaborative techniques like social intelligent for networked software and semantic web technology should be selected during elicitation.\par
Gabriela N. Aranda \hyperref[b12]{[12]}in his paper suggests the strategies to overcome the challenges like lack of face to face meetings and culture issues in GSD. Culture differences cannot be ignored but stakeholders can learn about these differences and training is the best solution for that. The author has explained in detail about the trainings and its strategies. Use of ontologies is suggested as best way to reduce language differences. Using ontologies can clarify the structure of knowledge and as well as reduce conceptual and terminological confusion. Technology selection must be discussed in team while doing elicitation because technology selection process is carried out by studying and confronting the personal preferences of people who need to work together.\par
Fabio Calefato \hyperref[b13]{[13]} discuss that as face to face communication during elicitation in GSD is difficult but still it is possible to have systems and technologies that can be alternative to face to face communication. After empirical studies the author design computer mediated tool for synchronous text solution in case where face to face communication is difficult. The tool contains audio and video conferencing facility. The tool was further evaluated through case study using students.\par
Neetu Kumari. S \hyperref[b3]{[3]} proposes the model which will address the issues with elicitation in GSD but the levels of this model are not defined. The model is limited to find the challenges only not the solutions. The characteristics of model are not explained. Further the methodology of collecting data from literature is not systematic so we need advance model which can address the challenges, critical success factors and the solutions for problems and challenges. 
\section[{III.}]{III.} 
\section[{Objectives}]{Objectives}\par
The objective of this research study is to develop REM in order to support vendor organizations in better elicitation of requirements in the context of GSD. This model will address challenges and success factors during requirement elicitation. The propose will address the solutions and practices needed to better implement success factors during elicitation and to reduce the effect of the challenges. For achieving the objectives, we will do the SLR and empirical study to find factors that are important during elicitation of requirements in GSD. For the implementation of factors, practices and solutions will be extracted through SLR and then questionnaire survey will be conducted to validate success factors, challenges and practices. Survey will be conducted in software industry to mention some new practices not mentioned in literature before. After finding the practices and solutions the propose model will be developed. The aim is to reduce the gap between researchers and software development vendors. Other researchers also adopted the same methodology in other fields to suggest such models \hyperref[b14]{[14]}.\par
IV. 
\section[{Research Questions}]{Research Questions}\par
The work reported in this paper is based on the five research questions which have posted in the following way: RQ1: What are the factors as identified from literature that have positive impact during requirement elicitation phase of RE in the context of GSD? RQ2: What are the factors in real practice that have positive impact during requirement elicitation phase of RE in the context of GSD? RQ3: What are the factors and challenges as identified from literature that have negative impact during requirement elicitation phase of RE in the context of GSD? RQ4: What are the factors in real practice that have negative impact during requirement elicitation phase of RE in the context of GSD? RQ5: Are there differences between the factors identified through the literature and the real-world practice? RQ6: Is the REM practically successful in terms of finding and alleviate implementation factors and challenges faced by vendor organizations during elicitation in GSD?\par
Through SLR, RQ1 and RQ3 will be address i.e. studying what factors (CSFs and Cs) have already been reported in the literature. In future in order to facilitate vendors in implementing factors important for success of requirement elicitation, we will program/code the REM in the form of software. Moreover for overcoming challenges faced by vendor organizations in GSD the REM will suggest solutions. This tool will produce different assessment reports and do different activities for the software vendor organizations.\par
V. 
\section[{Design of REM and Research Methodology}]{Design of REM and Research Methodology}\par
The methodology of the REM consists of the following three phases. Phase\#1: SLR will be conducted for data collection. Phase\#2: Empirical study will be conducted to validate the result of SLR and to find the practices for the mentioned factors. Phase\#3: For evaluation and validation of REM, Case study will be conducted. To explain the aforesaid three phases the following subsections are added. 
\section[{a) Collection of data and its analysis}]{a) Collection of data and its analysis}\par
i. CSFs (critical success factors): Factors that have a positive impact during requirement elicitation in GSD. ii. CRs (critical Risks): Factors that have a negative impact during requirement elicitation in GSD. iii. Practices: For implementing CSFs, practices will be extracted and used. SLR will be used to identify factors (CSFs and Cs). Through SLR we will extract, analyse and will explore data relevant to our research questions. SLR is different from ordinary literature reviews being formally planned and more systematic. According to Kitchenham \hyperref[b15]{[15]} SLR is divided into 3 phases. First phase is planning the review, second is conducting the review and implementation is the last phase. Before conducting SLR a protocol will be designed which include all the steps needed for SLR. From research questions a search string will be constructed for different libraries accordingly. Search procedure and plan will be defined and then protocol will be executed. After execution, inclusion and exclusion criteria will be define to tell which paper to include in final list. 
\section[{Figure 1: REM Development Cycle Activities}]{Figure 1: REM Development Cycle Activities}\par
To successfully implement factors (CSFs and Cs), a questionnaire survey will be conducted with experts working in the software industry. The purpose of this survey is:\par
? Validation of the results of SLR.\par
? To find new factors (CSFs and which are not previously identified. ? To identify practices for the success implementation of (CSFs and Cs).\par
After REM is successfully design then for evaluation in real world environment case studies will be conducted in software industry. 
\section[{b) Development of REM}]{b) Development of REM}\par
For the design of REM we have used the five stages as shown in Figure 2. A similar approach also been used another researcher \hyperref[b16]{[16,}\hyperref[b17]{17]}.\par
The development of REM is the first stage; it is used to set criteria for REM success. The below mentioned two criteria will be used for the development and assessment of REM. A. User satisfaction: This criteria focus on the satisfaction of end user from the result of REM. He/ She should be able to use the REM without any confusion or ambiguity to promote objectives according to their requirements and assumptions. B. Usability: This criteria emphasis on the structure easiness of the REM. It states that the structure of the REM should be flexible and easy to understand because organizations do not accept complex models and standards which require resources, training and effort. Data collection and analysis is the stage 2. Rationalization and structuring of results will be performed in stage 3. Development of REM based on the results of empirical studies in stage4. Evaluation and validation of the REM via case studies will be performed in final stage i.e. stage 5.\par
Planned structure of the REM is shown in Figure 3. Relationship between REM levels is also shown, factors/risks and practices used to address risks and success implementation of RE process. 
\section[{c) REM structure}]{c) REM structure}\par
We will build the structure of the REM on the bases of following three extensions.\par
? REM levels ? Factors (CSFs, Cs) in each level ? Practices and solutions for the implementation of factors Classification of CSFs and Cs in different categories will be the base for defining the levels of REM. Each level will be consisting of different factors (CSFs and Cs). For each factor in the particular level, practices will be given for its proper implementation. Like CMMI and other models, for organizations to achieve certain level they must address and should follow the practices for each CSFs and Cs under that particular level.  REM will be validated through industrial case studies. For case studies maximum of five organizations will be enough. Case study is the best tool for evaluating any model in real environment. A focus group session will be arranged to get feedback from the participant about REM. The criteria will be ease of use and user satisfaction as discussed in section 5.  
\section[{REM}]{REM} 
\section[{Conclusion and Future Work}]{Conclusion and Future Work}\par
In our paper we have presented the structure of REM with different levels and phases. We have discussed how this model will help vendors in better implementation of success factors during elicitation in GSD. Detail methodology for the development of REM was introduced. This model will be used as tool for software developers and will produce different assessment reports in different situations.  \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.8416256157635468\textwidth}P{0.008374384236453201\textwidth}}
\multicolumn{2}{l}{Requirement Elicitation Model (REM) in the Context of Global Software Development}\\
Year 2018\tabcellsep \\
40\tabcellsep \\
Volume XVIII Issue II Version I\tabcellsep 7.\\
( ) C\tabcellsep \\
Global Journal of Computer Science and Technology\tabcellsep \\
© 2018 Global Journals 1\tabcellsep \end{longtable} \par
  {\small\itshape [Note: VII.]} 
\caption{\label{tab_0}Literature review Supervisor inputs SLR and Survey Empirical studies Empirical Studies Literature review of Different models Case studies Specify criteria for REM development Data collection and analysis Rationalization and structuring of results Development of REM Evaluation of results via case study Existing Models (CMMI, SOVRM and SOPM) and supervisor input RESEARCH QUESTIONS Critical Success Factors and Critical Risks during Requirement elicitation in context of GSD REM LEVELS SLR AND EMPIRICAL STUDY REM Guidelines for GSD vendors Practices: How to implement Critical Success Factors and address Critical Risk in context of GSD}\end{figure}
 			\footnote{© 2018 Global JournalsRequirement Elicitation Model (REM) in the Context of Global Software Development} 		 		\backmatter   			 
\subsection[{Acknowledgment}]{Acknowledgment}\par
We are thankful to all members of the Software Engineering Research Group (SERG-UOM) at University of Malakand for their constructive reviews and also thankful to the anonymous reviewers of the conference. 			  			  				\begin{bibitemlist}{1}
\bibitem[Kumari and Pillai ()]{b3}\label{b3} 	 		‘A survey on global requirements elicitation issues and proposed research framework’.  		 			S 		,  		 			Neetu Kumari 		,  		 			A S Pillai 		.  	 	 		\textit{4th IEEE International Conference on},  				2013. 2013.  	 	 (presented at Software Engineering and Service Science (ICSESS) 
\bibitem[Pandey et al. ()]{b0}\label{b0} 	 		‘An effective requirement engineering process model for software development and requirements management’.  		 			U Pandey 		,  		 			A Suman 		,  		 			Ramani 		.  	 	 		\textit{Advances in Recent Technologies in Communication and Computing (ARTCom)},  				2010.  	 
\bibitem[Sabahat et al. ()]{b6}\label{b6} 	 		‘An iterative approach for global requirements elicitation: A case study analysis’.  		 			N Sabahat 		,  		 			F Iqbal 		,  		 			F Azam 		,  		 			M Y Javed 		.  	 	 		\textit{2010 International Conference On},  				2010.  	 	 (presented at Electronics and Information Engineering (ICEIE) 
\bibitem[Calefato et al. ()]{b13}\label{b13} 	 		‘Computermediated communication to support distributed requirements elicitations and negotiations tasks’.  		 			F Calefato 		,  		 			D Damian 		,  		 			F Lanubile 		.  	 	 		\textit{Empirical Software Engineering}  		2012. 17 p. .  	 
\bibitem[Yaseen et al. ()]{b8}\label{b8} 	 		‘Critical challenges for requirement implementation in context of global software development: A systematic literature review’.  		 			M Yaseen 		,  		 			S Baseer 		,  		 			S Sherin 		.  	 	 		\textit{2015 International Conference on Open Source Systems \& Technologies (ICOSST)},  				2015.  	 
\bibitem[Wen et al. ()]{b11}\label{b11} 	 		‘Distributed and Collaborative Requirements Elicitation based on Social Intelligence’.  		 			B Wen 		,  		 			Z Luo 		,  		 			P Liang 		.  	 	 		\textit{presented at Web Information Systems and Applications Conference (WISA)},  				2012 Ninth, 2012.  	 
\bibitem[Arthi ()]{b5}\label{b5} 	 		‘Distributed Requirements Negotiations Using Mixed Media’.  		 			B Arthi 		.  	 	 		\textit{Intâ??l Journal of Eng. and Technol}  		2009. 1.  	 
\bibitem[Lloyd et al. ()]{b2}\label{b2} 	 		‘Effectiveness of elicitation techniques in distributed requirements engineering’.  		 			W J Lloyd 		,  		 			M B Rosson 		,  		 			J D Arthur 		.  	 	 		\textit{Proceedings. IEEE Joint International Conference on},  				 (IEEE Joint International Conference on)  		2002. 2002.  	 	 (presented at Requirements Engineering) 
\bibitem[Kitchenham and Charters ()]{b15}\label{b15} 	 		\textit{Guidelines for performing Systematic Literature Reviews in Software Engineering},  		 			B Kitchenham 		,  		 			C Charters 		.  		 EBSE 2007-001.  		2007.  		 			Keele University and Durham University Joint 		 	 	 (Report) 
\bibitem[Kauppinen et al. ()]{b4}\label{b4} 	 		‘Implementing requirements engineering processes throughout organizations: success factors and challenges’.  		 			M Kauppinen 		,  		 			J Vartiainen 		,  		 			S Kontio 		,  		 			R Kujala 		,  		 			Sulonen 		.  	 	 		\textit{Information and Software Technology}  		2004. 46 p. .  	 
\bibitem[International Conference on ()]{b1}\label{b1} 	 		\textit{International Conference on},  				2010.  	 
\bibitem[Yaseen et al.]{b17}\label{b17} 	 		\textit{Requirement Implementation Model (RIM) in the Context of Global Software Development},  		 			M Yaseen 		,  		 			S Baseer 		,  		 			S Ali 		,  		 			S U Khan 		.  		 	 
\bibitem[Ahmad et al. ()]{b7}\label{b7} 	 		‘Requirements prioritization with respect to Geographically Distributed Stakeholders’.  		 			A Ahmad 		,  		 			A Shahzad 		,  		 			V K Padmanabhuni 		,  		 			A Mansoor 		,  		 			S Joseph 		,  		 			Z Arshad 		.  	 	 		\textit{2011 IEEE International Conference on},  				2011.  	 	 (presented at Computer Science and Automation Engineering (CSAE) 
\bibitem[Ali and Khan ()]{b16}\label{b16} 	 		‘Software Outsourcing Partnership (SOP): A Systematic Literature Review Protocol with Preliminary Results’.  		 			S Ali 		,  		 			S U Khan 		.  	 	 		\textit{International Journal of Hybrid Information Technology}  		2014. 7 p. .  	 
\bibitem[Ali and Khan ()]{b14}\label{b14} 	 		‘SOFTWARE OUTSOURCING PARTNERSHIP MODEL’.  		 			S Ali 		,  		 			S U Khan 		.  	 	 		\textit{Science International}  		2014. 26.  	 
\bibitem[Aranda et al. ()]{b12}\label{b12} 	 		‘Strategies to minimize problems in global requirements elicitation’.  		 			G N Aranda 		,  		 			A Vizcaãno 		,  		 			A Cechich 		,  		 			M Piattini 		.  	 	 		\textit{CLEI electronic journal}  		2008. 11.  	 
\bibitem[Romero et al. ()]{b10}\label{b10} 	 		‘Teaching requirements elicitation within the context of global software development’.  		 			M Romero 		,  		 			A Vizcaãno 		,  		 			M Piattini 		.  	 	 		\textit{Mexican International Conference on},  				2009. 2009.  	 	 (presented at Computer Science (ENC)) 
\bibitem[Illes-Seifert et al. ()]{b9}\label{b9} 	 		\textit{The Challenges of Distributed Software Engineering and Requirements Engineering: Results of an Online Survey},  		 			T Illes-Seifert 		,  		 			A Herrmann 		,  		 			M Geisser 		,  		 			T Hildenbrand 		.  		2007.  	 	 (presented at WORKSHOP P) 
\end{bibitemlist}
 			 		 	 
\end{document}
