The State of Software Maintenance

IEEE Transactions on Software Engineering

Volumn SE-13, Issue 3, 1987, Pages 303-310

  Schneidewind, Norman F ^a  

^a NAVAL POSTGRADUATE SCHOOL   (United States)

Author keywords

Metrics; models; software maintenance

Indexed keywords

MANAGEMENT; STANDARDS;

METRICS;

COMPUTER SOFTWARE;

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

References (37)

1. An American National Standard IEEE Standard Glossary of Software Engineering Terminology, ANSI/IEEE Standard 729, 1983
2. J. Martin and C. McClure, Software Maintenance: The Problem and Its Solutions. Englewood Cliffs, NJ: Prentice-Hall, 1983.
3. D. P. Freedman and G. M. Weinberg, “A checklist for potential side effects of a maintenance change,” in Techniques of Program and System Maintenance, Girish Parikh, Ed. Ethotech., Inc., 1980, pp. 61–68.
4. N. Zvegintzov, “Nanotrends,” Datamation, pp. 106–116, Aug. 1983.
5. B. P. Lientz and B. E. Swanson, “Problems in application software maintenance,” Commun. ACM, vol. 24, no. 11, pp. 763–769, Nov. 1981.
6. N. F. Schneidewind, “Quality metrics standards applied to software maintenance” (Abstract), in Proc. Comput. Standards Conf. 1986 (Addendum), IEEE Comput. Soc., May 113–15, 1986.
7. M. B. Kline and N. F. Schneidewind, “Life cycle comparisons of hardware and software maintainability,” in Proc. Third Nat. Rel. Conf., Birmingham, England, Apr./May 1981, p. 4A/3/1-4A/3/14.
8. E. Bush, “The automatic restructuring of COBOL,” in Proc. Conf. Software Maintenance 1985. Washington, DC: IEEE Comput. Soc. Press, Nov. 1985, pp. 35–41.
9. L. A. Belady, “Evolved software for the 80’s,” Computer, vol. 12, no. 2, pp. 79–82, Feb. 1979.
10. M. M. Lehman, “Programs, life cycles, and laws of software evolution,” Proc. IEEE, vol. 68, no. 9, Sept. 1980.
11. “Program evolution,” Dep. Computing, Imperial College of Science and Technology, London SW7 2BZ, England, Res. Rep. DoC 82/1, Dec. 1982.
12. B. P. Lientz and E. B. Swanson, Software Maintenance Management. Reading, MA: Addison-Wesley, 1980.
13. J. R. McKee, “Maintenance as a function of design,” in AFIPS Conf. Proc., vol. 53, 1984 Nat. Comput. Conf., pp. 187–193.
14. C. L. McClure, Managing Software Development and Maintenance. New York: Van Nostrand, 1981.
15. J. Silverman, N. Giddings, and J. Beane, “An approach to design-for-maintenance,” for-maintenance,” in Proc. Software Maintenance Workshop, R. S. Arnold, Ed. Washington, DC: IEEE Comput. Soc. Press, Dec. 1983, pp. 106–110.
16. R. L. Glass and R. A. Noiseux, Software Maintenance Guidebook. Englewood Cliffs, NJ: Prentice-Hall, 1981.
17. J. B. Munson, “Software maintainability: A practical concern for lifecycle cycle costs,” Computer, vol. 14, no. 11, pp. 103–109, Nov. 1981.
18. E. Yourdon, “Structured maintenance,” in Techniques of Program and System Maintenance, Girish Parikh, Ed. Ethotech, Inc., 1980, pp. 211–213.
19. S. Letovsky and E. Soloway, “Delocalized plans and program comprehension,” IEEE Software, vol. 3, no. 3, pp. 41–49, May 1986.
20. B. Boehm, “The economics of software maintenance,” in Proc. Software Maintenance Workshop, R. S. Arnold, Ed. Washington, DC: IEEE Comput. Soc. Press, Dec. 1983, pp. 9–37.
21. Z. Kishimoto, “Testing in software maintenance and software maintenance from the testing perspective,” in Proc. Software Maintenance Workshop, R. S. Arnold, Ed. Washington, DC: IEEE Comput. put. Soc. Press, Dec. 1983, pp. 166–177.
22. M. J. Lyons, “Salvaging your software asset (tools based maintenance),” in AFIPS Conf. Proc., 1981 Nat. Comput. Conf., pp. 337–341
23. S. S. Yau and J. S. Collofello, “Some stability measures for software maintenance,” IEEE Trans. Software Eng., vol. SE-6, pp. 545–552, Nov. 1980.
24. ——, “Design stability measures for software maintenance,” IEEE Trans. Software Eng., vol. SE-11, pp. 849–856, Sept. 1985.
25. G. M. Berns, “Assessing software maintainability,” Commun. ACM, vol. 27, no. 1, pp. 14–23.
26. H. Schafer, “Metrics for optimal maintenance management,” in Proc. Conf. Software Maintenance-1985. Washington, DC: IEEE Comput. put. Soc. Press, 1985, pp. 114–119.
27. R. S. Arnold and D. A. Parker, “The dimensions of healthy maintenance,” in Proc. 6th Int. Conf. Software Eng. Washington, DC: IEEE Comput. Soc. Press, Sept. 1982, pp. 10–27.
28. J. S. Collofello and J. W. Blaylock, “Syntactic information useful for software maintenance,” in AFIPS Conf. Proc., vol. 54, 1985 Nat. Comput. Conf., pp. 547–553.
29. N. F. Schneidewind, “Usability of military standards for the maintenance of embedded computer software,” in Advisory Group for Aerospace Research & Development Conf. Proc. 330, Software for Avionics, North Altantic Treaty Organization, The Hague, Netherlands, Sept. 6–10, 1982, pp. 21-1–21-6.
30. J. A. McCall, M. A. Herdon, and W. M. Osborne, “Software Maintenance Management,” Nat. Bureau Standards, NBS Special Publ. 500–129, Oct. 1985.
31. R. J. Martin and W. M. Osborne, “Guidance of software maintenance,” Nat. Bureau Standards, NBS Special Publ. 500–106, Dec. 1983.
32. N. F. Schneidewind, “Evaluation of maintainability enhancement for the TCP/TSP Revision 6.0 Update.20,” Naval Postgraduate School, Rep. NPS54-82-004, Feb. 1982.
33. G. Arango, “TMM: Software maintenance by transformation,” IEEE Software, vol. 3, no. 3, pp. 27–39, May 1986.
34. R. N. Britcher and J. J. Craig, “Using modern design practices to upgrade aging software systems,” IEEE Software, vol. 3, no. 3, pp. 16–24, May 1986.
35. N. Chapin, “Software maintenance with fourth-generation languages,” ACM Software Engineering Notes, vol. 9, no. 1, pp. 41–42, Jan. 1984.
36. “Software maintenance: A different view,” in AFIPS Conf. Proc. 54, Nat. Comput. Conf., 1985, pp. 509–513.
37. R. S. Arnold, N. F. Schneidewind, and N. Zvegintzov, “A software maintenance workshop,” Commun. ACM, vol. 27, no. 11, pp. 1120–1121. 1158.