State table analysis of programs in an algo-like language. - David Lorge Parnas (ACM National Conference, 1966)

A language for describing the functions of synchronous systems. - David Lorge Parnas (Commun. ACM, 1966)

On the preliminary report of C3S. - David Lorge Parnas (Commun. ACM, 1966)

On facilitating parallel and multiprocessing in ALGOL. - David Lorge Parnas (Commun. ACM, 1966)

State table analysis of programs in an ALGOL-like language. - David Lorge Parnas (Commun. ACM, 1966)

SODAS and a methodology for system design. - David Lorge Parnas; John A. Darringer (AFIPS Fall Joint Computing Conference, 1967)

Letters to the editor: on improving the quality of our technical meetings. - David Lorge Parnas (Commun. ACM, 1968)

On the use of transition diagrams in the design of a user interface for an interactive computer system. - David Lorge Parnas (ACM National Conference, 1969)

More on simulation languages and design methodology for computer systems. - David Lorge Parnas (AFIPS Spring Joint Computing Conference, 1969)

On simulating networks of parallel processes in which simultaneous events may occur. - David Lorge Parnas (Commun. ACM, 1969)

Information Distribution Aspects of Design Methodology. - David Lorge Parnas (IFIP Congress (1), 1971)

Concurrent Control with "Readers" and "Writers". - Pierre-Jacques Courtois; F. Heymans; David Lorge Parnas (Commun. ACM, 1971)

Some conclusions from an experiment in software engineering techniques. - David Lorge Parnas (AFIPS Fall Joint Computing Conference (1), 1972)

A course on software engineering techniques. - David Lorge Parnas (SIGCSE, 1972)

Comments on "A Comparison of Two Synchronizing Concepts by Per Brinch Hansen". - Pierre-Jacques Courtois; F. Heymans; David Lorge Parnas (Acta Informatica, 1972)

A Technique for Software Module Specification with Examples. - David Lorge Parnas (Commun. ACM, 1972)

On the Criteria To Be Used in Decomposing Systems into Modules. - David Lorge Parnas (Commun. ACM, 1972)

Comment on Deadlock Prevention Method. - David Lorge Parnas; A. Nico Habermann (Commun. ACM, 1972)

The design of the virtual memory aspects of a virtual machine. - David Lorge Parnas; William R. Price (Workshop on Virtual Computer Systems, 1973)

Software Engineering or Methods for the Multi - Person Construction of Multi - Version Programs. - David Lorge Parnas (Programming Methodology, 1974)

On a 'Buzzword': Hierarchical Structure. - David Lorge Parnas (IFIP Congress, 1974)

Information Streams Sharing a Finite Buffer: Other Solutions. - Lee W. Cooprider; F. Heymans; Pierre-Jacques Courtois; David Lorge Parnas (Inf. Process. Lett., 1974)

The influence of software structure on reliability. - David Lorge Parnas (Reliable Software, 1975)

Significant Event Simulation. - Alan F. Babich; John Grason; David Lorge Parnas (Commun. ACM, 1975)

On a Solution to the Cigarette Smoker's Problem (Without Conditional Statements). - David Lorge Parnas (Commun. ACM, 1975)

Use of the Concept of Transparency in the Design of Hierarchically Structured Systems. - David Lorge Parnas; Daniel P. Siewiorek (Commun. ACM, 1975)

Evaluation criteria for abstract machines with unknown applications. - David Lorge Parnas (SIGARCH Comput. Archit. News, 1975)

On the need for fewer restrictions in changing compile-time environments. - David Lorge Parnas; John E. Shore; W. David Elliott (ACM SIGPLAN Notices, 1975)

Design and Specification of the Minimal Subset of an Operating System Family (Abstract). - David Lorge Parnas; Georg Handzel; Harald Würges (ICSE, 1976)

Response to Undesired Events in Software Systems. - David Lorge Parnas; Harald Würges (ICSE, 1976)

Abstract Types Defined as Classes of Variables. - David Lorge Parnas; John E. Shore; David M. Weiss 001 (Conference on Data: Abstraction, Definition and Structure, 1976)

On the Design and Development of Program Families. - David Lorge Parnas (IEEE Trans. Software Eng., 1976)

Design and Specification of the Minimal Subset of an Operating System Family. - David Lorge Parnas; Georg Handzel; Harald Würges (IEEE Trans. Software Eng., 1976)

The Use of Precise Specification in the Development of Software. - David Lorge Parnas (IFIP Congress, 1977)

Building reliable software in BLOWHARD. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1977)

ACM (Association of Carriage Manufacturers): SIGTRANS notices - another historical item. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1977)

Using assertions about traces to write abstract specifications for software modules. - Wolfram Bartussek; David Lorge Parnas (ECI, 1978)

The non-problem of nested monitor calls. - David Lorge Parnas (ACM SIGOPS Oper. Syst. Rev., 1978)

Another view of the Dijkstra-dMLP controversy. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1978)

Designing Software for Ease of Extension and Contraction. - David Lorge Parnas (IEEE Trans. Software Eng., 1979)

A Procedure for Designing Abstract Interfaces for Device Interface Modules. - K. H. Britton; R. A. Parker; David Lorge Parnas (ICSE, 1981)

Lastig gepreek uit nuenen. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1981)

Rapid prototyping by means of abstract module specifications written as trace axioms. - John K. Dixon; John McLean; David Lorge Parnas (Rapid Prototyping, 1982)

A Technique for Software Module Specification with Examples (Reprint). - David Lorge Parnas (Commun. ACM, 1983)

A Generalized Control Structure and Its Formal Definition. - David Lorge Parnas (Commun. ACM, 1983)

Software Aspects of Strategic Defense Systems. - David Lorge Parnas (Commun. ACM, 1985)

The Parnas papers. - David Lorge Parnas (SIGCAS Comput. Soc., 1985)

The Modular Structure of Complex Systems. - David Lorge Parnas; Paul C. Clements; David M. Weiss 001 (IEEE Trans. Software Eng., 1985)

Why We Would Never Trust the SDI Software. - David Lorge Parnas (COMPCON, 1986)

A Rational Design Process: How and Why to Fake it. - David Lorge Parnas; Paul C. Clements (IEEE Trans. Software Eng., 1986)

Correction to "A Rational Design Process: How and Why to Fake It". - David Lorge Parnas; Paul C. Clements (IEEE Trans. Software Eng., 1986)

Warum ich an SDI nicht mitarbeite: Eine Auffassung beruflicher Verantwortung. - David Lorge Parnas (Inform. Spektrum, 1987)

Active design reviews: Principles and practices. - David Lorge Parnas; David M. Weiss 001 (J. Syst. Softw., 1987)

On Synchronization in Hard-Real-Time Systems. - Stuart R. Faulk; David Lorge Parnas (Commun. ACM, 1988)

Documentation of Communications Services and Protocols. - David Lorge Parnas (FORTE, 1989)

On "Artificial Intelligence and Expert Systems - Myths, Legends, and Facts". - David Lorge Parnas (IFIP Congress, 1989)

Functional Specifications for Old (and New) Software. - David Lorge Parnas (GI Jahrestagung (1), 1990)

Education for Computing Professionals (Abstract). - David Lorge Parnas (ICCI, 1990)

Evaluation of Safety-Critical Software. - David Lorge Parnas; A. John van Schouwen; Shu Po Kwan (Commun. ACM, 1990)

Education for Computing Professionals. - David Lorge Parnas (Computer, 1990)

On Iterative Constructs. - David Lorge Parnas (ACM Trans. Program. Lang. Syst., 1990)

Scheduling Processes with Release Times, Deadlines, Precedence, and Exclusion Relations. - Jia Xu; David Lorge Parnas (IEEE Trans. Software Eng., 1990)

Trace Rewriting Systems. - Yabo Wang; David Lorge Parnas (CTRS, 1992)

A Formal Approach to Computer Systems Requirements Documentation. - Marcin Engel; Marcin Kubica 001; Jan Madey; David Lorge Parnas; Anders P. Ravn; A. John van Schouwen (Hybrid Systems, 1992)

Documentation for Safety Critical Software. - Pierre-Jacques Courtois; David Lorge Parnas (ICSE, 1993)

Simulating the Behaviour of Software Modules by Trace Rewriting. - Yabo Wang; David Lorge Parnas (ICSE, 1993)

Documentation of requirements for computer systems. - A. John van Schouwen; David Lorge Parnas; Jan Madey (RE, 1993)

Some Theorems We Should Prove. - David Lorge Parnas (HUG, 1993)

Predicate Logic for Software Engineering. - David Lorge Parnas (IEEE Trans. Software Eng., 1993)

On Satisfying Timing Constraints in Hard-Real-Time Systems. - Jia Xu; David Lorge Parnas (IEEE Trans. Software Eng., 1993)

Correction to "On Satisfying Timing Constraints in Hard-Real-Time Systems''. - Jia Xu; David Lorge Parnas (IEEE Trans. Software Eng., 1993)

Software Aging. - David Lorge Parnas (ICSE, 1994)

Mathematical Description and Specification of Software. - David Lorge Parnas (IFIP Congress (1), 1994)

The Professional Responsibilities of Software Engineers. - David Lorge Parnas (IFIP Congress (2), 1994)

Inspection of Safety-Critical Software Using Program-Function Tables. - David Lorge Parnas (IFIP Congress (3), 1994)

Generating a Test Oracle from Program Documentation (Work in Progress). - Dennis K. Peters; David Lorge Parnas (ISSTA, 1994)

Precise Documentation of Well-Structured Programs. - David Lorge Parnas; Jan Madey; Michal Iglewski (IEEE Trans. Software Eng., 1994)

Simulating the Behavior of Software Modules by Trace Rewriting. - Yabo Wang; David Lorge Parnas (IEEE Trans. Software Eng., 1994)

The Future of Formal Methods in Industry. - Anthony Hall; David Lorge Parnas; Nico Plat; John M. Rushby; Chris T. Sennett (ZUM, 1995)

Language-Free Mathematical Methods for Software Design. - David Lorge Parnas (ZUM, 1995)

Teaching Programming as Engineering. - David Lorge Parnas (ZUM, 1995)

Functional Documents for Computer Systems. - David Lorge Parnas; Jan Madey (Sci. Comput. Program., 1995)

On ICSE's "most influential" papers. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1995)

An Invitation to Formal Methods. - Jonathan P. Bowen; Ricky W. Butler; David L. Dill; Robert L. Glass; David Gries; Anthony Hall; Michael G. Hinchey; C. Michael Holloway; Daniel Jackson 001; Cliff B. Jones; Michael J. Lutz; David Lorge Parnas; et al. (Computer, 1996)

Why Software Jewels Are Rare. - David Lorge Parnas (Computer, 1996)

Tabular Representations in Relational Documents. - Ryszard Janicki; David Lorge Parnas; Jeffery I. Zucker (Relational Methods in Computer Science, 1997)

Teaching for Change. - David Lorge Parnas (CSEE&T, 1997)

Software Engineering: An Unconsummated Marriage (Extended Abstract). - David Lorge Parnas (ESEC / SIGSOFT FSE, 1997)

Software Engineering: An Unconsummated Marriage. - David Lorge Parnas (Commun. ACM, 1997)

Software Engineering Programmes are not Computer Science Programmes. - David Lorge Parnas (Ann. Softw. Eng., 1998)

"Formal methods" technology transfer will fail. - David Lorge Parnas (J. Syst. Softw., 1998)

Successful software engineering research. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1998)

Who taught me about software engineering research? - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1998)

Using Test Oracles Generated from Program Documentation. - Dennis K. Peters; David Lorge Parnas (IEEE Trans. Software Eng., 1998)

An Easily Extensible Toolset for Tabular Mathematical Expressions. - David Lorge Parnas; Dennis K. Peters (TACAS, 1999)

Tools for Component Documentation, Analysis and Testing. - David Lorge Parnas (TOOLS (30), 1999)

Systematic Techniques for Inspecting Critical Software. - David Lorge Parnas (TOOLS (30), 1999)

Ten Myths About Y2K Inspections. - David Lorge Parnas (Commun. ACM, 1999)

On code reuse. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1999)

Parnas on Parnas: a life of indecision. - David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 1999)

Software Engineering Programs Are Not Computer Science Programs. - David Lorge Parnas (IEEE Softw., 1999)

Invited Talk: A Software Engineering Program of Lasting Value. - David Lorge Parnas (AMAST, 2000)

Making Mathematical Methods More Practical for Software Developers (Invited Talk). - David Lorge Parnas (AMAST, 2000)

The Use of Mathematics in Software Engineering. - David Lorge Parnas (ICFEM, 2000)

Requirements Documentation: Why a Formal Basis is Essential. - David Lorge Parnas (ICRE, 2000)

Two Positions on Licensing. - David Lorge Parnas (ICRE, 2000)

Priority Scheduling Versus Pre-Run-Time Scheduling. - Jia Xu; David Lorge Parnas (Real Time Syst., 2000)

Software Documentation and the Verification Process. - David Lorge Parnas (CAV, 2001)

Software Engineering Research Agendas Panel (SERA): What Can't We Do, But Need to Learn How to Do? - H. Dieter Rombach; Manfred Broy; Michael Evangelist; Ali Mili 001; Leon J. Osterweil; David Lorge Parnas (ICSE, 2001)

Systematic Documentation of Requirements. - David Lorge Parnas (RE, 2001)

University Programmes in Software Development. - David Lorge Parnas (SEUH, 2001)

Computers: boon or bane? - Peter G. Neumann; David Lorge Parnas (Commun. ACM, 2001)

RelMiS 2001 - Preface. - Wolfram Kahl; David Lorge Parnas; Gunther Schmidt 001 (RelMiS, 2001)

The Tabular Method for Relational Documentation. - David Lorge Parnas (RelMiS, 2001)

The Secret History of Information Hiding. - David Lorge Parnas (Software Pioneers, 2002)

On the Criteria To Be Used in Decomposing Systems into Modules (Reprint). - David Lorge Parnas (Software Pioneers, 2002)

On a 'Buzzword': Hierarchical Structure (Reprint). - David Lorge Parnas (Software Pioneers, 2002)

Licensing software engineers in Canada. - David Lorge Parnas (Commun. ACM, 2002)

Requirements-Based Monitors for Real-Time Systems. - Dennis K. Peters; David Lorge Parnas (IEEE Trans. Software Eng., 2002)

Software Inspections We Can Trust. - David Lorge Parnas (FIDJI, 2003)

Modularity in the New Millenium: A Panel Summary. - Premkumar T. Devanbu; Robert Balzer; Don S. Batory; Gregor Kiczales; John Launchbury; David Lorge Parnas; Peri L. Tarr (ICSE, 2003)

The Limits of Empirical Studies of Software Engineering. - David Lorge Parnas (ISESE, 2003)

Structured programming: A minor part of software engineering. - David Lorge Parnas (Inf. Process. Lett., 2003)

Guest Editors' Introduction: Inspection's Role in Software Quality Assurance. - David Lorge Parnas; Mark Lawford (IEEE Softw., 2003)

The Role of Inspection in Software Quality Assurance. - David Lorge Parnas; Mark Lawford (IEEE Trans. Software Eng., 2003)

New Year's Resolutions for Software Quality. - Victor R. Basili; Barry W. Boehm; Al Davis; Watts S. Humphrey; Nancy G. Leveson; Nancy R. Mead; John D. Musa; David Lorge Parnas; Shari Lawrence Pfleeger; Elaine J. Weyuker (IEEE Softw., 2004)

Document Driven Disciplined Development of Software. - David Lorge Parnas (Australian Software Engineering Conference, 2005)

Availability Evaluation of Hardware/Software Systems with Several Recovery Procedures. - Sergiy A. Vilkomir; David Lorge Parnas; Veena B. Mendiratta; Eamonn Murphy (COMPSAC (1), 2005)

A Family of Mathematical Methods for Professional Software Documentation. - David Lorge Parnas (IFM, 2005)

Disciplined Methods of Software Specification: A Case Study. - Robert L. Baber; David Lorge Parnas; Sergiy A. Vilkomir; Paul Harrison; Tony O'Connor (ITCC (2), 2005)

Wikipedia risks. - Peter J. Denning; Jim Horning; David Lorge Parnas; Lauren Weinstein (Commun. ACM, 2005)

Using information about functions in selecting test cases. - Markus Clermont; David Lorge Parnas (ACM SIGSOFT Softw. Eng. Notes, 2005)

Goals for software engineering student education. - David Lorge Parnas; Lillian Chik-Parnas (ACM SIGSOFT Softw. Eng. Notes, 2005)

Segregated failures model for availability evaluation of fault-tolerant systems. - Sergiy A. Vilkomir; David Lorge Parnas; Veena B. Mendiratta; Eamonn Murphy (ACSC, 2006)

Specification of Software Component Requirements Using the Trace Function Method. - Colm Quinn; Sergiy A. Vilkomir; David Lorge Parnas; Srdjan Kostic (ICSEA, 2006)

Inspection of Concurrent Systems: Combining Tables, Theorem Proving and Model Checking. - Vera Pantelic; Xiao-Hui Jin; Mark Lawford; David Lorge Parnas (Software Engineering Research and Practice, 2006)

Component Interface Documentation: What do we Need and Why do we Need it? - David Lorge Parnas (SoMeT, 2006)

Resolving Dilemmas in Software Engineering Education. - David Lorge Parnas (CSEE&T, 2007)

Precise Documentation of Critical Software. - David Lorge Parnas; Sergiy A. Vilkomir (HASE, 2007)

Document-Driven Software Design: A Novel Approach That Should Not Be Novel. - David Lorge Parnas (ICSOFT (PL/DPS/KE/MUSE), 2007)

Tabular Expressions and Total Functional Programming. - Baltasar Trancón y Widemann; David Lorge Parnas (IFL, 2007)

"No silver bullet" reloaded: retrospective on "essence and accidents of software engineering". - Steven Fraser 001; Frederick P. Brooks Jr.; Martin Fowler; Ricardo López; Aki Namioka; Linda M. Northrop; David Lorge Parnas; Dave A. Thomas (OOPSLA Companion, 2007)

Precise software documentation: making object-orientation work better. - David Lorge Parnas (OOPSLA Companion, 2007)

Software Product-Lines: What To Do When Enumaration Won't Work. - David Lorge Parnas (VaMoS, 2007)

Which is riskier: OS diversity or OS monopoly? - David Lorge Parnas (Commun. ACM, 2007)

Stop the numbers game. - David Lorge Parnas (Commun. ACM, 2007)

Fault Propagation in Tabular Expression-Based Specifications. - Xin Feng; David Lorge Parnas; T. H. Tse (COMPSAC, 2008)

Connecting Good Theory to Good Practice: Software Documentation: A Case Study. - David Lorge Parnas (Software Engineering, 2008)

Computer systems availability evaluation using a segregated failures model. - Sergiy A. Vilkomir; David Lorge Parnas; Veena B. Mendiratta; Eamonn Murphy (Qual. Reliab. Eng. Int., 2008)

Document based rational software development. - David Lorge Parnas (Knowl. Based Syst., 2009)

Point/Counterpoint. - David Lorge Parnas; Bill Curtis (IEEE Softw., 2009)

Precise Documentation: The Key to Better Software. - David Lorge Parnas (The Future of Software Engineering, 2010)

A documentation approach for the self-adaptive system design. - Wenhui Zhu; David Lorge Parnas (SEKE, 2010)

From Requirements to Architecture. - David Lorge Parnas (SoMeT, 2010)

Risks of undisciplined development. - David Lorge Parnas (Commun. ACM, 2010)

Really Rethinking 'Formal Methods'. - David Lorge Parnas (Computer, 2010)

Documenting and verifying systems assembled from components. - Zhiying Liu; David Lorge Parnas; Baltasar Trancón y Widemann (Frontiers Comput. Sci. China, 2010)

A family of computer systems for delivering individualized advice. - Lillian Chik-Parnas; Marius Dragomiroiu; David Lorge Parnas (Knowl. Based Syst., 2010)

Defining the meaning of tabular mathematical expressions. - Ying Jin 002; David Lorge Parnas (Sci. Comput. Program., 2010)

Software Engineering: Multi-person Development of Multi-version Programs. - David Lorge Parnas (Dependable and Historic Computing, 2011)

The Use of Mathematics in Software Development - (Extended Abstract). - David Lorge Parnas (ICTAC, 2011)

The risks of stopping too soon. - David Lorge Parnas (Commun. ACM, 2011)

Software Engineering - Missing in Action: A Personal Perspective. - David Lorge Parnas (Computer, 2011)

A Comparison of Tabular Expression-Based Testing Strategies. - Xin Feng; David Lorge Parnas; T. H. Tse; Tony O'Callaghan (IEEE Trans. Software Eng., 2011)

The use of mathematics in software quality assurance. - David Lorge Parnas (Frontiers Comput. Sci. China, 2012)

The real risks of artificial intelligence. - David Lorge Parnas (Commun. ACM, 2017)

Software Systems Engineering programmes a capability approach. - Carl E. Landwehr; Jochen Ludewig; Robert Meersman; David Lorge Parnas; Peretz Shoval; Yair Wand; David M. Weiss 001; Elaine J. Weyuker (J. Syst. Softw., 2017)

Software Structures: A Careful Look. - David Lorge Parnas (IEEE Softw., 2018)

Software Engineering: A Profession in Waiting. - David Lorge Parnas (Computer, 2021)