메뉴 건너뛰기




Volumn SE-13, Issue 3, 1987, Pages 335-343

The Use of Software Complexity Metrics in Software Maintenance

Author keywords

Complexity metrics; design analysis; maintenance; software metrics

Indexed keywords

COMPUTER PROGRAMMING;

EID: 0023312154     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.1987.233164     Document Type: Article
Times cited : (125)

References (24)
  • 1
    • 0042992364 scopus 로고
    • Evaluating software development characteristics: Assessment of software measures in the software engineering laboratory
    • NASA Goddard, Dec. 2
    • V. Basili, “Evaluating software development characteristics: Assessment of software measures in the software engineering laboratory,” in Proc. Sixth Annu. Software Eng. Workshop, NASA Goddard, Dec. 2, 1981.
    • (1981) Proc. Sixth Annu. Software Eng. Workshop
    • Basili, V.1
  • 2
    • 0020847290 scopus 로고
    • Metric analysis and data validation across Fortran projects
    • Nov.
    • V. Basili, R. Selby, and T. Phillips, “Metric analysis and data validation across Fortran projects,” IEEE Trans. Software Eng., vol. SE-9, 9, pp. 652–663, Nov. 1983.
    • (1983) IEEE Trans. Software Eng , vol.SE-9 , Issue.9 , pp. 652-663
    • Basili, V.1    Selby, R.2    Phillips, T.3
  • 3
    • 0017268047 scopus 로고
    • A model of large program development
    • L. Belady and M. Lehman, “A model of large program development,” IBM Syst. J., no. 3, pp. 225–252, 1976.
    • (1976) IBM Syst. J. , Issue.3 , pp. 225-252
    • Belady, L.1    Lehman, M.2
  • 4
    • 85042377749 scopus 로고
    • Quantitative evaluation of software quality
    • Oct. San Francisco, CA
    • B. Boehm, “Quantitative evaluation of software quality,” in Proc. 2nd Int. Conf. Software Eng., San Francisco, CA, Oct. 1976, pp. 592–605.
    • (1976) Proc. 2nd Int. Conf. Software Eng , pp. 592-605
    • Boehm, B.1
  • 5
    • 1842544875 scopus 로고
    • Software engineering-As it is
    • Munich, Germany
    • “Software engineering-As it is,” in Proc. 4th Int. Conf. Software Eng. Munich, Germany, 1979, pp. 11–21.
    • (1979) Proc. 4th Int. Conf. Software Eng , pp. 11-21
  • 6
    • 84941502497 scopus 로고
    • Why does software die?
    • Infotech State of the Art Rep., series 8
    • P. Brown, “Why does software die?” in Life Cycle Management, Infotech State of the Art Rep., series 8, no. 7, 1980.
    • (1980) Life Cycle Management , Issue.7
    • Brown, P.1
  • 8
    • 0018444615 scopus 로고
    • Measuring the psychological complexity of software maintenance tasks with the Halstead and McCabe metrics
    • Mar.
    • W. Curtis et al., “Measuring the psychological complexity of software maintenance tasks with the Halstead and McCabe metrics,” IEEE Trans. Software Eng., vol. SE-5, pp. 96–104, Mar. 1979.
    • (1979) IEEE Trans. Software Eng , vol.SE-5 , pp. 96-104
    • Curtis, W.1
  • 10
    • 3142588078 scopus 로고
    • Information flow metrics for the evaluation of operating systems' structure
    • S. Henry, “Information flow metrics for the evaluation of operating systems’ structure,” Ph.D., dissertation, Iowa State Univ., 1979.
    • (1979) Ph.D., dissertation, Iowa State Univ.
    • Henry, S.1
  • 11
    • 0019613747 scopus 로고
    • Software structure metrics based on information flow
    • Sept.
    • S. Henry and D. Kafura, “Software structure metrics based on information flow,” IEEE Trans. Software Eng., vol. SE-7, pp. 5109–518, Sept. 1981.
    • (1981) IEEE Trans. Software , vol.SE-7 , pp. 5109-5518
    • Henry, S.1    Kafura, D.2
  • 12
    • 84976702913 scopus 로고
    • On the relationships among three software metrics
    • S. Henry, D. Kafura, and K. Harris, “On the relationships among three software metrics,” Performance Evaluation Rev., vol. 10, no. 1, pp. 81–88, Spring 1981.
    • (1981) Performance Evaluation Rev , vol.10 , Issue.1 , pp. 81-88
    • Henry, S.1    Kafura, D.2    Harris, K.3
  • 13
    • 0021448910 scopus 로고
    • The evaluation of software systems' structure using quantitative software metrics
    • June
    • S. Henry and D. Kafura, “The evaluation of software systems’ structure using quantitative software metrics,” Software: Practice and Experience, vol. 14, no. 6, pp. 561–573, June 1984.
    • (1984) Software: Practice and Experience , vol.14 , Issue.6 , pp. 561-573
    • Henry, S.1    Kafura, D.2
  • 14
    • 0019577666 scopus 로고
    • Software quality metrics based on inter-connectivity
    • D. Kafura and S. Henry, “Software quality metrics based on inter-connectivity,” connectivity,” J. Syst. Software, vol. 2, pp. 121–131, 1981.
    • (1981) J. Syst. Software , vol.2 , pp. 121-131
    • Kafura, D.1    Henry, S.2
  • 15
    • 84941494029 scopus 로고
    • The independence of software metrics taken at different Life Cycle stages
    • NASA Goddard Nov.
    • D. Kafura, J. Canning, and G. Reddy, “The independence of software metrics taken at different Life Cycle stages,” in Proc. 9th Annu. Software Eng. Workshop, NASA Goddard, Nov. 1984, pp. 213–222.
    • (1984) Proc. 9th Annu. Software Eng. Workshop , pp. 213-222
    • Kafura, D.1    Canning, J.2    Reddy, G.3
  • 16
    • 0022287740 scopus 로고
    • A validation of software metrics using many metrics and two resources
    • London, England, Aug
    • D. Kafura and J. T. Canning, “A validation of software metrics using many metrics and two resources,” in Proc. 8th Int. Conf. Software Eng., London, England, Aug. 1985, pp. 378–385.
    • (1985) Proc. 8th Int. Conf. Software Eng , pp. 378-385
    • Kafura, D.1    Canning, J.T.2
  • 17
    • 50849153948 scopus 로고
    • On understanding laws, evolution and conservation in the large-program life cycle
    • M. M. Lehman, “On understanding laws, evolution and conservation in the large-program life cycle,” J. Syst. Software, vol. 1, no. 3, pp. 213–232, 1980.
    • (1980) J. Syst. Software , vol.1 , Issue.3 , pp. 213-232
    • Lehman, M.M.1
  • 18
    • 0017291489 scopus 로고
    • A complexity measure
    • Dec.
    • T. J. McCabe, “A complexity measure,” IEEE Trans. Software Eng., vol. SE-2, pp. 308–320, Dec. 1976.
    • (1976) IEEE Trans. Software Eng. , vol.SE-2 , pp. 308-320
    • Mccabe, T.J.1
  • 19
    • 0018282064 scopus 로고
    • A model for program complexity analysis
    • Atlanta, GA, May
    • C. McClure, “A model for program complexity analysis,” in Proc. 3rd Int. Conf. Software Eng., Atlanta, GA, May 1978, pp. 149–157.
    • (1978) Proc. 3rd Int. Conf. Software , pp. 149-157
    • Mcclure, C.1
  • 20
    • 84916563767 scopus 로고
    • Software design metrics for maintenance
    • NASA Goddard, Nov
    • H. Rombach, “Software design metrics for maintenance,” in Proc. 9th Annu. Software Eng. Workshop, NASA Goddard, Nov. 1984, pp. 100–135.
    • (1984) Proc. 9th Annu. Software Eng. Workshop , pp. 100-135
    • Rombach, H.1
  • 21
    • 0022315605 scopus 로고
    • Impact of software structure on maintenance
    • Nov.
    • —, “Impact of software structure on maintenance,” in Proc. Conf. Software Maintenance, Nov. 1985.
    • (1985) Proc. Conf. Software Maintenance
  • 22
    • 0022044747 scopus 로고
    • Identifying error-prone software-An empirical approach
    • Apr.
    • V. Shen et al., “Identifying error-prone software-An empirical approach,” IEEE Trans. Software Eng., vol. SE-11, pp. 317–323, Apr. 1985.
    • (1985) IEEE Trans. Software Eng , vol.SE-11 , pp. 317-323
    • Shen, V.1
  • 23
    • 3142584459 scopus 로고
    • Enhanced effort estimation by extending basic programming models to include modularity factors
    • S. Woodfield, “Enhanced effort estimation by extending basic programming models to include modularity factors,” Ph.D. dissertation, Purdue Univ., 1980.
    • (1980) Ph.D. dissertation, Purdue Univ.
    • Woodfield, S.1
  • 24
    • 0019080197 scopus 로고
    • Some stability measures for software maintenance
    • Sept.
    • S. Yau and J. Collofello, “Some stability measures for software maintenance,” IEEE Trans. Software Eng., vol. SE-6, pp. 545–552, Sept. 1980.
    • (1980) IEEE Trans. Software Eng , vol.SE-6 , pp. 545-552
    • Yau, S.1    Collofello, J.2


* 이 정보는 Elsevier사의 SCOPUS DB에서 KISTI가 분석하여 추출한 것입니다.