trunk/c_ird0/c_ird0.tex

%$Header$

\chapter{\cirdzerolongtitle{}}

\label{cird0}

\section{Introduction To \emph{Insektengericht} And Lessons Learned}

\emph{Insektengericht}\index{Insektengericht}
(German language:  \emph{insect court}) is a word
we learned from a page of a \emph{Beavis and Butthead}\index{Beavis and Butthead}
comic book purchased
in the M\"unchen Hauptbahnhoff around 1995.  In a page of this comic
book---titled \emph{Insektengericht}---Beavis and Butthead sit in judgement
of insects.  Without exception, the verdict is
\emph{schuldig} (guilty), and the sentence is harsh
(\emph{Tod durch explodieren}, or ``death by explosion'', is typical in the
Beavis and Butthead schema of insect justice).

Just like Beavis and Butthead, in this section we sit in judgement of software
defects (or bugs)---probably with a similar conviction rate and similar
sentencing guidelines.

The importance of analyzing software defects can't be overemphasized.
The analysis of defects supplies valuable information about what 
\emph{can} go wrong and what is \emph{most likely} to go wrong.
Because it isn't possible in any product development
process to eliminate \emph{all} types of
software defects, analysis of the relative frequency
of different types of software defects allows
one to concentrate on the ``hotspots'', or types of
software defects shown most likely to occur.

In this part of the work (\emph{Insektengericht}) we strive
to present each different \emph{type} of software defect we've
encountered, and we try to avoid presenting nearly
identical defects, as this is redundant and has no 
instructional value.  We haven't kept track of 
the relative frequency of different types of defects.

We begin in this chapter with a mother lode of intermittent software defects, 
interrupt service.


\section{Exercises}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\noindent\begin{figure}[!b]
\noindent\rule[-0.25in]{\textwidth}{1pt}
\begin{tiny}
\begin{verbatim}
$HeadURL$
$Revision$
$Date$
$Author$
\end{verbatim}
\end{tiny}
\noindent\rule[0.25in]{\textwidth}{1pt}
\end{figure}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 
%End of file C_IRD0.TEX
1	dashley	140	%$Header$
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	dashley	278	$HeadURL$
55			$Revision$
56			$Date$
57			$Author$
58	dashley	140	\end{verbatim}
59			\end{tiny}
60			\noindent\rule[0.25in]{\textwidth}{1pt}
61			\end{figure}
62
63	dashley	278	%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
64	dashley	140	%
65			%End of file C_IRD0.TEX
Name	Value
svn:eol-style	native
svn:keywords	Author Date Id Revision URL Header