David Lorge Parnas
David Lorge Parnas
Middle Road Software, McMaster University, University of Limerick
Verified email at mcmaster.ca - Homepage
Title
Cited by
Cited by
Year
On the criteria to be used in decomposing systems into modules
DL Parnas
Pioneers and Their Contributions to Software Engineering, 479-498, 1972
70771972
Software aging
DL Parnas
Proceedings of 16th International Conference on Software Engineering, 279-287, 1994
1745*1994
On the design and development of program families
DL Parnas
IEEE Transactions on software engineering, 1-9, 1976
13151976
Designing software for ease of extension and contraction
DL Parnas
IEEE transactions on software engineering, 128-138, 1979
12701979
A rational design process: How and why to fake it
DL Parnas, PC Clements
IEEE transactions on software engineering, 251-257, 1986
11351986
A technique for software module specification with examples
DL Parnas
Communications of the ACM 15 (5), 330-336, 1972
10131972
Concurrent control with “readers” and “writers”
PJ Courtois, F Heymans, DL Parnas
Communications of the ACM 14 (10), 667-668, 1971
7491971
Functional documents for computer systems
DL Parnas, J Madey
Science of Computer programming 25 (1), 41-61, 1995
696*1995
The modular structure of complex systems
DL Parnas, PC Clements, DM Weiss
IEEE Transactions on software Engineering, 259-266, 1985
6441985
Scheduling processes with release times, deadlines, precedence and exclusion relations
J Xu, DL Parnas
IEEE Transactions on software engineering 16 (3), 360-369, 1990
5431990
Software aspects of strategic defense systems
DL Parnas
Communications of the ACM 28 (12), 1326-1335, 1985
5251985
Evaluation of safety-critical software
DL Parnas, AJ Van Schouwen, SP Kwan
Communications of the ACM 33 (6), 636-648, 1990
4641990
Information distribution aspects of design methodology
DL Parnas
Carnegie Mellon University, 1971
4511971
On satisfying timing constraints in hard-real-time systems
J Xu, DL Parnas
IEEE transactions on software engineering 19 (1), 70-84, 1993
3491993
On the use of transition diagrams in the design of a user interface for an interactive computer system
DL Parnas
Proceedings of the 1969 24th national conference, 379-385, 1969
2871969
Software engineering programs are not computer science programs
DL Parnas
IEEE software 16 (6), 19-30, 1999
2861999
Wikipedia risks
P Denning, J Horning, D Parnas, L Weinstein
Communications of the ACM 48 (12), 152-152, 2005
2672005
Software requirements for the A-7E aircraft
KL Heninger
NRL Memorandum Report 3876, Naval Research Laboratory, 1978
2651978
On a “buzzword”: hierarchical structure
DL Parnas
Programming Methodology, 335-342, 1978
2581978
Assessment of safety-critical software in nuclear power plants.
DL Parnas, GJK Asmis, J Madey
Nuclear safety 32 (2), 189-198, 1991
2451991
The system can't perform the operation now. Try again later.
Articles 1–20