default search action
ACM SIGSOFT Software Engineering Notes, Volume 10
Volume 10, Number 1, January 1985
- Eugene N. Miya:
On "Software engineering". 12 - J. L. Lawrence:
Why is software always late? 19-30 - J. L. Lawrence:
The RC2000: a software success story. 31-42 - Bruce I. Blum:
Understanding the software paradox. 43-46 - Dennis P. Geller:
B-ware: contradictions in a software development plan. 48-51 - Lars Olenfeldt:
A very short paper on the OBJECT/EVENT-ANALYSIS. 52-57 - Donald J. Reifer:
Review of "Principles of productive software management" by Michael W. Evans, Pamela Piazza, and James B. Dolkes. John Wiley & Sons 1983. 58 - Kenneth A. Foster:
Revision of an error sensitive test rule. 62-67 - Abstracts in software engineering. 74-81
Volume 10, Number 2, April 1985
- Questionnaire responses. 12-15
- W. D. Maurer, Tim E. Barrios:
The parable of the two programmers, continued. 19-22 - Peter G. Neumann:
Review of "The Sachertorte algorithm and other antidotes to computer anxiety" by John Shore. Viking 1985. 23-27 - Graham Tate, Thomas W. G. Docker:
A rapid prototyping system based on data flow principles. 28-34 - Neil W. Rickert:
A system for managing shared files. 35-40 - Patrick H. Loy:
System partitioning: a critical and often belittled development phase. 41-44 - Rebecca Ann Lamb:
More on software quality assurance. 45 - Sam Harbaugh:
Beware of beware. 46 - Dick Dunn:
The emerging social significance of the magnetic-tape write-enable ring. 47-50 - David P. Schwartz:
Summary of IEEE CSM WG meeting #5, 23-25 Jan 85. 51-57 - Girish Parikh:
Software maintenance news. 58-59 - Peter B. Henderson:
Software development/programming environments. 60-62 - Proceedings of the ACM Ada TEC "Future Ada environment workshop". 77-117
- Abstracts in software engineering. 118-125
Volume 10, Number 3, July 1985
- Jerrold Heyman, William M. Lively:
Syntax-directed editing revisited. 24-27 - Jeff Parker:
Towards more intelligent programming environments. 28-32 - Les Belady, Charles Richter:
The MCC software technology program. 33-36 - Vijay Kumar Garg:
Functional composition: a mechanism to compose programs. 37-39 - Rosângela Dellosso Penteado, Paulo César Masiero, Fernão Stella R. Germano:
Structure charts for Jackson system development. 40-46 - Mark D. Spinrad, Curt Abraham:
The Wild-West Lifecycle (WILI). 47-48 - Tom Gilb:
Evolutionary Delivery versus the "waterfall model". 49-61 - David J. Schultz:
Standard for the software life-cycle process. 62 - Rudy Bazelmans:
Productivity: the role of the tools group. 63-75 - Robert G. Reynolds:
PARTIAL: a tool to monitor the stepwise refinement of Ada programs. 76-94 - Jean Renard Ward:
UNIX as an environment for non-UNIX software development: a case history. 95-108 - Abstracts in software engineering. 109-117
Volume 10, Number 4, August 1985
- Dan Craigen, Donald I. Good:
Overview of verification systems. 1 - David R. Musser:
AIDS to hierarchical specification structuring and reusing theorems in AFFIRM-85. 2-4 - Michael K. Smith, Richard M. Cohen:
Gypsy verification environment: status. 5-6 - Leo Marcus, Stephen D. Crocker, Jaisook Landauer:
SDVS: a system for verifying microcode correctness. 7-14 - Stephen D. Crocker:
Engineering requirements for production quality verification systems. 15-16 - Steven T. Eckmann, Richard A. Kemmerer:
INATEST: an interactive environment for testing formal specifications. 17-18 - Daniel M. Berry:
An Ina Jo® proof manager for the formal development method. 19-25 - Dan Putnam:
The VERUS™ design verification system. 26-27 - Ole-Johan Dahl, Olaf Owe:
A presentation of the specification and verification project "ABEL". 28-32 - Dan Craigen, Mark Saaltink:
An EVES update. 33-34 - S. Kamal Abdali, Ralph L. London:
Exploiting workstations and displays in verification systems. 35-36 - Susan L. Gerhart:
Prolog technology as a basis for verification systems. 37-40 - P. Michael Melliar-Smith, John Rushby:
The enhanced HDM system for specification and verification. 41-43 - James G. Williams, Charles H. Applebaum:
The Practical Verification System Project. 44-47 - Donald I. Good, Robert S. Boyer, J Strother Moore:
A second generation verification environment. 48 - James G. Williams:
Components of verification technology. 49-50 - Raymond J. Hookway:
Verifying Ada programs. 51-52
- D. Cooper:
Overview of Theorem Proving. 53-54 - Nachum Dershowitz, David A. Plaisted:
Conditional rewriting. 55-59 - Nachum Dershowitz:
Rewriting and verification. 60 - Brian T. Smith:
Position paper to be presented at "Verification workshop III (verkshop III)" to be held in Watsonville, CA. Feb. 18-21, 1985. 61-62 - Deepak Kapur, Paliath Narendran:
An equational approach to theorem proving in first-order predicate calculus. 63-66 - Deepak Kapur, G. Sivakumar:
RRL: theorem proving environment based on rewriting techniques. 67-68 - Sam Owre:
The Sytek theorem prover. 69 - William F. Wilson, Sam Owre:
Programmable heuristics for theorem provers. 70-71 - Robert S. Boyer, Matt Kaufmann:
A prototype theorem-prover for a higher-order functional language. 72-74
- Richard A. Kemmerer:
Overview of foundations. 75 - Janice I. Glasgow, Glenn H. MacEwen:
LUCID: a specification language for distributed systems. 76-79 - Dan Craigen:
Some thoughts arising from a language design effort. 80-81 - Mark Saaltink:
Relational semantics. 82-83 - Friedrich W. von Henke:
Reasoning with Hoare sentences. 84 - John McLean:
Two dogmas of program specification. 85-87 - Old-fashioned logic for verification. 87-89
- Dan Putnam:
Separating methodology and specification constructs. 90-91 - Mark R. Pixon:
Enhancing FDM for the expression of concurrency requirements. 92-94
- Karl N. Levitt, R. Alan Whitehurst:
Overview of applications. 95-96 - R. Alan Whitehurst:
The need for an integrated design, implementation, verification and testing methodology. 97-100 - Ben Di Vito:
Towards a definition of "Beyond AI" verification. 101-102 - Jeannette M. Wing:
Beyond functional behavior: combining methods to specify different classes of properties of large systems. 102-104 - John McHugh, Karl A. Nyberg:
Ada verification using existing tools. 104-106 - Carl E. Landwehr:
Does program verification help?: how much? 107 - Terry C. Vickers Benzel:
Verification technology and the A1 criteria. 108-109 - Daniel Davis:
Resource abstraction and validation. 110 - Carl E. Landwehr:
Some lessons from formalizing a security model. 111-112 - Tad Taylor:
Verkshop position paper. 113-116 - Norman Proctor:
The restricted access processor: an example of formal verification. 116-118 - William Earl Boebert, Richard Y. Kain:
The extended access matrix model of computer security. 119-125 - Ruaridh Macdonald:
Verifying a real system design: some of the problems. 126-129 - R. Stokes:
Some formal method activities in UK industry. 129-130
Volume 10, Number 5, October 1985
- David Lorge Parnas:
Software aspects of strategic defense systems. 15-23 - Jim Horning:
Computing in support of battle management. 24-27 - Martin J. Moore:
Software engineering and SDI. 28 - David Weiss:
Strategic defense initiative software feasibility (panel): panel discussion at the 8th ICSE. 29 - Kyu Y. Lee:
Response to Jim Horning's letter. 30 - David A. Nelson:
Will the real SE metaphors please stand up!: (or, I never metaphor I didn't like!). 31-32 - Martha A. Branstad, Leonard L. Tripp:
Summary of SESAW III. 33-36 - Rudy Bazelmans:
Evolution of configuration management. 37-46 - Vincent A. Mastro:
Three dimensional system development. 47-59 - Rajeev Aggarwal:
Management of dormant files. 60-61 - Jayashree Ramanathan, John M. Rose:
TRIAD: beyond isolated systems for development-in-the-large and programming-in-the-small. 62-72 - Jayashree Ramanathan, Robert Vermilyer, Thorbjorn Anderson, John M. Rose:
The use of a relational data base in method driven environments. 73-78 - Girish Parikh:
Discovering the world of software maintenance: selected readings. 79-88 - Girish Parikh:
Software maintenance: penny wise, program foolish. 89-98
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.