ACM Home Page
Please provide us with feedback. Feedback
Real-time complexity metric tools for visualAge smalltalk and C++
Full text PdfPdf (150 KB)
Source IBM Centre for Advanced Studies Conference archive
Proceedings of the 1996 conference of the Centre for Advanced Studies on Collaborative research table of contents
Toronto, Ontario, Canada
Page: 3  
Year of Publication: 1996
Authors
Subroto Bhattacharya  IBM North American Foundry, 3039 Cornwallis Road, RTP, NC
Stephen G. Graham  IBM North American Foundry, 3039 Cornwallis Road, RTP, NC
Sponsors
CRSNG : Natural Sci and EngRch Council of Canada
IBM Canada : IBM Canada
NRC : National Research Council - Canada
Publisher
IBM Press 
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 33,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  

ABSTRACT

"Anything that one cannot measure cannot be controlled." Software metrics provide insight into the quality of software, informing the developers about the status of a project. Both what to measure and when to inform the developer of changes in code quality are important factors in a software metrics tool.Our work describes metrics that measure some aspects of software complexity. Complexities of a system arise from size, from the relationships between parts and between a part and the whole, and from changes or evolution. The metrics described in this paper concentrate on measuring complexities due to size and relationships. The work on Smalltalk contains seven metrics; on C++, eight. Differences are due to idiosyncrasies of the languages.We believe the best time to inform the developer of changes in code quality is at the time source code is edited. Our tools provide real-time metric feedback on the complexity of methods (Smalltalk or C++) whenever methods are edited. Changes in code quality are immediately presented to the developer, encouraging him or her to take notice of increased code complexity and to rework the method to reduce that complexity. The tools present code quality information unobtrusively, and recommend how to proceed.This paper describes a body of method complexity metrics and tools that communicate to software developers.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
{1} Nicolis, G., and Ilya Prigogine. "Exploring Complexity". W.H. Freeman and Company, New York, 1989.
 
2
 
3
 
4
 
5
{5} Bhattacharya, Subroto. "Complexity metrics for C++ systems". White paper, North American Object Foundry, Cross Industry solutions, 1995.
 
6
{6} Ishikawa, Kaoru. "Guide to Quality Control". Asian Productivity Organization, 1982.
 
7
 
8
 
9
{9} McCabe, T.J. "A complexity measure". IEEE Transaction Software Eng. 2(4), 1976.
 
10
 
11
{11} Womack, J.P., D.T. Jones, and D. Roos. "The Machine That Changed The World". HarperPerennial, New York, 1991.
 
12
{12} Lewis, J. and S. Henry. "A methodology for integrating maintainability using software metrics". Procs. Conf. on Software Maintenance, Miami, October 16-19, 1989, IEEE, Piscataway, NJ.
 
13
 
14
{14} "VisualAge C++ for OS/2 documentation". IBM, May 1995.
 
15
{15} "Viceroy for IBM Smalltalk User's guide". IBM, May 1995.
 
16
{16} Masini, G., A. Napoli, D. Colnet, D. Leonard, and K. Tombre. "Object oriented languages". Academic Press, 1991.
 
17
{17} Joyner, I. "C++?? -- A Critique of C++". Unisys - ACUS, Australia.

Collaborative Colleagues:
Subroto Bhattacharya: colleagues
Stephen G. Graham: colleagues

Peer to Peer - Readers of this Article have also read: