David Lorge Parnas

ORCID

Publication Activity (10 Years)

Years Active: 1966-2021
Publications (10 Years): 4

Top Venues

Publications

David Lorge Parnas
Software Engineering: A Profession in Waiting. Computer 54 (5) (2021)
David Lorge Parnas
Software Structures: A Careful Look. IEEE Softw. 35 (6) (2018)
Carl E. Landwehr, Jochen Ludewig, Robert Meersman, David Lorge Parnas, Peretz Shoval, Yair Wand, David M. Weiss, Elaine J. Weyuker
Software Systems Engineering programmes a capability approach. J. Syst. Softw. 125 (2017)
David Lorge Parnas
The real risks of artificial intelligence. Commun. ACM 60 (10) (2017)
David Lorge Parnas
The use of mathematics in software quality assurance. Frontiers Comput. Sci. China 6 (1) (2012)
David Lorge Parnas
Software Engineering: Multi-person Development of Multi-version Programs. Dependable and Historic Computing (2011)
David Lorge Parnas
The risks of stopping too soon. Commun. ACM 54 (6) (2011)
David Lorge Parnas
The Use of Mathematics in Software Development - (Extended Abstract). ICTAC (2011)
Xin Feng, David Lorge Parnas, T. H. Tse, Tony O'Callaghan
A Comparison of Tabular Expression-Based Testing Strategies. IEEE Trans. Software Eng. 37 (5) (2011)
David Lorge Parnas
Software Engineering - Missing in Action: A Personal Perspective. Computer 44 (10) (2011)
David Lorge Parnas
Really Rethinking 'Formal Methods'. Computer 43 (1) (2010)
David Lorge Parnas
From Requirements to Architecture. SoMeT (2010)
Wenhui Zhu, David Lorge Parnas
A documentation approach for the self-adaptive system design. SEKE (2010)
David Lorge Parnas
Precise Documentation: The Key to Better Software. The Future of Software Engineering (2010)
Lillian Chik-Parnas, Marius Dragomiroiu, David Lorge Parnas
A family of computer systems for delivering individualized advice. Knowl. Based Syst. 23 (7) (2010)
Ying Jin, David Lorge Parnas
Defining the meaning of tabular mathematical expressions. Sci. Comput. Program. 75 (11) (2010)
Zhiying Liu, David Lorge Parnas, Baltasar Trancón y Widemann
Documenting and verifying systems assembled from components. Frontiers Comput. Sci. China 4 (2) (2010)
David Lorge Parnas
Risks of undisciplined development. Commun. ACM 53 (10) (2010)
David Lorge Parnas
Document based rational software development. Knowl. Based Syst. 22 (3) (2009)
David Lorge Parnas, Bill Curtis
Point/Counterpoint. IEEE Softw. 26 (6) (2009)
Xin Feng, David Lorge Parnas, T. H. Tse
Fault Propagation in Tabular Expression-Based Specifications. COMPSAC (2008)
Sergiy A. Vilkomir, David Lorge Parnas, Veena B. Mendiratta, Eamonn Murphy
Computer systems availability evaluation using a segregated failures model. Qual. Reliab. Eng. Int. 24 (4) (2008)
David Lorge Parnas
Connecting Good Theory to Good Practice: Software Documentation: A Case Study. Software Engineering (2008)
Steven Fraser, Frederick P. Brooks Jr., Martin Fowler, Ricardo López, Aki Namioka, Linda M. Northrop, David Lorge Parnas, Dave A. Thomas
"No silver bullet" reloaded: retrospective on "essence and accidents of software engineering". OOPSLA Companion (2007)
David Lorge Parnas
Which is riskier: OS diversity or OS monopoly? Commun. ACM 50 (8) (2007)
David Lorge Parnas
Document-driven Software Design - A Novel Approach that Should Not Be Novel. ENASE (2007)
David Lorge Parnas
Software Product-Lines: What To Do When Enumaration Won't Work. VaMoS (2007)
David Lorge Parnas
Resolving Dilemmas in Software Engineering Education. CSEE&T (2007)
David Lorge Parnas
Stop the numbers game. Commun. ACM 50 (11) (2007)
Baltasar Trancón y Widemann, David Lorge Parnas
Tabular Expressions and Total Functional Programming. IFL (2007)
David Lorge Parnas
Precise software documentation: making object-orientation work better. OOPSLA Companion (2007)
David Lorge Parnas
Document-Driven Software Design: A Novel Approach That Should Not Be Novel. ICSOFT (PL/DPS/KE/MUSE) (2007)
David Lorge Parnas, Sergiy A. Vilkomir
Precise Documentation of Critical Software. HASE (2007)
Vera Pantelic, Xiao-Hui Jin, Mark Lawford, David Lorge Parnas
Inspection of Concurrent Systems: Combining Tables, Theorem Proving and Model Checking. Software Engineering Research and Practice (2006)
Sergiy A. Vilkomir, David Lorge Parnas, Veena B. Mendiratta, Eamonn Murphy
Segregated failures model for availability evaluation of fault-tolerant systems. ACSC (2006)
David Lorge Parnas
Component Interface Documentation: What do we Need and Why do we Need it? SoMeT (2006)
Colm Quinn, Sergiy A. Vilkomir, David Lorge Parnas, Srdjan Kostic
Specification of Software Component Requirements Using the Trace Function Method. ICSEA (2006)
David Lorge Parnas
Document Driven Disciplined Development of Software. Australian Software Engineering Conference (2005)
Peter J. Denning, Jim Horning, David Lorge Parnas, Lauren Weinstein
Wikipedia risks. Commun. ACM 48 (12) (2005)
Markus Clermont, David Lorge Parnas
Using information about functions in selecting test cases. ACM SIGSOFT Softw. Eng. Notes 30 (4) (2005)
Sergiy A. Vilkomir, David Lorge Parnas, Veena B. Mendiratta, Eamonn Murphy
Availability Evaluation of Hardware/Software Systems with Several Recovery Procedures. COMPSAC (1) (2005)
David Lorge Parnas
A Family of Mathematical Methods for Professional Software Documentation. IFM (2005)
Markus Clermont, David Lorge Parnas
Using information about functions in selecting test cases. A-MOST (2005)
David Lorge Parnas, Lillian Chik-Parnas
Goals for software engineering student education. ACM SIGSOFT Softw. Eng. Notes 30 (4) (2005)
Robert L. Baber, David Lorge Parnas, Sergiy A. Vilkomir, Paul Harrison, Tony O'Connor
Disciplined Methods of Software Specification: A Case Study. ITCC (2) (2005)
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
New Year's Resolutions for Software Quality. IEEE Softw. 21 (1) (2004)
David Lorge Parnas
Software Inspections We Can Trust. FIDJI (2003)
David Lorge Parnas, Mark Lawford
The Role of Inspection in Software Quality Assurance. IEEE Trans. Software Eng. 29 (8) (2003)
Premkumar T. Devanbu, Robert Balzer, Don S. Batory, Gregor Kiczales, John Launchbury, David Lorge Parnas, Peri L. Tarr
Modularity in the New Millenium: A Panel Summary. ICSE (2003)
David Lorge Parnas
The Limits of Empirical Studies of Software Engineering. ISESE (2003)
David Lorge Parnas
Structured programming: A minor part of software engineering. Inf. Process. Lett. 88 (1-2) (2003)
David Lorge Parnas, Mark Lawford
Guest Editors' Introduction: Inspection's Role in Software Quality Assurance. IEEE Softw. 20 (4) (2003)
Dennis K. Peters, David Lorge Parnas
Requirements-Based Monitors for Real-Time Systems. IEEE Trans. Software Eng. 28 (2) (2002)
David Lorge Parnas
Licensing software engineers in Canada. Commun. ACM 45 (11) (2002)
Wolfram Kahl, David Lorge Parnas, Gunther Schmidt
RelMiS 2001 - Preface. Electron. Notes Theor. Comput. Sci. 44 (3) (2001)
David Lorge Parnas
Systematic Documentation of Requirements. RE (2001)
Peter G. Neumann, David Lorge Parnas
Computers: boon or bane? Commun. ACM 44 (3) (2001)
David Lorge Parnas
The Tabular Method for Relational Documentation. Electron. Notes Theor. Comput. Sci. 44 (3) (2001)
David Lorge Parnas
University Programmes in Software Development. SEUH (2001)
H. Dieter Rombach, Manfred Broy, Michael Evangelist, Ali Mili, Leon J. Osterweil, David Lorge Parnas
Software Engineering Research Agendas Panel (SERA): What Can't We Do, But Need to Learn How to Do? ICSE (2001)
David Lorge Parnas
Software Documentation and the Verification Process. CAV (2001)
David Lorge Parnas
Requirements Documentation: Why a Formal Basis is Essential. ICRE (2000)
David Lorge Parnas
The Use of Mathematics in Software Engineering. ICFEM (2000)
David Lorge Parnas
Making Mathematical Methods More Practical for Software Developers (Invited Talk). AMAST (2000)
David Lorge Parnas
Invited Talk: A Software Engineering Program of Lasting Value. AMAST (2000)
Jia Xu, David Lorge Parnas
Priority Scheduling Versus Pre-Run-Time Scheduling. Real Time Syst. 18 (1) (2000)
David Lorge Parnas
Two Positions on Licensing. ICRE (2000)
Dennis K. Peters, David Lorge Parnas
Requirements-based monitors for real-time systems. ISSTA (2000)
David Lorge Parnas
Ten Myths About Y2K Inspections. Commun. ACM 42 (5) (1999)
David Lorge Parnas, Dennis K. Peters
An Easily Extensible Toolset for Tabular Mathematical Expressions. TACAS (1999)
David Lorge Parnas
Software Engineering Programs Are Not Computer Science Programs. IEEE Softw. 16 (6) (1999)
David Lorge Parnas
On code reuse. ACM SIGSOFT Softw. Eng. Notes 24 (3) (1999)
David Lorge Parnas
Parnas on Parnas: a life of indecision. ACM SIGSOFT Softw. Eng. Notes 24 (4) (1999)
David Lorge Parnas
Systematic Techniques for Inspecting Critical Software. TOOLS (30) (1999)
David Lorge Parnas
Tools for Component Documentation, Analysis and Testing. TOOLS (30) (1999)
David Lorge Parnas
Software Engineering Programmes are not Computer Science Programmes. Ann. Softw. Eng. 6 (1998)
David Lorge Parnas
Successful software engineering research. ACM SIGSOFT Softw. Eng. Notes 23 (3) (1998)
David Lorge Parnas
Who taught me about software engineering research? ACM SIGSOFT Softw. Eng. Notes 23 (4) (1998)
David Lorge Parnas
"Formal methods" technology transfer will fail. J. Syst. Softw. 40 (3) (1998)
Dennis K. Peters, David Lorge Parnas
Using Test Oracles Generated from Program Documentation. IEEE Trans. Software Eng. 24 (3) (1998)
David Lorge Parnas
Software Engineering: An Unconsummated Marriage (Extended Abstract). ESEC / SIGSOFT FSE (1997)
David Lorge Parnas
Software Engineering: An Unconsummated Marriage. Commun. ACM 40 (9) (1997)
David Lorge Parnas
Teaching for Change. CSEE&T (1997)
Jonathan P. Bowen, Ricky W. Butler, David L. Dill, Robert L. Glass, David Gries, Anthony Hall, Michael G. Hinchey, C. Michael Holloway, Daniel Jackson, Cliff B. Jones, Michael J. Lutz, David Lorge Parnas, John M. Rushby, Jeannette M. Wing, Pamela Zave
An Invitation to Formal Methods. Computer 29 (4) (1996)
David Lorge Parnas
Why Software Jewels Are Rare. Computer 29 (2) (1996)
Anthony Hall, David Lorge Parnas, Nico Plat, John M. Rushby, Chris T. Sennett
The Future of Formal Methods in Industry. ZUM (1995)
David Lorge Parnas
On ICSE's "most influential" papers. ACM SIGSOFT Softw. Eng. Notes 20 (3) (1995)
David Lorge Parnas
Teaching Programming as Engineering. ZUM (1995)
David Lorge Parnas
Language-Free Mathematical Methods for Software Design. ZUM (1995)
David Lorge Parnas, Jan Madey
Functional Documents for Computer Systems. Sci. Comput. Program. 25 (1) (1995)
Yabo Wang, David Lorge Parnas
Simulating the Behavior of Software Modules by Trace Rewriting. IEEE Trans. Software Eng. 20 (10) (1994)
Dennis K. Peters, David Lorge Parnas
Generating a Test Oracle from Program Documentation (Work in Progress). ISSTA (1994)
David Lorge Parnas
Inspection of Safety-Critical Software Using Program-Function Tables. IFIP Congress (3) (1994)
David Lorge Parnas
Software Aging. ICSE (1994)
David Lorge Parnas
The Professional Responsibilities of Software Engineers. IFIP Congress (2) (1994)
David Lorge Parnas
Mathematical Description and Specification of Software. IFIP Congress (1) (1994)
David Lorge Parnas, Jan Madey, Michal Iglewski
Precise Documentation of Well-Structured Programs. IEEE Trans. Software Eng. 20 (12) (1994)
Yabo Wang, David Lorge Parnas
Simulating the Behaviour of Software Modules by Trace Rewriting. ICSE (1993)
David Lorge Parnas
Some Theorems We Should Prove. HUG (1993)
Jia Xu, David Lorge Parnas
On Satisfying Timing Constraints in Hard-Real-Time Systems. IEEE Trans. Software Eng. 19 (1) (1993)

David Lorge Parnas.css-eqlu8i{font-size:small;padding-left:4px;}

Publication Activity (10 Years)

Top Topics

Top Venues

David Lorge Parnas