\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={Simulation of Reliability of Software Component},
 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{2013-01-15 (revised: 15 January 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-01-15}
\title{Simulation of Reliability of Software Component}
\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]{Er.  Karambir}

             \author[2]{Dr. P.K.  Suri}

             \affil[1]{  University Institute of Eengg and Technology}

\renewcommand\Authands{ and }

\date{\small \em Received: 9 December 2012 Accepted: 2 January 2013 Published: 15 January 2013}

\maketitle


\begin{abstract}
        


Component-Based Software Engineering (CBSE) is increasingly being accepted worldwide for software development, in most of the industries. Software reliability is defined as the probability that a software system operates with no failure within a specified time on specified operating conditions. Software component reliability and failure intensity are two important parameters that Estimates the reliability of system after integration of component. The estimation of reliability of software can save loss of time, life and cost. In this paper, software reliability has been estimated by analyzing the failure data. The Imperfect Software Reliability Growth Models (SRGMs) model have been used for simulating the software reliability by estimating the number of remaining faults and the model parameters of the fault content rate function. We aim for simulating software reliability by connecting the imperfect debugging and Goel-Okumoto model. The estimation of reliability gives the time of stopping the unending testing of that component or time of release of software component.

\end{abstract}


\keywords{component based software engineering (cbse), software reliability growth model (srgm), reliability, goel- okumoto 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
ith the popularity of the web and networked computers are finding their way into a wide and spread range of working environments. This new computing model have made a competition of early development, reliable and distributed software components that communicate with one another across the underlying networked and extendable infrastructure as per the requirement of different user. A distributed software component can be plugged into distributed applications and can be used for some specific purpose. The intention of most of the developers behind is reuse or slight modification of old or reliable component and this makes more reliable by using distributed software components to build new systems. Even though, it is also important for developer to know the functionality of distributed or compatible software component in any system. The design of component and requirement specification should clearly document the functional input, output with conditions and moreover it is the reliability percentage wise. Software reliability has been defined as the probability that a software system operates with no failure for a specified time on specified operating conditions. In other words, by estimating or predicting the reliability \hyperref[b0]{[1]} of component, the quality of software product can be estimated. The satisfaction of customers is directly dependent on the quality of that software. The analysis report that is commonly used to describe software reliability has been derived from observed or failure intensity. Failure intensity is defined as the number of failures observed per unit time period. Failure intensity is a also good measure for reflecting the user perspective of software quality. As Computer applications are going more diverse and spreading through almost every area of everyday life then reliability factor becomes a very important characteristic of software or component systems. The reliable component is a base of system and part of system i.e. client, administrator and working environment. Since it is a matter of cost and performance to produce a system having documented and estimated reliability \hyperref[b1]{[2]} of system. Therefore, it is necessary to measure its reliability before releasing any software. When reliability reaches at threshold level then the software component can be released for further use. To do this, a number of models \hyperref[b2]{[3]} have been proposed and has been being developed. Software modeling is a statistical estimation \hyperref[b3]{[4]} method applied to failure data collected or simulated the software component or system developed after integration of software component by different approach of joining in software engineering .This can be one after a component testing has been executed so that failure data are available. The implementation of newly developed and modified models tries to make system better and help in predicting the reliability in a accurate way. The most important parameter of any software product are level of quality, time of delivery, and final cost of the product. The time of delivery and cost should be quantitative and pre decided, whereas these attributes is difficult to define Quantitatively. Reliability is one, and probably the most Software reliability is related directly to operation and performance instead of designing of a component.\par
Therefore, software reliability is estimated by analyzing the observed failure data [5] of component and then applying Goel -Okumoto Model  {\ref [6][7]} , rather than the number of remaining faults in a component. So, estimation of reliability of system is more useful than finding the number of remaining fault. The uncertainty involved in the estimation for a specific interval expressed in terms of confidence interval and estimation of parameter used. This paper evaluates the estimates the reliability of component by using the Goel-Okumoto( D D D D D D D D )\par
model on the set of failure data taken from simulating the real software applications. This should be done before any component release .The reusability of that component enhances the overall reliability of system and gives accurate estimation of value of reliability. The result shows that the proposed model has a technical point for improving software reliability and providing additional metrics for development project evaluation, management and time of delivery of new developed system. 
\section[{II.}]{II.} 
\section[{Goel Okumoto Model : NHPP SRGM Exponential Model}]{Goel Okumoto Model : NHPP SRGM Exponential Model}\par
Non Homogeneous Poisson Process (NHPP) based software reliability growth models are generally classified into two groups. The first group contains models, which use the machine execution time or calendar time \hyperref[b6]{[8]} as a unit of fault detection/removal period. Such models are called continuous time models. The second group contains models, which use the number of test occasions/cases as a unit of fault detection period. Such models are called discrete time models \hyperref[b7]{[9]}, since the unit of software fault detection period is countable. A Goel Okumoto Model also known as exponential NHPP model is based on the following assumptions:(a) All fault in a component are independent from the failure detected. (b)The number of failures detected at any time is proportional to the current number of fault in a component. (c) The fault is removed immediately as soon as the failure happens, no new faults are introduced during the removal of fault.\par
The following differential Equation1 include the above assumptions. Where m(t) is expected number of component failures by time t, a is Total fault content rate function, i.e., the sum of expected number of initial software faults and introduced faults by time t and b is Failure detection rate per fault at time t. important, aspect of software quality. S???? (??) ???? = ??[?? ? ??(??)]\textbf{(1)}\par
The mean value solution of above differential equation is given by Equation  {\ref 2}where tn is time of nth failure occurrence??(??) = ???1 ? e ?bt n ? (2)\par
Failure intensity function is given by Equation 3 as follows??(??) = ?????? ????? ??\textbf{(3)}\par
III. 
\section[{Estimation of Parameter}]{Estimation of Parameter}\par
The different a and b parameter also reflect different assumptions of the software testing processes. In this section, we derive a new NHPP model for an interrelationship dependent function between a and b parameter by a common parameter from a generalized class of model. The most common method for the estimation of parameters is the Maximum Likelihood Estimation (MLE) method. MLE method of estimation of a broad collection of software reliability for grouped data is discussed in detail. To estimate a and b for a sample of n units, first obtain the likelihood function: take the natural logarithm on both sides. The equation for estimation of a and b is given in Equation  {\ref 4}wherea = y n (1??? ??? ?? ?? (4)\par
Where yn is actual value of nth failure observed at time t. The parameter a can be estimated using MLE method based on the number o failures in a particular interval. Suppose that an observation interval \{0, tk\} is divided into set of sub intervals (0,ti],(t1,t2]???(tk-1,tk] , Equation 5 was used to determine the value of b .y n t n e ?bt n 1?e ?bt n = ? ? (y k ??? ???1 )(t k e ?bt k ?t k ?1 e ?bt k ?1 ) (e ?bt k ?1 ? e ?bt k ) ? ?? ??=1\textbf{(5)}\par
The number of failures per subinterval \hyperref[b6]{[8]} is recorded as ni(i=1,2,3..,k) with respect to the number of failures in(ti-1,ti].The parameters a and b are estimated using iterative Newton Raphson Method, which is given as in Equation  {\ref 6}Equation 7 and Equation \hyperref[formula_7]{8}.?? = b 0 ? f(b 0 ) f? (b 0 ) (6) ð??"ð??"(??) = y n t n e ?bt n 1 ? e ?bt n ? ? ? (y k ??? ???1 )(t k e ?bt k ?t k ?1 e ?bt k ?1 ) (e ?bt k ?1 ? e ?bt k ) ? = 0 ?? ??=1\textbf{(7)}ð??"ð??" ? (??) = ? ? (y k ??? ???1 )(t k ?t k ?1 ) 2 e ?b (t k +t k ?1 ) (e ?bt k ?1 ? e ?bt k ) 2 ? ?? ??=1\textbf{(8)}\par
IV. 
\section[{Model Analysis and Results}]{Model Analysis and Results} 
\section[{a) Data and Model Criteria}]{a) Data and Model Criteria}\par
Once the analytical expression for the mean value function m(t) is derived, in this paper, the model parameters to be estimated in the mean value function can then be obtained with the help of a developed octave program based on the least squares estimate (LSE) method. Goel and Okumoto described failure detection as a non-homogeneous Poisson process with an exponentially decaying rate function .It is a simple non-homogeneous Poisson process model. The data of failure of 25 days have been observed here for estimating the reliability \hyperref[b8]{[10]}. In table 1, the data of 25 days failure and cumulated failure have been shown here.\par
The two function of Reliability and Remaining fault function can be used to find the release of date or the additional testing time is required to reach ready state. After simulation the result of 25 days of testing were observed. Based on these data and using the MLE C method, the estimated values for the two parameter are given in the table. Each data set provides the cumulative number of faults by each week up to 25 weeks. The Fig. \hyperref[fig_2]{1} represents the cumulative number of faults versus the cumulative system test hours at the end of each The Phase 2 data set is given in Table \hyperref[tab_1]{2}. We developed a Octave program to perform the analysis and all the calculations for LSE estimates. The parameter a is the number of initial faults in the software and the parameter b is related to the failure detection rate during testing process. The software reliability R(x/t) is defined as the probability of a failure free operations of a complete software for a specified time i.e. interval (t, t +x) in a specified environment in Equation  {\ref 9}. The interval methods of estimation are explained by applying the results to the software failure data .The set of software errors analyzed here is borrowed from a simulated data ( an 1 days interval). where R(s|t) is reliability of component during (t, t+s) time.      ??(??????) = ?? ???(?? ????? ??? ??? (??+?? ) ) (9) 
\section[{Conclusion}]{Conclusion}\par
This work has proposed a method of estimating the reliability of reusable architecture which can be used to build a software by using Goel-Okumoto Software Reliability Growth Model. The data available from an exponential distribution are grouped and the this model used to illustrate the parameter estimation problem. The measurement of reliability decides the quality and level of reliability decides the time of delivery of any software the reliability is increased with testing time but the reliability never becomes 100\% even when the observed fault is close to zero. As per the other criteria in the above analysis, the best estimate for the remaining fault is less than 10 and then the component can be released. The integration of more reliable component can make the system more reliable. This solution will help the developer of third party component to predict the release the component with the specified marked reliability.\par
Volume XIII Issue XIII Version I \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_2}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{23}\includegraphics[]{image-3.png}
\caption{\label{fig_3}Figure 2 :Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-4.png}
\caption{\label{fig_4}Figure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-5.png}
\caption{\label{fig_5}Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{P{0.08341121495327103\textwidth}P{0.1350467289719626\textwidth}P{0.1985981308411215\textwidth}P{0.11121495327102802\textwidth}P{0.11121495327102802\textwidth}P{0.21051401869158878\textwidth}}
Days\tabcellsep Failure Observed\tabcellsep Cumulative Failure\tabcellsep Days\tabcellsep Failure Observed\tabcellsep CumulativeFailure\\
1\tabcellsep 32\tabcellsep 32\tabcellsep 14\tabcellsep 5\tabcellsep 127\\
2\tabcellsep 23\tabcellsep 55\tabcellsep 15\tabcellsep 5\tabcellsep 132\\
3\tabcellsep 11\tabcellsep 66\tabcellsep 16\tabcellsep 6\tabcellsep 138\\
4\tabcellsep 10\tabcellsep 76\tabcellsep 17\tabcellsep 3\tabcellsep 141\\
5\tabcellsep 11\tabcellsep 87\tabcellsep 18\tabcellsep 5\tabcellsep 146\\
6\tabcellsep 7\tabcellsep 94\tabcellsep 19\tabcellsep 1\tabcellsep 147\\
7\tabcellsep 2\tabcellsep 96\tabcellsep 20\tabcellsep 1\tabcellsep 148\\
8\tabcellsep 5\tabcellsep 101\tabcellsep 21\tabcellsep 3\tabcellsep 151\\
9\tabcellsep 6\tabcellsep 107\tabcellsep 22\tabcellsep 1\tabcellsep 152\\
10\tabcellsep 2\tabcellsep 109\tabcellsep 23\tabcellsep 2\tabcellsep 154\\
11\tabcellsep 4\tabcellsep 113\tabcellsep 24\tabcellsep 1\tabcellsep 155\\
12\tabcellsep 7\tabcellsep 120\tabcellsep 25\tabcellsep 1\tabcellsep 156\\
13\tabcellsep 2\tabcellsep 122\tabcellsep \tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_0}Table 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2} \par 
\begin{longtable}{P{0.3331081081081081\textwidth}P{0.11322393822393823\textwidth}P{0.10994208494208493\textwidth}P{0.050868725868725866\textwidth}P{0.10666023166023166\textwidth}P{0.1361969111969112\textwidth}}
Day\tabcellsep A\tabcellsep B\tabcellsep Remaining Fault\tabcellsep Reliability\tabcellsep Failure Intensity\\
15\tabcellsep 138.38\tabcellsep 0.1333\tabcellsep 16\tabcellsep 80.5\tabcellsep 2.1844\\
16\tabcellsep 133.71\tabcellsep 0.1432\tabcellsep 12\tabcellsep 84.66\tabcellsep 1.6769\\
17\tabcellsep 141.25\tabcellsep 0.1274\tabcellsep 14\tabcellsep 83.48\tabcellsep 1.8162\\
18\tabcellsep 139.72\tabcellsep 0.1304\tabcellsep 12\tabcellsep 85.91\tabcellsep 1.5286\\
19\tabcellsep 138.85\tabcellsep 0.1322\tabcellsep 10\tabcellsep 87.86\tabcellsep 1.3030\\
20\tabcellsep 140.34\tabcellsep 0.1290\tabcellsep 9\tabcellsep 88.71\tabcellsep 1.2052\\
21\tabcellsep 140.10\tabcellsep 0.1295\tabcellsep 8\tabcellsep 90.09\tabcellsep 1.0495\\
22\tabcellsep 141.91\tabcellsep 0.1255\tabcellsep 8\tabcellsep 90.60\tabcellsep 0.9929\\
23\tabcellsep 142.03\tabcellsep 0.1252\tabcellsep 7\tabcellsep 91.62\tabcellsep 0.8801\\
24\tabcellsep 142.3154\tabcellsep 0.1246\tabcellsep 6\tabcellsep 92.48\tabcellsep 0.7869\\
25\tabcellsep 141.13\tabcellsep 0.1275\tabcellsep 5\tabcellsep 93.71\tabcellsep 0.6538\\
b) Analysis\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
\multicolumn{4}{l}{In fig 1 the cumulative failure observed have}\tabcellsep \tabcellsep \\
\multicolumn{4}{l}{been shown as per number of days of testing. It is}\tabcellsep \tabcellsep \\
\multicolumn{4}{l}{obviously seen that the number of fault observed is}\tabcellsep \tabcellsep \\
\multicolumn{2}{l}{decreasing with days.}\tabcellsep \tabcellsep \tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_1}Table 2 :}\end{figure}
 			\footnote{© 2013 Global Journals Inc. (US)} 			\footnote{© 2013 Global Journals Inc. (US) Global Journal of Computer Science and Technology} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Teng and Pham ()]{b1}\label{b1} 	 		‘A New Methodology for Predicting Soft-ware Reliability in the Random Field Environments’.  		 			X Teng 		,  		 			H Pham 		.  	 	 		\textit{IEEE Transactions on Reliability}  		2006. 55  (3)  p. .  	 
\bibitem[Pham and Zhang ()]{b8}\label{b8} 	 		‘An NHPP Software Reliability Models and its Comparison’.  		 			H Pham 		,  		 			X Zhang 		.  	 	 		\textit{International Journal of Reliability, Quality and Safety Engineering}  		1997. 4  (3)  p. .  	 
\bibitem[Dr et al. (2011)]{b6}\label{b6} 	 		‘Assessing Software Reliability using Inter Failures Time Data’.  		 			R Dr 		,  		 			Bandla Satya Prasad 		,  		 			Dr R R L Srinivasa Rao 		,  		 			Kantham 		.  	 	 		\textit{International Journal of Computer Applications}  		March 2011. 18  (7) .  	 
\bibitem[Zhang et al. ()]{b7}\label{b7} 	 		‘Considering Fault Removal Efficiency in Software Reliability Assessment’.  		 			X Zhang 		,  		 			X Teng 		,  		 			H Pham 		.  	 	 		\textit{IEEE Transactions on Systems, Man, and Cybernetics -Part A}  		2003. 33  (1)  p. .  	 
\bibitem[Pham ()]{b3}\label{b3} 	 		\textit{Software Reliability Assessment: Imperfect Debugging and Multiple Failure Types in Software Development},  		 			H Pham 		.  		 EG and G-RAAM-10737.  		1993.  		 			Idaho National EngineeringLaboratory 		 	 
\bibitem[Yamada and Osaki ()]{b5}\label{b5} 	 		‘Software Reliability Growth Modeling: Models and Applications’.  		 			S Yamada 		,  		 			S Osaki 		.  	 	 		\textit{IEEE Transactions on Software Engineering}  		1985. 11  (12)  p. .  	 
\bibitem[Pham and Pham ()]{b2}\label{b2} 	 		‘Software Reliability Models with Time dependent Hazard Function Based on Bayesian Approach’.  		 			L Pham 		,  		 			H Pham 		.  	 	 		\textit{IEEE Transactions on Systems, Man, and Cybernetics Part A}  		2000. 30  (1)  p. .  	 
\bibitem[Pham ()]{b0}\label{b0} 	 		‘System Software Reliability’.  		 			H Pham 		.  	 	 		\textit{Springer Series in Reliability Engineering},  				 (London)  		2006. Springer. p. .  	 
\bibitem[Goel and Okumoto ()]{b4}\label{b4} 	 		‘Time-dependent Faultdetection Rate Model for Software and Other Performance Measures’.  		 			A L Goel 		,  		 			K Okumoto 		.  	 	 		\textit{IEEE Transactions on Reliability}  		1979. 28 p. .  	 
\end{bibitemlist}
 			 		 	 
\end{document}