@Preamble{"\ifx \undefined \booktitle \def \booktitle #1{{{\em #1}}} \fi"}
@String{ack-nhfb = "Nelson H. F. Beebe,
University of Utah,
Department of Mathematics, 110 LCB,
155 S 1400 E RM 233,
Salt Lake City, UT 84112-0090, USA,
Tel: +1 801 581 5254,
FAX: +1 801 581 4148,
e-mail: \path|beebe@math.utah.edu|,
\path|beebe@acm.org|,
\path|beebe@computer.org| (Internet),
URL: \path|http://www.math.utah.edu/~beebe/|"}
@String{j-SIGSOFT = "ACM SIGSOFT Software Engineering Notes"}
@Article{Wasserman:1976:TVS,
author = "Anthony Ira Wasserman",
title = "A top-down view of software engineering",
journal = j-SIGSOFT,
volume = "1",
number = "1",
pages = "8--14",
month = may,
year = "1976",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010726.1010727",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:16 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Kernighan:1976:ST,
author = "B. W. Kernighan and P. J. Plauger",
title = "Software tools",
journal = j-SIGSOFT,
volume = "1",
number = "1",
pages = "15--20",
month = may,
year = "1976",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010726.1010728",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:16 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Building on the work of others is the only way to make
substantial progress in any field. Yet computer
programming continues as a cottage industry because
programmers insist on reinventing programs for each new
application, instead of using what already exists. We
must encourage a way of packaging programs so that they
can be perceived as standard tools, each performing its
specialized task sufficiently well and interfacing to
other tools so conveniently that programmers seldom
feel any need to make their own version from scratch.
In this paper we show how programmers can view
substantial parts of what they do as tool building and
tool using. By studying some specific examples of
general purpose tools, we show how programs can be
packaged as tools, so other programmers will use them
in preference to building their own. We also comment on
the sort of programming environment which seems most
hospitable to the development and use of tools.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Reifer:1976:SSS,
author = "Donald J. Reifer",
title = "The smart stub as a software management tool",
journal = j-SIGSOFT,
volume = "1",
number = "2",
pages = "4--8",
month = oct,
year = "1976",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010680.1010681",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:17 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This note explains how the smart stub concept (also
called a performance stub) can be used by management to
improve its visibility and control during the top-down
development of large, complex structured programming
projects. Presently, program stubs are dummy segments
of code that serve as place holders for lower level
modules not yet completed as part of the present build.
Smart stubs augment these dummies with segments of code
that model the budgeted storage and timing resources
that will be consumed by the to-be-completed module.
How smart stubs can be integrated into the top-down,
structured programming methodology to provide early
visibility is discussed.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1976:ASE,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering",
journal = j-SIGSOFT,
volume = "1",
number = "2",
pages = "9--32",
month = oct,
year = "1976",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010680.1010682",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:17 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1977:ASEa,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering: part 2",
journal = j-SIGSOFT,
volume = "2",
number = "1",
pages = "6--14",
month = jan,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010723.1010724",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:18 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Ambler:1977:GLS,
author = "Allen L. Ambler and Donald I. Good and James C. Browne
and Wilhelm F. Burger and Richard M. Cohen and Charles
G. Hoch and Robert E. Wells",
title = "{Gypsy}: a language for specification and
implementation of verifiable programs",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "1--10",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808306",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "An introduction to the Gypsy programming and
specification language is given. Gypsy is a high-level
programming language with facilities for general
programming and also for systems programming that is
oriented toward communications processing. This
includes facilities for concurrent processes and
process synchronization. Gypsy also contains facilities
for detecting and processing errors that are due to the
actual running of the program in an imperfect
environment. The specification facilities give a
precise way of expressing the desired properties of the
Gypsy programs. All of the features of Gypsy are fully
verifiable, either by formal proof or by validation at
run time. An overview of the language design and a
detailed example program are given.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Popek:1977:NDE,
author = "G. J. Popek and J. J. Horning and B. W. Lampson and J.
G. Mitchell and R. L. London",
title = "Notes on the design of {Euclid}",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "11--18",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808307",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Euclid is a language for writing system programs that
are to be verified. We believe that verification and
reliability are closely related, because if it is hard
to reason about programs using a language feature, it
will be difficult to write programs that use it
properly. This paper discusses a number of issues in
the design of Euclid, including such topics as the
scope of names, aliasing, modules, type-checking, and
the confinement of machine dependencies; it gives some
of the reasons for our expectation that programming in
Euclid will be more reliable (and will produce more
reliable programs) than programming in Pascal, on which
Euclid is based.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Fischer:1977:EIO,
author = "Charles N. Fischer and Richard J. LeBlanc",
title = "Efficient implementation and optimization of run-time
checking in {PASCAL}",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "19--24",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808308",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Complete run-time checking of programs is an essential
tool for the development of reliable software. A number
of features of the programming language PASCAL (arrays,
subranges, pointers, record variants (discriminated
type unions), formal procedures, etc.) can require some
checking at run-time as well as during compilation. The
problem of efficiently implementing such checking is
considered. Language modifications to simplify such
checking are suggested. The possibility of optimizing
such checking is discussed.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Ambler:1977:SPP,
author = "Allen L. Ambler and Charles G. Hoch",
title = "A study of protection in programming languages",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "25--40",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808309",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The concept of ``protection'' in programming languages
refers to the ability to express directly in the
language the desired access control relationships for
all objects defined in the language. The use of such
mechanisms as data types, scope, parameter passing
mechanisms, routines as parameters, abstract data
types, and capabilities in Pascal, Concurrent Pascal,
Euclid, Clu, and Gypsy are explored via a simple
example which embodies many protection problems. The
usefulness of language defined and enforced protection
mechanisms to the process of formal verification is
discussed.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Friedman:1977:AAP,
author = "Daniel P. Friedman and David S. Wise",
title = "Aspects of applicative programming for file systems
(Preliminary Version)",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "41--55",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808310",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This paper develops the implications of recent results
in semantics for applicative programming. Applying
suspended evaluation (call-by-need) to the arguments of
file construction functions results in an implicit
synchronization of computation and output. The
programmer need not participate in the determination of
the pace and the extent of the evaluation of his
program. Problems concerning multiple input and
multiple output files are considered: typical behavior
is illustrated with an example of a rudimentary text
editor written applicatively. As shown in the trace of
this program, the driver of the program is the
sequential output device(s). Implications of
applicative languages for I/O bound operating systems
are briefly considered.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Herriot:1977:TIP,
author = "Robert G. Herriot",
title = "Towards the ideal programming language",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "56--62",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808311",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "A programming language with good features and notation
can help the programmer represent his abstractions in
the programming language, and can also help someone
else understand the original abstraction. There have
been numerous proposals for better features. In this
paper we propose several new ideas to improve the
notation. First we suggest that class instances be
named with a sequence of identifiers consisting of the
class name preceded by modifiers. Then we propose that
prepositions be placed before procedure parameters to
suggest their role. Finally, we suggest that
applicative and imperative operations can be separated
semantically, and then recombined syntactically through
the use of the ``which'' and passive operators.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Guttag:1977:SEA,
author = "Jhon V. Guttag and Ellis Horowitz and David R.
Musser",
title = "Some extensions to algebraic specifications",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "63--67",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808312",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Algebraic specifications of abstract data types are
beginning to gain wide currency. In this paper we
discuss an extension to this specification technique
which allows the specification of procedures which
alter their parameters, and various ways of handling
the specification of error conditions.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Buckle:1977:RDT,
author = "Normand Buckle",
title = "Restricted data types, specification and enforcement
of invariant properties of variables",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "68--76",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808313",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "When defining a data type, it is often useful to
specify restrictions on the permitted values of that
type. Pascal's subrange type declaration, a special
case of this kind of constraint definition, has already
proved itself to be quite useful. Restricted data types
allow more complex constraints to be defined and
checked; for example, a variable could be declared of
type ``odd integer'' or the day field of a ``date''
type variable could be checked for consistency with the
year and month fields. A simple mechanism is proposed,
allowing the formulation of such constraints and their
association with data types; the behaviour of a
restricted type variable is described. The effects of
the use of such a mechanism on program reliability,
readability and efficiency are discussed.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Cousot:1977:SDD,
author = "Patrick Cousot and Radhia Cousot",
title = "Static determination of dynamic properties of
generalized type unions",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "77--94",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808314",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The classical programming languages such as PASCAL or
ALGOL 68 do not provide full data type security.
Run-time errors are not precluded on basic operations.
Type safety necessitates a refinement of the data type
notion which allows subtypes. The compiler must also be
able to ensure that basic operations are applicable.
This verification consists in determining a local
subtype of globally declared variables or constants.
This may be achieved by improved compiler capabilities
to analyze the program properties or by language
constructs which permit the expression of these
properties. Both approaches are discussed and
illustrated by the problems of access to records via
pointers, access to variants of record structures,
determination of disjoint collections of linked
records, and determination of integer subrange. Both
approaches are complementary and a balance must be
found between what must be specified by the programmer
and what must be discovered by the compiler.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Melliar-Smith:1977:SRR,
author = "P. M. Melliar-Smith and B. Randell",
title = "Software reliability: The role of programmed exception
handling",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "95--100",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808315",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The paper discusses the basic concepts underlying the
issue of software reliability, and argues that
programmed exception handling is inappropriate for
dealing with suspected software errors. Instead it is
shown, using an example program, how exception handling
can be combined with the recovery block structure. The
result is to improve the effectiveness with which
problems due to anticipated faulty input data, hardware
components, etc., are dealt with, while continuing to
provide means for recovering from unanticipated faults,
including ones due to residual software design
errors.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{MacLaren:1977:EHP,
author = "M. Donald MacLaren",
title = "Exception handling in {PL/I}",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "101--104",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808316",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The PL/I language's facilities for handling
exceptional conditions are analyzed. The description is
based on the new PL/I standard. Special attention is
given to fine points which are not well known. The
analysis is generally critical. It emphasizes problems
in regards to implementation and structured
programming. A few suggestions for future language
design are offered.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Love:1977:EIE,
author = "Tom Love",
title = "An experimental investigation of the effect of program
structure on program understanding",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "105--113",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808317",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "A within-subjects experimental design was used to test
the effect of two variables on program understanding.
The independent variables were complexity of control
flow and paragraphing of the source code. Understanding
was measured by having the subjects memorize the code
for a fixed time and reconstruct the code verbatim.
Also some subjects were asked to describe the function
of the program after completing their reconstruction.
The two groups of subjects for the experiment were
students from an introductory programming class and
from a graduate class in programming languages. The
major findings were that paragraphing of the source had
no effect for either group of subjects but that
programs with simplified control flow were easier for
the computer science students to understand as measured
by their ability to reconstruct the programs. The
dependent variable, rated accuracy of their description
of the programs functions, did not differ as a function
of either independent variable. The paper is concluded
with a description of the utility of this experimental
approach relative to improving the reliability of
software and a discussion of the importance of these
findings.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Andrews:1977:LFP,
author = "Gregory R. Andrews and James R. McGraw",
title = "Language features for process interaction",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "114--127",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808318",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Languages for parallel programming should meet four
goals: expressiveness, data integrity, security, and
verifiability. This paper presents a set of language
features for describing processes and process
interaction, gives examples of their use, and briefly
discusses their relation to the goals. Two constructs,
resources and protected variables, are introduced as
the mechanisms for describing interaction. Resources
are extensions of the monitor concept of Hoare;
protected variables are global variables which can only
be accessed by one process at a time. Two types of
access control are introduced: restrictions on scope
rules for static access, and capabilities for dynamic
access. Examples include the interface to machine
devices, files and virtual devices, readers/writers,
device scheduling, device reservation, and buffer
allocation.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Lomet:1977:PSS,
author = "D. B. Lomet",
title = "Process structuring, synchronization, and recovery
using atomic actions",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "128--137",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808319",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This paper explores the notion of an atomic action as
a method of process structuring. This notion, first
introduced explicitly by Eswaren et al [6] in the
context of data base systems, reduces the problem of
coping with many processes to that of coping with a
single process within the atomic action. A form of
process synchronization, the await statement, is
adapted to work naturally with atomic actions. System
recovery is also considered and we show how atomic
actions can be used to isolate recovery action to a
single process. Explicit control of recovery is
provided by a reset procedure that permits information
from rejected control paths to be passed to subsequent
alternative paths.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Geschke:1977:EEM,
author = "Charles M. Geschke and James H. {Morris, Jr.} and
Edwin H. Satterthwaite",
title = "Early experience with {Mesa}",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "138",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808320",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The experiences of Mesa's first users --- primarily
its implementers --- are discussed, and some
implications for Mesa and similar programming languages
are suggested. The specific topics addressed are:
module structure and its use in defining abstractions,
data-structuring facilities in Mesa, equivalence
algorithm for types and type coercions, benefits of the
type system and why it is breached occasionally,
difficulty of making the treatment of variant records
safe.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Shaw:1977:AVA,
author = "Mary Shaw and Wm A. Wulf and Ralph L. London",
title = "Abstraction and verification in {Alphard}: Defining
and specifying iteration and generators",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "139",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808321",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The Alphard form provides the programmer with a great
deal of control over the implementation of abstract
data types. In this paper we extend the abstraction
techniques from simple data representation and function
definition to the iteration statement, the most
important point of interaction between data and the
control structure of the language itself. We introduce
a means of specializing Alphard's loops to operate on
abstract entities without explicit dependence on the
representation of those entities. We develop
specification and verification techniques that allow
the properties of the generators for such iterations to
be expressed in the form of proof rules. We obtain
results for common special cases of these loops that
are essentially identical to the corresponding
constructs in other languages. We also provide a means
of showing that a generator will terminate.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Liskov:1977:AMC,
author = "Barbara Liskov and Alan Snyder and Russell Atkinson
and Craig Schaffert",
title = "Abstraction mechanisms in {CLU}",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "140",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808322",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "CLU is a new programming language designed to support
the use of abstractions in program construction. Work
in programming methodology has led to the realization
that three kinds of abstractions, procedural, control,
and especially data abstractions, are useful in the
programming process. Of these, only the procedural
abstraction is supported well by conventional
languages, through the procedure or subroutine. CLU
provides, in addition to procedures, novel linguistic
mechanisms that support the use of data and control
abstractions. This paper provides an introduction to
the abstraction mechanisms in CLU. By means of
programming examples, we illustrate the utility of the
three kinds of abstractions in program construction and
show how CLU programs may be written to use and
implement abstractions. We also discuss the CLU
library, which permits incremental program development
with complete type-checking performed at
compile-time.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Gannon:1977:EED,
author = "J. D. Gannon",
title = "An experimental evaluation of data types on
programming reliability",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "141",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808323",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The language in which programs are written can have a
substantial effect on the reliability of the resulting
programs. This paper discusses an experiment that
compares the programming reliability of subjects using
a statically-typed language and a ``typeless''
language. Analysis of the number of errors and the
number of runs containing errors shows that, at least
in one environment, the use of a statically-typed
language can increase programming reliability. Detailed
analysis of the errors made by the subjects in
programming solutions to reasonably small problems
shows that the subjects had difficulty manipulating the
representation of data.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Wirth:1977:TDR,
author = "N. Wirth",
title = "Towards a discipline of real-time programming",
journal = j-SIGSOFT,
volume = "2",
number = "2",
pages = "142",
month = mar,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/390019.808324",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:19 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Programming is divided into three major categories
with increasing complexity of reasoning in program
validation: sequential programming, multi-programming,
and real-time programming. By adhering to a strict
programming discipline and by using a suitable
high-level language molded after this discipline, we
may drastically reduce the complexity of reasoning
about concurrency and execution time constraints. This
may be the only practical way to make real-time systems
analytically verifiable and ultimately reliable. A
possible discipline is outlined and expressed in terms
of the language Modula.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "Proceedings of an ACM conference on Language design
for reliable software.",
}
@Article{Parnas:1977:BRS,
author = "David L. Parnas",
title = "Building reliable software in {BLOWHARD}",
journal = j-SIGSOFT,
volume = "2",
number = "3",
pages = "5--6",
month = apr,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1012319.1012320",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:21 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Robinson:1977:RSD,
author = "L. Robinson",
title = "Reliable software and the design process",
journal = j-SIGSOFT,
volume = "2",
number = "3",
pages = "7--10",
month = apr,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1012319.1012321",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:21 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{King:1977:PLL,
author = "James C. King",
title = "Panel: limitations of language design for reliable
software",
journal = j-SIGSOFT,
volume = "2",
number = "3",
pages = "11--12",
month = apr,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1012319.1012322",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:21 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Wendel:1977:FED,
author = "Irv. K. Wendel and Richard L. Kleir",
title = "{FORTRAN} error detection through static analysis",
journal = j-SIGSOFT,
volume = "2",
number = "3",
pages = "22--28",
month = apr,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1012319.1012323",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:21 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/fortran1.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Rine:1977:RSE,
author = "David Rine",
title = "Review of {{\booktitle{Software engineering education:
needs and objectives}} by Anthony I. Wasserman and
Peter Freeman. Springer-Verlag 1976}",
journal = j-SIGSOFT,
volume = "2",
number = "3",
pages = "32--32",
month = apr,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1012319.1012324",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:21 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Riddle:1977:IDS,
author = "William E. Riddle and John H. Sayler and Alan R. Segal
and Jack C. Wileden",
title = "An introduction to the {DREAM} software design
system",
journal = j-SIGSOFT,
volume = "2",
number = "4",
pages = "11--24",
month = jul,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010730.1010731",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:22 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "We describe the underlying philosophy, the system
organization and the design language of the {\em Design
realization evaluation and modelling\/} system, a
prototype of a system being developed to aid software
system designers.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1977:ASEb,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering: part 3",
journal = j-SIGSOFT,
volume = "2",
number = "4",
pages = "24--28",
month = jul,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010730.1010732",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:22 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Dijkstra:1977:PPSb,
author = "Edsger W. Dijkstra",
title = "A position paper on software reliability",
journal = j-SIGSOFT,
volume = "2",
number = "5",
pages = "3--5",
month = oct,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005882.1005883",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib;
http://www.math.utah.edu/pub/mirrors/ftp.ira.uka.de/bibliography/SE/SEPL.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Parnas:1977:AAC,
author = "Dave Parnas",
title = "{ACM} (Association of Carriage Manufacturers):
{SIGTRANS} notices --- another historical item",
journal = j-SIGSOFT,
volume = "2",
number = "5",
pages = "6--7",
month = oct,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005882.1005884",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Good:1977:CVR,
author = "Donald I. Good",
title = "Constructing verified and reliable communications
processing systems",
journal = j-SIGSOFT,
volume = "2",
number = "5",
pages = "8--13",
month = oct,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005882.1005885",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "A comprehensive methodology that has been developed
for constructing verifiably reliable and secure
computing systems is summarized. The methodology can be
applied to many different kinds of systems, but is
specifically oriented toward communications processing
systems. The methodology is a system of methods for
attaining total system reliability and is based on
constructing verified software and highly reliable
hardware. The methodology has been formulated by
bringing a diversity of advanced research concepts to
bear on the real problems of communications systems.
This has led to the development and integration of*
program specification methods* program proof methods*
program validation methods* a program design language*
a program design system* hardware designs to support
verified software* hardware reliability analysis and
enhancement methods into a coherent methodology for
constructing verifiably reliable and secure systems.
The methodology has been successfully applied to the
experimental design of a secure message switching
system structured as a packet-switched computer
network.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Brown:1977:HLL,
author = "R. Leonard Brown and Paul G. Tuttle",
title = "High level language utilization of special hardware
features",
journal = j-SIGSOFT,
volume = "2",
number = "5",
pages = "14--16",
month = oct,
year = "1977",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005882.1005886",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Gerhart:1978:PPE,
author = "Susan L. Gerhart",
title = "A proposal for publication and exchange of program
proofs",
journal = j-SIGSOFT,
volume = "3",
number = "1",
pages = "7--17",
month = jan,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010734.1010735",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Kleine:1978:SAB,
author = "Karl Kleine",
title = "Selected annotated bibliography on software
engineering",
journal = j-SIGSOFT,
volume = "3",
number = "1",
pages = "18--25",
month = jan,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010734.1010736",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See comment \cite{Gilkey:1978:CKK}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Lamport:1978:SPB,
author = "Leslie Lamport",
title = "State the problem before describing the solution",
journal = j-SIGSOFT,
volume = "3",
number = "1",
pages = "26--26",
month = jan,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010734.1010737",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Ottenstein:1978:FVE,
author = "Linda M. Ottenstein",
title = "Further validation of an error hypothesis",
journal = j-SIGSOFT,
volume = "3",
number = "1",
pages = "27--28",
month = jan,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010734.1010738",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1978:ASEa,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering: part 5",
journal = j-SIGSOFT,
volume = "3",
number = "1",
pages = "28--32",
month = jan,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010734.1010739",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:23 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Linden:1978:SAD,
author = "Theodore A. Linden",
title = "Specifying abstract data types by restriction",
journal = j-SIGSOFT,
volume = "3",
number = "2",
pages = "7--13",
month = apr,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005888.1005889",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:24 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Restrictions are one instance of mathematically-based
relationships between types that can be used to
simplify program specifications. Restriction of an
abstract data type provides a theoretical justification
for the concept of a hidden function that appears in
some current specification methodologies. The use of
type restrictions to simplify formal specifications is
illustrated by the example of traversible stacks.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Dijkstra:1978:PPM,
author = "Edsger W. Dijkstra",
title = "On a Political Pamphlet from the {Middle Ages}",
journal = j-SIGSOFT,
volume = "3",
number = "2",
pages = "14--16",
month = apr,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005888.1005890",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:24 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See responses
\cite{DeMillo:1978:RRD,Jeffrey:1978:DPP,VanGhent:1978:LRS,Maurer:1978:ALC}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
remark = "This article refers to the paper Richard A. DeMillo,
Richard J. Lipton, Alan J. Perlis, \booktitle{Social
Processes and Proofs of Theorems and Programs},
Proceedings of the Fourth ACM Symposium on Principles
of Programming Languages, pp. 206--214 (January 1977)",
}
@Article{DeMillo:1978:RRD,
author = "Richard A. DeMillo and Richard J. Lipton and Alan J.
Perlis",
title = "Response from {R. A. DeMillo}, {R. J. Lipton}, {A. J.
Perlis}",
journal = j-SIGSOFT,
volume = "3",
number = "2",
pages = "16--17",
month = apr,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005888.1005891",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:24 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See \cite{Dijkstra:1978:PPM}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Jeffrey:1978:DPP,
author = "H. J. Jeffrey",
title = "On {Dijkstra}'s position paper on software
reliability",
journal = j-SIGSOFT,
volume = "3",
number = "2",
pages = "18--18",
month = apr,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005888.1005892",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:24 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See \cite{Dijkstra:1978:PPM}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Gilkey:1978:CKK,
author = "Thomas Gilkey",
title = "Comment on {Karl Kleine}'s ``selected bibliography''",
journal = j-SIGSOFT,
volume = "3",
number = "2",
pages = "19--19",
month = apr,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005888.1005893",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:24 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See \cite{Kleine:1978:SAB}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Turski:1978:CPM,
author = "W. M. Turski and Anthony I. Wasserman",
title = "Computer programming methodology",
journal = j-SIGSOFT,
volume = "3",
number = "2",
pages = "20--21",
month = apr,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005888.1005894",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:24 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Harrell:1978:NMR,
author = "Herbert Harrell",
title = "A note on methodological review",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "5--7",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010752",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Wurges:1978:SRU,
author = "Harald W{\"u}rges",
title = "Some remarks on the use of abstract specifications for
operating systems",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "8--12",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010753",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Nourani:1978:NLO,
author = "Farshid Nourani",
title = "A note on logic-oriented approaches to data
abstraction",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "13--15",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010754",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See reply \cite{Linden:1978:FSC}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Linden:1978:FSC,
author = "Theodore A. Linden",
title = "On formal specifications and completeness: reply to
{Farshid Nourani}",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "15--17",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010755",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See \cite{Nourani:1978:NLO}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Meyer:1978:SCP,
author = "Steve Meyer",
title = "Should computer programs be verified?",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "18--19",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010756",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{VanGhent:1978:LRS,
author = "Roger {Van Ghent}",
title = "Letter on real software, regarding the commentary by
{Dijkstra} and the reply by {DeMillo}, {Lipton} and
{Perlis}",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "20--21",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010757",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See
\cite{Dijkstra:1978:PPM,DeMillo:1978:RRD,Jeffrey:1978:DPP}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Maurer:1978:ALC,
author = "W. D. Maurer",
title = "Another letter on the correctness of real programs",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "22--24",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010758",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See
\cite{Dijkstra:1978:PPM,DeMillo:1978:RRD,Jeffrey:1978:DPP,VanGhent:1978:LRS}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Lassagne:1978:AKB,
author = "Theodore D. Lassagne",
title = "Analysis is the key to better software design",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "24--26",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010759",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Gilb:1978:MQG,
author = "Tom Gilb",
title = "Multidimensional quantified goals should direct
software design processes",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "26--28",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010760",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1978:ASEb,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering: part 6",
journal = j-SIGSOFT,
volume = "3",
number = "3",
pages = "31--33",
month = jul,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010751.1010761",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Riddle:1978:LRS,
author = "William E. Riddle and Jack C. Wileden",
title = "Languages for representing software specifications and
designs",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "7--11",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010742",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "We consider the nature of software system
specifications and designs, then survey the languages
used in representing them. We emphasize the utility of
language-based representations as a foundation for
computerized tools which provide aid during software
system development. The survey is based upon a
classification of the languages according to their
underlying representational constructs.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Parker:1978:CDM,
author = "John Parker",
title = "A comparison of design methodologies",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "12--19",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010743",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See letter \cite{Geller:1979:LPD}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Parnas:1978:AVD,
author = "David L. Parnas",
title = "Another view of the {Dijkstra--dMLP} controversy",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "20--21",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010744",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Shaw:1978:LLL,
author = "Mary Shaw",
title = "Letter on {Lebesgue}, logic, and program testing",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "21--21",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010745",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Raduchel:1978:MSD,
author = "William J. Raduchel",
title = "Managing software development",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "22--26",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010746",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Priebe:1978:SIR,
author = "Kathie Priebe",
title = "Some ideas on review methodology",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "27--29",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010747",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Zelkowitz:1978:PMS,
author = "Marvin V. Zelkowitz",
title = "Productivity measurement on software engineering
projects",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "30--31",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010748",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The milestone is often used as a measure of project
progress on large scale software developments. In this
report, a quantitative measure of the milestone is
developed and shown to be consistent with existing
estimating techniques.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1978:ASEc,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering: part 6",
journal = j-SIGSOFT,
volume = "3",
number = "4",
pages = "31--33",
month = oct,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010741.1010749",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:25 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Pfau:1978:AQA,
author = "Pamela R. Pfau",
title = "Applied quality assurance methodology",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "1--8",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811092",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "What is the charter of a Quality Assurance (Q.A.)
department? What are the activities? How are they
undertaken? What is the impact of Quality Assurance
upon a software product? The structure and operating
philosophy of the department are explained in this
report as is the definition of the work cycle as
applied to a new release of a software product.
Comments are made about the interaction between
departments: product development, product maintenance,
publications, education, field support, product
management, marketing, product distribution and quality
assurance. While this is a description of the
activities of a company involved in developing and
marketing software products, the concepts apply to
techniques and practices which would also be beneficial
to any data processing department that develops
in-house application software.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Bersoff:1978:SCM,
author = "Edward H. Bersoff and Vilas D. Henderson and Stan G.
Siegel",
title = "Software Configuration Management",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "9--17",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811093",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This paper is about discipline. It is about discipline
that managers should apply to software development. Why
is such discipline needed? Quite simply because the
software industry has traditionally behaved in an
undisciplined manner --- doing its own thing. The
products that the industry has turned out have
typically Contained other than what was expected
(usually less, rather than more); Been delivered much
later than scheduled; Cost more than anticipated; Been
poorly documented; and If you have been involved in any
of the situations quoted above, then this paper may be
of some help. In short, if you are now, or intend to
be, a software seller or buyer, then you should benefit
from an understanding of Software Configuration
Management. Lest you think that you are not now, or
ever will be, a software seller or buyer --- keep in
mind that the recent technology explosion in electronic
component miniaturization has placed the era of
personalized computing at hand. In that context, nearly
everyone may be considered a potential seller or buyer
of software. This paper is about the discipline called
Software Configuration Management (SCM). The objective
of SCM is to assist the software seller in achieving
product integrity and to assist the software buyer in
obtaining a product that has integrity.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Glass:1978:CFL,
author = "Robert L. Glass",
title = "Computing failure: a learning experience",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "18--19",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811094",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Computing people can learn from failure as well as
success. Most professional papers deal only with the
latter \ldots{} yet it is well known that some of our
most lasting learning experiences are based on failure.
This paper is a lighthearted, anecdotal discussion of a
computing failure, with an underlying message that
sharing the sometimes embarrassing truths about What
Goes Wrong In Our Field is at least as illuminating as
more serious discussions about Things That Look
Promising. There are some necessary defense mechanisms
to be dealt with in discussing failure. People who have
failed in general do not want the world to know about
it. Perhaps even more so, companies which have failed
also do not want the world to know about it. As a
result, the content of this paper is fictionalized to
some extent. That is, company names and people names
are creations of the author, and there are
corresponding distortions in some story details.
However, the computing meat of the paper, the basis for
the failure learning experience, is untouched.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Woodmancy:1978:SQI,
author = "Donald A. Woodmancy",
title = "A Software Quality Improvement Program",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "20--26",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811095",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "In late 1976, the NCR Corporation undertook a large
scale Quality Improvement Program for a major set of
systems software. That software set included some 103
separate products totaling 1.3 million source lines. It
included several operating systems, several compilers,
peripheral software, data utilities and
telecommunications handlers. This paper will describe
that effort and its results. The research and planning
that were done to define the program will be described.
The means by which the program was implemented will be
discussed in detail. Finally, some results of the
program will be identified.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Fujii:1978:CSA,
author = "Marilyn S. Fujii",
title = "A comparison of software assurance methods",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "27--32",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811096",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Several methods are currently employed by software
developers to improve software quality. This paper
explores the application of three of these methods:
quality assurance, acceptance testing, and independent
verification and validation. At first glance these
methods appear to overlap, but a closer evaluation
reveals that each has a distinct objective and an
established set of procedures. The purpose of this
paper is to clarify the role of each of these methods
by examining their scope, organization, and
implementation in the software development process.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Sukert:1978:EMA,
author = "Alan N. Sukert and Amrit L. Goel",
title = "Error modelling applications in software quality
assurance",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "33--38",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811097",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This paper presents the results of a two-phased
experiment conducted by Rome Air Development Center and
Syracuse University to demonstrate the potential
applicability of software error prediction models in
performing formalized qualification testing of a
software package. First, decisions based upon the
predictions of three software error prediction models
will be compared with actual program decisions for a
large command and control software development project.
Classical and Bayesian demonstration tests are used to
make accept/reject decisions about the software system.
Finally, the results of the two phases will be compared
and some conclusions drawn as to the potential use of
these predictive techniques to software quality
assurance.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Duran:1978:TMP,
author = "Joe W. Duran and John J. Wiorkowski",
title = "Toward models for probabilistic program correctness",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "39--44",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811098",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Program testing remains the major way in which program
designers convince themselves of the validity of their
programs. Software reliability measures based on
hardware reliability concepts have been proposed, but
adequate models of software reliability have not yet
been developed. Investigators have recently studied
formal program testing concepts, with promising
results, but have not seriously considered quantitative
measures of the ``degree of correctness'' of a program.
We present models for determining, via testing, such
probabilistic measures of program correctness as the
probability that a program will run correctly on
randomly chosen input data, confidence intervals on the
number of errors remaining in a program, and the
probability that the program has been completely
tested. We also introduce a procedure for enhancing
correctness estimates by quantifying the error reducing
performance of the methods used to develop and debug a
program.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Yin:1978:EUM,
author = "B. H. Yin and J. W. Winchester",
title = "The establishment and use of measures to evaluate the
quality of software designs",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "45--52",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811099",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "It has been recognized that success in producing
designs that realize reliable software, even using
Structured Design, is intimately dependent on the
experience level of the designer. The gap in this
methodology is the absence of easily applied
quantitative measures of quality that ease the
dependence of reliable systems on the rare availability
of expert designers. Several metrics have been devised
which, when applied to design structure charts, can
pinpoint sections of a design that may cause problems
during coding, debugging, integration, and
modification. These metrics can help provide an
independent, unbiased evaluation of design quality.
These metrics have been validated against program error
data of two recently completed software projects at
Hughes. The results indicate that the metrics can
provide a predictive measure of program errors
experienced during program development. Guidelines for
interpreting the design metric values are summarized
and a brief description of an interactive structure
chart graphics system to simplify metric value
calculation is presented.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Pierce:1978:RTT,
author = "Robert A. Pierce",
title = "A Requirements Tracing Tool",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "53--60",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811100",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "A software development aid termed the Requirements
Tracing Tool is described. Though originally designed
to facilitate requirements analysis and thus simplify
system verification and validation, it has also proven
useful as an aid for coping with changing software
requirements and estimating their consequent cost and
schedule impacts. This tool provides system analysts
with a mechanism for automated construction,
maintenance, and access to a requirements data base ---
an integrated file containing all types and levels of
system requirements. This tool was used during the
development of a large Navy undersea acoustic sensor
system. It is presently being used to support the
Cruise Missile Mission Planning Project. An outline
version of this tool is under development.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Davis:1978:RLP,
author = "Alan M. Davis and Walter J. Rataj",
title = "Requirements language processing for the effective
testing of real-time systems",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "61--66",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811101",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "GTE Laboratories is currently developing a trio of
software tools which automate the feature testing of
real-time systems by generating test plans directly
from requirements specifications. Use of the first of
these tools, the Requirements Language Processor (RLP),
guarantees that the requirements are complete,
consistent, non-ambiguous, and non-redundant. It
generates a model of an extended finite-state machine
which is used by the second tool, the Test Plan
Generator, to generate test plans which thoroughly test
the software for conformity to the requirements. These
test plans are supplied to the third tool, the
Automatic Test Executor, for actual testing. The RLP is
the subject of this paper. The primary goal of the RLP
is to provide the ability to specify the features of a
target real-time system in a vocabulary familiar to an
application-oriented individual and in a manner
suitable for test plan generation. The RLP produces a
document which can be easily understood by non-computer
personnel. It is expected that this document will
function as a key part of the ``contract'' between a
real-time system supplier and a customer. This document
must also serve as a springboard for the software
designers during their development of the actual
product. In addition to the requirements document, the
RLP also produces an augmented state transition table
which describes a finite state machine whose external
behavior is identical to the target real-time system as
defined by the specified requirements.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Peters:1978:RSR,
author = "Lawrence Peters",
title = "Relating software requirements and design",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "67--71",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811102",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Software development is a process which has evolved
into a number of phases. Although the names of the
phases and some of their characteristics differ from
contractor to contractor and customer to customer, the
functional similarities among sets of phases cannot be
ignored. The basic software development scenario
depicted by these phases starts with problem
identification and definition, requirements
specification, design, code, test, and installation and
maintenance. Although some ``smearing\&rdquo of one
phase activity into other(s) may occur, this represents
the basic flow. However, it is just that smearing which
occurs between requirements and design that we wish to
explore here. Identifying or defining problems and
solving problems are viewed by many to be separate,
distinguishable activities. They are complementary in
that one identifies what must be done (requirements)
while the other depicts how it will be done (design).
But software designers complain bitterly that
requirements are poorly defined while customers and
analysts often complain that the design is not
responsive to the problem(s) as they perceive it.
Somehow software designers end up discovering
previously unknown requirements and end up solving a
problem which is foreign to the customer. Is there a
workable mechanism to reduce this difficulty?",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Stavely:1978:DFU,
author = "Allan M. Stavely",
title = "Design feedback and its use in software design aid
systems",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "72--78",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811103",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "It is argued that software system designers would
benefit greatly from feedback about the consequences of
a proposed design if this feedback could be obtained
early in the development process. A taxonomy of
possible types of feedback and other design aids is
presented, and the capabilities of several existing
design aid systems are described relative to this
taxonomy.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Yoder:1978:NSC,
author = "Cornelia M. Yoder and Marilyn L. Schrag",
title = "{Nassi--Shneiderman} charts an alternative to
flowcharts for design",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "79--86",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811104",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "In recent years structured programming has emerged as
an advanced programming technology. During this time,
many tools have been developed for facilitating the
programmer's use of structured programming. One of
these tools, the Structured Flowcharts developed by I.
Nassi and B. Shneiderman in 1972, is proving its value
in both the design phase and the coding phase of
program development. Several programming groups in
System Products Division, Endicott, New York, have used
the Nassi-Shneiderman charts as replacements for
conventional flowcharts in structuring programs. The
charts have been used extensively on some projects for
structured walk-throughs, design reviews, and
education. This paper describes the Nassi-Shneiderman
charts and provides explanations of their use in
programming, in development process control, in
walk-throughs, and in testing. It includes an analysis
of the value of Nassi-Shneiderman charts compared to
other design and documentation methods such as
pseudo-code, HIPO charts, prose, and flowcharts, as
well as the authors' experiences in using the
Nassi-Shneiderman charts. The paper is intended for a
general data processing audience and although no
special knowledge is required, familiarity with
structured programming concepts would be helpful. The
reader should gain insight into the use of
Nassi-Shneiderman charts as part of the total
development process.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Benson:1978:SQA,
author = "J. P. Benson and S. H. Saib",
title = "A software quality assurance experiment",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "87--91",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811105",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "An experiment was performed to evaluate the ability of
executable assertions to detect programming errors in a
real time program. Errors selected from the categories
of computational errors, data handling errors, and
logical errors were inserted in the program. Assertions
were then written which detected these errors. While
computational errors were easily detected, data
handling and logical errors were more difficult to
locate. New types of assertions will be required to
protect against these errors.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Bauer:1978:AGE,
author = "Jonathan Bauer and Susan Faasse and Alan Finger and
William Goodhue",
title = "The automatic generation and execution of function
test plans for electronic switching systems",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "92--100",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811106",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "A three phase functional testing methodology is
described for use in the development cycle of
electronic switching systems. The methodology centers
on a directed graph model of the system and provides
for the checking of system requirements, the generation
of functional tests and the automatic execution of
these tests.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Martin:1978:SAT,
author = "K. A. Martin",
title = "Software acceptance testing that goes beyond the
book",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "101--105",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811107",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The design of software acceptance tests is as
important to meeting contract goals as is the design of
algorithms. This statement is particularly significant
on fixed price contracts with tight schedules. An
extreme instance of the demand placed on acceptance
testing can be found in software projects wherein the
only rigorous testing that required the Computer
Program Configuration Item (CPCI) to exercise its
repertoire of load and store instructions was the
Formal Qualification Test (FQT). This paper is about
such a project, the lessons learned from it, and
provides an effective test approach for fixed price
contracts. A word or two about the project is
appropriate to establish the context that underscores
the impact of the above assertion. Initially 30K (core
words), 16-bit program instructions were to be
developed within one year using a Varian 73 computer
with 32K words of memory for a Command and Control
application under a fixed price contract. A set of a
priori conditions existed that tended to convey the
impression that the inherent risks of this endeavor
were reasonable. They were the ``facts'' that: Of the
30K (core words) to be written, 30\% of this code
already existed and would be used. Contractor standards
would be allowed for documentation with limited use of
Military Specifications No formal Design Reviews or
audits would accompany the deliverable CPCI. Existent
executive software would suffice. A competent and
enthusiastic team was committed to the effort.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Drasch:1978:ITP,
author = "Frederick J. Drasch and Richard A. Bowen",
title = "{IDBUG}: a tool for program development",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "106--110",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811108",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The construction of a reliable computer program
requires, in part, a means of verification of its
component parts prior to their integration into the
overall system. The verification process may consist of
building a test harness to exercise or exhaustively
test a procedure. This technique is known as dynamic
testing. In practice, the application of dynamic
testing requires the coding of a special harness for
each procedure. This consumes valuable programming
time, as much as 50\% of the total effort (FAIR78). It
is also restrictive because the test harness cannot be
easily modified to test aspects of a program which it
was not originally designed to test. We have built a
facility called IDBUG that reduces the programming
effort required to employ dynamic testing by automating
the construction of the test harness. Additionally, it
provides an interactive test environment which permits
more flexible testing. This paper describes IDBUG and
discusses our experience in its application to
maintenance tasks in a commercial environment. Nyone of
the ideas put forth here will be especially novel;
dynamic testing as a software testing tool has been in
use for some time. What we hope to do is illustrate the
beneficial aspects of a particular application of
dynamic testing. It is argued that testing should play
a more limited role in assuring the reliability of
software in light of techniques such as structured
coding, top-down design, proof of correctness, etc.
(McG075). While it is true that eventually the ``art of
computer programming'' will become the ``science of
producing correct programs'', we believe that more
emphasis must be placed on interim solutions to aid in
the construction of reliable software. We present IDBUG
as such a solution.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Stickney:1978:AGT,
author = "M. E. Stickney",
title = "An application of graph theory to software test data
selection",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "111--115",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811109",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Graph theory is playing an increasingly important role
in the design, analysis, and testing of computer
programs. It's importance is derived from the fact that
flow of control and flow of data for any program can be
expressed in terms of directed graphs. From the graph
representing the flow of control, called the program
graph, many others can be derived that either partially
or completely preserve the program control structure.
One derived graph known as a cyclomatic tree is of
particular value in program testing. It is so named
because the number of leaves of the tree is equal to
the cyclomatic number of the program graph. A thorough
treatment of cyclomatic numbers is provided in [3]. A
program called the Complexity/Path Analyzer (CPA) has
been developed that builds and utilizes a program
cyclomatic tree to provide test planning information,
automatically place software counters called probes as
discussed in [9] and [10] in a program, and provide
selected parameters such as program length and program
graph cyclomatic number. The paper discusses the
features and derivation of cyclomatic trees as well as
their value and application to testing and test data
generation. A cyclomatic tree provides a test planner
with information useful for planning program tests. In
particular, it furnishes test data selection criteria
for developing tests that are minimally thorough as
defined by Huang in [9]. A test data selection
criterion will be defined as minimally thorough if any
complete test with respect to the criterion is at least
minimally thorough. The term complete is used as
defined by Goodenhough and Gerhart in [13]. A test is
defined to be a non empty sequence of test cases. Each
test case consists of an element selected from the
input domain of the program being tested. The paper
discusses the merits of one particular technique
selected to achieve a minimally thorough test data
selection criteria. Part of the technique is automated
by the CPA program.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Fischer:1978:SQA,
author = "Kurt F. Fischer",
title = "Software quality assurance tools: Recent experience
and future requirements",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "116--121",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811110",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The objective of software quality assurance (QA) is to
assure sufficient planning, reporting, and control to
affect the development of software products which meet
their contractual requirements. To implement this
objective, eight QA functions can be identified: 1.
Initial quality planning 2. Development of software
standards and procedures 3. Development of quality
assurance tools 4. Conduct of audits and reviews 5.
Inspection and surveillance of formal tests 6.
Configuration verifications 7. Management of the
discrepancy reporting system 8. Retention of QA records
The purpose of this paper is to document experiences
gained in the use of selected QA tools that perform
some of the above functions, to discuss lessons
learned, and to suggest future needs.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Glasser:1978:ESC,
author = "Alan L. Glasser",
title = "The evolution of a Source Code Control System",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "122--125",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811111",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The Source Code Control System (SCCS) is a system for
controlling changes to files of text (typically, the
source code and documentation of software systems). It
is an integral part of a software development and
maintenance system known as the Programmer's Workbench
(PWB). SCCS has itself undergone considerable change.
There have been nine major versions of SCCS. This paper
describes the facilities provided by SCCS, and the
design changes that were made to SCCS in order to
provide a useful and flexible environment in which to
conduct the programming process.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Josephs:1978:MCB,
author = "William H. Josephs",
title = "A mini-computer based library control system",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "126--132",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811112",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/fortran1.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "One of the major problems encountered in any large
scale programming project is the control of the
software. Invariably, such large programs are divided
into many smaller elements since these are easier to
code, test and document. However, such a division adds
new complexity to the task of Configuration Management
since the many source modules, data base elements, JCL
(Job Control Language) and DATA files must be
controlled with the goal of maximizing program
integrity and minimizing the chances of procedural
errors. Furthermore, whenever any program is released
either for field test or for final production, an
entire change control procedure must be implemented in
order to trace, install, debug and verify fixes or
extensions to the original program. These maintenance
activities can account for up to 80 percent of the
entire programming cost in a large, multi-year project.
The library control program (SYSM) presented here was
developed to aid in these processes. It has facilities
for capturing all elements of a program (commonly
called baselining), editing any element or group of
elements that have been baselined to build an updated
version of the program, adding and/or deleting elements
of a program, and listing the current contents of a
given element or elements. SYSM is written mainly in
FORTRAN, and runs on a Hewlett--Packard HP-21MX
computer with two tape drives, the vendor supplied
RTE-II or RTE-III operating system, and at least 16K of
user available core. It can be used to control code
targeted for either the HP21MX itself, or, using the
optional HP/LSI-11 link program, code targeted for a
Digital Equipment Corp. LSI-11 system.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Cavano:1978:FMS,
author = "Joseph P. Cavano and James A. McCall",
title = "A framework for the measurement of software quality",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "133--139",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811113",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Research in software metrics incorporated in a
framework established for software quality measurement
can potentially provide significant benefits to
software quality assurance programs. The research
described has been conducted by General Electric
Company for the Air Force Systems Command Rome Air
Development Center. The problems encountered defining
software quality and the approach taken to establish a
framework for the measurement of software quality are
described in this paper.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Cobb:1978:MSU,
author = "Gary W. Cobb",
title = "A measurement of structure for unstructured
programming languages",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "140--147",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811114",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Software Science is a field of Natural Science which
deals with the development of measurements which reveal
properties of software programs. These measurements are
qualified as to their degree of correlation to human
beings being able to construct or understand a subject
program. Maurice Halstead has pioneered much of the
theories in this field ((5) through (10)), which
applies statistical and psychological testing
techniques to the evaluation of the measurements. The
basic inputs to the Halstead predictors are easily
measured: the number of distinct operators and
operands, and the number of occurrences of the
operators and operands. Due to the statistical nature
of the measurements, there can be erroneous results
when applying them to small sample spaces. However, the
predictors are very adequate when applied to large
samples, that is, large software systems. In an
excellent review article by Fitzsimmons and Love (4),
it is pointed out that several of the estimators
defined by Halstead assumed that the subject programs
were well-structured, and inaccuracy in the predictors
can result if they are applied to ``unpolished''
programs. In fact, Halstead qualified six classes of
impurities in code which can cause the length predictor
to be inaccurate. The definition of volume for
software, another predictor introduced in Halstead's
book, is related to the level of the specification of
the program. An algorithm which is written in assembly
language will have a greater volume than the same
algorithm written in Pascal, due to the richness of the
semantic constructs that are available in the
higher-level languages. Hence, this predictor is
language dependent.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Bowen:1978:CAS,
author = "John B. Bowen",
title = "Are current approaches sufficient for measuring
software quality?",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "148--155",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811115",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Numerous software quality studies have been performed
over the past three years-mostly sponsored by the Rome
Air Development Center. It is proposed by the author
that more emphasis should be placed on devising and
validating quantitative metrics that are indicative of
the quality of software when it is being designed and
coded. Such measures could be applied effectively, as
relative guidelines without formal validation. However
for such measures to be predictive of the quality of
the delivered software, they must be validated with
actual operational error data or data gathered in a
simulated operational environment. This paper includes
a review of proposed metrics from the literature a
report of a Hughes intramodule metric study, and
recommendations for refining proposed software quality
assurance criteria.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Lockett:1978:UPM,
author = "Joann Lockett",
title = "Using performance metrics in system design",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "156--159",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811116",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Complexities of system design are great and often lead
designers to be inward looking in their analyses.
Knowledge from various fields can be of benefit in
designing systems [1]. Management accountants can
describe economic effects of delays in closing
schedules, psychologist can provide significant
insights into the behavioral characteristics of users
to complex command syntax, computer performance
analysts can provide alternatives to describe and to
measure responsiveness of systems. Even in the case of
an innovative system design, the designer can employ
such approaches to identify incipient problems and
create alternatives with increased cost effectiveness.
This paper describes how performance metrics can be
used effectively to support system design.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Southworth:1978:RM,
author = "Richard N. Southworth",
title = "Responding to {MIL-S-52779}",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "160--164",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811117",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The art and science of computer software development
is still changing considerably from year to year, and
therefore lacks the established control mechanisms of
hardware production programs. Also, because most
software is produced in a one-time development program
it does not lend itself to the established discrepancy
detection and correction techniques used in hardware
production programs. Consequently, the software QA
program must provide the methodology to detect a
deficiency the first time it occurs and effect
corrective action. MIL-S-52779: ``Software Quality
Assurance Program Requirements,'' has provided a much
needed impetus for software development contractors to
develop software QA techniques. But much remains to be
done. As the state of the art advances MIL-S-52779
should be revised accordingly. In this paper the author
responds to the present form of the specification,
suggests some revisions and additions and briefly
discusses a set of QA procedures that should be
responsive (fully compliant) with MIL-S-52779.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Tighe:1978:VPS,
author = "Michael F. Tighe",
title = "The value of a proper software quality assurance
methodology",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "165--172",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811118",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This paper describes the experiences of a project
development team during an attempt to ensure the
quality of a new software product. This product was
created by a team of software engineers at Digital
Equipment Corporation, a mainframe manufacturer. As a
result, the definition of ``to ensure the quality of a
software product'' meant minimizing the maintenance
costs of the new product. Ease of maintenance and a low
bug rate after release to the customer were very
important goals from the beginning of the project. This
paper compares the degree of application and resultant
effects of several software quality assurance
methodologies upon different parts of the final
product. Many of the product's subsystems were created
using all of the discussed methodologies rigorously.
Some subsystems were created with little or no use of
the methodologies. Other subsystems used a mixture. The
observed quality of the various subsystems when related
to the methodology used to create them provides
insights into the interactions between the
methodologies. These observations also supply
additional experience to reinforce established beliefs
concerning the value of quality assurance
methodologies.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Belford:1978:QEE,
author = "Peter Chase Belford and Carlo Broglio",
title = "A quantitative evaluation of the effectiveness of
quality assurance as experienced on a large-scale
software development effort",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "173--180",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811119",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "The purpose of quality assurance on software projects
is to achieve high quality products on schedule, within
cost, and in compliance with contract requirements.
However, historically, the effectiveness of these
activities on software projects has not been
quantitatively demonstrable because of a lack of data
collected on the project combined with a lack of
insight into the operational reliability of the system.
Quality assurance is a collection of activities on a
contractual deliverable whose purpose is to impart a
degree of confidence that the deliverable will conform
to the customer's concept of what was procured. Under
these conditions, quality assurance must be performed
with respect to a documented baseline of the concept.
This baseline can address the need in the form of
requirement statements; the conceptual approach to be
followed in the form of a functional specification; or
the design to be implemented in the form of a design
specification. Further, these baselines are
hierarchical in the sense that when quality assurance
is applied to a level it is implicitly applied to all
lower levels; e.g., if the need is to be satisfied, the
conceptual approach must be satisfied. Effective
quality assurance programs impart a high degree of
confidence to the customer without significant impacts
on schedule or cost. Historically, this effectiveness
has not been quantitatively demonstrable because of a
lack of data collected on the project combined with a
lack of insight into the operational reliability of the
system.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Kacik:1978:ESQ,
author = "Paul J. Kacik",
title = "An example of software quality assurance techniques
used in a successful large scale software development",
journal = j-SIGSOFT,
volume = "3",
number = "5",
pages = "181--186",
month = nov,
year = "1978",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/953579.811120",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:26 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "Development of the software package for the Combat
Grande Air Defense System was considered by the Hughes
Aircraft Company to be highly successful in that a
reliable system was produced that met customer
requirements and was completed within time and budget
allocations --- a feat not often attained in large
scale software developments. Much of the success can be
attributed to the software quality assurance (QA)
techniques used. Some of these QA techniques are listed
in Table 1 along with the phases in which they were
used. This paper describes these QA techniques in some
detail, as well as those aspects of the system and
software development program that permitted these
techniques to be used effectively. Background
information is presented first which describes the
system, software, organization and software
configuration management. This is followed by a
description of the three major phases of software
development. The overall results are then presented,
followed by recommended improvements and conclusions.
Many of the QA techniques listed in Table 1 were used
in several phases of software development. However, a
particular technique is discussed only in the phase in
which it was most extensively used.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Miller:1979:SSS,
author = "Edward F. Miller",
title = "Some statistics from the software testing service",
journal = j-SIGSOFT,
volume = "4",
number = "1",
pages = "8--11",
month = jan,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010773.1010774",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:28 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Fairley:1979:MCSa,
author = "Richard E. Fairley",
title = "Masters curriculum in software engineering",
journal = j-SIGSOFT,
volume = "4",
number = "1",
pages = "12--17",
month = jan,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010773.1010775",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:28 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This paper is a status report on the curricular
efforts of the IEEE Computer Society's subcommittee on
software engineering education. The first draft of a
proposed Masters program in software engineering is
presented, as is the undergraduate preparation required
for admission to the program. Potential implementation
problems are discussed, and future plans are
mentioned.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Geller:1979:LPD,
author = "Dennis P. Geller",
title = "Letter on {Parker}'s {``Design methodologies: a
comparison''}",
journal = j-SIGSOFT,
volume = "4",
number = "1",
pages = "18--18",
month = jan,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010773.1010776",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:28 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
note = "See \cite{Parker:1978:CDM}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Kilov:1979:LPV,
author = "H. Kilov",
title = "Letter on {Parnas}' view of {Dijkstra} vs. {deMillo},
{Lipton} and {Perlis}",
journal = j-SIGSOFT,
volume = "4",
number = "1",
pages = "19--19",
month = jan,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010773.1010777",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:28 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/bibnet/authors/d/dijkstra-edsger-w.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1979:ASP,
author = "{Software Engineering Notes Staff}",
title = "An alternative to structured programming: syndicate
programming",
journal = j-SIGSOFT,
volume = "4",
number = "1",
pages = "19--20",
month = jan,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010773.1010778",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:28 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1979:NPA,
author = "{Software Engineering Notes Staff}",
title = "A note on the psychology of abstraction {(PGN)}",
journal = j-SIGSOFT,
volume = "4",
number = "1",
pages = "21--21",
month = jan,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010773.1010779",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:28 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1979:ASEa,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering: part 8",
journal = j-SIGSOFT,
volume = "4",
number = "1",
pages = "22--24",
month = jan,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010773.1010780",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:28 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Gelperin:1979:TM,
author = "David Gelperin",
title = "Testing maintainability",
journal = j-SIGSOFT,
volume = "4",
number = "2",
pages = "7--12",
month = apr,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010763.1010764",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:29 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Fairley:1979:MCSb,
author = "Richard E. Fairley",
title = "Masters curriculum in software engineering",
journal = j-SIGSOFT,
volume = "4",
number = "2",
pages = "13--16",
month = apr,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010763.1010765",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:29 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Hamlet:1979:RFT,
author = "Richard Hamlet",
title = "Report on {Florida} testing workshop",
journal = j-SIGSOFT,
volume = "4",
number = "2",
pages = "17--18",
month = apr,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010763.1010766",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:29 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Staff:1979:ASEb,
author = "{Software Engineering Notes Staff}",
title = "Abstracts in software engineering: part 9",
journal = j-SIGSOFT,
volume = "4",
number = "2",
pages = "19--20",
month = apr,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010763.1010767",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:29 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Schneidewind:1979:STR,
author = "Norm Schneidewind",
title = "{Secretary-Treasurer}'s report to {SIGSOFT} members",
journal = j-SIGSOFT,
volume = "4",
number = "3",
pages = "3--5",
month = jul,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005896.1005900",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:30 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Bail:1979:UES,
author = "William G. Bail",
title = "User experiences with specification tools: (panel from
{Specifications of Reliable Software Conference})
({April 3--5, 1979})",
journal = j-SIGSOFT,
volume = "4",
number = "3",
pages = "7--14",
month = jul,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005896.1005902",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:30 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Shore:1979:LSW,
author = "John E. Shore and Kathryn L. Heninger",
title = "Limits to specifications: why not more progress?
{Panel} at {IEEE} conference on specifications of
reliable software",
journal = j-SIGSOFT,
volume = "4",
number = "3",
pages = "15--16",
month = jul,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005896.1005903",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:30 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Zave:1979:PSA,
author = "Pamela Zave",
title = "Panel session: Approaches to specification-various
models: {\em an informal report}",
journal = j-SIGSOFT,
volume = "4",
number = "3",
pages = "17--18",
month = jul,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005896.1005904",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:30 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Ardis:1979:SRS,
author = "Mark A. Ardis",
title = "Specifications of reliable software --- what next?",
journal = j-SIGSOFT,
volume = "4",
number = "3",
pages = "19--21",
month = jul,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005896.1005905",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:30 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Marca:1979:MSS,
author = "David Marca",
title = "A method for specifying structured programs",
journal = j-SIGSOFT,
volume = "4",
number = "3",
pages = "22--31",
month = jul,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005896.1005897",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:30 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "This paper briefly describes the ``Structured
Programming Design Method'' (SPDM). A synopsis of
structured flowcharts is given together with
enhancements that make the language more practical. The
concept of an author-reader review cycle is introduced
and combined with structured flowcharts to form the
method. Benefits and shortcomings are discussed, and
comparisons are made with other kinds of design
documentation.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Gilb:1979:CDM,
author = "Tom Gilb",
title = "A comment on {``The definition of maintainability''}",
journal = j-SIGSOFT,
volume = "4",
number = "3",
pages = "32--33",
month = jul,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005896.1005898",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:30 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Horning:1979:NPR,
author = "Jim Horning",
title = "A note on program reliability",
journal = j-SIGSOFT,
volume = "4",
number = "4",
pages = "6--8",
month = oct,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005907.1005908",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:31 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "I introduced a recent pair of lectures [1] with some
remarks about program reliability, in the form of an
example, a safe prediction, a nightmare, an
observation, and a challenge. Although the technical
content of these lectures has already been published
[2], the introductory remarks have not, and some
students were kind enough to suggest that they were
worthy of circulation to a wider audience via Software
Engineering Notes.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Babb:1979:ADA,
author = "Robert G. Babb and Leonard L. Tripp",
title = "An approach to defining areas within the field of
software engineering",
journal = j-SIGSOFT,
volume = "4",
number = "4",
pages = "9--17",
month = oct,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005907.1005909",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:31 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1980.bib",
note = "See correction \cite{Anonymous:1980:CBT}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Emery:1979:SSS,
author = "James E. Emery",
title = "Small-scale software components",
journal = j-SIGSOFT,
volume = "4",
number = "4",
pages = "18--21",
month = oct,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005907.1005910",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:31 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
abstract = "An empirical study to identify standardizable
small-scale software components from existing source
code is described. The rationale for such an effort is
presented, followed by a description of the specific
study performed by the author. Component identification
methods are presented along with preliminary findings.
Future identification efforts and possible notational
schemes are also discussed.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Schorer:1979:PTP,
author = "Pete Schorer",
title = "A program testing problem: request for references
and\slash or consultants",
journal = j-SIGSOFT,
volume = "4",
number = "4",
pages = "22--22",
month = oct,
year = "1979",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1005907.1005911",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:31 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
@Article{Anonymous:1980:CBT,
author = "Anonymous",
title = "Correction to {Babb} and {Tripp} paper",
journal = j-SIGSOFT,
volume = "5",
number = "1",
pages = "29--29",
month = jan,
year = "1980",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/1010782.1010786",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:11:31 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft1970.bib;
http://www.math.utah.edu/pub/tex/bib/sigsoft1980.bib",
note = "See \cite{Babb:1979:ADA}.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}
