Journal: ACM SIGSOFT Software Engineering Notes

Volume 4, Issue 4

6 -- 8Jim Horning. A note on program reliability
9 -- 17Robert G. Babb II, Leonard L. Tripp. An approach to defining areas within the field of software engineering
18 -- 21James E. Emery. Small-scale software components
22 -- 0Peter Schorer. A program testing problem: request for references and/or consultants

Volume 4, Issue 3

3 -- 5Norman F. Schneidewind. Secretary-Treasurer's report to SIGSOFT members
7 -- 14William G. Bail. User experiences with specification tools: (panel from specifications of reliable software conference) (April 3-5, 1979)
15 -- 16John E. Shore, Kathryn L. Heninger. Limits to specifications: why not more progress? Panel at IEEE conference on <u>specifications of reliable software</u>
17 -- 18Pamela Zave. Panel session: approaches to specification-various models <u>an informal report</u>
19 -- 21Mark A. Ardis. Specifications of reliable software - what next?
22 -- 31David A. Marca. A method for specifying structured programs
32 -- 33Tom Gilb. A comment on "the definition of maintainability"

Volume 4, Issue 2

7 -- 12David Gelperin. Testing maintainability
13 -- 16Richard E. Fairley. Masters curriculum in software engineering
17 -- 18Richard G. Hamlet. Report on Florida testing workshop
19 -- 20. Abstracts in software engineering: part 9

Volume 4, Issue 1

8 -- 11Edward F. Miller. Some statistics from the software testing service
12 -- 17Richard E. Fairley. Masters curriculum in software engineering
18 -- 0Dennis P. Geller. Letter on Parker's "design methodologies: a comparison"
19 -- 20. An alternative to structured programming: syndicate programming
19 -- 0Haim Kilov. Letter on Parnas' view of Dijkstra vs. deMillo, Lipton and Perlis
21 -- 0. A note on the psychology of abstraction (PGN)
22 -- 24. Abstracts in software engineering: part 8