Evaluating Software Design Processes by Analyzing Change Data Over Time

IEEE Transactions on Software Engineering

Volumn 16, Issue 7, 1990, Pages 729-740

  Chmura, L J ^a   Norcio, A F ^a,b   Wicinski, T J ^a  

^a NAVAL RESEARCH LABORATORY   (United States)

^b UNIVERSITY OF MARYLAND BALTIMORE COUNTY   (United States)

Author keywords

Data collection; Software Cost Reduction project; software design

Indexed keywords

ECONOMICS;

CHANGE DATA; SOFTWARE COST REDUCTION;

COMPUTER SOFTWARE;

EID: 0025462764     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/32.56099     Document Type: Article

References (30)

1. V. R. Basili and B. T. Perricone. “Software errors and complexity: An empirical investigation.” Commun. ACM, vol. 27. pp. 42–52. 1984.
2. V. R. Basili and D. M. Weiss, “A methodology for collecting valid software engineering data,” IEEE Trans. Software Eng., vol. SE-10. no. 6, pp. 728–738. 1984.
3. L. A. Belady and M. M. Lehman. “A model of large program development.” IBM Syst. J., vol. 3. pp. 225–252. 1976.
4. B. W. Boehm. Software Engineering Economies. Englewood Cliffs, NJ: Prentice-Hall. 1981.
5. K. H. Britton and D. L. Parnas. A-7E Module Guide. Naval Res. Lab., Washington. DC. Rep. 4702. 1981.
6. L. J. Chmura. “Proposed new design and code change report form (CRF) for the software cost reduction (SCR) project,” Naval Res. Lab., Washington. DC. Tech. Memo. 7590–34:LC. 1983.
7. L. J. Chmura and A. F. Norcio. “Accuracy of software activity data: The software cost reduction project.” Naval Res. Lab., Washington. DC. Rep. 8780. 1983.
8. L. J. Chmura and D. M. Weiss, “The A-7E software requirements document: Three years of change data.” Naval Res. Lab., Washington. DC. Memo. Rep. 4938, 1982.
9. V. Church, D. Card, F. McGarry, and V. Basili, “Guide to data collection.” NASA/Goddard SEL, Greenbelt. MD. Tech. Rep. SEL-81-001. 1981.
10. P. C. Clements, “Software cost reduction through disciplined design.” Naval Res. Lab. 1984 Rev., pp. 79–87. 1985.
11. P. C. Clements, R. A. Parker, D. L. Parnas, and J. Shore. “A standard organization for specifying abstract interfaces.” Naval Res. Lab., Washington, DC, Rep. 8815, 1984.
12. R. Day. “A history of software maintenance for a complex U.S. Army battlefield automated system,” in Proc. Conf. Software Maintenance. 1985. pp. 181–187.
13. E. W. Dijkstra. “Cooperating sequential processes.” in Programming Languages, F. Genuys. Ed. New York: Academic. 1968, pp. 43–112.
14. W. J. Dixon and F. J. Masscy, Jr., Introduction to Statistical Analysis. New York: McGraw-Hill, 1969.
15. A. Endres. “An analysis of errors and their causes in system programs,” IEEE Trans. Software Eng., vol. SE-1. no. 2. pp. 140–149. 1975.
16. R. B. Grady. “Measuring and managing software maintenance.” IEEE Software, pp. 35–45 Sept. 1987.
17. K. L. Heninger. J. W. Kallander. J. E. Shore. D. L. Parnas. and Staff. “Software requirements for the A-7E aircraft,” Naval Res. Lab., Washington. DC, Memo. Rep. 3876. 1978.
18. B. P. Lientz, E. B. Swanson, and G. E. Tompkins, “Characteristics of application software maintenance.” Commun. ACM. vol. 21. no. 6. pp. 466–471. 1978.
19. B. Meyer. “On formalism in specifications.” IEEE Software, vol. 2. no. 1. pp. 6–27. 1985.
20. A. F. Norcio and L. J. Chmura. “Design activity in developing modules for complex software.” in Empirical Studies of Programmers, E. Soloway and S. Iyengar. Eds. Norwood. NJ: Ablex. 1986.
21. A. Parker, K. L. Heninger, D. Parnas, and J. Shore, “Abstract interface specification for the device interface module.” Naval Res. Lab., Washington. DC. Memo. Rep. 4385. 1980.
22. D. L. Parnas. “On the criteria to be used in decomposing systems into modules.” Commun. ACM. vol. 15. pp. 1053–1058. 1972.
23. —. “Use of abstract interfaces in the development of software for embedded systems.” Naval Res. Lab., Washington. DC. Rep. 8047. 1977.
24. D. L. Parnas and P. C. Clements. “A rational design process: How and why to fake it.” IEEE Trans. Software Eng., vol. SE-12. no. 2. pp. 251–257. 1986.
25. D. L. Parnas, P. C. Clements, and D. M. Weiss, “The modular structure of complex systems.” IEEE Trans. Software Eng., vol. SE-11. no. 3. pp. 259–266. 1985.
26. M. L. Shooman and M. I. Bolsky. “Types, distribution, and test and correction times for programming errors.” in Proc. Int. Conf. Reliable Software, pp. 347–357.
27. E. B. Swanson. “The dimensions of maintenance.” in Proc. Second Int. Conf. Software Engineering. 1976. pp. 492–497.
28. D. M. Weiss, “A comparison of errors in different software-development environments,” Naval Res. Lab., Washington, DC. NRL Rep. 8598. 1982.
29. D. M. Weiss and V. R. Basili. “Evaluating software development by analysis of changes: Some data from the Software Engineering Laboratory.” IEEE Trans. Software Eng., vol. SE-11, no. 2. pp. 157–168. 1985.
30. R. Z. Xu. “An empirical investigation: Software errors and their influence upon development of WPADT,” in Proc. COMPSAC 85. 1985. pp. 4–8.