Software errors and complexity: an empirical investigation0
Communications of the ACM
Papers presented at the first workshop on empirical studies of programmers on Empirical studies of programmers
Analyzing the high frequency bugs in novice programs
Papers presented at the first workshop on empirical studies of programmers on Empirical studies of programmers
Empirical studies of programmers: second workshop
Empirical studies of programmers: second workshop
An analysis of the on-line debugging process
Empirical studies of programmers: second workshop
Software testing techniques (2nd ed.)
Software testing techniques (2nd ed.)
Practical results from measuring software quality
Communications of the ACM
Cognitive bias in software engineering
Communications of the ACM
Novice programmer errors: language constructs and plan composition
International Journal of Human-Computer Studies
The Psychological Study of Programming
ACM Computing Surveys (CSUR)
An experimental evaluation of data type conventions
Communications of the ACM
A Discipline for Software Engineering
A Discipline for Software Engineering
Empirical Studies of Programmers: Fifth Workshop
Empirical Studies of Programmers: Fifth Workshop
An Experimental Comparison of the Effectiveness of Branch Testing and Data Flow Testing
IEEE Transactions on Software Engineering
Certification of Software Components
IEEE Transactions on Software Engineering
A Preliminary Software Engineering Theory as Investigated by Published Experiments
Empirical Software Engineering
Quality, Productivity, and Learning in Framework-Based Development: An Exploratory Case Study
IEEE Transactions on Software Engineering
A practical type system and language for reference immutability
OOPSLA '04 Proceedings of the 19th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Javari: adding reference immutability to Java
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Type inference for spreadsheets
Proceedings of the 8th ACM SIGPLAN international conference on Principles and practice of declarative programming
An update calculus for expressing type-safe program updates
Science of Computer Programming
A Type System Based on End-User Vocabulary
VLHCC '07 Proceedings of the IEEE Symposium on Visual Languages and Human-Centric Computing
Proceedings of the ACM international conference on Object oriented programming systems languages and applications
ECOOP'10 Proceedings of the 24th European conference on Object-oriented programming
Proceedings of the 7th symposium on Dynamic languages
Proceedings of the 3rd ACM SIGPLAN workshop on Evaluation and usability of programming languages and tools
An empirical study of the influence of static type systems on the usability of undocumented software
Proceedings of the ACM international conference on Object oriented programming systems languages and applications
Do developers benefit from generic types?: an empirical comparison of generic and raw types in java
Proceedings of the 2013 ACM SIGPLAN international conference on Object oriented programming systems languages & applications
Aliasing in Object-Oriented Programming
| Hi-index | 0.00 |
Type checking is considered an important mechanism for detectingprogramming errors, especially interface errors. This reportdescribes an experiment to assess the defect-detection capabilitiesof static, intermodule type checking. The experiment uses ANSI Cand Kernighan&Ritchie (K&R) C. The relevant difference isthat the ANSI C compiler checks module interfaces (i.e., theparameter lists calls to external functions), whereas K&R Cdoes not. The experiment employs a counterbalanced design in whicheach of the 40 subjects, most of them CS PhD students, writes twonontrivial programs that interface with a complex library (Motif).Each subject writes one program in ANSI C and one in K&R C. Theinput to each compiler run is saved and manually analyzed fordefects. Results indicate that delivered ANSI C programs containsignificantly fewer interface defects than delivered K&R Cprograms. Furthermore, after subjects have gained some familiaritywith the interface they are using, ANSI C programmers removedefects faster and are more productive (measured in both deliverytime and functionality implemented).