\markboth{Chao}{Chao}
%%%%%% TEMPLATE.TEX for WISR'93, version 1.2, 4/22/93 %%%%%%
%%%%%% Updated by Jeffrey S. Poulin, May 1993         %%%%%%
 
\documentstyle[11pt]{article}
 
% Standard Spacing for WISR - do not change!!
%
% Page dimensions.
%
\oddsidemargin  0.26in % Leave enough for binding margin
\evensidemargin 0.26in %
\topmargin      -1.00in % (adjusted for printer bias)
\headheight      .00in  % (no headers)
\headsep         .75in  % (top margin + headers + skip)
\footheight     12.0pt  % ??? (seems to work ok)
\footskip       25.0pt  % ??? ( "   "  )
\textheight     9.425in % (instructions: 9 1/8" min, 9 7/16" max)
\textwidth      6.5in   %
%
% Paragraph changes.
%
 
\markboth{Chao}{Chao}
\pagestyle{myheadings}

\parindent=0pt
\parskip=10pt
%
% can make the title box even smaller
%
\def\@maketitle{\vbox to 2.6in{\hsize\textwidth
    \linewidth\hsize \vfil \centering
    {\large \@title \par}
    \vskip 2em
    {\normalsize
    \begin{tabular}[t]{c}\@author
    \end{tabular}\par}
    \vfil}
}
 
\begin{document}
 
\bibliographystyle{ieeetr}
 
\title{Software Reuse: Major Issues Need to Be Resolved Before Benefits
Can Be Achieved}
 
\author{David Chao\\
\\
U.S. General Accounting Office\\
441 G Street, N.W.\\
Techworld - Room 9715\\
Washington, DC  20548\\
Tel: 202-512-6354\\
Email: chaod@source.asset.com  OR  cvy@cu.nih.com\\
Fax: 202-512-6450\\
}
\date{}
 
\maketitle
 
\begin{abstract}

On February 7, 1992 the Chairman of the Subcommitte on Defense,
House Appropriations Committee, requested that we provide
background information on software reuse, including an overview
of issues that can inhibit effective software reuse, and
information on Defense's strategy to implement a departmentwide
software reuse program.


\vspace{0.2in}
\noindent
{\bf Keywords:} Reuse inhibitors, US Government, General Accounting Office
 
\vspace{0.2in}
\noindent
{\bf Workshop Goals:} To keep abreast of state of the art and state of the
practice in software reuse
 
\vspace{0.2in}
\noindent
{\bf Working Groups:} 
Reuse management, organization, and economics.
 
\end{abstract}
 
\newpage
 
\section{Position}

Developing and maintaining software in organizations such as the
Department of Defense is very costly.  According to many experts
in the software community, software reuse is a possible solution
to reduce these costs, as well as to increase software productivity
and reliability.  Although these benefits and savings are
compelling, achieving them will require the resolution of
significant technical, organizational, and legal issues.

Even while proclaiming the potential of reuse, many software experts
have questioned the maturity of software reuse.  These experts
indicate that the methodologies to implement reuse have not been
fully developed, tools to support a reuse process are lacking, and
standards to guide critical software reuse activities have not
been established.

Beyond such technical difficulties, organizations also face
numerous challenges to effectively implement and practice
reuse.  An organization must make a significant commitment to reuse
because fundamental changes in the organization's software
development approach will be needed and significant up-front costs
for training and tools will be required.  Further, uncertainties in
legal policies, such as liability and intellectual property rights
that currently hinder software reuse, need to be addressed, and
acquisition policies need to be modified to better promote reuse.

Additional information regarding these results can be found in:
GAO Report: GAO/IMTEC-93-16.  Software Reuse - Major Issues Need
to Be Resolved Before Benefits Can Be Achieved, January 1993.

 
 
\section{Biography}
 
David Chao is a Senior Technical Advisor with the Accounting and
Information Management Division of the General Accounting Office.
He is currently involved in the follow-on review of DoD's strategy
to implement software reuse and the effectiveness of its approach.
In addition, he was involved in the review of DoD's Integrated-
Computer Aided Software Engineering (I-CASE) procurement, which a
report was published in June 1993.  Previously, he has held software
Engineering positions with Texas Instruments Incorporated and
McDonnell Douglas Corporation, in the design and development of
business and scientific applications.

\end{document}
