A Methodology for Collecting Valid Software Engineering Data

IEEE Transactions on Software Engineering

Volumn SE-10, Issue 6, 1984, Pages 728-738

  Basili, Victor R ^a   Weiss, David M ^b  

^a UNIVERSITY OF MARYLAND   (United States)

^b NAVAL RESEARCH LABORATORY   (United States)

Author keywords

Data collection; data collection methodology; error analysis; error classification; software engineering experimentation

Indexed keywords

DATA PROCESSING - DATA ACQUISITION;

DATA COLLECTION METHODOLOGY; ERROR ANALYSIS; ERROR CLASSIFICAION; SOFTWARE ENGINEERING LABORATORY (SEL); VALIDATION;

COMPUTER SOFTWARE;

EID: 0021518088     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.1984.5010301     Document Type: Article

References (42)

1. B. Boehm et al., Information Processing/Data Automation Implications of Air Force Command and Control Requirements in the 1980’s (CCIP-85), Space and Missile Syst. Org., Los Angeles, CA Feb. 1972.
2. B. Boehm, “Software and its impact: A quantitative assessment,” Datamation, vol. 19, pp. 48–59, May 1973.
3. R. Wolverton, “The cost of developing large scale software,” IEEE Trans. Comput., vol. C-23, no. 6, 1974.
4. T. Bell, D. Bixler, and M. Dyer, “An extendable approach to computer-aided software requirements engineering,” IEEE Trans. Software Eng., vol. SE-3, pp. 49–60, Jan. 1977.
5. A. Ambler, D. Good, J. Browne, et al., “GYPSY: A language for specification and implementation of verifiable programs,” in Proc. ACM Conf Language Design for Reliable Software, Mar. 1977, pp. 1–10.
6. Z. Manna and R. Waldinger, “Synthesis: Dreams => programs,” IEEE Trans. Software Eng., vol. SE-5, pp. 294–329, July 1979.
7. K. Heninger, “Specifying requirements for complex systems: New techniques and their application,” IEEE Trans. Software Eng., vol. SE-6, pp. 2–13, Jan. 1980.
8. D. L. Parnas, “A technique for software module specification wtih examples,” Commun. Ass. Comput. Mach., vol. 15, pp. 330–336, May 1972.
9. J. Guttag, “The specification and application to programming of abstract data types,” Comput. Syst. Res. Group, Dep. Comput. Sci., Univ. Toronto, Ont., Canada, Rep. CSRG-59, 1975.
10. J. Guttag, “Abstract Database types and the development of data structures,” Commun. Ass. Comput. Mach., vol. 20, pp. 396–404, June 1976.
11. B. Liskov and S. Zilles, “Specification techniques for data abstraction,” IEEE Trans. Software Eng., vol. SE-1, pp. 7–19, Mar. 1975.
12. H. Mills, R. Linger, and B. Witt, Structured Programming Theory and Practice. Reading, MA: Addison-Wesley, 1979.
13. S. Caine and E. Gordon, “PDL-A tool for software design,” in Proc. Nat. Comput. Conf., 1975, pp. 271–276.
14. H. Elovitz, “An experiment in software engineering: The architecture research facility as a case study,” in Proc. 4th Int. Conf. Software Eng., 1979, pp. 145–152.
15. D. Weiss, “Evaluating software development by error analysis: The data from the architecture research facility,” J. Syst. Software, vol. 1979.
16. E. W. Dijkstra, A Discipline of Programming. Englewood Cliffs, NJ: Prentice-Hall, 1976.
17. R. W. Floyd, “Assigning meanings to programs,” in Proc. XIX Symp. Appl. Math., Amer. Math. Soc., 1967, pp. 19–32.
18. C. A. R. Hoare, “An axiomatic basis for computer programming,” Commun. Ass. Comput. Mach., vol. 12, Oct. 1969.
19. F. Baker, “Chief programmer team management of production programming,” IBM Syst. J., vol. 11, no. 1, pp. 56–73, 1972.
20. E. W. Dijkstra, “Notes on structured programming,” in Structured Programming. London, England: Academic, 1972.
21. D. E. Knuth, “Structured programming with go to statements,” Comput. Surveys, vol. 6, pp. 261–301, Dec. 1974.
22. H. Mills, “Chief programmer teams: Principles and procedures,” IBM Fed. Syst. Div., FSC 71–5108, 1971.
23. H. Mills, “Mathematical foundations for structured programming,” IBM Fed. Syst. Div., FSC 72–6012, 1972.
24. N. Wirth, “Program development by stepwise refinement,” Commun. Ass. Comput. Mach., vol. 14, pp. 221–227, Apr. 1971.
25. E. Satterthwaite, “Debugging tools for high-level languages,” Software-Practice and Exp., vol. 2, pp. 197–217, July-Sept. 1972.
26. W. Howden, “Theoretical and empirical studies of program testing,” in Proc. 3rd Int. Conf. Software Eng., May 1978, pp. 305–310.
27. J. Goodenough and S. Gerhart, “Toward a theory of test data selection,” in Proc. Int. Conf. Reliable Software, 1975, pp. 493–510.
28. J. Gannon, “Language design to enhance programming reliability,” Comput. Syst. Res. Group, Dep. Comput. Sci., Univ. Toronto, Toronto, Ont., Canada, Rep. CSRG-47, 1975.
29. J. Gannon and J. Horning, “Language design for programming reliability,” IEEE Trans. Software Eng., vol. SE-1, June 1975.
30. C. A. R. Hoare and N. Wirth, “An axiomatic definition of the programming language Pascal,” Acta Inform., vol. 2, pp. 335–355, 1973.
31. K. Jensen and N. Wirth, Pascal User Manual and Report, 2nd ed. New York: 1974.
32. V. Basili and D. Weiss, “Evaluation of a software requirements document by analysis of change data,” in Proc. 5th Int. Conf. Software Eng., Mar. 1981, 314–323.
33. D. Weiss, “Evaluating software development by analysis of change data,” Comput. Sci. Cen., Univ. Maryland, College Park, Rep. TR-1120, Nov. 1981.
34. L. Chmura and D. Weiss, “Evaluation of the A-7E software requirements document by analysis of changes: Three years of data,” presented at NATO A GARD Avionics Symp., Sept. 1982.
35. V. Basili and D. Weiss, “Evaluating software development by analysis of changes: Some data from the Software Engineering Laboratory,” IEEE Trans. Software Eng., to be published.
36. V. Basili, M. Zelkowitz, F. McGarry, et al., “The Software Engineering Laboratory,” Univ. Maryland, College Park, Rep. TR-535, May 1977.
37. B. Boehm, “An experiment in small-scale application software engineering,” TRW, Rep. TRW-SS-80-01, 1980.
38. A. Endres, “Analysis and causes of errors in systems programs,” in Proc. Int. Conf Reliable Software, 1975, pp. 327–336.
39. G. Miller, “The magical number seven, plus or minus two: Some limits on our capacity for processing information,”Psychol. Rev., vol. 63, pp. 81–97, Mar. 1956.
40. J. Bailey and V. Basili, “A meta-model for software development resource expenditures,” in Proc. 5th Int. Conf. Software Eng., Mar. 1981, pp. 107–116.
41. D. L. Parnas, “On the criteria to be used in decomposing systems into modules,” Commun. Ass. Comput. Mach., vol. 15, pp. 1053–1058, Dec. 1972.
42. J. Brown, The Social Psychology of Industry. Baltimore, MD: Penguin, 1954.