Please note: This is a beta version of the new dblp website.
You can find the classic dblp view of this page here.
You can find the classic dblp view of this page here.
David Lorge Parnas
2010 – today
- 2012
[j71]David Lorge Parnas: The use of mathematics in software quality assurance. Frontiers of Computer Science in China 6(1): 3-16 (2012)- 2011
- [j70]
- [j69]David Lorge Parnas: Software Engineering - Missing in Action: A Personal Perspective. IEEE Computer 44(10): 54-58 (2011)
- [j68]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): 616-634 (2011)
- [c74]David Lorge Parnas: Software Engineering: Multi-person Development of Multi-version Programs. Dependable and Historic Computing 2011: 413-427
- [c73]David Lorge Parnas: The Use of Mathematics in Software Development - (Extended Abstract). ICTAC 2011: 4-5
- 2010
- [j67]
- [j66]
- [j65]Zhiying Liu, David Lorge Parnas, Baltasar Trancón-y-Widemann: Documenting and verifying systems assembled from components. Frontiers of Computer Science in China 4(2): 151-161 (2010)
- [j64]Lillian Chik-Parnas, Marius Dragomiroiu, David Lorge Parnas: A family of computer systems for delivering individualized advice. Knowl.-Based Syst. 23(7): 645-666 (2010)
- [j63]Ying Jin, David Lorge Parnas: Defining the meaning of tabular mathematical expressions. Sci. Comput. Program. 75(11): 980-1000 (2010)
- [c72]David Lorge Parnas: Precise Documentation: The Key to Better Software. The Future of Software Engineering 2010: 125-148
- [c71]Wenhui Zhu, David Lorge Parnas: A documentation approach for the self-adaptive system design. SEKE 2010: 791-796
- [c70]
2000 – 2009
- 2009
- [j62]David Lorge Parnas: Document based rational software development. Knowl.-Based Syst. 22(3): 132-141 (2009)
- [j61]
- 2008
- [j60]Sergiy A. Vilkomir, David Lorge Parnas, Veena B. Mendiratta, Eamonn Murphy: Computer systems availability evaluation using a segregated failures model. Quality and Reliability Eng. Int. 24(4): 447-465 (2008)
- [c69]Xin Feng, David Lorge Parnas, T. H. Tse: Fault Propagation in Tabular Expression-Based Specifications. COMPSAC 2008: 180-183
- [c68]David Lorge Parnas: Connecting Good Theory to Good Practice: Software Documentation: A Case Study. Software Engineering 2008: 17-20
- 2007
- [j59]
- [j58]
- [c67]
- [c66]David Lorge Parnas: Document-driven Software Design - A Novel Approach that Should Not Be Novel. ENASE 2007: 7
- [c65]David Lorge Parnas, Sergiy A. Vilkomir: Precise Documentation of Critical Software. HASE 2007: 237-244
- [c64]David Lorge Parnas: Document-Driven Software Design: A Novel Approach That Should Not Be Novel. ICSOFT (PL/DPS/KE/MUSE) 2007: 7
- [c63]Baltasar Trancón-y-Widemann, David Lorge Parnas: Tabular Expressions and Total Functional Programming. IFL 2007: 219-236
- [c62]David Lorge Parnas: Precise software documentation: making object-orientation work better. OOPSLA Companion 2007: 725
- [c61]Steven Fraser, Frederick P. Brooks Jr., Martin Fowler, Ricardo Lopez, 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: 1026-1030
- [c60]David Lorge Parnas: Software Product-Lines: What To Do When Enumaration Won't Work. VaMoS 2007: 9-14
- 2006
- [c59]Sergiy A. Vilkomir, David Lorge Parnas, Veena B. Mendiratta, Eamonn Murphy: Segregated failures model for availability evaluation of fault-tolerant systems. ACSC 2006: 55-61
- [c58]Colm Quinn, Sergiy A. Vilkomir, David Lorge Parnas, Srdjan Kostic: Specification of Software Component Requirements Using the Trace Function Method. ICSEA 2006: 50
- [c57]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: 629-635
- [c56]David Lorge Parnas: Component Interface Documentation: What do we Need and Why do we Need it? SoMeT 2006: 3-21
- 2005
- [j57]Peter J. Denning, Jim Horning, David Lorge Parnas, Lauren Weinstein: Wikipedia risks. Commun. ACM 48(12): 152 (2005)
- [j56]Markus Clermont, David Lorge Parnas: Using information about functions in selecting test cases. ACM SIGSOFT Software Engineering Notes 30(4): 1-7 (2005)
- [j55]David Lorge Parnas, Lillian Chik-Parnas: Goals for software engineering student education. ACM SIGSOFT Software Engineering Notes 30(4): 6-8 (2005)
- [c55]Markus Clermont, David Lorge Parnas: Using information about functions in selecting test cases. A-MOST 2005
- [c54]David Lorge Parnas: Document Driven Disciplined Development of Software. Australian Software Engineering Conference 2005: 2-3
- [c53]Sergiy A. Vilkomir, David Lorge Parnas, Veena B. Mendiratta, Eamonn Murphy: Availability Evaluation of Hardware/Software Systems with Several Recovery Procedures. COMPSAC (1) 2005: 473-478
- [c52]David Lorge Parnas: A Family of Mathematical Methods for Professional Software Documentation. IFM 2005: 1-4
- [c51]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: 428-437
- 2004
- [j54]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 Software 21(1): 12-13 (2004)
- 2003
- [j53]David Lorge Parnas: Structured programming: A minor part of software engineering. Inf. Process. Lett. 88(1-2): 53-58 (2003)
- [j52]David Lorge Parnas, Mark Lawford: Guest Editors' Introduction: Inspection's Role in Software Quality Assurance. IEEE Software 20(4): 16-20 (2003)
- [j51]David Lorge Parnas, Mark Lawford: The Role of Inspection in Software Quality Assurance. IEEE Trans. Software Eng. 29(8): 674-676 (2003)
- [c50]
- [c49]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: 723-725
- [c48]
- 2002
- [j50]
- [j49]Dennis K. Peters, David Lorge Parnas: Requirements-Based Monitors for Real-Time Systems. IEEE Trans. Software Eng. 28(2): 146-158 (2002)
- 2001
- [j48]
- [j47]David Lorge Parnas: The Tabular Method for Relational Documentation. Electr. Notes Theor. Comput. Sci. 44(3): 1-26 (2001)
- [j46]Wolfram Kahl, David Lorge Parnas, Gunther Schmidt: RelMiS 2001 - Preface. Electr. Notes Theor. Comput. Sci. 44(3): 221-223 (2001)
- [c47]
- [c46]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: 698
- [c45]
- [c44]
- 2000
- [j45]Jia Xu, David Lorge Parnas: Priority Scheduling Versus Pre-Run-Time Scheduling. Real-Time Systems 18(1): 7-23 (2000)
- [c43]
- [c42]David Lorge Parnas: Making Mathematical Methods More Practical for Software Developers (Invited Talk). AMAST 2000: 9-10
- [c41]
- [c40]
- [c39]
- [c38]Dennis K. Peters, David Lorge Parnas: Requirements-based monitors for real-time systems. ISSTA 2000: 77-85
1990 – 1999
- 1999
- [j44]
- [j43]David Lorge Parnas: Software Engineering Programs Are Not Computer Science Programs. IEEE Software 16(6): 19-30 (1999)
- [c37]David Lorge Parnas, Dennis K. Peters: An Easily Extensible Toolset for Tabular Mathematical Expressions. TACAS 1999: 345-359
- [c36]
- [c35]
- 1998
- [j42]David Lorge Parnas: Software Engineering Programmes are not Computer Science Programmes. Ann. Software Eng. 6: 19-37 (1998)
- [j41]David Lorge Parnas: "Formal methods" technology transfer will fail. Journal of Systems and Software 40(3): 195-198 (1998)
- [j40]Dennis K. Peters, David Lorge Parnas: Using Test Oracles Generated from Program Documentation. IEEE Trans. Software Eng. 24(3): 161-173 (1998)
- 1997
- [j39]
- [c34]David Lorge Parnas: Software Engineering: An Unconsummated Marriage (Extended Abstract). ESEC / SIGSOFT FSE 1997: 1-3
- 1996
- [j38]
- [j37]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. IEEE Computer 29(4): 16-30 (1996)
- 1995
- [j36]David Lorge Parnas, Jan Madey: Functional Documents for Computer Systems. Sci. Comput. Program. 25(1): 41-61 (1995)
- [c33]
- [c32]Anthony Hall, David Lorge Parnas, Nico Plat, John M. Rushby, Chris T. Sennett: The Future of Formal Methods in Industry. ZUM 1995: 237-242
- [c31]
- 1994
- [j35]Yabo Wang, David Lorge Parnas: Simulating the Behavior of Software Modules by Trace Rewriting. IEEE Trans. Software Eng. 20(10): 750-759 (1994)
- [j34]David Lorge Parnas, Jan Madey, Michal Iglewski: Precise Documentation of Well-Structured Programs. IEEE Trans. Software Eng. 20(12): 948-976 (1994)
- [c30]
- [c29]David Lorge Parnas: Inspection of Safety-Critical Software Using Program-Function Tables. IFIP Congress (3) 1994: 270-277
- [c28]David Lorge Parnas: The Professional Responsibilities of Software Engineers. IFIP Congress (2) 1994: 332-339
- [c27]David Lorge Parnas: Mathematical Description and Specification of Software. IFIP Congress (1) 1994: 354-359
- [c26]Dennis K. Peters, David Lorge Parnas: Generating a Test Oracle from Program Documentation (Work in Progress). ISSTA 1994: 58-65
- 1993
- [j33]Jia Xu, David Lorge Parnas: On Satisfying Timing Constraints in Hard-Real-Time Systems. IEEE Trans. Software Eng. 19(1): 70-84 (1993)
- [j32]Jia Xu, David Lorge Parnas: Correction to ``On Satisfying Timing Constraints in Hard-Real-Time Systems''. IEEE Trans. Software Eng. 19(3): 310 (1993)
- [j31]David Lorge Parnas: Predicate Logic for Software Engineering. IEEE Trans. Software Eng. 19(9): 856-862 (1993)
- [c25]
- [c24]Pierre-Jacques Courtois, David Lorge Parnas: Documentation for Safety Critical Software. ICSE 1993: 315-323
- [c23]
- 1992
- [c22]
- [c21]Marcin Engel, Marcin Kubica, Jan Madey, David Lorge Parnas, Anders P. Ravn, A. John van Schouwen: A Formal Approach to Computer Systems Requirements Documentation. Hybrid Systems 1992: 452-474
- 1990
- [j30]David Lorge Parnas, A. John van Schouwen, Shu Po Kwan: Evaluation of Safety-Critical Software. Commun. ACM 33(6): 636-648 (1990)
- [j29]
- [j28]
- [j27]Jia Xu, David Lorge Parnas: Scheduling Processes with Release Times, Deadlines, Precedence, and Exclusion Relations. IEEE Trans. Software Eng. 16(3): 360-369 (1990)
- [c20]David Lorge Parnas: Functional Specifications for Old (and New) Software. GI Jahrestagung (1) 1990: 3-14
- [c19]
1980 – 1989
- 1989
- [c18]
- [c17]David Lorge Parnas: On "Artificial Intelligence and Expert Systems - Myths, Legends, and Facts". IFIP Congress 1989: 1145-1146
- 1988
- [j26]Stuart R. Faulk, David Lorge Parnas: On Synchronization in Hard-Real-Time Systems. Commun. ACM 31(3): 274-287 (1988)
- 1987
- [j25]David Lorge Parnas: Warum ich an SDI nicht mitarbeite: Eine Auffassung beruflicher Verantwortung. Informatik Spektrum 10(1): 3-10 (1987)
- [j24]David Lorge Parnas, David M. Weiss: Active design reviews: Principles and practices. Journal of Systems and Software 7(4): 259-265 (1987)
- 1986
- [j23]David Lorge Parnas, Paul C. Clements: A Rational Design Process: How and Why to Fake it. IEEE Trans. Software Eng. 12(2): 251-257 (1986)
- [j22]David Lorge Parnas, Paul C. Clements: Correction to "A Rational Design Process: How and Why to Fake It". IEEE Trans. Software Eng. 12(8): 874 (1986)
- [c16]
- 1985
- [j21]David Lorge Parnas: Software Aspects of Strategic Defense Systems. Commun. ACM 28(12): 1326-1335 (1985)
- [j20]David Lorge Parnas, Paul C. Clements, David M. Weiss: The Modular Structure of Complex Systems. IEEE Trans. Software Eng. 11(3): 259-266 (1985)
- [c15]David Lorge Parnas, David M. Weiss: Active Design Reviews: Principles and Practices. ICSE 1985: 132-136
- [c14]David Lorge Parnas, Paul C. Clements: A Rational Design Process: How and Why to Fake It. TAPSOFT, Vol.2 1985: 80-100
- 1984
- [c13]David Lorge Parnas, Paul C. Clements, David M. Weiss: The Modular Structure of Complex Systems. ICSE 1984: 408-419
- 1983
- [j19]David Lorge Parnas: A Technique for Software Module Specification with Examples (Reprint). Commun. ACM 26(1): 75-78 (1983)
- [j18]David Lorge Parnas: A Generalized Control Structure and Its Formal Definition. Commun. ACM 26(8): 572-581 (1983)
- 1981
- [c12]K. H. Britton, R. A. Parker, David Lorge Parnas: A Procedure for Designing Abstract Interfaces for Device Interface Modules. ICSE 1981: 195-206
1970 – 1979
- 1979
- [j17]David Lorge Parnas: Designing Software for Ease of Extension and Contraction. IEEE Trans. Software Eng. 5(2): 128-138 (1979)
- 1978
- [c11]Wolfram Bartussek, David Lorge Parnas: Using assertions about traces to write abstract specifications for software modules. ECI 1978: 211-236
- [c10]
- 1977
- [c9]David Lorge Parnas: The Use of Precise Specification in the Development of Software. IFIP Congress 1977: 861-867
- 1976
- [j16]David Lorge Parnas: On the Design and Development of Program Families. IEEE Trans. Software Eng. 2(1): 1-9 (1976)
- [j15]David Lorge Parnas, Georg Handzel, Harald Würges: Design and Specification of the Minimal Subset of an Operating System Family. IEEE Trans. Software Eng. 2(4): 301-307 (1976)
- [c8]David Lorge Parnas, Georg Handzel, Harald Würges: Design and Specification of the Minimal Subset of an Operating System Family (Abstract). ICSE 1976: 123
- [c7]David Lorge Parnas, Harald Würges: Response to Undesired Events in Software Systems. ICSE 1976: 437-446
- [c6]David Lorge Parnas, John E. Shore, David M. Weiss: Abstract Types Defined as Classes of Variables. Conference on Data: Abstraction, Definition and Structure 1976: 149-153
- 1975
- [j14]David Lorge Parnas: On a Solution to the Cigarette Smoker's Problem (Without Conditional Statements). Commun. ACM 18(3): 181-183 (1975)
- [j13]Alan F. Babich, John Grason, David Lorge Parnas: Significant Event Simulation. Commun. ACM 18(6): 323-329 (1975)
- [j12]David Lorge Parnas, Daniel P. Siewiorek: Use of the Concept of Transparency in the Design of Hierarchically Structured Systems. Commun. ACM 18(7): 401-408 (1975)
- 1974
- [j11]Lee W. Cooprider, F. Heymans, Pierre-Jacques Courtois, David Lorge Parnas: Information Streams Sharing a Finite Buffer: Other Solutions. Inf. Process. Lett. 3(1): 16-21 (1974)
- [c5]David Lorge Parnas: Software Engineering or Methods for the Multi - Person Construction of Multi - Version Programs. Programming Methodology 1974: 225-235
- [c4]
- 1972
- [j10]Pierre-Jacques Courtois, F. Heymans, David Lorge Parnas: Comments on "A Comparison of Two Synchronizing Concepts by Per Brinch Hansen". Acta Inf. 1: 375-376 (1972)
- [j9]David Lorge Parnas: A Technique for Software Module Specification with Examples. Commun. ACM 15(5): 330-336 (1972)
- [j8]David Lorge Parnas, A. Nico Habermann: Comment on Deadlock Prevention Method. Commun. ACM 15(9): 840-841 (1972)
- [j7]David Lorge Parnas: On the Criteria To Be Used in Decomposing Systems into Modules. Commun. ACM 15(12): 1053-1058 (1972)
- [c3]David Lorge Parnas: Some conclusions from an experiment in software engineering techniques. AFIPS Fall Joint Computing Conference (1) 1972: 325-329
- 1971
- [j6]Pierre-Jacques Courtois, F. Heymans, David Lorge Parnas: Concurrent Control with "Readers" and "Writers". Commun. ACM 14(10): 667-668 (1971)
- [c2]David Lorge Parnas: Information Distribution Aspects of Design Methodology. IFIP Congress (1) 1971: 339-344
1960 – 1969
- 1969
- [j5]David Lorge Parnas: On simulating networks of parallel processes in which simultaneous events may occur. Commun. ACM 12(9): 519-531 (1969)
- 1968
- [j4]David Lorge Parnas: Letters to the editor: on improving the quality of our technical meetings. Commun. ACM 11(8): 537-538 (1968)
- 1967
- [c1]David Lorge Parnas, John A. Darringer: SODAS and a methodology for system design. AFIPS Fall Joint Computing Conference 1967: 449-474
- 1966
- [j3]David Lorge Parnas: A language for describing the functions of synchronous systems. Commun. ACM 9(2): 72-76 (1966)
- [j2]
- [j1]David Lorge Parnas: On facilitating parallel and multiprocessing in ALGOL. Commun. ACM 9(4): 257 (1966)
Coauthor Index
data released under the ODC-BY 1.0 license. See also our legal information page
last updated on 2013-02-08 20:41 CET by the dblp team