From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109fba,8c86ad0efdcc1266,start X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,8c86ad0efdcc1266,start X-Google-Attributes: gid103376,public From: zhuo911@cs.uidaho.edu (Jianqiang Zhuo) Subject: OO Relative Complexity Metric Date: 1997/02/22 Message-ID: <5elenl$h8h$1@newshound.csrv.uidaho.edu>#1/1 X-Deja-AN: 220544188 Distribution: world Content-Type: text/plain; charset=US-ASCII Organization: University of Idaho, Moscow, Idaho Mime-Version: 1.0 Newsgroups: comp.lang.c++,comp.lang.ada Date: 1997-02-22T00:00:00+00:00 List-Id: Here at the Idaho Software Engineering Test Lab we have created a modified relative complexity metric for OO code. Unlike traditional metric models, the modified relative complexity metric takes into consideration both class-level and procedural-level (e.g., functions and methods) complexity, and aggregates those complexities into a single value representing the complexity of an OO file, subsystem or test functionality. Initial tests with industrial code show that it is promising for both fault prediction and test resource allocation. But we need more data to validate it. Does anyone have any OO code or metrics that you can share with us? We would analyze your data and show you the results as well as the steps necessary to compute the new metrics. At a minimum, what we need are: a) class and method level complexity metrics for OO code b) an a priori analysis of that code; either fault data, complexity rank ordering, quality circle analysis, construction or maintenance effort, or similar measurement. Optionally, if you have C++ code and can share it with us, we'd be glad to compute the metrics and do the analyses. Please contact myself, Michael Zhuo (michael@silver.cs.uidaho.edu) or Dr. Paul Oman (oman@cs.uidaho.edu) if you think you have data that would work and you want to get it analyzed. Thanks, Michael Zhuo Software Engineering Test Lab University of Idaho.