\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={Probability Testing a Component of Advance Software Testing},
 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{2016-01-15 (revised: 15 January 2016)}
\def\TheID{\makeatother }
\def\TheDate{2016-01-15}
\title{Probability Testing a Component of Advance Software Testing}
\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]{Debashis  Ghatak}

             \affil[1]{  West Bengal University of Technology}

\renewcommand\Authands{ and }

\date{\small \em Received: 10 December 2015 Accepted: 5 January 2016 Published: 15 January 2016}

\maketitle


\begin{abstract}
        


The present invention relates to the ProbabilityTesting which is a new testing technique under Software Testing. This invention belongs to Software Testing, especially a new intellectual testing technique. The Probability Testing introduces a new mathematical formula in Software Testing as well as Software Engineering. Probabilistic Testing Architecture which gives a brief idea of Probability Testing before the start of the software testing.

\end{abstract}


\keywords{knowledge, thinking, assumption.}

\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[{I. Introduction}]{I. Introduction}\par
ach and every incident in this world has done its own logic which can be fabricated by a set of mathematical rules. It has been noticed that technological people have some fabrication knowledge that software development section established by logic or follows the rules of mathematics whereas Software Testing section doesn't follow any logic or any mathematical rule. But this concept is truly wrong. Suppose a logic for calculating two amounts like x and y and get the result in z like "x+y=z". During the time of software development, a developer can assemble this logic with the help of "DATA STRUCTURE" and different programming language. Similarly, a "Software Tester" can check the entire development, according to the requirement as well as in a different way like "Mandatory Fragment, Mandatory Sub Fragment, Dependent Mandatory Sub Fragment, Different Condition, Boundary Value Analysis, Statement Coverage, Equivalent Partitioning and Exit Criteria". All the respective checking is directly or indirectly related to "Mathematics" or some "Mathematical Rule". The backbone of any Software stands on five unique sections such as "REQUIRE-MENT, LOGIC, DESIGN, CODE GENERATION, TESTING" (See  {\ref Fig 1)}.\par
When a Software scamper in the real time scenario at that time it has been observed that the software has been failed due to a different unique situation rather than traditional scenario. Origination of Probability Testing is to avoid such kind of different unique situation which happens during the time of real time scenarioz. "Probability Testing" belong to two phases such as first "PLANNING" secondly "ACTING". "Software Tester" first prepares a mock unique situation that may be or must be happening during real time. Software tester will make a decision that which field is required to create such kind of scenario and activity (See  {\ref Fig 2)}.\par
Human intelligence comes from inherent thinking power and way of thinking of a person. It varies from person to person wise. Planning is the blossom of THINKING and the ASSUMPTION power of the person. Before the preparation of any planning, it requires an extensive area of THINKING, ASSUMPTION and thoroughly KNOWLEDGE about that particular item. Probability Testing belongs to the "Real Time" unique situation oriented Testing. In the "Probability Testing", a Software Tester must be needed three things 1. KNOWLEDGE 2. THINKING 3. ASSUMPTION Details Architectural Diagram of "Probability Testing" is as follows (See Fig \hyperref[fig_2]{3}).\par
In the "Probability Testing" corresponding "LOGIC" segment will prepare different mock real time "Logical Scenarios". "PLAN" is the consequence of "KNOWLEDGE + THINKING + ASSUMPTION". The mother of any intelligent logic comes from the methodically "KNOWLEDGE". Application of the "KNOWLE-DGE" comes when the steam of "THINKING" starts on that "KNOWLEDGE". At that time it has been noticed that different types of "ASSUMPTION" will come in the mind automatically and then different types of "ASSUMPTION" will be converted into the different "PLAN" like "PLAN1,PLAN2,PLAN3,???.,PLANn".\par
Any Software works on the basic functionality of some "Mandatory Fragment", "Mandatory Sub Fragment", "Dependent Mandatory Sub Fragment", "Different Conditional Fragment" and related non-functional Fragments. It is following "TOP DOWN" architecture of the "Data Structure" model.\par
The objective of "Probability Testing" is the good choice for "Software Testing". According to the derived formula for a total number of "Test Case" generation for "Software Testing", it has been noticed that "Software Testing" is a combination of the different level of Fragment in different in different ways. In terms of mathematics, it is called "Permutation". Any software is a combination of various "Mandatory Fragment", "Mandatory Sub Fragment", "Dependents Mandatory Sub Fragment", "Conditional Fragment" and "Nonfunctional Fragment". "Fragment" dependency can arise any part of any "Software" according to the requirement. Probability Testing follows the "Probability Theory" that is "Permutation" of n distinct objects has taken r at a time such that nPr=n! / (n-r)! .Where some of the fragments are obtained as concealed in the test design.\par
During the time of "Probability Testing", the tester will generate different mock real time situation, according to the business requirement and business logic. According to the different mock probable scenario which may be happening in the real time on the basis of that Software Tester try to find out the different kind of defects on the basis of various scenarios for taking requisite corrective measures in the software coding and eliminating the defects.\par
After a release of the software globally there are a numerous number of bugs has been found in multiple specific situations. "Probability Testing" is very much required to avoid such kind of situation before releasing the software globally. "Probability Testing" is the place where testers have a freedom of thinking and implement the said, thinking capability during the time of real-time testing. Considering the following relation in the software testing, n n Pi=? Mi+ ? CF l i=1 l=1\par
Where CF= nCr Let "M" belongs to the "Mandatory Fragment". "CF" which also belongs to the others "Child Fragment" which is correlated with "Mandatory Fragment" and chooses a different combination of respective "Child Fragment" corresponding "r" at a time. The above formula will help for the tester that in which way and how a Software Tester will prepare different mock real time scenario during the time of "Probability Testing" also it will track the total count of the mock real time scenario throughout the operational time.\par
Every different "Fragment" has a relationship as like as "Parent" with "Child" as "Mandatory Fragment" with "Child Fragment". During the time of "Probability Testing", each individual "Fragment" can be prepared by using the above formula.\par
Formation of mock real time situation, corresponding "Mandatory Fragment" should be treated as "Parent Fragment" related sub-fragment is treated as "Child Fragment". Creation of the Mock real time situation during the time of "Probability Testing" is basically a "Top down" approach and corresponding relational diagram will go into synchronously from Parent to Child (See  {\ref Fig 4)}.\par
"Child Fragment" will come up according to the mock real time situation and in every different, unique case will diverge according to the different mock real time situation. During the time of "Probability Testing", a tester will generate mock real time scenario like Any Unmanned Ground vehicle (UGV) or Unmanned Arial vehicle (UAV) directly controlled by satellite or some elevated power wireless communication system. The "Unmanned Ground vehicle (UGV) or Unmanned Arial vehicle (UAV)" will perform their assignments in the inaccessible area where human meddling is impossible. This is traditional system and traditional testing, which is sufficient for such kind of scenario. But "Probability Testing" is quite different, suppose if they said "Unmanned Ground vehicle (UGV) or Unmanned Arial vehicle (UAV)" moves under a long tunnel or hilly dense forest where satellite network or wireless communication system is not reached or not available such kind of situation, how the "Unmanned Ground vehicle (UGV) or Unmanned Arial vehicle (UAV)" will rescue and reinstate the communication with respective satellite or wireless communication system such kind of scenario based testing have done by Probability testing.\par
In the general insurance for a "Private Car Package" product, suppose a car owner has a private car like "Mercedes Benz". During the time of "Policy Generation" of the said new vehicle owner was taken the "Sum Insured" that is "\$100000"along with that several "Risk Cover" was taken like "Theft", "Accessories" etc.. After a few days later person was filed an endorsement that is "Change in Sum Insured" Endorsement from "\$100000" to "130000". After successfully passed the said endorsement the owner of the vehicle faced an accident where one person was dying and one person was severely injured. Both family members were filed different claims like "Death \& Injury" against the policy of the receptive person. "General Insurance Company" was appointed a surveyor against the said claim to find out the authenticity of the respective claims. Suddenly the said owner of the vehicle drove on the hilly road and faced on the "Land Slide". The owner was spot death along with that vehicle was smashed.\par
In the above type of cases, the family members of the owner will file a "Death" as well as "Own Damage" claim against the respective policy number. Software Tester will test what types of defects have been generated such type of mock real time situation that has been created during the time of "Probability Testing".  
\section[{Global Journal of}]{Global Journal of} 
\section[{H}]{H}\par
Probability Testing a Component of Advance Software Testing "Probability Testing" will testing will test such kind of mock real time scenario oriented testing and find out the defects against that incident. In the above mock real time situation based testing is not possible either in "Integration" or "Regression Testing". Because "Integration" and "Regression Testing" have done on the basis of "Test Cases" and "Probability Testing" has done on the basis of "Mock real time Test Scenario". Knowledge, Assumption \& Thinking ability are the key of "Probability Testing".    "Probability Testing" of Software Testing Which comprises, create mock real time intellectual situation, that the scenario which will probably happen in future during runtime and test the software on the basis of that scenario.\par
Said Software testing can be performed only after completion of "Integration Testing" and "Regression esting". KNOWLEDGE, THINKING, ASSUMPTION is the key of Probability Testing. 
\section[{III. Acknowledgment}]{III. Acknowledgment}\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 4 :}\end{figure}
 			\footnote{© 2016 Global Journals Inc. (US) 1} 		 		\backmatter   			 \par
The authors would like to thank Government of India for his/her moral support. 			  			  				\begin{bibitemlist}{1}
\bibitem[ IEEE Standard Glossary of Software Engineering Terminology]{b2}\label{b2} 	 		\textit{},  	 	 		\textit{IEEE Standard Glossary of Software Engineering Terminology}  		610 p. .  	 	 (IEEE Std) 
\bibitem[Sannella ()]{b4}\label{b4} 	 		\textit{Constraint Satisfaction Debugging for Interactive User Interfaces},  		 			M J Sannella 		.  		1994.  		 			University of Washington 		 	 	 (Doctoral Thesis) 	 (UMI Order Number: UMI Order No. GAX95-09398) 
\bibitem[Fundamental of Software Engineering: Rajib Mall 7. Software Engineering a Practitioner Approach]{b5}\label{b5} 	 		\textit{Fundamental of Software Engineering: Rajib Mall 7. Software Engineering a Practitioner Approach},  				Roger S Pressman.  	 
\bibitem[IEEE Standard for Software Maintenance. IEEE Std 1219-1993 IEEE ()]{b0}\label{b0} 	 		‘IEEE Standard for Software Maintenance. IEEE Std 1219-1993’.  	 	 		\textit{IEEE}  		1993. Institute of Electrical and Electronics Engineers.  	 
\bibitem[IEEE Standard for Software Verification and Validation Plans (Reaff.1992). IEEE Std]{b1}\label{b1} 	 		\textit{IEEE Standard for Software Verification and Validation Plans (Reaff.1992). IEEE Std},  				p. .  	 
\bibitem[Jj Kuhl ()]{b3}\label{b3} 	 		\textit{Project Lifecycle Models: How They Differ and When to Use Them},  		 			Jj Kuhl 		.  		2002.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
