\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={Software Engineering: Factors Affect on Requirement Prioritization},
 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{Software Engineering: Factors Affect on Requirement Prioritization}
\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. Shams Ul  Hassan}

             \author[2]{Salman Afsar  Awan}

             \affil[1]{  University of Agriculture, Faisalabad, Pakistan.}

\renewcommand\Authands{ and }

\date{\small \em Received: 13 December 2011 Accepted: 1 January 2012 Published: 15 January 2012}

\maketitle


\begin{abstract}
        


Software engineering research is yet in its early stages hence it needs evaluation. So, software engineers think about experimental research and try to adopt analytical approaches to validate results like in other sciences. It should be asserting that requirement engineering process is to use requirements prioritization. The use of requirements prioritization helps the anatomy of requirements and isolates the most important requirements. A lot of prioritization techniques, practices and methodologies are used in software requirements. But lack of empirical search program and proficient methodology, was not decide which should be implemented. In this research, the requirement prioritization for systematical reviews was carried out. Based on systematic review, a framework is introduced for further research within requirement prioritization. This paper described a framework for scrutinize the discussion that take place during requirements elicitation and requirements prioritization. The survey presented in the paper gives a practical view how to prioritize the requirements. It also reflects the requirements prioritization in the industries needs. Which factors of the requirements engineering affect the requirements prioritization.

\end{abstract}


\keywords{framework, requirements prioritization, software engineering, requirement engineering, systematic review.}

\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
he term requirement may be defined as demand or need. In the world of the software engineering, a requirement is a explanation of what the purposed system should do or perform. A system may have a lot of requirements. Software requirements demand what must be accomplished, shaped or provided. Requirement elicitation is all about knowing the desires of stakeholders. \hyperref[b0]{[1]} The term requirement has been used in the software engineering society since 1960. The requirements provide a firm basis for the success of the project and delivery of the product. The requirements often shrink the gap between software team and end users. Requirement phase begin at the analysis phase.\par
Requirements managed throughout the project life cycle. So requirements are the report of the services that a system must perform and operate under some constraints.\par
Author ? : University of Agriculture (Computer Science Department), Faisalabad, 38000, Pakistan. E-mails : shams219gb@hotmail.com, ? salmanafsar@hotmail.com Requirement Engineering (RE) is worried about the naming of the goals, achieved by the imagine system. Most difficult and critical to be achieve the better quality of the requirement. Incomplete, inconsistent and ambiguous requirements have the most serious impact on the required software. If requirement errors correction perform late the cost raise up to 200 times as compared the requirement errors correction perform in time. Requirement Engineering deals with a wide range of business domains and tasks like decision, administrative support. \hyperref[b1]{[2]} Even though the considerable Requirement Engineering (RE) explore and research attempts over the many past years but the gap between the industry and research still hang about constantly. Now Requirement Engineering research society tries to address these issues. \hyperref[b3]{[3]} Requirement Engineering (RE) comparatively new field. Requirement Engineering is a system and processes that covers the activities based on computer system. \hyperref[b4]{[4]} Requirement elicitation and requirement management have healthy documented using UML (Unified Modeling Language). Many tools are available that support the UML standards in any way. These tools have their own advantages and disadvantages. Many available tools need customization to meet the special requirements. The prototypes also used to create system requirements automatically. \hyperref[b5]{[5]} Requirement elicitation is a technique to collect the requirements. Professionals like system engineers, software analysts work with the stakeholders; this is useful for finding and solving the problems. There are many requirement elicitation techniques like interviews; questionnaire etc. [6] Requirement elicitation is the main movement in the requirement engineering process. It occupied to find out the needs and collecting the required software requirements from the stakeholders. There are some problems occurred by software engineers when they perform requirement elicitation processes. Requirement elicitation faced many problems like users' involvement and perfect documentation. To get the correct requirements and complete requirements required the right stakeholders. So there must be need to adopt the technique that could help in recognize and decide the stakeholders. \hyperref[b6]{[7]} It is the major problem with software developers that developed software does not meet stakeholders' requirements. It stresses the user to focus importance of( D D D D )\par
C the requirements concerning the implementation cost. Time pressure and budget constraint force the software engineers to make plan for consecutive releases of software. \hyperref[b7]{[8]} Prioritization is a method where person or group of persons rank the item in order based on their recognize importance. Prioritization is the process of starting procedure based upon urgent and longstanding need of the organizations. Prioritization leads the organization sensible plan and performs on leaders dream for the future business plan. In any good organization, it is significant to develop priorities based on IT project to move right directions. Due to time constraint and lack of budget, it is very complicated to execute all requirements that elicited during the analysis. So prioritization helps to determine which would apply first.\par
The objective of the current article is to knowing the factors affect on the requirement prioritization. The current survey provides the support of requirement prioritization. These requirement prioritization factors (RPF) improve the ability of the prioritization. These requirement prioritization factors (RPF) effect the cost of the imagine system. 
\section[{II.}]{II.} 
\section[{Requirement prioritization and stakeholders}]{Requirement prioritization and stakeholders}\par
The role of prioritization of requirements is imperative to an efficient and result oriented product development. Requirement prioritization marks high risk and most important requirements to be given priority in implementation. \hyperref[b8]{[9]} Usually stakeholder expectations are high but shortage of time, limited resources and budget constraints make it difficult to implement all requirements that have been elicited for the system. With the help of prioritization, it can be decide which one should be implement first.\par
In several known customers prioritization adopt difficult shapes because of different users involve as well as have different thinking and separate preferences. A most important issue arises when stakeholders are scattered different geographical areas. There priorities are not same, all the time. Every requirement analyst performs the process of prioritization. Software engineers are not well trained to elicit, gather, analyze and security requirements.\par
[10] Requirement prioritization is extremely dangerous are of requirement engineering.\par
Without appropriate requirement prioritization, offer by different stakeholders, the necessary objectives of the end product cannot be achieved properly. The product may fails to meet its heart objectives on the basis of several requirements prioritization techniques presented by different researchers. \hyperref[b10]{[11]} III. 
\section[{Requirement prioritization and agile software development}]{Requirement prioritization and agile software development}\par
Agile development techniques become more accepted during last decade. Many methods built for the faster delivery of the software and those techniques ensure the developed software meets the user requirements. Requirement engineering depends on the documentation for the customer needs and agile technique depends on face to face association between the stakeholders to get the same requirements. \hyperref[b11]{[12]} Agile software development scenarios and stories are used. Use case modeling also popular method for requirements gathering and analysis. To collect the requirements through these methods always are complete, clear and validate. \hyperref[b12]{[13]} In habitual software development techniques customers or stakeholders predefined their software requirements and software analysts' analysis these requirements for specification. It is very difficult and not cost effective for complete requirements. This difficulty solves by the XP methods. \hyperref[b13]{[14]} Agile methods give the importance of continuous requirements prioritization from customer point of view. A agile approach give the client's critical role in making decision. \hyperref[b14]{[15]} IV. 
\section[{Research method and data collection}]{Research method and data collection}\par
The experience was drawn from this study conducted on seventeen different industries. The purpose of the survey based research was to find out how the software engineers could produce the product that might give good satisfaction of the stakeholder needs by the requirement prioritization. The organizations have different type of application domain. Through the questionnaire survey, studied the actual requirements prioritization work in special stage of software development. To get the clarification of the current requirement prioritization methods in-depth interviews were conducted. There are three groups according to their application domain.  The purpose of the focus group was to determine how organizations prioritize the requirements and which development phases involved in practice. Through the survey, it was concluded that which issues effect the prioritization and from which basis the stakeholders elicit the information on which they decide the requirement prioritization. In addition, picture was drawn to minimize the cost and enhance the effectiveness of the software though the requirement prioritization. The stakeholders and their associations to the requirement prioritization have shown the following table. 
\section[{Table 2 : Company and its stakeholder's designation}]{Table 2 : Company and its stakeholder's designation}\par
The age of the analysts affect the result of requirement prioritization as show below.   The team leader or business analyst required at least bachelor's degree. A survey showed that the inhouse development industry try to hire at least bachelor employees for analysis, requirements analysis and prioritization but industries desired for business analysts having brilliant computer education like M.Sc. (CS) etc. Because their professional work involves solutions to meet the customer business needs and customer challenges. As industries have over all well educated and experienced persons in different working areas and industries businesses enhance day to day. In the result of this requirements of industries generate dynamically. To control and prioritized all those requirements, the team leader should be high qualified and have ability to translate industries requirements into system requirements with prioritization for software developers. They should have expertise in open range of business effect and software programs. Education generates the ability in analyst to understand the business requirements, identify those requirements, document those requirements and prioritized them for business application for software developers. They get the ability to cope the relationship between different departments, effective communication, strategy of development those prioritized requirements.\par
The importance of the requirements is never neglected. The requirements prioritization is based on the following factors. Study indicated that there are three factors which affect the priorities. It is the base line for the profit of any organization. These factors minimize the gap between the stakeholders. Any issue like relationships, communication problem and project involvement between the customers and analysts can be shrinking using these factors. There is no defined method for inhouse development to prioritize the requirements. The organization must know these attributes in any software engineers. Any software developer who contains these attributes can make easily requirements prioritization and logical implementation of these requirements. The skill and education attributes cover the geographical region made their requirements priorities. It is not easy to say which individual factors affect the prioritization of the requirements.\par
V. 
\section[{CONCLUSION}]{CONCLUSION}\par
The study has been conducted at three types of industries, to find out the results about requirements prioritization that gives the high level satisfaction of the customer. To achieve the explanation of the actual requirements prioritization, conduct the survey indepth. The purpose of the survey was to determine how organizations prioritize the requirements. The term priority is the property or attribute of the requirement. In the survey organization, the requirements elicitation and requirements prioritization interacts the domain expert users.\par
The survey study indicated that there are three factors like analyst's qualification, experience and age which affect the prioritization. These factors help to minimize the distance between the stakeholders. The defined three factors resolved the issues like relationships, communication problems between users and software engineers. Any software developer pursuing these attributes can make easily requirements prioritization and implementation of the requirements. Accurate requirements prioritization produced the cost effective solution for the organization. \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Table 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-6.png}
\caption{\label{fig_4}Figure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-7.png}
\caption{\label{fig_5}Figure 5 :}\end{figure}
  			\footnote{© 2012 Global Journals Inc. (US)} 			\footnote{© 2012 Global Journals Inc. (US) Global Journal of Computer Science and Technology} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[
			JoachimK
		 ()]{b8}\label{b8} 	 		‘A Cost-Value Approach for Prioritizing Requirements’.  		 			JoachimK 		,  		 			Kevin 		.  	 	 		\textit{IEEE Software}  		1997.  	 
\bibitem[Arif and Al ()]{b4}\label{b4} 	 		 			S Arif 		,  		 			Al 		.  	 	 		\textit{Requirements Engineering Processes Tools/Technology},  				 (Islamabad, Pakistan)  		2010.  	 
\bibitem[Sadiq and Mohd ()]{b0}\label{b0} 	 		‘Elicitation and Prioritization of Software Requirements’.  		 			Sadiq 		,  		 			Mohd 		.  	 	 		\textit{Internation Journal of Recent Trends in Engineering}  		2009. 2  (3)  p. .  	 
\bibitem[Firesmith ()]{b9}\label{b9} 	 		‘Engineering Security Requirements’.  		 			D G Firesmith 		.  	 	 		\textit{Journal of Object Technology. U.S.A}  		2003. 2  (1)  p. .  	 
\bibitem[Firesmith ()]{b12}\label{b12} 	 		‘Generating Complete. Unambiguous, and Verifiable Requirements from Stories, Scenarios and Use Cases’.  		 			Firesmith 		.  	 	 		\textit{Journal of Object Technology. U.S.A}  		2004. 3  (10)  p. .  	 
\bibitem[Int. Conf. on the Software Engineering]{b2}\label{b2} 	 		\textit{Int. Conf. on the Software Engineering},  				 		 			University of Limerick, Ireland 		 	 
\bibitem[Reprioritization the Requirements in Agile Software Development: towards a conceptual model from clients perspective]{b14}\label{b14} 	 		\textit{Reprioritization the Requirements in Agile Software Development: towards a conceptual model from clients perspective},  		 \url{http://eprints.eemcs.utwente.nl/16055/01/SEKE-Racheva-Daneva.pdf}  		 	 
\bibitem[Paetsch ()]{b11}\label{b11} 	 		‘Requirement Engineering and Agile Software Development’.  		 			F Paetsch 		.  	 	 		\textit{Proc. 20th IEEE Int. Workshop on enabling technologies: Infrastructure for Collaborative Enterprises (WETICE'03)},  				 (20th IEEE Int. Workshop on enabling technologies: Infrastructure for Collaborative Enterprises (WETICE'03)Washington, USA)  		2003.  	 
\bibitem[Lamsweerde ()]{b1}\label{b1} 	 		‘Requirement Engineering in the Year 00: A Research Perspective’.  		 			A Lamsweerde 		.  	 	 		\textit{Proc. 22nd},  				 (22nd)  		2000.  	 
\bibitem[Rozilawati and Fares ()]{b6}\label{b6} 	 		‘Selecting he Right Stakeholders for Requirements Elicitation: A Systematic Approach’.  		 			Rozilawati 		,  		 			Fares 		.  	 	 		\textit{Journal of theortical and Applied Information Technology. Malaysia}  		2011. 33  (2)  p. .  	 
\bibitem[Chetankumar and Muthu ()]{b13}\label{b13} 	 		‘Story Card Based agile Software Development’.  		 			Chetankumar 		,  		 			Muthu 		.  	 	 		\textit{Int. Journal of Hybride Information Technology}  		2009. 2  (2)  p. .  	 
\bibitem[Meisenbacher ()]{b5}\label{b5} 	 		‘The Challenges of Tool Integration for requirements Engineering’.  	 	 		\textit{Proc. of SREO'05. France. 6. Ganesh and Gunda},  				 			L K Meisenbacher 		 (ed.)  		 (of SREO'05. France. 6. Ganesh and Gunda)  		2005. 2008.  		 			Requirement Engineering: Elicitation Techniques. Dept. of Technology, Mathematics and Computer Science. Sweden 		 	 
\bibitem[Sparrow ()]{b3}\label{b3} 	 		\textit{the Slow Wheel of Requirements Engineering Research: Responding to the Challenges of Societal Change},  		 			L Sparrow 		.  		2006. Australia.  		 			Deakin University 		 	 
\bibitem[Ramzan ()]{b10}\label{b10} 	 		‘Value Based Intelligent Requirements prioritization (VIRP): Expert Driven Fuzzy Logic Based Prioritization Technique’.  		 			M Ramzan 		.  	 	 		\textit{Int. Journal. Innovative Computing, Information and Control. Islamabad, Pakisatn}  		2011. 7  (3)  p. .  	 
\bibitem[Viggo ()]{b7}\label{b7} 	 		 			Viggo 		.  		\textit{An Experiment Comparision of Five Prioritization Methods Master Thesis Software Engineering},  				 (Sweden)  		2005.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
