 | 2009 |
|---|
| 127 |       | David Lorge Parnas:
Document based rational software development.
Knowl.-Based Syst. 22(3): 132-141 (2009) |
| 2008 |
|---|
| 126 | | Xin Feng,
David Lorge Parnas,
T. H. Tse:
Fault Propagation in Tabular Expression-Based Specifications.
COMPSAC 2008: 180-183 |
| 125 |  | David Lorge Parnas:
Connecting Good Theory to Good Practice: Software Documentation: A Case Study.
Software Engineering 2008: 17-20 |
| 124 | | 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) |
| 2007 |
|---|
| 123 | | David Lorge Parnas:
Resolving Dilemmas in Software Engineering Education.
CSEE&T 2007 |
| 122 | | David Lorge Parnas,
Sergiy A. Vilkomir:
Precise Documentation of Critical Software.
HASE 2007: 237-244 |
| 121 | | David Lorge Parnas:
Document-Driven Software Design: A Novel Approach That Should Not Be Novel.
ICSOFT (PL/DPS/KE/MUSE) 2007: 7 |
| 120 | | Baltasar Trancón-y-Widemann,
David Lorge Parnas:
Tabular Expressions and Total Functional Programming.
IFL 2007: 219-236 |
| 119 | | 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 |
| 118 | | David Lorge Parnas:
Precise software documentation: making object-orientation work better.
OOPSLA Companion 2007: 725 |
| 117 | | David Lorge Parnas:
Software Product-Lines: What To Do When Enumaration Won't Work.
VaMoS 2007: 9-14 |
| 116 | | David Lorge Parnas:
Stop the numbers game.
Commun. ACM 50(11): 19-21 (2007) |
| 115 | | David Lorge Parnas:
Which is riskier: OS diversity or OS monopoly?
Commun. ACM 50(8): 112 (2007) |
| 2006 |
|---|
| 114 | | 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 |
| 113 | | Colm Quinn,
Sergiy A. Vilkomir,
David Lorge Parnas,
Srdjan Kostic:
Specification of Software Component Requirements Using the Trace Function Method.
ICSEA 2006: 50 |
| 112 | | David Lorge Parnas:
Component Interface Documentation: What do we Need and Why do we Need it?
SoMeT 2006: 3-21 |
| 111 | | 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 |
| 2005 |
|---|
| 110 | | Markus Clermont,
David Lorge Parnas:
Using information about functions in selecting test cases.
A-MOST 2005 |
| 109 | | David Lorge Parnas:
Document Driven Disciplined Development of Software.
Australian Software Engineering Conference 2005: 2-3 |
| 108 | | 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 |
| 107 | | David Lorge Parnas:
A Family of Mathematical Methods for Professional Software Documentation.
IFM 2005: 1-4 |
| 106 | | 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 |
| 105 | | Markus Clermont,
David Lorge Parnas:
Using information about functions in selecting test cases.
ACM SIGSOFT Software Engineering Notes 30(4): 1-7 (2005) |
| 104 | | David Lorge Parnas,
Lillian Chik-Parnas:
Goals for software engineering student education.
ACM SIGSOFT Software Engineering Notes 30(4): 6-8 (2005) |
| 103 | | Peter J. Denning,
Jim Horning,
David Lorge Parnas,
Lauren Weinstein:
Wikipedia risks.
Commun. ACM 48(12): 152 (2005) |
| 2004 |
|---|
| 102 | | 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 |
|---|
| 101 | | David Lorge Parnas:
Software Inspections We Can Trust.
FIDJI 2003: 153-154 |
| 100 | | 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 |
| 99 | | David Lorge Parnas:
The Limits of Empirical Studies of Software Engineering.
ISESE 2003: 2-7 |
| 98 | | David Lorge Parnas,
Mark Lawford:
Guest Editors' Introduction: Inspection's Role in Software Quality Assurance.
IEEE Software 20(4): 16-20 (2003) |
| 97 | | David Lorge Parnas,
Mark Lawford:
The Role of Inspection in Software Quality Assurance.
IEEE Trans. Software Eng. 29(8): 674-676 (2003) |
| 96 | | David Lorge Parnas:
Structured programming: A minor part of software engineering.
Inf. Process. Lett. 88(1-2): 53-58 (2003) |
| 2002 |
|---|
| 95 | | David Lorge Parnas:
Licensing software engineers in Canada.
Commun. ACM 45(11): 96-98 (2002) |
| 94 | | Dennis K. Peters,
David Lorge Parnas:
Requirements-Based Monitors for Real-Time Systems.
IEEE Trans. Software Eng. 28(2): 146-158 (2002) |
| 2001 |
|---|
| 93 | | David Lorge Parnas:
Software Documentation and the Verification Process.
CAV 2001: 1 |
| 92 | | 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-698 |
| 91 | | David Lorge Parnas:
Systematic Documentation of Requirements.
RE 2001: 248 |
| 90 | | David Lorge Parnas:
University Programmes in Software Development.
SEUH 2001: 9-10 |
| 89 | | Peter G. Neumann,
David Lorge Parnas:
Computers: boon or bane?
Commun. ACM 44(3): 168 (2001) |
| 88 | | Wolfram Kahl,
David Lorge Parnas,
Gunther Schmidt:
RelMiS 2001 - Preface.
Electr. Notes Theor. Comput. Sci. 44(3): (2001) |
| 87 | | David Lorge Parnas:
The Tabular Method for Relational Documentation.
Electr. Notes Theor. Comput. Sci. 44(3): (2001) |
| 2000 |
|---|
| 86 | | David Lorge Parnas:
Invited Talk: A Software Engineering Program of Lasting Value.
AMAST 2000: 1 |
| 85 | | David Lorge Parnas:
Making Mathematical Methods More Practical for Software Developers (Invited Talk).
AMAST 2000: 9-10 |
| 84 | | David Lorge Parnas:
The Use of Mathematics in Software Engineering.
ICFEM 2000: 1 |
| 83 | | David Lorge Parnas:
Two Positions on Licensing.
ICRE 2000: 154 |
| 82 | | David Lorge Parnas:
Requirements Documentation: Why a Formal Basis is Essential.
ICRE 2000: 81-84 |
| 81 | | Dennis K. Peters,
David Lorge Parnas:
Requirements-based monitors for real-time systems.
ISSTA 2000: 77-85 |
| 80 | | Jia Xu,
David Lorge Parnas:
Priority Scheduling Versus Pre-Run-Time Scheduling.
Real-Time Systems 18(1): 7-23 (2000) |
| 1999 |
|---|
| 79 | | David Lorge Parnas,
Dennis K. Peters:
An Easily Extensible Toolset for Tabular Mathematical Expressions.
TACAS 1999: 345-359 |
| 78 | | David Lorge Parnas:
Tools for Component Documentation, Analysis and Testing.
TOOLS (30) 1999: 2 |
| 77 | | David Lorge Parnas:
Systematic Techniques for Inspecting Critical Software.
TOOLS (30) 1999: 410 |
| 76 | | David Lorge Parnas:
Ten Myths About Y2K Inspections.
Commun. ACM 42(5): 128 (1999) |
| 75 | | David Lorge Parnas:
Software Engineering Programs Are Not Computer Science Programs.
IEEE Software 16(6): 19-30 (1999) |
| 1998 |
|---|
| 74 | | David Lorge Parnas:
Software Engineering Programmes are not Computer Science Programmes.
Ann. Software Eng. 6: 19-37 (1998) |
| 73 | | Dennis K. Peters,
David Lorge Parnas:
Using Test Oracles Generated from Program Documentation.
IEEE Trans. Software Eng. 24(3): 161-173 (1998) |
| 72 | | David Lorge Parnas:
"Formal methods" technology transfer will fail.
Journal of Systems and Software 40(3): 195-198 (1998) |
| 1997 |
|---|
| 71 | | David Lorge Parnas:
Software Engineering: An Unconsummated Marriage (Extended Abstract).
ESEC / SIGSOFT FSE 1997: 1-3 |
| 70 | | David Lorge Parnas:
Software Engineering: An Unconsummated Marriage.
Commun. ACM 40(9): 128 (1997) |
| 1996 |
|---|
| 69 | | David Lorge Parnas:
Why Software Jewels Are Rare.
IEEE Computer 29(2): 57-60 (1996) |
| 68 | | 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 |
|---|
| 67 | | Anthony Hall,
David Lorge Parnas,
Nico Plat,
John M. Rushby,
Chris T. Sennett:
The Future of Formal Methods in Industry.
ZUM 1995: 237-242 |
| 66 | | David Lorge Parnas:
Language-Free Mathematical Methods for Software Design.
ZUM 1995: 3-4 |
| 65 | | David Lorge Parnas:
Teaching Programming as Engineering.
ZUM 1995: 471-481 |
| 64 | | David Lorge Parnas,
Jan Madey:
Functional Documents for Computer Systems.
Sci. Comput. Program. 25(1): 41-61 (1995) |
| 1994 |
|---|
| 63 | | David Lorge Parnas:
Software Aging.
ICSE 1994: 279-287 |
| 62 | | David Lorge Parnas:
Mathematical Description and Specification of Software.
IFIP Congress (1) 1994: 354-359 |
| 61 | | David Lorge Parnas:
The Professional Responsibilities of Software Engineers.
IFIP Congress (2) 1994: 332-339 |
| 60 | | David Lorge Parnas:
Inspection of Safety-Critical Software Using Program-Function Tables.
IFIP Congress (3) 1994: 270-277 |
| 59 | | Dennis K. Peters,
David Lorge Parnas:
Generating a Test Oracle from Program Documentation (Work in Progress).
ISSTA 1994: 58-65 |
| 58 | | Yabo Wang,
David Lorge Parnas:
Simulating the Behavior of Software Modules by Trace Rewriting.
IEEE Trans. Software Eng. 20(10): 750-759 (1994) |
| 57 | | David Lorge Parnas,
Jan Madey,
Michal Iglewski:
Precise Documentation of Well-Structured Programs.
IEEE Trans. Software Eng. 20(12): 948-976 (1994) |
| 1993 |
|---|
| 56 | | David Lorge Parnas:
Some Theorems We Should Prove.
HUG 1993: 155-162 |
| 55 | | Yabo Wang,
David Lorge Parnas:
Simulating the Behaviour of Software Modules by Trace Rewriting.
ICSE 1993: 14-23 |
| 54 | | Pierre-Jacques Courtois,
David Lorge Parnas:
Documentation for Safety Critical Software.
ICSE 1993: 315-323 |
| 53 | | Jia Xu,
David Lorge Parnas:
On Satisfying Timing Constraints in Hard-Real-Time Systems.
IEEE Trans. Software Eng. 19(1): 70-84 (1993) |
| 52 | | Jia Xu,
David Lorge Parnas:
Correction to ``On Satisfying Timing Constraints in Hard-Real-Time Systems''.
IEEE Trans. Software Eng. 19(3): 310 (1993) |
| 51 | | David Lorge Parnas:
Predicate Logic for Software Engineering.
IEEE Trans. Software Eng. 19(9): 856-862 (1993) |
| 1992 |
|---|
| 50 | | Yabo Wang,
David Lorge Parnas:
Trace Rewriting Systems.
CTRS 1992: 343-356 |
| 49 | | 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 |
|---|
| 48 | | David Lorge Parnas:
Functional Specifications for Old (and New) Software.
GI Jahrestagung (1) 1990: 3-14 |
| 47 | | David Lorge Parnas:
Education for Computing Professionals (Abstract).
ICCI 1990: 2-3 |
| 46 | | David Lorge Parnas:
On Iterative Constructs.
ACM Trans. Program. Lang. Syst. 12(1): 139-141 (1990) |
| 45 | | David Lorge Parnas,
A. John van Schouwen,
Shu Po Kwan:
Evaluation of Safety-Critical Software.
Commun. ACM 33(6): 636-648 (1990) |
| 44 | | David Lorge Parnas:
Education for Computing Professionals.
IEEE Computer 23(1): 17-22 (1990) |
| 43 | | Jia Xu,
David Lorge Parnas:
Scheduling Processes with Release Times, Deadlines, Precedence, and Exclusion Relations.
IEEE Trans. Software Eng. 16(3): 360-369 (1990) |
| 1989 |
|---|
| 42 | | David Lorge Parnas:
Documentation of Communications Services and Protocols.
FORTE 1989: 277-280 |
| 41 | | David Lorge Parnas:
On "Artificial Intelligence and Expert Systems - Myths, Legends, and Facts".
IFIP Congress 1989: 1145-1146 |
| 1988 |
|---|
| 40 | | Stuart R. Faulk,
David Lorge Parnas:
On Synchronization in Hard-Real-Time Systems.
Commun. ACM 31(3): 274-287 (1988) |
| 1987 |
|---|
| 39 | | David Lorge Parnas:
Warum ich an SDI nicht mitarbeite: Eine Auffassung beruflicher Verantwortung.
Informatik Spektrum 10(1): 3-10 (1987) |
| 38 | | David Lorge Parnas,
David M. Weiss:
Active design reviews: Principles and practices.
Journal of Systems and Software 7(4): 259-265 (1987) |
| 1986 |
|---|
| 37 | | David Lorge Parnas:
Why We Would Never Trust the SDI Software.
COMPCON 1986: 91-93 |
| 36 | | 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) |
| 35 | | 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) |
| 1985 |
|---|
| 34 | | David Lorge Parnas,
David M. Weiss:
Active Design Reviews: Principles and Practices.
ICSE 1985: 132-136 |
| 33 | | David Lorge Parnas,
Paul C. Clements:
A Rational Design Process: How and Why to Fake It.
TAPSOFT, Vol.2 1985: 80-100 |
| 32 | | David Lorge Parnas:
Software Aspects of Strategic Defense Systems.
Commun. ACM 28(12): 1326-1335 (1985) |
| 31 | | David Lorge Parnas,
Paul C. Clements,
David M. Weiss:
The Modular Structure of Complex Systems.
IEEE Trans. Software Eng. 11(3): 259-266 (1985) |
| 1984 |
|---|
| 30 | | David Lorge Parnas,
Paul C. Clements,
David M. Weiss:
The Modular Structure of Complex Systems.
ICSE 1984: 408-419 |
| 1983 |
|---|
| 29 | | David Lorge Parnas:
A Technique for Software Module Specification with Examples (Reprint).
Commun. ACM 26(1): 75-78 (1983) |
| 28 | | David Lorge Parnas:
A Generalized Control Structure and Its Formal Definition.
Commun. ACM 26(8): 572-581 (1983) |
| 1981 |
|---|
| 27 | | K. H. Britton,
R. A. Parker,
David Lorge Parnas:
A Procedure for Designing Abstract Interfaces for Device Interface Modules.
ICSE 1981: 195-206 |
| 1979 |
|---|
| 26 | | David Lorge Parnas:
Designing Software for Ease of Extension and Contraction.
IEEE Trans. Software Eng. 5(2): 128-138 (1979) |
| 1978 |
|---|
| 25 | | Wolfram Bartussek,
David Lorge Parnas:
Using assertions about traces to write abstract specifications for software modules.
ECI 1978: 211-236 |
| 24 | | David Lorge Parnas:
Designing Software for Ease of Extension and Contraction.
ICSE 1978: 264-277 |
| 1977 |
|---|
| 23 | | David Lorge Parnas:
The Use of Precise Specification in the Development of Software.
IFIP Congress 1977: 861-867 |
| 1976 |
|---|
| 22 | | 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 |
| 21 | | David Lorge Parnas,
Georg Handzel,
Harald Würges:
Design and Specification of the Minimal Subset of an Operating System Family (Abstract).
ICSE 1976: 123 |
| 20 | | David Lorge Parnas,
Harald Würges:
Response to Undesired Events in Software Systems.
ICSE 1976: 437-446 |
| 19 | | David Lorge Parnas:
On the Design and Development of Program Families.
IEEE Trans. Software Eng. 2(1): 1-9 (1976) |
| 18 | | 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) |
| 1975 |
|---|
| 17 | | David Lorge Parnas:
On a Solution to the Cigarette Smoker's Problem (Without Conditional Statements).
Commun. ACM 18(3): 181-183 (1975) |
| 16 | | Alan F. Babich,
John Grason,
David Lorge Parnas:
Significant Event Simulation.
Commun. ACM 18(6): 323-329 (1975) |
| 15 | | 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 |
|---|
| 14 | | David Lorge Parnas:
On a 'Buzzword': Hierarchical Structure.
IFIP Congress 1974: 336-339 |
| 13 | | David Lorge Parnas:
Software Engineering or Methods for the Multi - Person Construction of Multi - Version Programs.
Programming Methodology 1974: 225-235 |
| 12 | | 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) |
| 1972 |
|---|
| 11 | | 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) |
| 10 | | David Lorge Parnas:
On the Criteria To Be Used in Decomposing Systems into Modules.
Commun. ACM 15(12): 1053-1058 (1972) |
| 9 | | David Lorge Parnas:
A Technique for Software Module Specification with Examples.
Commun. ACM 15(5): 330-336 (1972) |
| 8 | | David Lorge Parnas,
A. Nico Habermann:
Comment on Deadlock Prevention Method.
Commun. ACM 15(9): 840-841 (1972) |
| 1971 |
|---|
| 7 | | David Lorge Parnas:
Information Distribution Aspects of Design Methodology.
IFIP Congress (1) 1971: 339-344 |
| 6 | | Pierre-Jacques Courtois,
F. Heymans,
David Lorge Parnas:
Concurrent Control with "Readers" and "Writers".
Commun. ACM 14(10): 667-668 (1971) |
| 1969 |
|---|
| 5 | | David Lorge Parnas:
On simulating networks of parallel processes in which simultaneous events may occur.
Commun. ACM 12(9): 519-531 (1969) |
| 1968 |
|---|
| 4 | | David Lorge Parnas:
Letters to the editor: on improving the quality of our technical meetings.
Commun. ACM 11(8): 537-538 (1968) |
| 1966 |
|---|
| 3 | | David Lorge Parnas:
A language for describing the functions of synchronous systems.
Commun. ACM 9(2): 72-76 (1966) |
| 2 | | David Lorge Parnas:
On the preliminary report of C3S.
Commun. ACM 9(4): 242-243 (1966) |
| 1 | | David Lorge Parnas:
On facilitating parallel and multiprocessing in ALGOL.
Commun. ACM 9(4): 257 (1966) |
