Last update:
Thu Nov 3 12:53:30 MDT 2022
Anthony Ira Wasserman A top-down view of software engineering 8--14
B. W. Kernighan and
P. J. Plauger Software tools . . . . . . . . . . . . . 15--20
Donald J. Reifer The smart stub as a software management
tool . . . . . . . . . . . . . . . . . . 4--8
Software Engineering Notes Staff Abstracts in software engineering . . . 9--32
Software Engineering Notes Staff Abstracts in software engineering: part
2 . . . . . . . . . . . . . . . . . . . 6--14
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 Gypsy: a language for specification and
implementation of verifiable programs 1--10
G. J. Popek and
J. J. Horning and
B. W. Lampson and
J. G. Mitchell and
R. L. London Notes on the design of Euclid . . . . . 11--18
Charles N. Fischer and
Richard J. LeBlanc Efficient implementation and
optimization of run-time checking in
PASCAL . . . . . . . . . . . . . . . . . 19--24
Allen L. Ambler and
Charles G. Hoch A study of protection in programming
languages . . . . . . . . . . . . . . . 25--40
Daniel P. Friedman and
David S. Wise Aspects of applicative programming for
file systems (Preliminary Version) . . . 41--55
Robert G. Herriot Towards the ideal programming language 56--62
Jhon V. Guttag and
Ellis Horowitz and
David R. Musser Some extensions to algebraic
specifications . . . . . . . . . . . . . 63--67
Normand Buckle Restricted data types, specification and
enforcement of invariant properties of
variables . . . . . . . . . . . . . . . 68--76
Patrick Cousot and
Radhia Cousot Static determination of dynamic
properties of generalized type unions 77--94
P. M. Melliar-Smith and
B. Randell Software reliability: The role of
programmed exception handling . . . . . 95--100
M. Donald MacLaren Exception handling in PL/I . . . . . . . 101--104
Tom Love An experimental investigation of the
effect of program structure on program
understanding . . . . . . . . . . . . . 105--113
Gregory R. Andrews and
James R. McGraw Language features for process
interaction . . . . . . . . . . . . . . 114--127
D. B. Lomet Process structuring, synchronization,
and recovery using atomic actions . . . 128--137
Charles M. Geschke and
James H. Morris, Jr. and
Edwin H. Satterthwaite Early experience with Mesa . . . . . . . 138
Mary Shaw and
Wm A. Wulf and
Ralph L. London Abstraction and verification in Alphard:
Defining and specifying iteration and
generators . . . . . . . . . . . . . . . 139
Barbara Liskov and
Alan Snyder and
Russell Atkinson and
Craig Schaffert Abstraction mechanisms in CLU . . . . . 140
J. D. Gannon An experimental evaluation of data types
on programming reliability . . . . . . . 141
N. Wirth Towards a discipline of real-time
programming . . . . . . . . . . . . . . 142
David L. Parnas Building reliable software in BLOWHARD 5--6
L. Robinson Reliable software and the design process 7--10
James C. King Panel: limitations of language design
for reliable software . . . . . . . . . 11--12
Irv. K. Wendel and
Richard L. Kleir FORTRAN error detection through static
analysis . . . . . . . . . . . . . . . . 22--28
David Rine Review of \booktitleSoftware engineering
education: needs and objectives by
Anthony I. Wasserman and Peter Freeman.
Springer-Verlag 1976 . . . . . . . . . . 32--32
William E. Riddle and
John H. Sayler and
Alan R. Segal and
Jack C. Wileden An introduction to the DREAM software
design system . . . . . . . . . . . . . 11--24
Software Engineering Notes Staff Abstracts in software engineering: part
3 . . . . . . . . . . . . . . . . . . . 24--28
Edsger W. Dijkstra A position paper on software reliability 3--5
Dave Parnas ACM (Association of Carriage
Manufacturers): SIGTRANS notices ---
another historical item . . . . . . . . 6--7
Donald I. Good Constructing verified and reliable
communications processing systems . . . 8--13
R. Leonard Brown and
Paul G. Tuttle High level language utilization of
special hardware features . . . . . . . 14--16
Susan L. Gerhart A proposal for publication and exchange
of program proofs . . . . . . . . . . . 7--17
Karl Kleine Selected annotated bibliography on
software engineering . . . . . . . . . . 18--25
Leslie Lamport State the problem before describing the
solution . . . . . . . . . . . . . . . . 26--26
Linda M. Ottenstein Further validation of an error
hypothesis . . . . . . . . . . . . . . . 27--28
Software Engineering Notes Staff Abstracts in software engineering: part
5 . . . . . . . . . . . . . . . . . . . 28--32
Theodore A. Linden Specifying abstract data types by
restriction . . . . . . . . . . . . . . 7--13
Edsger W. Dijkstra On a Political Pamphlet from the Middle
Ages . . . . . . . . . . . . . . . . . . 14--16
Richard A. DeMillo and
Richard J. Lipton and
Alan J. Perlis Response from R. A. DeMillo, R. J.
Lipton, A. J. Perlis . . . . . . . . . . 16--17
H. J. Jeffrey On Dijkstra's position paper on software
reliability . . . . . . . . . . . . . . 18--18
Thomas Gilkey Comment on Karl Kleine's ``selected
bibliography'' . . . . . . . . . . . . . 19--19
W. M. Turski and
Anthony I. Wasserman Computer programming methodology . . . . 20--21
Herbert Harrell A note on methodological review . . . . 5--7
Harald Würges Some remarks on the use of abstract
specifications for operating systems . . 8--12
Farshid Nourani A note on logic-oriented approaches to
data abstraction . . . . . . . . . . . . 13--15
Theodore A. Linden On formal specifications and
completeness: reply to Farshid Nourani 15--17
Steve Meyer Should computer programs be verified? 18--19
Roger Van Ghent Letter on real software, regarding the
commentary by Dijkstra and the reply by
DeMillo, Lipton and Perlis . . . . . . . 20--21
W. D. Maurer Another letter on the correctness of
real programs . . . . . . . . . . . . . 22--24
Theodore D. Lassagne Analysis is the key to better software
design . . . . . . . . . . . . . . . . . 24--26
Tom Gilb Multidimensional quantified goals should
direct software design processes . . . . 26--28
Software Engineering Notes Staff Abstracts in software engineering: part
6 . . . . . . . . . . . . . . . . . . . 31--33
William E. Riddle and
Jack C. Wileden Languages for representing software
specifications and designs . . . . . . . 7--11
John Parker A comparison of design methodologies . . 12--19
David L. Parnas Another view of the Dijkstra--dMLP
controversy . . . . . . . . . . . . . . 20--21
Mary Shaw Letter on Lebesgue, logic, and program
testing . . . . . . . . . . . . . . . . 21--21
William J. Raduchel Managing software development . . . . . 22--26
Kathie Priebe Some ideas on review methodology . . . . 27--29
Marvin V. Zelkowitz Productivity measurement on software
engineering projects . . . . . . . . . . 30--31
Software Engineering Notes Staff Abstracts in software engineering: part
6 . . . . . . . . . . . . . . . . . . . 31--33
Pamela R. Pfau Applied quality assurance methodology 1--8
Edward H. Bersoff and
Vilas D. Henderson and
Stan G. Siegel Software Configuration Management . . . 9--17
Robert L. Glass Computing failure: a learning experience 18--19
Donald A. Woodmancy A Software Quality Improvement Program 20--26
Marilyn S. Fujii A comparison of software assurance
methods . . . . . . . . . . . . . . . . 27--32
Alan N. Sukert and
Amrit L. Goel Error modelling applications in software
quality assurance . . . . . . . . . . . 33--38
Joe W. Duran and
John J. Wiorkowski Toward models for probabilistic program
correctness . . . . . . . . . . . . . . 39--44
B. H. Yin and
J. W. Winchester The establishment and use of measures to
evaluate the quality of software designs 45--52
Robert A. Pierce A Requirements Tracing Tool . . . . . . 53--60
Alan M. Davis and
Walter J. Rataj Requirements language processing for the
effective testing of real-time systems 61--66
Lawrence Peters Relating software requirements and
design . . . . . . . . . . . . . . . . . 67--71
Allan M. Stavely Design feedback and its use in software
design aid systems . . . . . . . . . . . 72--78
Cornelia M. Yoder and
Marilyn L. Schrag Nassi--Shneiderman charts an alternative
to flowcharts for design . . . . . . . . 79--86
J. P. Benson and
S. H. Saib A software quality assurance experiment 87--91
Jonathan Bauer and
Susan Faasse and
Alan Finger and
William Goodhue The automatic generation and execution
of function test plans for electronic
switching systems . . . . . . . . . . . 92--100
K. A. Martin Software acceptance testing that goes
beyond the book . . . . . . . . . . . . 101--105
Frederick J. Drasch and
Richard A. Bowen IDBUG: a tool for program development 106--110
M. E. Stickney An application of graph theory to
software test data selection . . . . . . 111--115
Kurt F. Fischer Software quality assurance tools: Recent
experience and future requirements . . . 116--121
Alan L. Glasser The evolution of a Source Code Control
System . . . . . . . . . . . . . . . . . 122--125
William H. Josephs A mini-computer based library control
system . . . . . . . . . . . . . . . . . 126--132
Joseph P. Cavano and
James A. McCall A framework for the measurement of
software quality . . . . . . . . . . . . 133--139
Gary W. Cobb A measurement of structure for
unstructured programming languages . . . 140--147
John B. Bowen Are current approaches sufficient for
measuring software quality? . . . . . . 148--155
Joann Lockett Using performance metrics in system
design . . . . . . . . . . . . . . . . . 156--159
Richard N. Southworth Responding to MIL-S-52779 . . . . . . . 160--164
Michael F. Tighe The value of a proper software quality
assurance methodology . . . . . . . . . 165--172
Peter Chase Belford and
Carlo Broglio A quantitative evaluation of the
effectiveness of quality assurance as
experienced on a large-scale software
development effort . . . . . . . . . . . 173--180
Paul J. Kacik An example of software quality assurance
techniques used in a successful large
scale software development . . . . . . . 181--186
Edward F. Miller Some statistics from the software
testing service . . . . . . . . . . . . 8--11
Richard E. Fairley Masters curriculum in software
engineering . . . . . . . . . . . . . . 12--17
Dennis P. Geller Letter on Parker's ``Design
methodologies: a comparison'' . . . . . 18--18
H. Kilov Letter on Parnas' view of Dijkstra vs.
deMillo, Lipton and Perlis . . . . . . . 19--19
Software Engineering Notes Staff An alternative to structured
programming: syndicate programming . . . 19--20
Software Engineering Notes Staff A note on the psychology of abstraction
(PGN) . . . . . . . . . . . . . . . . . 21--21
Software Engineering Notes Staff Abstracts in software engineering: part
8 . . . . . . . . . . . . . . . . . . . 22--24
David Gelperin Testing maintainability . . . . . . . . 7--12
Richard E. Fairley Masters curriculum in software
engineering . . . . . . . . . . . . . . 13--16
Richard Hamlet Report on Florida testing workshop . . . 17--18
Software Engineering Notes Staff Abstracts in software engineering: part
9 . . . . . . . . . . . . . . . . . . . 19--20
Norm Schneidewind Secretary-Treasurer's report to SIGSOFT
members . . . . . . . . . . . . . . . . 3--5
William G. Bail User experiences with specification
tools: (panel from Specifications of
Reliable Software Conference) (April
3--5, 1979) . . . . . . . . . . . . . . 7--14
John E. Shore and
Kathryn L. Heninger Limits to specifications: why not more
progress? Panel at IEEE conference on
specifications of reliable software . . 15--16
Pamela Zave Panel session: Approaches to
specification-various models: an
informal report . . . . . . . . . . . . 17--18
Mark A. Ardis Specifications of reliable software ---
what next? . . . . . . . . . . . . . . . 19--21
David Marca A method for specifying structured
programs . . . . . . . . . . . . . . . . 22--31
Tom Gilb A comment on ``The definition of
maintainability'' . . . . . . . . . . . 32--33
Jim Horning A note on program reliability . . . . . 6--8
Robert G. Babb and
Leonard L. Tripp An approach to defining areas within the
field of software engineering . . . . . 9--17
James E. Emery Small-scale software components . . . . 18--21
Pete Schorer A program testing problem: request for
references and/or consultants . . . . . 22--22
Anonymous Correction to Babb and Tripp paper . . . 29--29