Turnover among DP personnel: a casual analysis
Communications of the ACM
The effect of programming team structures on programming tasks
Communications of the ACM
Problems in application software maintenance
Communications of the ACM
Easing fault location in large systems
Communications of the ACM
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
A theory of small program complexity
ACM SIGPLAN Notices
Language features to support reusability
ACM SIGPLAN Notices
ACM SIGSOFT Software Engineering Notes
The impact of programming styles on debugging efficiency
ACM SIGSOFT Software Engineering Notes
An analysis of software development environments
ACM SIGSOFT Software Engineering Notes
Psychosocial implications of computer software development and use: Zen and the art of computing
ACM SIGSOFT Software Engineering Notes
A preliminary experiment in automated software testing
ACM SIGSOFT Software Engineering Notes
A formalization of Myers cause-effect graphs for unit testing
ACM SIGSOFT Software Engineering Notes
The IEEE standard for software maintenance
ACM SIGSOFT Software Engineering Notes
Computer
| Hi-index | 0.01 |
Much has been written about error free code; what it is, and how to attain it. Given that error free code is desirable and worth striving for, can it ever be realized in the majority of our code? I believe that the answer regrettably, is no. If one were to disregard the every day simple applications; like our 50th update program, or simple reports, error free code in large systems is not attainable. There are a number of reasons for that pessimistic statement, such as the following: multiplicity of design methodologies, non use of reusable code, time constraints, user misunderstanding, and testing. The following is an examination of each of the previous reasons.