[Title Page] [TOC] [Prev] [Next] [End]

13 References


[BERGE]

Berge, C., Graphs and Hypergraphs, North-Holland, 1973.

[BERTOLINO]

Bertolino, A. and L. Strigini, "On the Use of Testability Measures for Dependability Assessment," IEEE Transactions on Software Engineering, February 1996.

[BORGER]

Borger, D., "Supporting Process Improvement With McCabe Tools," Proceedings of the 1995 McCabe Users Group Conference, May 1995.

[BOYD]

Boyd, D., "Application of the McCabe Metric in Evolutionary Prototyping," Proceedings of the 1995 McCabe Users Group Conference, May 1995.

[BRILLIANT]

Brilliant, S. and J. Knight and N. Leveson, "The Consistent Comparison Problem in N-Version Software," ACM Software Engineering Notes, January 1987.

[CALDIERA]

Caldiera, G. and V. Basili, "Identifying and Qualifying Reusable SW Components," IEEE Computer, February 1991.

[CARVER]

Carver, D., "Producing Maintainable Software," Computers and Industrial Engineering, April 1987.

[CHIDAMBER]

Chidamber, S. and C. Kemerer, ``Towards a Metrics Suite for Object Oriented Design,'' Proceedings of OOPSLA, July 1991.

[COLEMAN]

Coleman, D. and D. Ash and B. Lowther and P. Oman, "Using Metrics to Evaluate Software System Maintainability," IEEE Computer, August 1994.

[DAHL]

Dahl, O. and E. Dijkstra and C. Hoare, Structured Programming, Academic Press, 1973.

[FEGHALI]

Feghali, I. and A. Watson, "Clarification Concerning Modularization and McCabe's Cyclomatic Complexity," Communications of the ACM, April 1994.

[FIRESMITH]

Firesmith, D., "Testing Object-Oriented Software," Software Engineering Strategies, November/December 1993.

[GEORGE]

George, P., "Proving Design Integrity," Proceedings of the 1993 McCabe Users Group Conference, April 1993.

[GIBSON]

Gibson, V. and J. Senn, "System Structure and Software Maintenance Performance," Communications of the ACM, March 1989.

[GILL]

Gill, G. and C. Kemerer, "Cyclomatic Complexity Density and Software Maintenance Productivity," IEEE Transactions on Software Engineering, December 1991.

[HANSON]

Hanson, D., "Printing Common Words," Communications of the ACM, July 1987.

[HEIMANN]

Heimann, D., "Complexity and Defects in Software-A CASE Study," Proceedings of the 1994 McCabe Users Group Conference, May 1994.

[HENRY]

Henry, S. and D. Kafura and K. Harris, "On the Relationships Among Three Software Metrics," 1981 ACM Workshop/Symposium on Measurement and Evaluation of Software Quality, March 1981.

[HETZEL]

Hetzel, W., The Complete Guide to Software Testing, QED Information Sciences, 1984.

[HOPCROFT]

Hopcroft, J. and J. Ullman, Introduction to Automata Theory, Languages, and Computation, Addison-Wesley, 1979.

[JONES]

Jones, C., Applied Software Measurement, McGraw-Hill, 1991.

[KAFURA]

Kafura, D. and G. Reddy, "The Use of Software Complexity Metrics in Software Maintenance," IEEE Transactions on Software Engineering, March 1987.

[KERNIGHAN]

Kernighan, B. and P. Plauger, The Elements of Programming Style, McGraw-Hill, 1974.

[KNUTH]

Knuth, D., "An Empirical Study of FORTRAN Programs," Software Practice and Experience, April-June 1971.

[KOSHGOFTAAR]

Koshgoftaar, T. and E. Allen and K. Kalaichelvan and N. Goel, "Early Quality Prediction: A Case Study in Telecommunications," IEEE Software, January 1996.

[LEVESON]

Leveson, N., SAFEWARE: System Safety and Computers, Addison-Wesley, 1995.

[MCCABE1]

McCabe, T., "A Complexity Measure," IEEE Transactions on Software Engineering, December 1976.

[MCCABE2]

McCabe T. and C. Butler, "Design Complexity Measurement and Testing," Communications of the ACM, December 1989.

[MCCABE3]

McCabe, T. and L. Dreyer and A. Dunn and A. Watson, "Testing an Object-Oriented Application," Journal of the Quality Assurance Institute, October 1994.

[MCCABE4]

McCabe, T. and A. Watson, "Combining Comprehension and Testing in Object-Oriented Development," Object Magazine, March-April 1994.

[MCCABE5]

McCabe, T. and A. Watson, "Software Complexity," CrossTalk: The Journal of Defense Software Engineering December 1994.

[MCCABE6]

McCabe, T., "Cyclomatic Complexity and the Year 2000," IEEE Software, May 1996.

[MILLER]

Miller, G., ``The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information,'' The Psychological Review, March 1956.

[MOSEMANN]

Mosemann, L., "Metrics Are Meaningful," CrossTalk: The Journal of Defense Software Engineering, August 1992.

[MUSA]

Musa, J. and A. Ackerman, "Quantifying Software Validation: When to Stop Testing?," IEEE Software, May 1989.

[MYERS1]

Myers, G., "An Extension to the Cyclomatic Measure of Program Complexity," SIGPLAN Notices, October 1977.

[MYERS2]

Myers, G., The Art of Software Testing, Wiley, 1989.

[NBS99]

NBS Special Publication 500-99, T. McCabe, "Structured Testing: A Software Testing Methodology Using the Cyclomatic Complexity Metric," U.S. Department of Commerce/National Bureau of Standards (U.S.), December 1982.

[NIST234]

NIST Special Publication 500-234, D. Wallace and L. Ippolito and B. Cuthill, ``Reference Information for the Software Verification and Validation Process,'' U.S. Department of Commerce/National Institute of Standards and Technology, April 1996.

[NIST5737]

NISTIR 5737, J. Poole, "A Method to Determine a Basis Set of Paths to Perform Program Testing," U.S. Department of Commerce/National Institute of Standards and Technology, November 1995.

[PARNAS]

Parnas, D., "On Criteria to be used in Decomposing Systems into Modules," Communications of the ACM, April 1972.

[PRESSMAN]

Pressman, R., Software Engineering: A Practitioner's Approach, McGraw-Hill, 1992.

[ROBERTS]

Roberts, B., "Using the McCabe Tools on Real-Time Embedded Computer Software," Proceedings of the 1994 McCabe Users Group Conference, May 1994.

[SCHNEIDEWIND1]

Schneidewind, N. and H. Hoffmann, "An Experiment in Software Error Data Collection and Analysis," IEEE Transactions on Software Engineering, May 1979.

[SCHNEIDEWIND2]

Schneidewind, N., "Methodology For Validating Software Metrics," IEEE Transactions on Software Engineering, May 1992.

[SCHULTZ-JONES]

Schultz-Jones, T., "Reverse Engineering With Forward Engineering Tools," Proceedings of the 1995 McCabe Users Group Conference, May 1995.

[SHEPPARD]

Sheppard, S. and E. Kruesi, "The Effects of the Symbology and Spatial Arrangement of Software Specifications in a Coding Task," Technical Report TR-81-388200-3, General Electric Company, 1981.

[VENTRESS]

Ventress, A., "Bailey's Multiplatform Implementation," Proceedings of the 1995 McCabe User Group Conference, May 1995.

[VOAS]

Voas, J. and K. Miller, "Software Testability: The New Verification," IEEE Software, May 1995.

[WALSH]

Walsh, T., "A Software Reliability Study Using a Complexity Measure," AFIPS Conference Proceedings, AFIPS Press, 1979.

[WARD]

Ward, W., "Software Defect Prevention Using McCabe's Complexity Metric," Hewlett-Packard Journal, April 1989.

[WATSON1]

Watson, A., "Incremental Reengineering: Keeping Control of Software," CrossTalk: The Journal of Defense Software Engineering, January 1994.

[WATSON2]

Watson, A., "Why Basis Path Testing?," McCabe & Associates Outlook, Winter 1994-1995.

[WATSON3]

Watson, A., "McCabe Complexity in Software Development," Systems Development Management 34-40-35, Auerbach, 1995.

[WATSON4]

Watson, A., "Error Detection with Basis Path Testing," McCabe & Associates Outlook, Winter 1995-1996.

[WATSON5]

Watson, A., Structured Testing: Analysis and Extensions, Ph.D. dissertation, Princeton University, in preparation.

[YOURDON]

Yourdon, E. and L. Constantine, Structured Design, Yourdon Press, 1978.

[ZUSE]

Zuse, H., Software Complexity: Measures and Methods, de Gruyter, 1990.



[Title Page] [TOC] [Prev] [Next] [End]