Norman E. Fenton
- 1.Abdel-Hamid TK, "The slippery path to productivity improvement; IEEE Software, 13(4), 43-52, 1996. Google Scholar
Digital Library
- 2.Adams E , "Optimizing preventive service of software products, IBM Research Journal, 28(1), 2-14, 1984.Google ScholarDigital Library
- 3.Agena L t d , "Bayesian Belief Nets", http://www.agena.co.uk/bbn_article/bbns.htmlGoogle Scholar
- 4.Akiyama F, "An example of software system debugging", Inf Processing 71,353-379, 1971.Google Scholar
- 5.Albrecht A.J, Measuring Application Development, Proceedings of IBM Applications Development joint SHARE/GUIDE symposium. Monterey CA, pp 83-92, 1979.Google Scholar
- 6.Basili VR and Rombach liD, The TAME project: Towards improvement-oriented software environments, IEEE Transactions on Software Engineering 14(6), pp 758-773, 1988.Google ScholarDigital Library
- 7.Basili VR and Perricone BT, "Software Errors and Complexity: An Empirical Investigation", Communications of the ACM, Vol. 27, No.l, pp.42-52, 1984. Google ScholarDigital Library
- 8.Basili VR and Reiter RW, A controlled experiment quantitatively comparing software development approaches, IEEE Trans Soft Eng SE-7(3), 1981.Google ScholarDigital Library
- 9.Basili VR, Selby RW and Hutchens DH, Experimentation in software engineering, IEEE Trans Soft Eng SE-12(7), 733- 743, 1986. Google ScholarDigital Library
- 10.Bhargava HK, Sridhar S, Herrick C, Beyond spreadsheets: tools for building decision support systems, IEEE Computer, 32(3), 31-39, 1999. Google ScholarDigital Library
- 11.Boehm BW, Software Engineering Economics, Prentice- Hall, New York, 1981. Google ScholarDigital Library
- 12.Briand LC, Morasca S, Basili VR, Property-based software engineering measurement, IEEE Transactions on Software Engineering, 22(1), 68-85, 1996. Google ScholarDigital Library
- 13.Brocklehurst, S and Littlewood B, New ways to get accurate software reliability modelling, IEEE Software, 34-42, July, 1992. Google ScholarDigital Library
- 14.Chidamber SR and Kemerer CF, A metrics suite for object oriented design, IEEE Trans Software Eng, 20 (6), 476-498, 1994. Google ScholarDigital Library
- 15.Chulani S, Boehm B, Steece B, "Bayesian analysis of empirical software engineering cost models, IEEE Transactions on Software Engineering, 25(4), 573-583, 1999. Google ScholarDigital Library
- 16.DeMarco T, 'Controlling Software Projects', Yourden Press, New York, 1982Google Scholar
- 17.Fenton NE, "Software Measurement Programs", Software Testing & Quality Engineering 1(3), 40-46, 1999.Google Scholar
- 18.Fenton NE, Software Metrics: A Rigorous Approach, Chapman and Hall, 1991. Google ScholarDigital Library
- 19.Fenton NE, Littlewood B, Neil M, Strigini L, Sutcliffe A, Wright D, Assessing Dependability of Safety Critical Systems using Diverse Evidence, lEE Proceedings Software Engineering, 145(1), 35-39, 1998.Google Scholar
- 20.Fenton NE and Neil M, A Critique of Software Defect Prediction Models, IEEE Transactions on Software Engineering, 25(5), 675-689, 1999. Google ScholarDigital Library
- 21.Fenton NE and Neil M, "Software Metrics and Risk", Proc 2nd European Software Measurement Conference (FESMA'99), TI-KVIV, Amsterdam,ISBN 90-76019-07-X, 39-55, 1999.Google Scholar
- 22.Fenton NE and Ohlsson N, Quantitative Analysis of Faults and Failures in a Complex Software System, IEEE Transactions on Software Engineering, to appear, 2000. Google ScholarDigital Library
- 23.Fenton NE and Pfleeger SL, Software Metrics: A Rigorous and Practical Approach (2nd Edition), International Thomson Computer Press, 1996. Google ScholarDigital Library
- 24.Gaffney JR, "Estimating the Number of Faults in Code", IEEE Trans. Software Eng., Vol.10, No.4, 1984.Google ScholarDigital Library
- 25.Gilb T, Software Metrics, Chartwell-Bratt, 1976.Google Scholar
- 26.Glass RL, "A tabulation of topics where software practice leads software theory", J Systems Software, 25, 219-222, 1994. Google ScholarDigital Library
- 27.Grady R and Caswell D, Software Metrics: Establishing a Company-wide Program, Prentice Hall, Engiewood Cliffs, New Jersey, 1987. Google ScholarDigital Library
- 28.Grady, R.B, Practical Software Metrics for Project Management and Process Improvement, Prentice-Hall, 1992. Google ScholarDigital Library
- 29.Hall T and Fenton NE, "Implementing effective software metrics programmes", IEEE Software, 14(2), 55-66, 1997. Google ScholarDigital Library
- 30.Halstead M, Elements of Software Science, North Holland,, 1977. Google ScholarDigital Library
- 31.Harrison R, Counsell SJ, Nithi RV, "An evaluation of he MOOD set of object-oriented software metrics", IEEE Transactions on Software Engineering, 24(6). 491-496, 1998. Google ScholarDigital Library
- 32.Hugin A/S: www.hugin.com, Hugin Expert A/S, P.O. Box 8201 DK-9220 Aalborg, Denmark, 1999Google Scholar
- 33.Humphrey WS, Managing the Software Process, Addison- Wesley, Reading, Massachusetts, 1989. Google ScholarDigital Library
- 34.Jeffery DR and Lotta LG, "Empirical Software Engineering: Guest editors special section introduction", IEEE Transactions on Software Engineering, 25(4), 435-437, 1999. Google ScholarDigital Library
- 35.Jensen FV, An Introduction to Bayesian Networks, UCL Press, 1996. Google ScholarDigital Library
- 36.Jones C, "Applied Software Measurement", McGraw Hill, 1991. Google ScholarDigital Library
- 37.Kitchenham B, Pickard L, Pfleeger SL, "Case studies for method and tool evaluation", IEEE Software, 12(3), 52-62, July, 1995. Google ScholarDigital Library
- 38.Lauritzen SL and Spiegelhalter DJ, "Local Computations with Probabilities on Graphical Structures and their Application to Expert Systems (with discussion)", J. R. Staffs. Soc. B, 50, No 2, pp 157-224, 1988.Google Scholar
- 39.Lipow M, "Number of Faults per Line of Code", IEEE Trans. Software Eng., Vol. 8, No.4, 437-439, 1982.Google ScholarDigital Library
- 40.McCabe T, A Software Complexity Measure, IEEE Trans. Software Engineering SE-2(4), 308-320, 1976. Google ScholarDigital Library
- 41.Munson JC, and Khoshgoflaar TM, The detection of faultprone programs, IEEE Transactions on Software Engineering,18(5), 423-433, 1992. Google ScholarDigital Library
- 42.Neil M, Fenton NE, Nielsen L, "Building large-scale Bayesian Networks; submitted Knowledge Engineering Review, 1999. Google ScholarDigital Library
- 43.Putnam LH, A general empirical solution to the macro software sizing and estimating problem, IEEE Trans Soft Eng SE-4(4), 1978, 345-361, 1978.Google ScholarDigital Library
- 44.Putnam LH, Mah M, Myers W, "First, get the front end right", Cutter IT Journal 12(4), 20-28, 1999.Google Scholar
- 45.SERENE consortium, SERENE (SafEty and Risk Evaluation using bayesian Nets): Method Manual, ESPRIT Project 22187, http://www.csr.city.ac.uk/people/norman.fenton/serene.htm, 1999.Google Scholar
- 46.Shen VY, Yu T, Thebaut SM, and Paulsen LR, "Identifying error-prone software - an empirical study", IEEE Trans. Software Eng., Vol. 11, No.4, pp. 317-323, 1985. Google ScholarDigital Library
- 47.Stark G, Durst RC and Vowell CW, Using metrics in management decision making, IEEE Computer, 42-49, Sept, 1994. Google ScholarDigital Library
- 48.Symons, CR, Software Sizing & Estimating: Mark II Function point Analysis, John Wiley, 1991. Google ScholarDigital Library
- 49.TRACS (Transport Reliability Assessment & Calculation System): Overview, DELLA project E20262, http://www.agena.co.uk/tracs/index.html, 1999Google Scholar
- 50.Vineke P, Multicriteria Decision Aid, J Wiley, New York, 1992.Google Scholar
- 51.Yang JB and Singh MG, An evidential reasoning approach for multiple attribute decision making with uncertainty, IEEE Transactions Systems, Man, and Cybernetics, 24, 1-18, 1994.Google ScholarCross Ref
- 52.Zuse H, Software Complexity: Measures and Methods, De Gruyter. Berlin, 1991 Google ScholarDigital Library
Index Terms
- Software metrics: roadmap
Recommendations
Detection of Software Anomalies Using Object-oriented Metrics
ICEIS 2014: Proceedings of the 16th International Conference on Enterprise Information Systems - Volume 2The development of quality software has always been the aim of many studies in past years, in which the
focus was on seeking for better software production with high effectiveness and quality. In order to evaluate software quality, software metrics were ...
A Methodology For Risk Assessment Of Functional Specification Of Software Systems Using Colored Petri Nets
METRICS '97: Proceedings of the 4th International Symposium on Software MetricsThe paper presents a methodology for risk assessment in complex real time software systems at the early stages of development, namely the analysis/design phase. A heuristic risk assessment technique is described based on colored Petri net (CPN) models. ...
A Bayesian network approach to assist on the interpretation of software metrics
SAC '15: Proceedings of the 30th Annual ACM Symposium on Applied ComputingDespite the quantity of software metrics that has been proposed, their adoption and application by practitioners has been limited. A challenge to their use is to interpret them to perform assessments and predictions. The existing approaches to assist ...
Comments