Reengineering Inspection

Communications of the ACM

Volumn 41, Issue 2, 1998, Pages 49-53

  Johnson, Philip M ^a  

^a University of Hawai'i at Manoa   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

GRAPHICAL USER INTERFACES; INPUT OUTPUT PROGRAMS; KNOWLEDGE BASED SYSTEMS; LOCAL AREA NETWORKS; MANAGEMENT INFORMATION SYSTEMS; QUALITY ASSURANCE; REENGINEERING; SOCIETIES AND INSTITUTIONS; WIDE AREA NETWORKS;

DATA QUALITY MANAGEMENT; FORMAL TECHNICAL REVIEW; REENGINEERING INSPECTION; SOFTWARE QUALITY IMPROVEMENT TECHNIQUE; WIDE AREA DEVELOPMENT;

SOFTWARE ENGINEERING;

EID: 0031988343     PISSN: 00010782     EISSN: None     Source Type: Journal    
DOI: 10.1145/269012.269020     Document Type: Article

References (9)

1. Dyer, M. The Cleanroom Approach to Quality Software Development. John Wiley, New York, 1992.
2. Fagan, M.E. Design and code inspections to reduce errors in program development. IBM Syst. J. 15, 3 (1976) pp. 182-211.
3. Gilb, T. and Graham, D. Software Inspection. Addison-Wesley, Reading, Mass., 1993.
4. Grady, R. and Van Slack, T. Key lessons in achieving widespread inspection use. IEEE Softw. 11, 4 (July 1994).
5. Johnson, P.M. An instrumented approach to improving software quality through formal technical review. In Proceedings of the 16th International Conference on Software Engineering. (May 1994, Sorrento, Italy).
6. Kierk, I. Electronic software design reviews smooth development process. Total Quality MOSO 16 (Dec. 1993).
7. Porter, A.A. Votta, L.G., Basili, V.R. Comparing detection methods for software requirements inspections: A replicated experiment. IEEE Trans. Softw. Eng. 21, 6 (June 1995) pp. 563-575.
8. Votta, L.G. Does every inspection need a meeting? In ACM/SIGSOFT 1993 Symposium on Foundations of Software Engineering. (Dec. 1993).
9. Weller, E.F. Lessons learned from three years of inspection data. IEEE Softw. (Sept. 1993) pp 38-45.