default search action
Reliable Software 1975: Los Angeles, CA, USA
- Martin L. Shooman, Raymond T. Yeh:
Proceedings of the International Conference on Reliable Software 1975, Los Angeles, California, USA, April 21-23, 1975. ACM 1975, ISBN 978-1-4503-7385-2 - Ruth M. Davis:
The software reliability game. 1 - Edsger W. Dijkstra:
Guarded commands, non-determinacy and a calculus for the derivation of programs. 2 - R. D. Williams:
Managing the development of reliable software. 3-8 - Victor A. Vyssotsky:
Large-scale reliable software: Recent experience at bell labs. 9 - John D. Gannon, James J. Horning:
The impact of language design on the production of reliable software. 10-22 - Niklaus Wirth:
An assessment of the programming language PASCAL. 23-30 - Charles M. Geschke, James G. Mitchell:
On the problem of uniform references to data structures. 31-42 - A. Cicu, Marco Maiocchi, Roberto Polillo, A. Sardoni:
Organizing tests during software evolution. 43-50 - Edward F. Miller Jr., R. A. Melton:
Automated generation of testcase datasets. 51-58 - Leon G. Stucki, Gary L. Foshee:
New assertion concepts for self-metric software validation. 59-71 - Barbara Liskov, Stephen N. Zilles:
Specification techniques for data abstractions. 72-87 - Susan L. Gerhart:
Knowledge about programs: A model and case study. 88-95 - Laurian M. Chirica, David F. Martin:
An approach to compiler correctness. 96-103 - J.-C. Rault:
Design verification techniques - a review. 104 - Barry W. Boehm, Robert K. McClean, D. B. Urfrig:
Some experience with automated aids to the design of large-scale reliable software. 105-113 - Frank DeRemer, Hans H. Kron:
Programming-in-the large versus programming-in-the-small. 114-121 - William A. Wulf:
Reliable hardware-software architecture. 122-130 - Donald J. Reifer:
Automated aids fob reliable software. 131-142 - Shmuel Katz, Zohar Manna:
Towards automatic debugging of programs. 143-155 - Friedrich W. von Henke, David C. Luckham:
A methodology for verifying programs. 156-164 - Michel Caplain:
Finding Invariant assertions for proving programs. 165-171 - F. Terry Baker:
Structured programming in a production programming environment. 172-185 - L. M. Culpepper:
A system for reliable engineering software. 186-192 - Frederick P. Brooks Jr.:
The Mythical Man-Month. 193 - Isao Miyamoto:
"Software reliability in online real time environment". 194-203 - Bev Littlewood:
A reliability model for Markov structured software. 204-207 - Ashok K. Trivedi, Martin L. Shooman:
A many-state Markov model for the estimation and prediction of computer software performance parameters. 208-220 - Peter Henderson:
Finite state modelling in program development. 221-227 - James C. King:
A new approach to program testing. 228-233 - Robert S. Boyer, Bernard Elspas, Karl N. Levitt:
SELECT - a formal system for testing and debugging programs by symbolic execution. 234-245 - Raymond J. Rubey:
Quantitative aspects of software validation. 246-251 - William C. Lynch, John W. Langner, Marvin S. Schwartz:
Reliability experience with Chi/OS. 252-259 - D. E. W. Bucher:
Maintenance of the computer sciences teleprocessing system. 260-266 - Lawrence Robinson, Karl N. Levitt, Peter G. Neumann, Ashok R. Saxena:
On attaining reliable software for a secure operating system. 267-284 - Kenneth G. Walter, Samuel I. Schaen, William F. Ogden, William C. Rounds, D. G. Shumway, D. D. Schaeffer, K. J. Biba, Franklyn T. Bradshaw, S. R. Ames, J. M. Gilligan:
Structured specification of a Security Kernel. 285-293 - Gerald J. Popek, Charles S. Kline:
A verifiable protection system. 294-304 - Per Brinch Hansen:
The purpose of concurrent Pascal. 305-309 - Ashok R. Saxena, Thomas H. Bredt:
A structured specification of a hierarchical operating system. 310-318 - Michel Sintzoff, Axel van Lamsweerde:
Constructing correct and efficient concurrent programs. 319-326 - Albert Endres:
An analysis of errors and their causes in system programs. 327-336 - Norman F. Schneidewind:
Analysis of error processes in computer software. 337-346 - Martin L. Shooman, M. I. Bolsky:
Types, distribution, and test and correction times for programming errors. 347-357 - David Lorge Parnas:
The influence of software structure on reliability. 358-362 - Harlan D. Mills:
How to write correct programs and know it. 363-370 - A. O. Buda, A. A. Granovaky, Andrei P. Ershov:
Implementation of the Alpha-6 programming system. 371-381 - C. V. Ramamoorthy, Siu-Bun F. Ho:
Testing large software with automated software evaluation systems. 382-394 - Loren C. Carpenter, Leonard L. Tripp:
Software design validation tool. 395-400 - N. P. Edwards:
The effect of certain modular design principles on testability. 401-410 - Donald I. Good:
Provable programming. 411-419 - Mark S. Laventhal:
Verifying programs which operate on data structures. 420-426 - R. Infante, U. Montanary:
Proving structured programs correct, level by level. 427-436 - Brian Randell:
System structure for software fault tolerance. 437-449 - Stephen S. Yau, R. C. Cheung:
Design of self-checking software. 450-455 - Algirdas Avizienis:
Fault-tolerance and fault-intolerance: Complementary approaches to reliable computing. 458-464 - Rod M. Burstall, John Darlington:
Some transformations for developing recursive programs. 465-472 - Norihisa Suzuki:
Verifying programs by algebraic and logical reduction. 473-481 - Donald I. Good, Ralph L. London, W. W. Bledsoe:
An interactive program verification system. 482-492 - John B. Goodenough, Susan L. Gerhart:
Toward a theory of test data selection. 493-510 - Hermann Kopetz:
On the connections between range of variable and control structure testing. 511-517 - John R. Brown, Myron Lipow:
Testing for software reliability. 518-527 - C. A. R. Hoare:
Data reliability. 528-533 - Ralph L. London:
A view of program verification. 534-545 - Edsger W. Dijkstra:
Correctness concerns and, among other things, why they are resented. 546
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.