sort by
approximate search
1shortlisttitle datasearch history  
results search [or] ISN:0000000073729733 | 1 hits
Person
ISNI: 
0000 0000 7372 9733
Name: 
David Parnas (Amerikaans informaticus)
David Parnas (amerikansk ingeniør og informatikar)
David Parnas (amerikansk ingeniør og informatiker)
David Parnas (amerikansk ingenjör och datavetare)
David Parnas (Canadian software engineer)
David Parnas (US-amerikanischer Pionier der Softwaretechnik)
Lorge Parnas, David
Parnas, D. L.
Parnas, David L.
Parnas, David Lodge
Parnas, David Lorge
דייוויד פרנס
دیوید پارناس (دانشمند علوم کامپیوتر و مهندس آمریکایی)
デイビッド・パーナス
Dates: 
1941-
Creation class: 
article
cre
Language material
txt
Creation role: 
author
contributor
Related names: 
Bentley, Jon Louis
Cohen, Danny
Hoffman, Daniel M.
McMaster University. Communications Research Laboratory
Qiao, Sanzheng
Queen's University (Kingston, Ont.). Studies in Communication and Information Technology
Theses
Trio
Viveros, R.
Weiss, David M. (1945- ))
Weiss, David M. (1945-)
Wydawnictwa Naukowo-Techniczne
Titles: 
Abstract interface specifications for the A-7E device interface module
Abstract types defined as classes of variables
Active design reviews:principles and practices
Applying mathematical software documentation
Assessment of safety-critical software in nuclear power plants.
Building reliable software in BLOWHARD
Computers: Boon or bane?
Design and Specification of the Minimal Subset of an Operating System Family
Estimating software reliability using inverse sampling
Evaluation of safety-critical software
Family of Computer Systems for Delivering Individualized Advice, A
Formal documentation of well-structured programs
"Formal methods" technology transfer will fail
Formally specifying a communications protocol using the trace assertion method
generalized control structure and its formal definition, A
Inside Risks Ten Myths About Y2K Inspections
Inspection procedures for critical programs that model physical phenomena
Inspection's role in software quality assurance
Interface specifications for the SCR (A-7E) Extended computer module. D. L. Parnas.
Language-Free Mathematical Methods for Software Design
Licensing software engineers in Canada
Limits of Empirical Studies of Software Engineering, The
Modular Structure of Complex Systems, The
On a solution to the cigarette smoker's problem (without conditional statements)
On Code Reuse
On ICSE's "most influential" papers
On iterative constructs
On satisfying timing constraints in hard-real-time systems
On simulating networks of parallel processes in which simultaneous events may occur
On synchronization in hard-real-time systems
On the computational complexity of the maximum trade problem
On the criteria to be used in decomposing systems into modules
On the use of transition diagrams in the design of a user interface for an interactive computer system
Podstawy oprogramowania : zbiór artykułów Davida L. Parnasa
Precise documentation of well-structured programs
Precisely annotated hierarchical pictures of programs
Predicate logic for software engineering
Priority scheduling versus pre-run-time scheduling
Rational Design Process: How and Why to Fake It, A
Requirements-based monitors for real-time systems
Requirements documentation: Why a formal basis is essential
Risks of Stopping Too Soon, The
Risks of Undisciplined Development
role of inspection in software quality assurance, The
Scheduling Processes with Release Times, Deadlines, Precedence, and Exclusion Relations
SDI, two views of professional responsibility, 1987:
Significant event simulation
Simulating the behaviour of software modules by trace rewriting
Software aging
Software aspects of strategic defense systems
Software engineering (extended abstract):an unconsummated marriage
Software engineering programs are not computer science programs
Software fundamentals : collected papers by David L. Parnas
Structured programming: a minor part of software engineering.
Successful software engineering research
System function description algol a language for the description of the functions of finite state systems, the simulation of finite state systems, and the automatic production of the state tables of such sustems
Table transformation tools : why and how
Tabular representations in relational documents
Teaching Programming as Engineering
technique for software module specification with examples, A
Trace rewriting systems
Two positions on licensing
Use of the concept of transparency in the design of hierarchically structured systems
Using information about functions in selecting test cases
Using test oracles generated from program documentation
Which is Riskier : OS Diversity or OS Monopoly?
Why Engineers Should Not Use Artificial Intelligence
Contributed to or performed: 
COMMUNICATIONS- ACM
IEEE SOFTWARE
IEEE TRANSACTIONS ON SOFTWARE ENGINEERING SE
INFORMATION PROCESSING LETTERS
JOURNAL OF SYSTEMS AND SOFTWARE
LECTURE NOTES IN COMPUTER SCIENCE
SOFTWARE ENGINEERING NOTES
Notes: 
Theses
Sources: 
VIAF DNB LAC LC NLP NUKAT WKD
NTA
TEL
ZETO