\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={Agile Software Development and Testing: Approach and Challenges in Advanced Distributed Systems},
 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{2014-01-15 (revised: 15 January 2014)}
\def\TheID{\makeatother }
\def\TheDate{2014-01-15}
\title{Agile Software Development and Testing: Approach and Challenges in Advanced Distributed Systems}
\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]{  P.Rajasekhar}

             \affil[1]{  SEAGI/JNTU-A}

\renewcommand\Authands{ and }

\date{\small \em Received: 9 December 2013 Accepted: 1 January 2014 Published: 15 January 2014}

\maketitle


\begin{abstract}
        


More and more companies are adopting Agile methods as a flexible way to introduce new software products. An important part of any software project is testing. Agile testing may have similar aims as traditional software testing, but the structure of the team is different, testers need to support quality infusion through entire team. Test automation and selection of test tool can help project teams deliver more effectively, and in shorter timescales. The challenges in testing of cloud are visible also in the tools for automatic test case execution. This paper addresses some of these challenges and also highlights every aspect of software testing process in Agile development.

\end{abstract}


\keywords{agile methods, unit testing, cloud testing.}

\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
n general Software engineering involves the design, develop, maintenance and documentation of software systems. Software engineering can be viewed as an approach that combines computer science and the customer to develop a set of tools and techniques to solve problems \hyperref[b1]{[2]}. As we notice the methodologies continually looking for ways building delivery models which offer their customers workable, innovative solutions which provide competitive advantage. During early 1990s, the methodologies war was between object-oriented (OO) design and traditional development models. Developing applications in complex environments presents challenges that never before faced by the management gurus. There are complexity results from the inherent complexity nature of applications themselves. For example internet based applications are highly distributed-may contain components written in a variety of languages deployed across machines with different architectures and operating systems. In its early days the proponents of OO argued that its widespread adoption would allow for greater flexibility in software development for distributed networked applications than earlier structured techniques. Many researchers and professionals involved in promoting the OOP techniques. However Object-Oriented Programming (OOP) technology is not a software development model; OOP does enhance the effectiveness of earlier software development models. As Software development involved more critical, dynamic and customer centric projects, new challenges are emerged which effects the growth of companies. These difficulties include more customer involvement, changing nature of customer requirements, projects with tight deadlines and over budgets. With the existence of such problems, the OOP technology cannot satisfy the objectives of software development companies. A number of IT professionals started to work individually on new approaches to develop software. Currently Agile is one of the highly practiced methodologies. Trends in distributed software systems have gained increasing importance in recent years have been for software to move to much larger venues in the web, cloud and mobile applications. One way to handle software development in an ever changing environment is by imbibing Agile methodologies as part of development process.\par
The Agile software development methods evolved in the mid-1990s as a reaction against heavyweight waterfall model of development. The early implementations of agile methods include Extreme programming  {\ref (Beck)}, Scrum (Schwaber), Crystal (Alistair Cockburn), Feature Driven Development, Agile Modeling. These are now typically referred to as agile methodologies, after the Agile Manifesto Published in 2001. The formulation of Agile Manifesto occurred when a group of IT professionals with similar ideas and objectives met in Salt Lake City, Utah, USA, and issued so called the Agile Manifesto  {\ref [9]}. 
\section[{Agile Manifesto}]{Agile Manifesto}\par
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have came to value:\par
? Individuals and interactions over processes and tools ? Working software over comprehensive documentation ? Customer collaboration over contract negotiation ? Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.  
\section[{end-to-end sdlc with agile methodology}]{end-to-end sdlc with agile methodology}\par
There are a number of different Agile methodologies (XP, Scrum etc.,), each with its own combination of practices. All these methods follow the core principles of Agile manifesto with common goal and values. Agile methods emphasize working software as a primary measure of progress. In his book, Extreme Programming Explained \hyperref[b0]{[1]}, Beck proposes twelve different ideas that are key to his form of agile development. These key factors provide agility to a project aiming at speed, communication, group effort, customer feedbacks. Agile software development process is a conceptual framework for software engineering where the entire project is divided into smaller pieces or in iterations, each of which handled separately \hyperref[b2]{[3]}.Software development during one unit of time is referred to as an iteration, each defining its own set of tasks(features) that combine to make requirements.\par
In Agile development user stories describes the system requirements. Using these high level user stories, team will create a useful map of the full system that is valuable for telling big stories about the end to end use of the entire system .Then the system is divided into different iterations during the release planning step. Iterations are short time frames that typically last from one to four weeks, each iteration involves a cross functional team working in all areas of development: design, coding, testing. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release with minimal bugs. When the iteration is developed and tested, the system is sent to the customer for feedback. The customer provides his/her feedback in the form of stories and again the same steps are followed later. When the required levels of functionalities are delivered then customer stops writing stories and development stopped. Multiple iterations might be required to release a product or new features(Figure \hyperref[fig_1]{-1}). Every release should be as small as possible, containing the most valuable business requirements \hyperref[b0]{(Beck, Kent 2000)}.  
\section[{Software Testing and Quality Assurance in Agile Development}]{Software Testing and Quality Assurance in Agile Development}\par
In Agile methods there is no specific testing phase, instead integrates testing into development process \hyperref[b4]{[5]}.Programmers do some integration testing and also unit testing while developing the iteration. The incremental feature acceptance (acceptance test) is usually done by the customer. This minimizes overall risk and allows the project to adapt to changes quickly \hyperref[b3]{[4]}. A highly practiced QA activity in Agile method rely on customer feedback. According to Agile manifesto people are more important than process and tools; customer interaction at every level is important aspect of an Agile process. The following (Figure \hyperref[fig_2]{-2}) explains the testing activities in Agile method during one iteration. Software quality assurance is the systematic activities providing evidence of the fitness for use of the total software product. Different Agile methods follow different strategies in practice. These practices are broadly summarized as follows: a) Unit testing: One typical way of software quality assurance is developer testing: developers test their code as they write, often in the form of unit testing. Unit testing is a good way to communicate over issues in the code under development without waiting for other units to be available, provides fault detection at a lower cost comparing to do so at a later stage \hyperref[b5]{[6]}.  
\section[{IV. Agile Testing and Testing Challenges}]{IV. Agile Testing and Testing Challenges}\par
In the previous section we described some of the useful testing and quality assurance activities in Agile methods. It's a common misconception that Agile projects don't need a rigorous approach to testing. But if we compare Agile with other traditional approaches, then we will come to know that from testing perspective Agile methods have lacked in different important aspects of software testing process \hyperref[b6]{[7]}. In Agile development there is no specific role defined for tester and often testers are treated as junior developers.\par
A good tester has many distinguishing feature that make difference with developer. In \hyperref[b6]{[7]} the authors say that Agile development can be benefited through a team of professional testers.\par
Agile Testing is a software testing practice that follows the principles of Agile software development. Agile Testing involves a cross-functional Agile team actively relying on the special expertise contributed by testers. This allows the combined team to better meet the project's defined business, software usability, quality, and timeline objectives.\par
Unit tests are foundations of any Agile projects, effective unit test can be done with automation. The more the team can automate the testing, the faster they can move on to the next developments. But testing in an Agile way is not without its challenges, are left in utilizing the automated tools in some applications. Testing in complex distributed environment like cloud testing poses significant challenges for a tester to perform unit testing with an automated test generation tool. Moving the application to the cloud will in some cases present some differences in how to implement a certain test or test case depending on the cloud environment. Often, a test case requires the system under test to have a certain internal state as a starting point of the test case. A big challenge for the tester is to achieve the required state prior to test case execution. Another problem with Agile methodologies is that testing is not done in a fixed pattern at the end of the development phase, but instead after each package or integration of packages. Hence a project based on Agile methodology, planned tests must be creative in order to allow adaptation to the changes as well as the schedule.\par
V. 
\section[{Conclusion}]{Conclusion}\par
Studying the role of testing and identifying a set of issues when building and testing complex distributed database systems in a cloud, the focus of our thesis, is the least researched area. Very few papers have been published that focus directly on software testing of cloud applications. The main result revealed by our primary study is that for developing and providing a system aimed for the cloud is effective with Agile development process. But it is critical that an Agile tester who is expected to test the quality and performance of cloud applications has a good understanding of what makes a Cloud Computing application and distributed architecture, as well as a good understanding of the tools available and their strengths and weakness for testing different types of cloud applications. To support our work an additional research goal was made to evaluate the applicability and support of various techniques and open source tools for advanced distributed database testing like in a cloud environment. \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_1}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_2}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{fig_3}}\end{figure}
 			\footnote{© 2014 Global Journals Inc. (US)} 			\footnote{e-mail: prajasekhar456@gmail.com} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Abrahamsson et al. ()]{b4}\label{b4} 	 		\textit{Agile Software Development Methods: Review and Analysis},  		 			P Abrahamsson 		,  		 			O Salo 		,  		 			J Ronkainen 		,  		 			J Warsta 		.  		2002. VTT Publications. 478.  	 
\bibitem[Beck ()]{b0}\label{b0} 	 		\textit{Extreme Programming Explained},  		 			Kent Beck 		.  		2000. Addison-Wesley.  	 
\bibitem[Cohn and Ford (2003)]{b3}\label{b3} 	 		\textit{Introducing an Agile Process to an Organization},  		 			M Cohn 		,  		 			D Ford 		.  		June 2003. 36 p. .  	 
\bibitem[Ammann and Offutt ()]{b5}\label{b5} 	 		\textit{Introduction to Software Testing},  		 			Paul Ammann 		,  		 			Jeff Offutt 		.  		2008. Cambridge Univ Press.  	 
\bibitem[Itkonen et al.]{b6}\label{b6} 	 		 			Juha Itkonen 		,  		 			Kristian Rautianinen 		,  		 			Casper Lassenius 		.  		\textit{Towards Understanding Quality Assurance in Agile Software Development", International Conference on Agility Management (ICAM 2005)},  				 	 
\bibitem[Pfleeger and Atlee ()]{b1}\label{b1} 	 		\textit{Software Engineering: Theory and Practice},  		 			S L Pfleeger 		,  		 			J M Atlee 		.  		2005. Prentice Hall.  	 
\bibitem[Conchango ()]{b2}\label{b2} 	 		\textit{The Agile revolution: Reduce project failure rates through adoption of Agile},  		 			Conchango 		.  		 \url{URL:www.conchango.com}  		2005.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
