| James M. Bieman and Josephine Xia Zhao. Reuse Through Inheritance: A Quantitative Study of C++ Software. In Proceedings of the Symposium on Software Reusability. ACM SIGSOFT, August 1995. Software Engineering Notes. |
.... together with two further inheritance based design metrics developed as part of the MOOPS project [17] 18] The results of our analysis (and that of other investigations) seem to support the thesis that inheritance is either used sparingly during the development process, or is used incorrectly [5][9] Use of inheritance does not seem to be delivering the benefits it promised, and it is not clear that systems using inheritance are easier to maintain than those that do not. In this paper, an analysis of the faults found in three of the five systems investigated showed very little ....
....and simplicity in favour of reuse. This would seem to imply a view that inheritance hinders the maintenance process. In Chidamber, Darcy and Kemerer [10] three commercial object oriented system are empirically investigated, and, again, none showed significant use of inheritance. Bieman and Zhao [5] describe a study of 19 C systems, containing 2,744 classes in total. They found that only 37 of these systems had a median class inheritance depth greater than 1; the GUI applications studied showed the highest mean inheritance depth (3.46) This was significantly smaller than the maximum ....
[Article contains additional citation context not shown here]
Bieman, J.M., and Zhao, J.X., "Reuse through inheritance: A quantitative study of C++ software", Proceedings of ACM Software Reusability Symposium, (SRS 94), 1994.
.... LW93, Kar95, GR95] On the other side, many examples of non object oriented reusable systems show that objects are neither necessary nor sufficient for software reuse [Tra95, Gri95] Unfortunately, only a few empirical studies about the impact of object orientation on software reuse were conducted [LHKS91, BZ95]. The assumptions are based more on intuition than on scientific experimental evidence. Our aim is to review the current trends in the area of software reuse[SN96] We shall be concerned with principles, as well as with methods for software reuse. After reviewing them in general, we shall ....
J. M. Bieman and J. X. Zhao. Reuse through inheritance: A quantitative study of C++ software. ACM SIGSOFT, Proc. of the Symposium on Software Reusability SSR'95, 20(special issue August):47--52, 1995.
....the average number of cycles elapsed between message sends. As this value increases, we expect the overall performance impact of the optimizations to decrease. Bieman and Zhao also used the first three of these metrics (and some additional ones) in their study of inheritance in C applications [Bieman Zhao 95] They utilized the metrics to assess the amount of code reuse through inheritance in large C programs; in contrast, we are interested in characterizing how the structure of the inheritance hierarchy affects the need for optimization. In previous work, we applied several metrics to measure the ....
James M. Bieman and Josephine Xia Zhao. Reuse Through Inheritance: A Quantitative Study of C++ Software. In Proceedings of the Symposium on Software Reusability. ACM SIGSOFT, August 1995. Software Engineering Notes.
....of how frequently message sends are used in the program. As this value increases, we expect the overall performance impact of the optimizations to decrease. Bieman and Zhao also used the first three of these metrics (and some additional ones) in their study of inheritance in C applications [Bieman Zhao 95] They utilized the metrics to assess the amount of code reuse through inheritance in large C programs; in contrast, we are interested in characterizing how the structure of the inheritance hierarchy affects the need for optimization. In previous work, we applied several metrics to measure the ....
JamesM. Bieman and JosephineXia Zhao. Reuse Through Inheritance: A Quantitative Study of C++ Software. In Proceedings of the Symposium on Software Reusability. ACM SIGSOFT, August 1995. Software Engineering Notes.
....achieved software quality characteristics are exactly due to the corresponding design options. One of the most important design options is the degree of incorporation of available library components. This is often referred as external reuse as opposed to internal reuse (reuse through inheritance) [8]. Reusable components tend to be better designed than ordinary program code, either because their conception is more careful, or because its repeated use brings out quickly any flaws in its design or implementation. Therefore the amount of reuse is expected to produce a positive impact on overall ....
J. M. Bieman; J. X. Zhao. "Reuse Through Inheritance: a Quantitative Study of C++ Software". In S. Samadzadeh and M. Zand (editors), Proc. of the ACM SIGSOFT Symposium on Software Reusability, Seattle, WA, April 28-30, 1995.
....[5] We are interested in quantifying the inheritance structure of entire inheritance hierarchies rather than individual classes. The mean and median of the measures for individual classes provides enough information to roughly characterize the use of inheritance in entire object oriented systems [4]. Such measures have been used to evaluate optimizing compilers [6] Measures that focus on properties of entire systems forests of inheritance trees should provide information that can better answer questions about the system as a whole. Reuse in object oriented systems can be measured ....
....Then, each component is not being averaged over many levels. We use three components as an approximation, in part, because of MGR = 1.5 MGR = 1.5 MGR = 1 MGR = 1 Figure 3. Example Mean Growth Rate (MGR) Calculations empirical evidence that inheritance hierarchies do not tend to have great depth [4]. Definition 6 The three average widths (TAW) of an inheritance tree or forest of trees is a 3 tuple, where each component is a real number that indicates the mean number of classes at each level of depth in one third of the tree: 13 A BDC=A3EFC=AHGI where AJB , A3E , and A3G are, ....
[Article contains additional citation context not shown here]
J.M. Bieman and J.X. Zhaox. Reuse through inheritance: A quantitative study of c++ software. Proc. ACM Software Reusability Symp. (SRS'94), pages 47-- 52, April 1995.
....methods is the often asserted claim that they lead to more reusable and adaptable systems. Measures of reuse and reusability are needed to evaluate these claims. Several relevant reuse abstractions, attributes, measures, and measurement tools are applicable to object oriented systems [3, 6, 8]. The measures and tools are based on both the inheritance and calling structure of a system. Inheritance and inheritance hierarchies are unique features of object oriented systems and should have measurable attributes. Properties of inheritance hierarchies, or inheritance clusters [34] are ....
J. Bieman and J. Zhao. Reuse through inheritance: A quantitative study of c++ software. Proc. ACM Symp. Software Reusability (SSR'95), pp. 47--52, April 1995.
....representation and DLC measurement. We generated the restructured program code by selecting a program slice or slices that correspond to one or more output components of each restructured IODG. 7.2. Applying the Restructuring Process The data for the case study was the JASMIN software system (Bieman and Zhao, 1995). JASMIN is a research tool that collects data concerning the use of inheritance in C software. JASMIN measures the depth of the inheritance, number of classes with without private sections, number of classes derived from classes with without private sections, and number of private, public, and ....
Bieman, J. and Zhao, J. X. (1995) `Reuse through inheritance: A quantitative study of C++ software', SIGSOFT Software Engineering Notes, 20(5), 47--52.
....[5] We are interested in quantifying the inheritance structure of entire inheritance hierarchies rather than individual classes. The mean and median of the measures for individual classes provides enough information to roughly characterize the use of inheritance in entire object oriented systems [4]. Such measures have been used to evaluate optimizing compilers [6] Measures that focus on properties of entire systems forests of inheritance trees should provide information that can better answer questions about the system as a whole. Reuse in object oriented systems can be measured ....
....over many levels. We use three components as an approximation, in part, because of MGR = 2 MGR = 2 MGR = 1.5 MGR = 1.5 MGR = 1 MGR = 1 MGR = 0.5 MGR = 0.5 Figure 3. Example Mean Growth Rate (MGR) Calculations empirical evidence that inheritance hierarchies do not tend to have great depth [4]. Definition 6 The three average widths (TAW) of an inheritance tree or forest of trees is a 3 tuple, where each component is a real number that indicates the mean number of classes at each level of depth in one third of the tree: TAW = w1; w2; w3) where w1, w2, and w3 are, respectively, the ....
[Article contains additional citation context not shown here]
J.M. Bieman and J.X. Zhaox. Reuse through inheritance: A quantitative study of c++ software. Proc. ACM Software Reusability Symp. (SRS'94), pages 47-- 52, April 1995. Reprinted in ACM Software Engineering Notes, August 1995.
No context found.
James M. Bieman and Josephine Xia Zhao. Reuse Through Inheritance: A Quantitative Study of C++ Software. In Proceedings of the Symposium on Software Reusability. ACM SIGSOFT, August 1995. Software Engineering Notes.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC