Dear Reuser, WISR'x will again bring together the leading researchers and practitioners in Software Reuse. Because this workshop emphasizes the exchange of information and experience, we seek short position papers rather than full length submissions. Please do not send a full paper! Below you will find a LATEX template for you to follow when preparing your position paper. For those not familiar with LATEX, the template includes a short tutorial. We provide a printed copy of the WISR proceedings at the workshop and like to have all papers in a common format. We also maintain softcopies of the papers and working group reports for future reference. For this reason we need to have an electronic version of your submission. (See below for instructions on how to get the proceedings of past workshops.) We prefer (by far!) that you use the LATEX template to prepare your position paper. If you cannot, please submit your paper in one of the formats below, listed in order of preference. In any case, we ask that you provide a "flat-ascii" file (via e-mail or diskette) that we may use for our on-line records. In all cases please mail me a hardcopy of your position paper as a backup. First choice: LATEX Second choice: Microsoft Word Third Choice: Flat file (ascii) Fourth (distant) Choice: (IF ALL ELSE FAILS, send us a hardcopy following the suggested format as best you can.) We also solicit proposals for WORKING GROUP topics and leaders. Responsibilities of the working group leaders include preparing an initial structure for their session, moderating the group's efforts throughout the workshop, and reporting on the working group findings. Anyone interested in chairing a working group may send an informal proposal to me outlining the topic and how/what you would like to accomplish. The program committee will select the final working groups and chairpersons based on interest and strength of your proposal; we will give first consideration to proposals that include some advance preparation so that the working group may quickly build on last year's work (See how to get a summary of last year's workshop, below). Thank-you. -Kevin and Larry Co-Chairs, WISR'7 ======================================= Kevin Wentzel Hewlett Packard Laboratories 1501 Page Mill Road, Palo Alto, CA 94303 Telephone (415)857-4018 Fax: (415)857-8526 e-mail: wentzel@hpl.hp.com Larry Latour University of Maine Department of Computer Science 222 Neville Hall Orono, Maine, 04469 Telephone: (207)581-3523 Fax: (207)581-4977 e-mail: larry@gandalf.umcs.maine.edu ======================================================================= HOW TO OBTAIN PROCEEDINGS OF PAST WORKSHOPS You may obtain copies of the Proceedings of the past four WISR proceedings (WISR'4-7) via anonymous ftp to: gandalf.umcs.maine.edu (/pub/WISR/wisrN directory, where N represents the workshop number) A summary of the WISR'5 working group reports also appears in the April 1993 issue of the ACM SIGSOFT Software Engineering Notes. For additional information, contact: Larry Latour University of Maine Department of Computer Science 222 Neville Hall Orono, Maine 04469 tel: (207)581-3523, fax.x.4977 e-mail: larry@gandalf.umcs.maine.edu ======================================================================= %%%%%% TEMPLATE.TEX for WISR'93, version 1.2, 4/22/93 %%%%%% %%%%%% Updated by Jeffrey S. Poulin, May 1993 %%%%%% %%%%%% Updated by Larry Latour, March, 1995 \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 75.0pt % ??? ( " " ) \textheight 9.425in % (instructions: 9 1/8" min, 9 7/16" max) \textwidth 6.5in % % % Paragraph changes. % \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{alpha} \title{The Craft of Preparing a Winning WISR'95 Reuse Position Paper} \author{Kevin Wentzel\\ \\ Hewlett Packard Laboratories\\ 1501 Page Mill Road, Palo Alto, CA 94303\\ Tel: (415) 857-4018\\ Fax: (415) 857-8526\\ Email: wentzel@hpl.hp.com\\ \\ Larry Latour\\ \\ University of Maine\\ Department of Computer Science\\ 222 Neville Hall\\ Orono, Maine, 04469\\ Tel: (207) 581-3523\\ Fax: (207) 581-4977\\ Email: larry@gandalf.umcs.maine.edu\\ } \date{} \maketitle \begin{abstract} If you submitted a position paper over the past few years, this process has not changed much. In fact, we owe this "how to" file to Martin Griss of Hewlett-Packard and Larry Latour of the University of Maine, who prepared it for the '92 Palo Alto WISR workshop! This short article provides reusable guidelines on writing a WISR position paper in the suggested \LaTeX\ workshop format. It is {\em important} for prospective contributors to realize that they should {\bf not} submit {\bf research papers}, but {\bf position papers}! A position paper is between 3 and 5 pages long and must follow a certain format. It starts off with an {\bf Abstract} which includes a succinct list of {\bf Keywords, Workshop Goals} and preferred {\bf Working Group} affiliations. The main body of the paper consists of three sections: {\bf Background, Position,} and {\bf Comparison} followed by the {\bf References} and {\bf Biography} sections. \vspace{0.2in} \noindent {\bf Keywords:} Reuse, position paper, \LaTeX\ guidelines, practice \vspace{0.2in} \noindent {\bf Workshop Goals:} Learning; networking; advance state of theory of reusable position papers. \vspace{0.2in} \noindent {\bf Working Groups:} reuse process models, reuse education, position paper guidelines. \end{abstract} \newpage \section{Background} This set of guidelines are written using \LaTeX\ in the way we expect the position paper itself to be written. You could simply take a copy of this file ({\em template.tex}), and begin to edit your text in place of the example.\footnote{We recommend that you name your file using the first author name, as {\em author.tex}.} You can also refer to a printed copy, obtainable by running \LaTeX\ on this ``template.tex'' file, or request that we mail or FAX a printed copy to you. If you are unfamiliar with \LaTeX, you might be able to use this printed text and sample {\em template.tex} file as a guide. \section{Position} Based on our prior experience with WISRs '91, '92, and '93, the position paper should be no longer than 3-5 pages, about 2000 words. It should be written specifically as a position paper, rather than as a regular research paper. The goal is to highlight succinctly your involvement, interest, and experience with reuse, and to state a position, hypothesis, opinion, theory, research or practical result that will enable the selection committee to quickly determine what area your work addresses, and your contribution/involvement with the workshop. \subsection{Position Paper Format} To make the reviewing process effective, the paper should include at least the following sections, with other sections and subsections as appropriate: \begin{description} \item[{\bf Cover Page:}] Should include a title, author names, addresses and email/FAX/telephone (for subsequent communication about workshop). \item[{\bf Abstract:}] Should include a 100-200 word abstract and 5-10 keywords (or key phrases). \item[{\bf Workshop Goals:}] Should indicate goals for participation in workshop. \item[{\bf Working Groups:}] Should indicate which of several working group areas you would like to participate in, including but not limited to (combinations of):\footnote{More details on proposed working groups will be created from responses and mailed later.} \begin{itemize}\itemsep -3pt \item Reuse process models \item Reuse maturity models \item Reuse management, organization and economics \item Reuse terminology standards \item Domain analysis/engineering \item Design guidelines for reuse - general, Ada, and/or C++ \item Reuse and OO methods \item Reuse and formal methods \item Useful and collectible metrics \item Reusable component certification \item Tools and environments \item Reuse handbook \item Education \end{itemize} \item[{\bf Background:}] summarize your involvement in software reuse. \item[{\bf Position:}] a statement on a problem in the state of the art or state of the practice of software reuse that interests you and how your work has improved or will improve the state of the art or state of the practice. \item[{\bf Comparison:}] discuss at least 2 or 3 references to work being done similar to yours comparing your approach/results and theirs. \item[{\bf References:}] this is done automatically by \LaTeX, when you submit a .bib file. \item[{\bf Biography:}] this contains more general information than in the {\bf Background} section, which just deals with reuse experience. \end{description} \subsection{Figures} Figures should be ideally provided in embedded \LaTeX\ picture commands or included ``PostScript'' format, reserving space for them using the \LaTeX {\em \verb+ \begin {figure} +} and {\em \verb+ \end{figure}+ } commands. \LaTeX\ provides some low-level drawing commands, which can be created by hand or by using tools such as {\em XFIG.} \begin{figure*}[t] \vspace{2in} \caption{This reserves space for a 2 inch figure} \label{fig:1} \end{figure*} If you are using ``PostScript'' pictures, separate the ``PostScript'' into separate files so that pictures can be generated independently, one by one\footnote{Using the {\em special} command within {\em dvips} caused some problems last year.}. \begin{verbatim} \begin{figure*}[t] \special{PS: include "author-fig1.ps"} \vspace{3 in} \caption{Here is figure 1} \label{fig:1} \end{figure*} \end{verbatim} If neither of these methods work for you, and you still need include a figure, we can do a final ``cut and paste'' if you provide figure originals on paper, leaving appropriately sized spaces in the text, as in Figure~\ref{fig:1}, created by the \LaTeX\ commands: \begin{verbatim} \begin{figure*}[t] \vspace{2in} \caption{This reserves space for a 2 inch figure} \label{fig:1} \end{figure*} \end{verbatim} \section{Paper Submission} Position papers are due by May 1st. The favored route is email: \begin{enumerate} \item The best route is to email your \LaTeX\ submission to Kevin Wentzel at {\em wentzel@hpl.hp.com }, as a pair of files: {\em author.tex} and {\em author.bib}; also, send a paper copy by USMAIL or FEDEX. \item If your \LaTeX\ file includes ``PostScript'' pictures, separate the ``PostScript'' files so that pictures can be generated independently, one by one. Name the files as {\em author-fig1.tex},{\em author-fig2.tex}, etc. Mark the back of the paper copies of the figures with the same name. \item If you cannot create a \LaTeX\ file, send plain ASCII (or ``PostScript'' files + ASCII version + text formatter version if not \LaTeX) by email and a paper copy by USMAIL or FEDEX. \item If this is not feasible, send \LaTeX\ or ASCII or ``PostScript'' by floppy with paper copy. \item If all else fails, send a USMAIL/FEDEX plain paper. \end{enumerate} \subsection{Last Year's Experience} For past WISR proceedings, most submissions were in \LaTeX\ and presented minimal trouble. The most hassle was with non-\LaTeX\ stuff and \LaTeX\ with pictures. We had to work with submitters, one on one, to clean up the final draft (either through email and/or mail and/or phone and/or Fax...). Page numbering is {\em not} a problem. We will adjust your submissions to fit our proceedings needs. \section{Minimal Introduction to \LaTeX} These notes are not a complete guide, but may help understand the examples used within this short paper. Comments in the file are lines started with a \% (percent sign) and continue to end of line. Most \LaTeX\ commands start with the `backslash character' \verb+\+ character, followed by a keyword, followed by parameters, usually enclosed in `curly braces': \verb+ { and }+. Sections and subsections are started by the lines: \begin{verbatim} \section{Section Title} \subsection{Subsection Title} \end{verbatim} Bold faced text appears like this: {\bf This piece should be bold}. Emphasized (italic text) appears like this: {\em This should be emphasized}. \subsection{Bulleted and Enumerated Lists} A region of lists is bracketed by a {\em \verb+ \begin{list-type} + } and {\em \verb+ \end{list-type} + } pair, mentioning the list type. Individual list items are introduced by the {\em \verb+ \item +} command. We recommend the use of only the following forms of lists: \subsubsection{Itemized Lists} \begin{itemize} \item First bulleted line. \item Second bulleted line. An unbulleted line under the second bulleted line. \item Third bulleted line \end{itemize} \subsubsection{Description Lists} \begin{description} \item[{\bf First line.}] Here we need a long piece of text to show how the outdenting of the leading item sets off the paragraph. \item[{\bf Second line.}] Also has a paragraph of text following it to show outdenting. Another line under the description heading. \item[{\bf Third line}] this is actually the last line. \end{description} \subsubsection{Enumerated Lists} \begin{enumerate}\itemsep -3pt \item First line. \item Second line. An unmarked line under the second line. \item Third bulleted line \end{enumerate} \noindent {\bf Notice} that this list is compact because {\em \verb+ \begin{enumerate}\itemsep -3pt + } was used to start the list. \subsection{References} References are generated by the use of {\em \verb+ \cite {key} +}, where {\em key} is a bibliography citation key, usually constructed from author name and last 2 digits of the year, such as {\em lubars90} or {\em biggerstaff86c}. The additional letters {\em a, b, c, } etc. are used to disambiguate if more than one paper appears in the same year. The citation will appear in the text as: \cite{lubars90} for {\em lubars90}, and \cite{biggerstaff86c,biggerstaff86d} for two papers by {\em biggerstaff} in 1986. The order list of references will be inserted at the appropriate point in the document, by using the {\em \verb+ \bibliography +} command. The references are extracted by citation key from a bibliography file, called a {\em .bib} file. For the {\em template.tex} file, this is {\em template.bib}. The {\em .bib} file should mimic the structure of the file {\em template.bib}. Each citation has a structure similar to: \begin{verbatim} @techreport(lubars90, AUTHOR="M.D. Lubars", INSTITUTION="Microelectronics and Computer Technology Corporation", TITLE="{The ROSE-2 Strategies for Supporting High-Level Software Design Reuse}", YEAR="1990", Number="STP-303-90") \end{verbatim} The first line indicates the type of citation {\em article, techreport, book, inproceedings, } etc., and the citation key. The subsequent lines provide a required or optional fields for the {\em author, title, month, year, journal, booktitle, publisher}\/ or {\em institution} as appropriate. \bibliography{template} \section{Biography} {\em Include a short biography for each author. The following is an example:} {\bf Martin L. Griss} is Principal Laboratory Scientist for Software Engineering at Hewlett-Packard Laboratories, Palo Alto. He leads research on software reuse, software-bus frameworks, and hypertext-based reuse tools. He works closely with HP Corporate Engineering to systematically introduce software reuse into HP's software development processes. He was previously Director of HP's Software Technology Laboratory, researching expert systems, object-oriented databases, programming technology, human-computer interaction, and distributed computing. Before that, he was an Associate Professor of Computer Science at the University of Utah, working on computer algebra and portable LISP systems (PSL). He received a Ph.D. in Physics from the University of Illinois in 1971. \end{document} %%%%%% TEMPLATE.BIB for WISR'92, version 1.0, 6/26/92 %%%%%% @techReport(lubars90, AUTHOR="M.D. Lubars", INSTITUTION="Microelectronics and Computer Technology Corporation", KEY="Lubars", TITLE="{The ROSE-2 Strategies for Supporting High-Level Software Design Reuse}" , YEAR="1990", Number="STP-303-90") @techReport(basili91, Key="Basili", Author="V.R. Basili and H.D. Rombach", Title="{Support for Comprehensive Reuse}", Number="UMIACS-TR-91-23", Year="1991", Month="February", Address="College Park, Md.", Institution="University of Maryland") @article(frakes90, Key="Frakes", Author="W.B. Frakes and P.B. Gandel", Title="{Representing Reusable Software}", Year="1990", Month="December", Volume="32", Number="10", PAges="653-664", Journal="Information and Software Technology") @TechReport(tracz92a, Key="Tracz", Author="W. Tracz and L. Coglianese", Title="{Domain Engineering Process Guidelines}", Year="1992", Month="March", Institution="IBM Federal Sector Division", Number="ADAGE-IBM-92-02") @TechReport(prieto-diaz91d, Key="PrietoDiaz", Author="R. Prieto-Diaz", Title="{Reuse Library Process Model}", Year="1991", Month="July", Institution="STARS", Number="AD-B157091, IBM CDRL 03041-002") @TechReport(kang90, Key="Kang", Author="K.C. Kang and S.G. Cohen and J.A. Hess and W.E. Novak and A.S. Peterson ", Title="{Feature-Oriented Domain Analysis (FODA) Feasibility Study}", Year="1990", Month="November", Institution="Software Engineering Institute", Number="CMU/SEI-90-TR-21") @Article(kaneko86a, Key="Kaneko", Pages="11-14", Author="S. Kaneko", Volume="42", Number="8", Title="Technology for Development and Reuse of Software Parts", Year="1986", Note="in Japanese", Journal="Toshiba Review") @Inproceedings(goguen89f, Key="Goguen", Author="J.A. Goguen", Title="{Principles of Parameterized Programming}", BookTitle="{Software Reusability Volume I, Concepts and Models}", Year="1989", Editors="T. Biggerstaff and A. Perlis", Publisher="Addison-Wesley Publishing Company") @Inproceedings(mcilroy69, Key="McIlroy", Author="M.D. McIlroy", Title="{Mass Produced Software Components}", Year="1969", Pages="88-98", editors="P. Naur and B. Randell and J.N. Buxton", Publisher="Petrocelli/Charter",Address="New York", BookTitle="{Proceedings of NATO Conference on Software Engineering}") @Article(johnson88, Key="Johnson", Author="R.E. Johnson and B. Foot", Title="{Designing Reusable Classes}", PAges="22-35", Year="1988", Month="June/July", Number="1",Volume="2", Journal="Journal of Object-Oriented Programming") @Inproceedings(arango89, key="Arango", title="{Domain Analysis: From Art to Engineering Discipline}", Year="1989", pages="152-159", Author="G. Arango", Month="May 19-20", BookTitle="{Proceedings Fifth International Workshop on Software Specification and Design}") @Article(biggerstaff84, Title="{Forward: Special Issue on Software Reusability}", Key="Biggerstaff", PAges="474-476", Author="T.J. Biggerstaff and A.J. Perlis", Number="5", Volume="SE-10", Year="1984", Month="September", Journal="IEEE Transactions on Software Engineering") @Incollection(matsumoto87, Key="Matsumoto", Author="Y. Matsumoto", Title="{A Software Factory: An Overall Approach to Software Production}", Year="1987", Publisher="IEEE Computer Society Press", Editor="Peter Freeman", Pages="155-178", BookTitle="{Tutorial: Software Reusability}") @Inproceedings(tracz87b, Key="Tracz", Author="W. Tracz", Title="{Software Reuse: Motivators and Inhibitors}", Year="1987", Month="February", BookTitle="{Proceedings of COMPCON87}") @Article(prieto-diaz87, Key="Prieto", PAges="6-16", Author="R. Prieto-Diaz and P. Freeman", Volume="4", Number="1", Title="{Classifying Software for Reusability}", Year="1987", Month="January", Journal="IEEE Software") @Article(biggerstaff87b, Key="Biggerstaff", PAges="41-49", Author="T. Biggerstaff and C. Richter", Volume="4", Number="2", Title="{Reusability Framework, Assessment and Directions}", Year="1987", Month="March", Journal="IEEE Software") @Inproceedings(bailin88, Key="Bailin", Author="Bailin, S.C.", Title="{An Environment for Reusing Software Life-Cycle Products}", Year="1988", Month="April 13-14", Address="Washington, D.C.", Publisher="National Institute of Software Quality and Productivity", BookTitle="{Proceedings, National Conference on Software Reuseability}") @techReport(batory91, AUTHOR="D.S. Batory and S.W. O'Malley", INSTITUTION="University of Texas", KEY="Batory", TITLE="{The Design and Implementation of Hierarchical Software Systems}", YEAR="1991", Number="TR-91-22") @Article(tracz88e, Key="Tracz", Author="W. Tracz", Volume="13", Number="4", Title="{Software Reuse Maxims}", Year="1988", Month="October", PAges="28-31", Journal="ACM Software Engineering Notices") @Article(tracz91, Key="Tracz", Author="W. Tracz", Volume="16", Number="3", Title="{A Conceptual Model for Megaprogramming}", Year="1991", Month="July", Pages="36-45", Journal="ACM Software Engineering Notices") @article(honiden86, AUTHOR="S. Honiden and N. Sueda and A. Hoshi and N. Uchihira and K. Mikame", JOURNAL="Journal of Information Processing (JAPAN)", KEY="Honiden", TITLE="{Software Prototyping with Reusable Components}", YEAR="1986", Number="3", Pages="123-129", Volume="9") @techReport(biggerstaff86c, AUTHOR="Biggerstaff, T.J.", INSTITUTION="Microelectronics and Computer Technology Corporation", KEY="Biggerstaff", TITLE="{Research Problems in Automating the Reuse of Designs}", YEAR="1986", Month="June", Number="STP-197-86") @techReport(biggerstaff86d, AUTHOR="Biggerstaff, T.J.", INSTITUTION="Microelectronics and Computer Technology Corporation", KEY="Biggerstaff", TITLE="{Reusability Overview}", YEAR="1986", Month="May", Number="STP-168-86") @InProceedings(yamaoto86, AUTHOR="Yamamoto, S., and Isoda, S.", BOOKTITLE="{Proceedings of 10th Anniversary COMSAC '86}", KEY="Yamamoto", ORGANIZATION="IEEE Computer Society Press", TITLE="{SoftDA: A Reuse Oriented Design System}", YEAR="1986", Pages="284-290") @InProceedings(matsumoto86c, AUTHOR="Matsumoto, Y.", BOOKTITLE="Proceedings of 1986 National Computer Conference", KEY="Matsumoto", ORGANIZATION="AFIPS Press", TITLE="{Experiences in Software Manufacturing}", YEAR="1986", Pages="93-94") @InProceedings(prieto-diaz87a, AUTHOR="Prieto-Diaz, R.", BOOKTITLE="Proceedings of COMPSAC 87", KEY="Prieto-Diaz", TITLE="{Domain Analysis for Reusability}", YEAR="1987") @article(cardelli85, AUTHOR="Cardelli, L., and Wegner, P.", JOURNAL="Computing Surveys", KEY="Cardelli", TITLE="{On Understanding Types, Data Abstractions, and Polymorphism}", YEAR="1985", Number="4", Pages="471-522", Volume="17") @Article(parnas76, Title="{On the Design and Development of Software Families}", Key="Parnas", PAges="1-9", Author="D.L. Parnas", Number="1", Volume="SE-2", Year="1976", Month="January", Journal="IEEE Trans. Software Engineering") @book(cusumano91, Title="{Japan's Software Factories}", Key="Cusumano", Author="M.A. Cusumano", Year="1991", Publisher="Oxford University Press") @Article(jones84, Title="{Reusability in Programming: A Survey of the State of the Art}", Key="Jones", PAges="488-493", Author="T.C. Jones", Number="5", Volume="SE-10", Year="1984", Month="September", Journal="IEEE Transactions on Software Engineering") @Article(lanergan84, Title="{Software Engineering with Reusable Design and Code}", Key="Lanergan", PAges="498-501", Author="R.G. Lanergan and C.A. Grasso", Number="5", Volume="SE-10", Year="1984", Month="September", Journal="IEEE Transactions on Software Engineering") @Inproceedings(breuer89, Key="Breuer", Author="P.T. Breuer and K. Lano", Title="{REDO at Oxford}", Year="1989", Pages="39-49", Month="November", editors="L. Dusink and P.A. Hall", Publisher="Springer-Verlag", BookTitle="{Proceedings of the Software Re-use Workshop}") @Inproceedings(cramer89, Key="Cramer", Author="J. Cramer and H. Hunnekens and W. Schafer and S. Wolf", Title="{The MERLIN Approach to the Re-use of Software Components}", Year="1989", Pages="57-75", Month="November", editors="L. Dusink and P.A. Hall", Publisher="Springer-Verlag", BookTitle="{Proceedings of the Software Re-use Workshop}")