| 1 |
%$Header: /home/dashley/cvsrep/e3ft_gpl01/e3ft_gpl01/dtaipubs/esrgubka/c_ird0/c_ird0.tex,v 1.2 2001/07/01 20:37:27 dtashley Exp $
|
| 2 |
|
| 3 |
\chapter{\cirdzerolongtitle{}}
|
| 4 |
|
| 5 |
\label{cird0}
|
| 6 |
|
| 7 |
\section{Introduction To \emph{Insektengericht} And Lessons Learned}
|
| 8 |
|
| 9 |
\emph{Insektengericht}\index{Insektengericht}
|
| 10 |
(German language: \emph{insect court}) is a word
|
| 11 |
we learned from a page of a \emph{Beavis and Butthead}\index{Beavis and Butthead}
|
| 12 |
comic book purchased
|
| 13 |
in the M\"unchen Hauptbahnhoff around 1995. In a page of this comic
|
| 14 |
book---titled \emph{Insektengericht}---Beavis and Butthead sit in judgement
|
| 15 |
of insects. Without exception, the verdict is
|
| 16 |
\emph{schuldig} (guilty), and the sentence is harsh
|
| 17 |
(\emph{Tod durch explodieren}, or ``death by explosion'', is typical in the
|
| 18 |
Beavis and Butthead schema of insect justice).
|
| 19 |
|
| 20 |
Just like Beavis and Butthead, in this section we sit in judgement of software
|
| 21 |
defects (or bugs)---probably with a similar conviction rate and similar
|
| 22 |
sentencing guidelines.
|
| 23 |
|
| 24 |
The importance of analyzing software defects can't be overemphasized.
|
| 25 |
The analysis of defects supplies valuable information about what
|
| 26 |
\emph{can} go wrong and what is \emph{most likely} to go wrong.
|
| 27 |
Because it isn't possible in any product development
|
| 28 |
process to eliminate \emph{all} types of
|
| 29 |
software defects, analysis of the relative frequency
|
| 30 |
of different types of software defects allows
|
| 31 |
one to concentrate on the ``hotspots'', or types of
|
| 32 |
software defects shown most likely to occur.
|
| 33 |
|
| 34 |
In this part of the work (\emph{Insektengericht}) we strive
|
| 35 |
to present each different \emph{type} of software defect we've
|
| 36 |
encountered, and we try to avoid presenting nearly
|
| 37 |
identical defects, as this is redundant and has no
|
| 38 |
instructional value. We haven't kept track of
|
| 39 |
the relative frequency of different types of defects.
|
| 40 |
|
| 41 |
We begin in this chapter with a mother lode of intermittent software defects,
|
| 42 |
interrupt service.
|
| 43 |
|
| 44 |
|
| 45 |
\section{Exercises}
|
| 46 |
|
| 47 |
|
| 48 |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
| 49 |
|
| 50 |
\noindent\begin{figure}[!b]
|
| 51 |
\noindent\rule[-0.25in]{\textwidth}{1pt}
|
| 52 |
\begin{tiny}
|
| 53 |
\begin{verbatim}
|
| 54 |
$RCSfile: c_ird0.tex,v $
|
| 55 |
$Source: /home/dashley/cvsrep/e3ft_gpl01/e3ft_gpl01/dtaipubs/esrgubka/c_ird0/c_ird0.tex,v $
|
| 56 |
$Revision: 1.2 $
|
| 57 |
$Author: dtashley $
|
| 58 |
$Date: 2001/07/01 20:37:27 $
|
| 59 |
\end{verbatim}
|
| 60 |
\end{tiny}
|
| 61 |
\noindent\rule[0.25in]{\textwidth}{1pt}
|
| 62 |
\end{figure}
|
| 63 |
|
| 64 |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
| 65 |
% $Log: c_ird0.tex,v $
|
| 66 |
% Revision 1.2 2001/07/01 20:37:27 dtashley
|
| 67 |
% Move out of binary mode for use with CVS.
|
| 68 |
%
|
| 69 |
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
| 70 |
% $History: c_ird0.tex $
|
| 71 |
%
|
| 72 |
% ***************** Version 2 *****************
|
| 73 |
% User: Dashley1 Date: 1/31/01 Time: 4:20p
|
| 74 |
% Updated in $/uC Software Multi-Volume Book (A)/Chapter, IRD0, Interrupt-Related Software Defects
|
| 75 |
% Edits.
|
| 76 |
%
|
| 77 |
% ***************** Version 1 *****************
|
| 78 |
% User: Dashley1 Date: 1/28/01 Time: 10:08p
|
| 79 |
% Created in $/uC Software Multi-Volume Book (A)/Chapter, IRD0, Interrupt-Related Software Defects
|
| 80 |
% Initial check-in.
|
| 81 |
%
|
| 82 |
%End of file C_IRD0.TEX
|
Parent Directory
| 
Revision Log