Experimental evaluation of software documentation formats

The Journal of Systems and Software

Volumn 9, Issue 2, 1989, Pages 167-207

  Curtis, Bill ^a   Sheppard, Sylvia B ^b   Kruesi Bailey, Elizabeth ^c   Bailey, John ^c   Boehm Davis, Deborah A ^d  

^a Microelectronics Computer Technology Corporation   (United States)

^b Computer Technology Associates Inc Lanham MarylandUSA ^*  (United States)

^c Software Metrics Inc   (United States)

^d GEORGE MASON UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER PROGRAMMING;

DOCUMENTATION FORMATS; SOFTWARE DOCUMENTATION;

COMPUTER SOFTWARE;

EID: 0024612626     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/0164-1212(89)90019-8     Document Type: Article

References (68)

1. Problem Solving and the Development of Abstract Categories in Programming Lanugages
2. Cognitive structures in the Comprehension and Memory of Computer Programs: An Investigation of Computer Program Debugging
3. Understanding and Documenting Programs
4. Formats for Representing Procedural Instructions
5. Paivio's Dual-coding Model of Meaning Revisited
6. Documentation of Concurrent Programs
7. An Experimental Study of Flowcharts as an Aid to Identification of Procedural Faults
8. Experimental Studies of Flowchart Use at Different Stages of Program Debugging
9. Studying Programmer Behavior Experimentally The Problems of Proper Methodology
10. Towards a Theory of the Comprehension of Computer Programs
11. PDL—A Tool for Software Design
12. Coefficient Alpha and the Internal Structure of Tests
13. Measurement and Experimentation in Software Engineering
14. Substantiating Programmer Variability
15. Third Time Charm: Stronger Prediction of Programmer Performance by Software Complexity Metrics
16. Cognitive Issues in Software Science
17. Software Psychology: The Need for an Interdisciplinary Program
18. Notes on Structured Programming
19. When Do Diagrams Make Good Computer Languages?
20. An Investigation of the Utility of Flowcharts During Computer Program Debugging
21. Conditional Program Statements and Their Comprehensibility to Professional Programmers
22. Pictures of Programs and Other Processes Or How to Do Things with Lines
23. Structured Programming
24. A Survey of Programming Design and Specification Techniques
25. The Comprehension of Printed Instructions and the Flowchart Alternative
26. Relating Individual Differences in Computer Programming Performance to Human Information Processing Abilities
27. Comprehension as Affected by the Structure of the Problem Representation
28. What Have We Learned in the Last Six Years
29. Knowledge Organization and Skill Differences in Computer Programmers
30. An Evaluation of Modern Programming Practices in an Aerospace Environment
31. Remembering, Understanding, and Representation
32. Flowcharts vs. Program Design Languages: An Experimental Comparison
33. Knowledge-Based Fault Localization in Debugging
34. The Psychological Study of Programming
35. Modern Coding Practices and Programmer Performance
36. An Empirical Evaluation of Software Documentation Formats
37. Exploratory Experiments in Programmer Behavior
38. Control Flow and Data Structure Documentation: Two Experiments
39. Syntactic/semantic Models of Programmer Behavior: A Model and Experimental Results
40. Experimental Investigations of the Utility of Detailed Flowcharts in Programming
41. Scope Marking in Computer Conditionals A Psychological Evaluation
42. Cognitive Strategies and Looping Constructs: An Empirical Study
43. Empirical Studies of Programming Knowledge
44. A Goal/Plan Analysis of Buggy Pascal Programs
45. Expertise in Debugging Computer Programs: A Process Analysis
46. Conditional Statements and Program Coding: An Experimental Evaluation
47. Structured Tools and Conditional Logic: An Empirical Investigation
48. Programmers Use Slices When Debugging
49. Beacons in Computer Program Comprehension
50. Written Information: Some Alternatives to Prose for Expressing the Outcome of Complex Contingencies
51. Design Stability Measures for Software Maintenance