dblp.uni-trier.dewww.uni-trier.de

David Lorge Parnas Vis

List of publications from the DBLP Bibliography Server - FAQ
Coauthor Index - Ask others: ACM DL/Guide - CiteSeerX - CSB - MetaPress - Google - Bing - Yahoo
Home Page

*2009
127EEDavid Lorge Parnas: Document based rational software development. Knowl.-Based Syst. 22(3): 132-141 (2009)
2008
126EEXin 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
124EESergiy 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
123EEDavid Lorge Parnas: Resolving Dilemmas in Software Engineering Education. CSEE&T 2007
122EEDavid 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
120EEBaltasar Trancón-y-Widemann, David Lorge Parnas: Tabular Expressions and Total Functional Programming. IFL 2007: 219-236
119EESteven 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
118EEDavid Lorge Parnas: Precise software documentation: making object-orientation work better. OOPSLA Companion 2007: 725
117EEDavid Lorge Parnas: Software Product-Lines: What To Do When Enumaration Won't Work. VaMoS 2007: 9-14
116EEDavid Lorge Parnas: Stop the numbers game. Commun. ACM 50(11): 19-21 (2007)
115EEDavid Lorge Parnas: Which is riskier: OS diversity or OS monopoly? Commun. ACM 50(8): 112 (2007)
2006
114EESergiy A. Vilkomir, David Lorge Parnas, Veena B. Mendiratta, Eamonn Murphy: Segregated failures model for availability evaluation of fault-tolerant systems. ACSC 2006: 55-61
113EEColm 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
110EEMarkus Clermont, David Lorge Parnas: Using information about functions in selecting test cases. A-MOST 2005
109EEDavid Lorge Parnas: Document Driven Disciplined Development of Software. Australian Software Engineering Conference 2005: 2-3
108EESergiy 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
107EEDavid Lorge Parnas: A Family of Mathematical Methods for Professional Software Documentation. IFM 2005: 1-4
106EERobert 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
105EEMarkus Clermont, David Lorge Parnas: Using information about functions in selecting test cases. ACM SIGSOFT Software Engineering Notes 30(4): 1-7 (2005)
104EEDavid Lorge Parnas, Lillian Chik-Parnas: Goals for software engineering student education. ACM SIGSOFT Software Engineering Notes 30(4): 6-8 (2005)
103EEPeter J. Denning, Jim Horning, David Lorge Parnas, Lauren Weinstein: Wikipedia risks. Commun. ACM 48(12): 152 (2005)
2004
102EEVictor 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
101EEDavid Lorge Parnas: Software Inspections We Can Trust. FIDJI 2003: 153-154
100EEPremkumar 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
99EEDavid Lorge Parnas: The Limits of Empirical Studies of Software Engineering. ISESE 2003: 2-7
98EEDavid Lorge Parnas, Mark Lawford: Guest Editors' Introduction: Inspection's Role in Software Quality Assurance. IEEE Software 20(4): 16-20 (2003)
97EEDavid Lorge Parnas, Mark Lawford: The Role of Inspection in Software Quality Assurance. IEEE Trans. Software Eng. 29(8): 674-676 (2003)
96EEDavid Lorge Parnas: Structured programming: A minor part of software engineering. Inf. Process. Lett. 88(1-2): 53-58 (2003)
2002
95EEDavid Lorge Parnas: Licensing software engineers in Canada. Commun. ACM 45(11): 96-98 (2002)
94EEDennis K. Peters, David Lorge Parnas: Requirements-Based Monitors for Real-Time Systems. IEEE Trans. Software Eng. 28(2): 146-158 (2002)
2001
93EEDavid 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
91EEDavid Lorge Parnas: Systematic Documentation of Requirements. RE 2001: 248
90 David Lorge Parnas: University Programmes in Software Development. SEUH 2001: 9-10
89EEPeter G. Neumann, David Lorge Parnas: Computers: boon or bane? Commun. ACM 44(3): 168 (2001)
88EEWolfram Kahl, David Lorge Parnas, Gunther Schmidt: RelMiS 2001 - Preface. Electr. Notes Theor. Comput. Sci. 44(3): (2001)
87EEDavid Lorge Parnas: The Tabular Method for Relational Documentation. Electr. Notes Theor. Comput. Sci. 44(3): (2001)
2000
86EEDavid Lorge Parnas: Invited Talk: A Software Engineering Program of Lasting Value. AMAST 2000: 1
85EEDavid Lorge Parnas: Making Mathematical Methods More Practical for Software Developers (Invited Talk). AMAST 2000: 9-10
84EEDavid Lorge Parnas: The Use of Mathematics in Software Engineering. ICFEM 2000: 1
83EEDavid Lorge Parnas: Two Positions on Licensing. ICRE 2000: 154
82EEDavid Lorge Parnas: Requirements Documentation: Why a Formal Basis is Essential. ICRE 2000: 81-84
81EEDennis 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
79EEDavid Lorge Parnas, Dennis K. Peters: An Easily Extensible Toolset for Tabular Mathematical Expressions. TACAS 1999: 345-359
78EEDavid Lorge Parnas: Tools for Component Documentation, Analysis and Testing. TOOLS (30) 1999: 2
77EEDavid Lorge Parnas: Systematic Techniques for Inspecting Critical Software. TOOLS (30) 1999: 410
76EEDavid Lorge Parnas: Ten Myths About Y2K Inspections. Commun. ACM 42(5): 128 (1999)
75EEDavid 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)
73EEDennis K. Peters, David Lorge Parnas: Using Test Oracles Generated from Program Documentation. IEEE Trans. Software Eng. 24(3): 161-173 (1998)
72EEDavid Lorge Parnas: "Formal methods" technology transfer will fail. Journal of Systems and Software 40(3): 195-198 (1998)
1997
71EEDavid 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
63EEDavid 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
59EEDennis K. Peters, David Lorge Parnas: Generating a Test Oracle from Program Documentation (Work in Progress). ISSTA 1994: 58-65
58EEYabo Wang, David Lorge Parnas: Simulating the Behavior of Software Modules by Trace Rewriting. IEEE Trans. Software Eng. 20(10): 750-759 (1994)
57EEDavid Lorge Parnas, Jan Madey, Michal Iglewski: Precise Documentation of Well-Structured Programs. IEEE Trans. Software Eng. 20(12): 948-976 (1994)
1993
56EEDavid Lorge Parnas: Some Theorems We Should Prove. HUG 1993: 155-162
55EEYabo Wang, David Lorge Parnas: Simulating the Behaviour of Software Modules by Trace Rewriting. ICSE 1993: 14-23
54EEPierre-Jacques Courtois, David Lorge Parnas: Documentation for Safety Critical Software. ICSE 1993: 315-323
53EEJia Xu, David Lorge Parnas: On Satisfying Timing Constraints in Hard-Real-Time Systems. IEEE Trans. Software Eng. 19(1): 70-84 (1993)
52EEJia Xu, David Lorge Parnas: Correction to ``On Satisfying Timing Constraints in Hard-Real-Time Systems''. IEEE Trans. Software Eng. 19(3): 310 (1993)
51EEDavid 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
46EEDavid 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)
43EEJia 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)
38EEDavid 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
33EEDavid 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
22EEDavid 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
13EEDavid 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
5EEDavid Lorge Parnas: On simulating networks of parallel processes in which simultaneous events may occur. Commun. ACM 12(9): 519-531 (1969)
1968
4EEDavid Lorge Parnas: Letters to the editor: on improving the quality of our technical meetings. Commun. ACM 11(8): 537-538 (1968)
1966
3EEDavid Lorge Parnas: A language for describing the functions of synchronous systems. Commun. ACM 9(2): 72-76 (1966)
2EEDavid Lorge Parnas: On the preliminary report of C3S. Commun. ACM 9(4): 242-243 (1966)
1EEDavid Lorge Parnas: On facilitating parallel and multiprocessing in ALGOL. Commun. ACM 9(4): 257 (1966)

Coauthor Index

1Robert L. Baber [106]
2Alan F. Babich [16]
3Robert Balzer [100]
4Wolfram Bartussek [25]
5Victor R. Basili [102]
6Don S. Batory [100]
7Barry W. Boehm [102]
8Jonathan P. Bowen [68]
9K. H. Britton [27]
10Frederick P. Brooks Jr. [119]
11Manfred Broy [92]
12Ricky W. Butler [68]
13Lillian Chik-Parnas [104]
14Paul C. Clements [30] [31] [33] [35] [36]
15Markus Clermont [105] [110]
16Lee W. Cooprider [12]
17Pierre-Jacques Courtois [6] [11] [12] [54]
18Al Davis (Alan L. Davis) [102]
19Peter J. Denning [103]
20Premkumar T. Devanbu [100]
21David L. Dill [68]
22Marcin Engel [49]
23Michael Evangelist [92]
24Stuart R. Faulk [40]
25Xin Feng [126]
26Martin Fowler [119]
27Steven Fraser [119]
28Robert L. Glass [68]
29John Grason [16]
30David Gries [68]
31A. Nico Habermann [8]
32Anthony Hall [67] [68]
33Georg Handzel [18] [21]
34Paul Harrison [106]
35F. Heymans [6] [11] [12]
36Michael G. Hinchey (Mike Hinchey) [68]
37C. Michael Holloway [68]
38James J. Horning (Jim Horning) [103]
39Watts S. Humphrey [102]
40Michal Iglewski [57]
41Daniel Jackson [68]
42Xiao-Hui Jin [111]
43Cliff B. Jones [68]
44Wolfram Kahl [88]
45Gregor Kiczales [100]
46Srdjan Kostic [113]
47Marcin Kubica [49]
48Shu Po Kwan [45]
49John Launchbury [100]
50Mark Lawford [97] [98] [111]
51Nancy G. Leveson [102]
52Ricardo Lopez [119]
53Michael J. Lutz [68]
54Jan Madey [49] [57] [64]
55Nancy R. Mead [102]
56Veena B. Mendiratta [108] [114] [124]
57Ali Mili [92]
58Eamonn Murphy [108] [114] [124]
59John D. Musa [102]
60Aki Namioka [119]
61Peter G. Neumann [89]
62Linda M. Northrop [119]
63Tony O'Connor [106]
64Leon J. Osterweil [92]
65Vera Pantelic [111]
66R. A. Parker [27]
67Dennis K. Peters [59] [73] [79] [81] [94]
68Shari Lawrence Pfleeger [102]
69Nico Plat [67]
70Colm Quinn [113]
71Anders P. Ravn [49]
72H. Dieter Rombach [92]
73John M. Rushby [67] [68]
74Gunther Schmidt [88]
75A. John van Schouwen [45] [49]
76Chris T. Sennett [67]
77John E. Shore [22]
78Daniel P. Siewiorek [15]
79Peri L. Tarr [100]
80Dave A. Thomas [119]
81Baltasar Trancón-y-Widemann [120]
82T. H. Tse [126]
83Sergiy A. Vilkomir [106] [108] [113] [114] [122] [124]
84Yabo Wang [50] [55] [58]
85Lauren Weinstein [103]
86David M. Weiss [22] [30] [31] [34] [38]
87Elaine J. Weyuker [102]
88Jeannette M. Wing [68]
89Harald Würges [18] [20] [21]
90Jia Xu [43] [52] [53] [80]
91Pamela Zave [68]

Colors in the list of coauthors

Copyright © Tue Nov 3 08:52:44 2009 by Michael Ley (ley@uni-trier.de)