J. M. Bieman and B.-K. Kang. Cohesion and reuse in an object-oriented system. In Proc. Symp. Software Reusability, pages 259--262, April 1995.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....based on behavioral compatibility, the implementation inheritance can lead to programs that are hard to maintain and extend. Thus, it is common that the use of implementation inheritance is discouraged, and delegation is suggested as an alternative mechanism to achieve the desired codereuse[30 ] 5.2 Principal Component Analysis In order to cope with the problems in the existing cohesion measures, we proposed a new cohesion measure CBMC based on the new notion of special methods and the new cohesion criterion of member connectivity. We performed Principal Component ....

....point the Mahalanobis Distance from the sample space centroid. Outliers are data points with a large distance from the centroid and are excluded from the analysis. The T max procedure based on the Mahalanobis distance is used to detect outliers. See [24] for more details on outlier analysis. 3. Perform principal component analysis. If a group of variables in a data set are strongly correlated, these variables are likely to measure the same underlying dimension(i.e. class property) of the object to be measured. PCA is a standard technique to identify relations between the variables in ....

[Article contains additional citation context not shown here]

J. M. Bieman and B. -K. Kang, `Cohesion and Reuse in an Object-Oriented System', Proceedings of ACM Symposium on SoftwareReusability, 1995, pp. 259-262.

....accurate quality prediction models. In addition, the success and widespread diffusion of object oriented software systems have drawn a good deal of interest towards the study of the attributes of objectoriented software systems. A number of studies have been published (see for instance [19] [8], 28] and [5] 6] for an extensive survey) These studies generally deal with the proposal of new measures or the reuse of existing ones in the framework of object oriented software code. Our study goes one step in the direction of object orientation, at the high level design stage, in that it ....

....This stems in part from the definition of LCOM where the measure is set to 0 when the number of class pairs sharing variable instances is larger than that of the ones not sharing any instances. Several other measures have been proposed in the literature for object oriented cohesion, e.g. see [8], 28] Due to space constraints, no thorough comparison can be made here. The interested reader is referred to [6] where an extensive survey and classification have been proposed. From a general perspective, these measures differ according to their underlying experimental hypotheses and ....

J.M. Bieman and B.-K. Kang, "Cohesion and Reuse in an ObjectOriented System," Proc. ACM Symp. Software Reusability (SSR'94), pp. 259-262, 1995.

....follow universal laws and quality models must be developed locally, wherever needed. Keywords Metrics, measurement, empirical validation, coupling, cohesion, inheritance, object oriented. 1 Introduction A large number of object oriented (OO) measures have been proposed in the literature ( 5] [11], 13] 14] 19] 22] 24] 25] 26] 27] A particular emphasis has been given to the measurement of design artifacts, in order to help assess quality early on during the development process. Such measures are aimed at providing ways of assessing the quality of software, for example, in ....

....which directly uses attribute a. Two methods are called connected, if they directly or indirectly use common attributes. TCC is defined as the percentage of pairs of public methods of the class which are connected, i.e. pairs of methods which directly or indirectly use common attributes. [11] LCC Loose class cohesion. Same as TCC, except that this measure also considers pairs of indirectly connected methods. If there are methods m 1 , m n , such that m i and m i 1 are connected for i=1, n 1, then m 1 and m n are indirectly connected. Measure LCC is the percentage of pairs ....

[Article contains additional citation context not shown here]

J.M. Bieman, B.-K. Kang, "Cohesion and Reuse in an Object-Oriented System", in Proc. ACM Symp. Software Reusability (SSR'94), 259-262, 1995.

.... Many measures have been proposed in the literature to capture the structural quality of object oriented (OO) code and design (Chidamber and Kemerer, 1991; Chidamber and Kemerer, 1994; Li and Henry, 1993; Lee et al. 1995; Briand et al. 1997b; Henderson Sellers, 1996; Hitz and Montazeri, 1995; Bieman and Kang, 1995; Lake and Cook, 1994; Lorenz and Kidd, 1994; Tegarden et al. 1992) Such measures are aimed at providing ways of assessing the quality of software, for example, in the context of large scale software acquisition (Mayrand and Coallier, 1996) Such an assessment of design quality is objective, and ....

....which directly uses attribute a. Two methods are called connected, if they directly or indirectly use common attributes. TCC is defined as the percentage of pairs of public methods of the class which are connected, i.e. pairs of methods which directly or indirectly use common attributes. (Bieman and Kang, 1995) LCC (loose class cohesion) Same as TCC, except that this measure also considers pairs of indirectly connected methods. If there are methods m 1 , m n , such that m i and m i 1 are connected for i=1, n 1, then m 1 and m n are indirectly connected. Measure LCC is the percentage of ....

[Article contains additional citation context not shown here]

Bieman, J., Kang, B., 1995. Cohesion and Reuse in an Object-Oriented System. Proc. ACM Symp. Software Reusability (SSR'94), 259-262.

....based on a study at Texas Instruments, Brooks, 1993] has reported that McCabe cyclomatic complexity appeared to be an inadequate metric for use in software development based on OO technology. To address this issue, OO metrics have recently been proposed in the literature [Abreu Carapua, 1994; Bieman Kang, 1995; Chidamber Kemerer, 1994] However, with a few exceptions [Briand et.al. 1994] and [Li Henry, 1993] most of them have not undergone an experimental validation. The work described in this paper is an additional step toward an experimental validation of the OO metric suite defined in ....

J. M. Bieman and B.-K. Kang (1995). "Cohesion and Reuse in an Object-Oriented System". In Proc. of the ACM SIGSOFT Symposium on Software Reusability, Seattle WA. pages 259--262.

....possible quality or flexibility related problems of the system Object oriented software metrics are expected to support these tasks, but in practice they have only been applied with limited success. Though a vast amount of metrics have been defined in the past (see for example [CK94] LH93] or [BK95] there is little experience in how to actually use metrics for model capture or problem detection. To improve this situation, this paper describes a practical approach to use metrics in order to help understanding the basic structure and workings of legacy system and some experiences that were ....

J. M. Bieman and B. K. Kang. Cohesion and reuse in an object-oriented system. Proc. ACM Symposium on Software Reusability, apr 1995.

....there is no systematic way to look at a related part of the AST; in general, such non local accesses must be done using standard stack or global variables. However, in practice, the compromises made in this interface have not proven a barrier to users; a range of applications have been reported [2, 4, 5, 31, 21, 15, 18] 5 Future Work: retargetable debuggers Our current research is focused on a di#erent task: debugging programs. Specifically, we are interested in debugging domain specific languages. We briefly describe this research before concluding the paper. The software industry is under great pressure to ....

J. Bieman and B-K. Kang. Cohesion and reuse in an object oriented system. In Proceedings Proc. Symposium on Software Reusability (SSR'95), 1995.

....of the cohesion of classes in an object oriented system. In short, our understanding of existing cohesion measures is not what it should be. Several authors have introduced different approaches and proposed measures to characterise cohesion in object oriented systems, e.g. CK91, CK94] HM95] [BK95], Hen96] LLWW95] BMB93, BMB94] Eder et al. define a framework aimed at providing qualitative criteria for cohesion; they also assign relative strengths to different levels of cohesion they identify within this framework [EKS94] However, neither this framework nor the different approaches ....

....are analysed, which includes theoretical validation of these measures. 4.1 Existing approaches to measure cohesion Eder et al. EKS94] propose a framework aimed at providing qualitative criteria for cohesion. Chidamber and Kemerer [CK91, CK94] Hitz and Montazeri [HM95] Bieman and Kang [BK95], Henderson Sellers [Hen96] Lee et al. LLWW95] and Briand et al. BMB93, BMB94] each propose different approaches to measure cohesion in object oriented or object based systems and define various cohesion measures accordingly. We discuss these frameworks and approaches in the following ....

[Article contains additional citation context not shown here]

J.M. Bieman, B.-K. Kang, "Cohesion and Reuse in an Object-Oriented System", in Proc. ACM Symp. Software Reusability (SSR'94), 259-262, 1995. ISERN-97-05 31

....and build accurate quality prediction models. In addition, the success and widespread diffusion of object oriented software systems have drawn a good deal of interest towards the study of the attributes of object oriented software systems. A number of studies have been published (see for instance [CK94, BK95, HM95] and [BDW96, 97] for an extensive survey) These studies generally deal with the proposal of new measures or the reuse of existing ones in the framework of object oriented software code. Our study goes one step in the direction of object orientation, at the high level design stage, in that it ....

....This stems in part from the definition of LCOM where the measure is set to 0 when the number of class pairs sharing variable instances is larger than that of the ones not sharing any instances. Several other measures have been proposed in the literature for object oriented cohesion (e.g. see [CK94, BK95, HM95]) Due to space constraints, no thorough comparison can be made here. The interested reader is referred to [BDW97] where an extensive survey and classification have been proposed. From a general perspective, these 21 measures differ according to their underlying experimental hypotheses and ....

J.M. Bieman, B.-K. Kang, "Cohesion and Reuse in an Object-Oriented System", in Proc. ACM Symp. Software Reusability (SSR'94), pp.259-262, 1995.

....Keywords: coupling, cohesion, inheritance, object oriented, metrics, measurement, empirical validation 1. 0 Introduction Many measures have been proposed in the literature to capture the structural quality of object oriented (OO) code and design [CK91, CK94, LH93, LLWW95, BDM97, Hen96, HM95, BK95, LC94, LK94, TSM92] Such measures are aimed at providing ways of assessing the quality of software, for example, in the context of large scale software acquisition [MC96] Such an assessment of design quality is objective, and the measurement can be automated. Once the necessary measurement ....

....method which directly uses attribute a. Two methods are called connected, if they directly or indirectly use common attributes. TCC is defined as the percentage of pairs of public methods of the class which are connected, i.e. pairs of methods which directly or indirectly use common attributes. BK95] LCC (loose class cohesion) Same as TCC, except that this measure also considers pairs of indirectly connected methods. If there are methods m 1 , m n , such that m and m i 1 are connected for i=1, n 1, then m 1 and m n are indirectly connected. Measure LCC is the percentage of pairs of ....

[Article contains additional citation context not shown here]

J.M. Bieman, B.-K. Kang, "Cohesion and Reuse in an Object-Oriented System", in Proc. ACM Symp. Software Reusability (SSR'94), 259-262, 1995.

....such as maintainability, reusability, and reliability. To test this hypothesis, a good measure of class cohesion is needed. We examine the problem of measuring class cohesion in object oriented systems written in Java. The research utilizes the class cohesion measure as proposed by Bieman and Kang [Bieman95]. The measure counts the proportion of method pairs in a class exhibiting connectedness through the use of one or more common instance variables of that class. For a measure to be valid, it must obey the requirements of measurement theory. The Bieman and Kang cohesion measure is shown to meet in ....

....context of procedural programs for some time. Object oriented cohesion is a concept still under development. The need to establish a firm basis for object oriented cohesion motivates the current research. 1. 2 Overview of Research This research applies the class cohesion measure of Bieman and Kang [Bieman95] to Java programs. Classes are measured as to their relative internal connectivity. The measure of cohesion is the proportion of visible method pairs in a class which exhibit connectivity through their communication with a common instance variable of the class, compared with the total number of ....

[Article contains additional citation context not shown here]

James Bieman, Byung-Kyoo Kang. "Cohesion and Reuse in an Object-Oriented System." Proceedings of the ACM Symposium Software Reusability (SSR'95), pp. 259-262, April 1995.

....follow universal laws and quality models must be developed locally, wherever needed. Keywords Metrics, measurement, empirical validation, coupling, cohesion, inheritance, object oriented. 1 Introduction A large number of object oriented (OO) measures have been proposed in the literature ( 4] [9], 11] 12] 18] 20] 22] 23] 24] 25] A particular emphasis has been given to the measurement of design artifacts, in order to help assess quality early on during the development process. Such measures are aimed at providing ways of assessing the quality of software, for example, in ....

....a method which directly uses attribute a. Two methods are called connected, if they directly or indirectly use common attributes. TCC is defined as the percentage of pairs of public methods of the class which are connected, i.e. pairs of methods which directly or indirectly use common attributes. [9] LCC Loose class cohesion. Same as TCC, except that this measure also considers pairs of indirectly connected methods. If there are methods m 1 , m n , such that m i and m i 1 are connected for i=1, n 1, then m 1 and m n are indirectly connected. Measure LCC is the percentage of pairs of ....

[Article contains additional citation context not shown here]

J.M. Bieman, B.-K. Kang, "Cohesion and Reuse in an Object-Oriented System", in Proc. ACM Symp. Software Reusability (SSR'94), 259-262, 1995.

....model our intuition about relative distances of a structure of classes from a particular pattern. We can then define ordinal, and eventually ratio, scale measures from such empirical relation systems. This is the approach that we took to develop measures of functional cohesion and class cohesion [7, 5]. Our hypothesis is that components that play roles in a small number of well defined architectural contexts will be easier to maintain, reuse, and test than components that play no role in these contexts or that play roles in many contexts. We are testing this hypothesis by examining commercial ....

....quantify properties of individual classes and their relationships to the rest of a system. Chidamber and Kemerer s suite of object oriented measures include only single class measures [17] Other researchers, including one of the authors, have developed cohesion measures for individual classes [5, 11, 31, 39]. Work on quantifying interclass properties (properties of collections of classes) includes Hitz and Montazeri s work to quantify coupling in object oriented systems [31] They classify individual dependencies between classes and between objects, and they propose an ordinal measure of the ....

J. Bieman and B.-K. Kang. Cohesion and reuse in an objectoriented system. Proc. ACM Symp. Software Reusability (SSR'95), pp. 259--262, April 1995.

....design representations. The basic approach in our restructuring framework can be applied to object oriented software. We plan to extend our work to the restructuring of object oriented software. We have already defined a model to represent object oriented programs and two class cohesion measures (Bieman and Kang, 1995). 8. RELATED WORK 8.1. Cohesion and Coupling Measurement Closely related work includes the development of cohesion and coupling measures, and restructuring methods based on design or code level analyses. Emerson s Cohesion Measurement. Emerson developed a cohesion measure in terms of a control ....

....in this paper is on procedural software. However, there is active work on developing cohesion and coupling measures for object oriented and object based software. Bieman and Kang define class cohesion measures based on dependencies between methods through their references to instance variables (Bieman and Kang, 1995). Chidamber and Kemerer define another class cohesion measure, lack of cohesion between methods (LCOM) which is also based on method interconnections through instance variable references (Chidamber and Kemerer, 1994) Hitz and Montazeri (1995) define coupling measures based on the distinction ....

Bieman, J. and Kang, B.-K. (1995) `Cohesion and reuse in an object-oriented system', SIGSOFT Software Engineering Notes, 20(5), 259--262.

....Threads: awe2 0.1 0.7237 0 10 0.7237 1 1 0 presto1.0 0.6071 0 10 0.6071 1 1 0 Others: RPC 0.1250 0 1 0.1250 0 1 0 MC 0.02 0.4694 0 8 0.4694 0 1 0 c suite 1.0 0.3333 0 5 0.3333 0 4 3.70 newmat 0.7222 0 9 0. 7222 1 1 0 attributes of object oriented systems including method and class cohesion [4, 2], method reuse through inheritance, and coupling through message passing. We also want to measure the redefinition of methods and instance variables by subclasses, since such redefinition can increase the difficulty of verification and testing [13] Measurements of these additional attributes ....

J.M. Bieman and B-K. Kang. Cohesion and reuse in an object-oriented system. Proc. ACM Symposium on Software Reusability (SSR'95), April, 1995, Seattle, Washington.

....bieman cs.colostate.edu, Fort Collins, CO 80523, USA. 970)491 7096, Fax: 970) 491 2466. Class cohesion measures for object oriented software have also been defined using a slice based approach, and by analyzing the connectivity between methods through common references to instance variables[1, 5, 6]. Method bodies are needed to apply these code level class cohesion measures. In this paper, we show that module cohesion can be objectively assessed using only design level information. We develop and compare design level cohesion measures using both the association based and slice based ....

.... : 0; sum1 : 0; begin if flag = 1 for i : 1 to n1 do sum1 : sum1 arr1[i] else end; for i : 1 to n2 do sum2 : sum2 arr2[i] sum2 : integer ) procedure Sum1 or Sum2 var i : integer; var sum1, e) arr1, arr2 : int array; n1, n2, flag : integer; b) n fib arr begin for i : 3 to n fib arr[1] : 1; fib arr[2] 2; i : integer; var asum : int array; var fib arr : int array; n : integer; Sum(n, fib arr, sum) end; fib arr[i] fib arr[i 1] fib arr[i 2] Sequential cohesion d i d d Sum d procedure Fibo Avg var avg : float ) avg : sum n; avg n arr sum Functional cohesion d ....

[Article contains additional citation context not shown here]

J. Bieman and B-K Kang. Cohesion and reuse in an object-oriented system. Proc. ACM Symp. Software Reusability. (SSR'94), pages 259--262, April 1995. Reprinted in ACM Software Engineering Notes, Aug. 1995.

....a design or an implementation. We are now implementing tools to generate IODG s from software designs and implementations, to graphically display IODG s, and to support the restructuring process. We have already developed class cohesion measures and measurement tools for object oriented software [3]. We also plan to evaluate the effects of restructuring on external quality attributes such as testability, reusability, reliability, and maintainability. ....

J. Bieman and B-K Kang. Cohesion and reuse in an object-oriented system. Proc. ACM Symp. Software Reusability. (SSR'94), pp. 259--262, April 1995. Reprinted in ACM Software Engineering Notes, Aug. 1995.

....form of cohesion, namely data cohesion, rather than functional cohesion [5] We examine two slice based approaches for measuring object oriented cohesion [19] One approach, by Ott and Gupta [9] is a direct extension of our work on functional cohesion. The other approach, by Bieman and Kang [1], evolved from Chidamber and Kemerer s measure of the lack of cohesion (LCOM) between methods [4] In both approaches, the class is the basic unit and the instance variables are the glue that connects the methods in a class. The difference in the approaches is in the granularity of the analysis. ....

....tokens, and 5 super glue. Hence, SDC(CSA(stack) 5 19 = 26 WDC(CSA(stack) 12 19 = 63 DA(CSA(stack) 7 Delta 2 5 Delta 3 19 Delta 3 = 51 6. 2 Class Cohesion Bieman and Kang treat the method and instance variable class components as the key class units that may or may not be connected [1]. Thus, if a slice includes a method, it includes the method as an indivisible unit. A method and an instance variable are related by the way that an instance variable is used by the method. Two methods are related (connected) through instance variable(s) if both methods use the instance ....

[Article contains additional citation context not shown here]

J. Bieman and B-K Kang. Cohesion and reuse in an object-oriented system. In Proc. ACM Symposium on Software Reusability (SSR'95), pages 259--262, April 1995.

....= 5 19 = 26 WDC(CSA(stack) 12 19 = 63 DA(CSA(stack) 7 Delta 2 5 Delta 3 19 Delta 3 = 51 3 Bieman and Kang s approach. Jim Bieman and Byung Kyoo (Benjamin) Kang treat the method and instance variable class components as the key class units that may or may not be connected [1]. A method and an instance variable are related by the way that an instance variable is used by the method. Two methods are related (connected) through instance variable(s) if both methods use the instance variable(s) Using this orientation, class cohesion can be measured by the relative ....

....class. 3.1 Measuring Class Cohesion The MIV relation model includes the information to define class cohesion. In our model, a method is represented as a set of instance variables directly or indirectly used by the method. A more detailed derivation of our class cohesion measures are contained in [1]. Here we summarize the derivation. An instance variable is directly used by a method M if the instance variable appears as a data token in the method M . The instance variable may be defined in the same class as M or in an ancestor class of the class. A direct indirect call relation defines the ....

[Article contains additional citation context not shown here]

J.M. Bieman and B-K Kang. Cohesion and reuse in an object-oriented system. Proc. ACM Symposium on Software Reusability (SSR'95), pages 259--262, April 1995.

.... of module cohesion has been difficult to automate, and cohesion has not been effectively used as a software quality indicator [18] Existing techniques can measure or assess the cohesion of procedural code [5, 9, 2] structured design documents [15, 16] packages [13, 12, 3] and classes [4, 14, 1]. Our objective is to develop techniques to objectively measure cohesion in terms of information available from the detailed design of modules in procedural programs. More precisely, for each procedure we assume that a detailed design includes the specification of a procedure or function interface ....

....output slices. The computation of functional cohesion also requires code level information. Class cohesion measures for object oriented software have also been defined using a slice based approach, and by analyzing the connectivity between methods through common references to instance variables[1, 10, 11]. Method bodies are needed to apply these code level class cohesion measures. Cohesion is only one of many attributes that designers strive to improve. For example, designers also aim to reduce coupling. We need to be able to objectively measure such attributes in order to evaluate alternative ....

[Article contains additional citation context not shown here]

J. Bieman and B-K Kang. Cohesion and reuse in an object-oriented system. Proc. ACM Symp. Software Reusability. (SSR'95), pages 259--262, April 1995. Reprinted in ACM Software Engineering Notes, Aug. 1995.

No context found.

J. M. Bieman and B.-K. Kang. Cohesion and reuse in an object-oriented system. In Proc. Symp. Software Reusability, pages 259--262, April 1995.

No context found.

J.M. Bieman, B.K. Kang. Cohesion and Reuse in Object-Oriented Systems. Proceedings of the ACM Symposium on Software Reusability, April 1995.

No context found.

J.M. Bieman, B.K. Kang. Cohesion and Reuse in an Object-Oriented System. Proc. ACM Symposium on Software Reusability, April 1995.

No context found.

J. Bieman and B. Kang. Cohesion and reuse in an objectoriented system. In Proceedings ACM Symposium on Software Reusability, Apr. 1995.

No context found.

James M. Bieman and Byung-Kyoo Kang. Cohesion and reuse in an object-oriented system. In ACM SIGSOFT Symposium on Software Reusability, pages 259--262, 1995.

No context found.

J. M. Bieman and B.-K. Kang. Cohesion and Reuse in an Object-Oriented System. In ACM SIGSOFT Symposium on Software Reusability, pages 259--262, 1995.

No context found.

Prem Devanbu Bieman, J. and Kang, B.-K. 1995. Cohesion and reuse in an object oriented system. In Proceedings Proc. Symposium on Software Reusability (SSR'95) (1995).

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