The SCEAS System
Navigation Menu

Search the dblp DataBase

Title:
Author:

David Lorge Parnas: [Publications] [Author Rank by year] [Co-authors] [Prefers] [Cites] [Cited by]

Publications of Author

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

  116. Fault Propagation in Tabular Expression-Based Specifications. [Citation Graph (, )][DBLP]


  117. Precise Documentation of Critical Software. [Citation Graph (, )][DBLP]


  118. Document-Driven Software Design: A Novel Approach That Should Not Be Novel. [Citation Graph (, )][DBLP]


  119. Tabular Expressions and Total Functional Programming. [Citation Graph (, )][DBLP]


  120. Connecting Good Theory to Good Practice: Software Documentation: A Case Study. [Citation Graph (, )][DBLP]


  121. Using information about functions in selecting test cases. [Citation Graph (, )][DBLP]


  122. Software Product-Lines: What To Do When Enumaration Won't Work. [Citation Graph (, )][DBLP]


  123. Component Interface Documentation: What do we Need and Why do we Need it? [Citation Graph (, )][DBLP]


  124. Really Rethinking 'Formal Methods'. [Citation Graph (, )][DBLP]


Search in 1.053secs, Finished in 1.059secs
NOTICE1
System may not be available sometimes or not working properly, since it is still in development with continuous upgrades
NOTICE2
The rankings that are presented on this page should NOT be considered as formal since the citation info is incomplete in DBLP
 
System created by asidirop@csd.auth.gr [http://users.auth.gr/~asidirop/] © 2002
for Data Engineering Laboratory, Department of Informatics, Aristotle University © 2002