Software metrics knowledge and databases for project management

IEEE Transactions on Knowledge and Data Engineering

Volumn 11, Issue 1, 1999, Pages 255-264

  Paul, Raymond A ^a,b   Kunii, Tosiyasu L ^a,c   Shinagawa, Yoshihisa ^d   Khan, Muhammad F ^e  

^a IEEE

^b ARMED FORCES INSTITUTE OF PATHOLOGY   (United States)

^c UNIVERSITY OF AIZU   (Japan)

^d UNIVERSITY OF TOKYO   (Japan)

^e PURDUE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER ARCHITECTURE; COMPUTER SOFTWARE SELECTION AND EVALUATION; COST EFFECTIVENESS; DATABASE SYSTEMS; KNOWLEDGE BASED SYSTEMS; LARGE SCALE SYSTEMS; PROJECT MANAGEMENT; RISK MANAGEMENT; SOFTWARE ENGINEERING;

KNOWLEDGE ABSTRACTION; SOFTWARE METRICS DATABASES; SOFTWARE PROJECT MANAGEMENT;

KNOWLEDGE ACQUISITION;

EID: 0032675226     PISSN: 10414347     EISSN: None     Source Type: Journal    
DOI: 10.1109/69.755633     Document Type: Article

References (20)

1. "Department of the Army Pamphlet (DA Pam) 73-1," Part 7, Software T&E Guidelines, Sept. 1992.
2. V. Basili and D.M. Weiss, "A Methodology for Collecting Valid Software Engineering Data," IEEE Trans. Software Eng., vol. 10, no. 6, pp. 728-738, Nov. 1984.
3. L.A. Belady, "Software is the Glue in Large Systems," IEEE Comm., vol. 27, no. 8, pp. 33-36, Aug. 1989.
4. B. Boehm, Software Economics, 1991.
5. N. Fenton, Software Metrics: A Rigorous Approach, Chapman and Hall, New York, 1991.
6. A. Goel, K. Ozturk, and R. Paul, "Statistical Analysis of Metrics Data," U.S. Army OPTECH Technical Report 94-1, Jan. 1994.
7. R. Grady, "Successfully Applying Software Metrics," Computer, pp. 18-25, Sept. 1994.
8. S. Grey, "Project Cost and Schedule Risk Analysis," Digest Colloqium Risk Analysis Methods and Tools, no. 134, London, IEE, pp. 7/1-4, 1992.
9. D.L. Lanning and T.M. Khoshgoftaar, "Modeling the Relationship Between Source Code Complexity and Maintenance Difficulty," Computer, pp. 35-40, Sept. 1994.
10. R.K. Madsen and R.W. Selby, "Metric Driven Classification Models for Analyzing Large-Scale Software," Arcadia Technical Report UCI-91-0, Dept. of Computer Science, Univ. of California, Irvine, Jan. 1991.
11. S.G. Mallet, "A Theory For Multiresolution Signal Decomposition: The Wavelet Representation," IEEE Trans. Pattern Analysis and Machine Intelligence, vol. 11, no. 7, pp. 674-693, 1989.
12. NASA Johnson Space Center, DA3 Software Development Metrics Handbook, Version 2.1, JSC-25519, Houston, 1992.
13. M. Ouyang and M. Golay, "An Integrated Formal Approach for Developing High Quality Software of Safety-Critical Systems," Technical Report MIT-ANP-TR-035, Massachusetts Inst. of Technology, Cambridge, Mass., 1991.
14. A. Porter and R.W. Selby, "Empirically Guided Software Development Using Metric-Based Classification Trees," IEEE Software, Mar. 1990.
15. H.D. Rombach and B.T. Ulery, "Improving Software Maintenance Through Measurement," Proc. IEEE, vol. 77, no. 4, pp. 581-595, Apr. 1989.
16. "Software Engineering Tools Experiment," final report, vol. 1, Dept. of Defense, Strategic Defense Initiative, Washington, D.C., 1990.
17. G. Stark, R.C. Durst, and C.W. Vowell, "Using Metrics In Management Decision Making," Computer, pp. 42-48, Sept. 1994.
18. I. Thomas and B. Nejmeh, "Definitions of Tool Integration for Environments," IEEE Software, pp. 29-34, Mar. 1992.
19. E. Weller, "Lessons from Three Years of Inspection Data," IEEE Software, vol. 10, no. 5, pp. 38-45, Sept. 1993.
20. W. Zage and M. Zage, "Evaluating Design Metrics on Large Scale Software," IEEE Software, vol. 10, no. 4, pp. 75-80, July 1993.