Emerson, T. J., "A Discriminant Metric for Module Cohesion," 7th International Conference on Software Engineering, March 1984, pp 294303.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....and its cohesion as depicted in a slice profile [28] The insights gained from this earlier work were instrumental in developing the data slice model of cohesion and cohesion measures presented here. Other researchers have also examined the problem of measuring cohesion including Emerson [8] [9], Lakhotia [20] Troy and Zweben [34] and Selby and Basili [32] A. Emerson s work Emerson bases his cohesion measure on a control flow graph representation of a module [8] 9] The graph con tains a node for each statement in the module that contains a variable. After construction of the ....

....measures presented here. Other researchers have also examined the problem of measuring cohesion including Emerson [8] 9] Lakhotia [20] Troy and Zweben [34] and Selby and Basili [32] A. Emerson s work Emerson bases his cohesion measure on a control flow graph representation of a module [8] [9]. The graph con tains a node for each statement in the module that contains a variable. After construction of the graph, a reference set is constructed for each variable in the module which in dicates the nodes in the control flow graph that reference that variable. A flow subgraph, R , is ....

[Article contains additional citation context not shown here]

T.J. Emerson, "A discriminant metric for module cohesion," in Prom 7th Int. Conf. Software Eng. (ICSE-7), pp. 294-303, 1984.

....controlled experiment conducted to answer this question. The above questions are important since Stevens et al. s cohesion relations are paraphrased in several, if not most, software engineering textbooks [10, 12, 20, 21] There have also been proposals for source code based measures for cohesion [1, 3, 5, 11, 15]. These proposals implicitly or explicitly map their measures of cohesion to the cohesion levels proposed by Stevens et al. although such mappings have not been validated. A positive answer to the questions being investigated would have important ramifications towards the development and ....

.... a measure for cohesion by simply translating into logic the rules of cohesion proposed by Stevens et al. 11, 15] Since such a translation, to the extent possible, preserves the intent of the original rules, our measure could be treated as a reference measure for comparing other proposed measures [1, 3, 5, 17, 18]. This experiment is a step in that direction. In our experiment fifteen subjects (graduate student programmers) were trained on the concepts of cohesion and were then asked to classify stimulus materials (four programs) The data collected was subjected to various analyses. A nominal statistical ....

Thomas J. Emerson. A discriminant metric for module cohesion. In Proceedings of the 7th International Conference on Software Engineering, March 1984.

....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 flow graph model (Emerson, 1984). Flow subgraphs are generated for each variable referenced in a module. The precise cohesion value depends upon the ratio of the size and cyclomatic complexity of the subgraphs to the size of the complete flowgraph. Unfortunately, multiplying the reference set size by the cyclomatic complexity ....

Emerson, T. (1984) `A discriminant metric for module cohesion', in Proceedings of the 7th International Conference on Software Engineering, IEEE Computer Society Press, Los Alamitos CA, pp.

.... the objectoriented paradigm as being the silver bullet for solving the software crisis [15, 16, 19] Claims made about the advantages of the object oriented paradigm are based primarily on opinions or anecdotes rather than on rigorous and quantitative studies and metrics to support the claims [9, 17]. Software metrics have been proposed for both the procedural and the object oriented paradigms to measure various attributes like software quality, programmer productivity, and program complexity [3, 5, 7, 9, 17, 20, 19, 24] Among these, software complexity has gained special focus. Module ....

.... anecdotes rather than on rigorous and quantitative studies and metrics to support the claims [9, 17] Software metrics have been proposed for both the procedural and the object oriented paradigms to measure various attributes like software quality, programmer productivity, and program complexity [3, 5, 7, 9, 17, 20, 19, 24]. Among these, software complexity has gained special focus. Module independence is argued to be the key to reducing complexity and hence improving the quality and reliability of software [8, 22, 25, 29] In an attempt to produce more reliable and maintainable software, researchers have measured ....

[Article contains additional citation context not shown here]

T. J. Emerson. A discriminant metric for module cohesion. Proceedings 7th Int. Conf. on Software Engineering (ICSE-7), pages 294--303, 1984.

....1, 2, 3, 4, 5, 6, 7, 9, 10, 12, and 13. In [14] it is shown how slice profiles visually indicate the cohesion level of a module. In order to do this more effectively, slices are computed on the set of variables which are outputs from the module. Also slices are restricted to what Emerson [3] calls VRES or variable referent executable statements. These are all statements which reference a variable. Note that when slices are restricted to VRES, they are not executable. This is not in agreement with Weiser s original definition. For the remainder of this paper, slice profiles will ....

T. J. Emerson. A discriminant metric for module cohesion. In Proc. 7th International Conference on Software Engineering, pages 294--303, 1984.

....and scetion 5 the actual experiment. We draw conclusions in section 6, and present prospects for future work in section 7. 2. Software metrics There are currently many different metrics for assessing software. Metrics may focus on lines of code, complexity [10, 11] volume[6] or cohesion [2, 3] to name a few. Among the many metrics (and their variants) that exist, the McCabe and Halstead metrics are probably the most widely known, frequently appearing in introductory material on the subject. More current and complete coverage of this area appear in work such as [12] Traditionally, ....

Emerson, T. J., "A Discriminant Metric for Module Cohesion," Proc. 7th International Conference on Software Engineering, Los Alamitos, California, IEEE Computer Society, 1984, pp. 294-303.

....a module and its cohesion as depicted in a slice profile [26] The insights gained from this earlier work were instrumental in developing the data slice model of cohesion and cohesion measures presented here. Other researchers have also examined the problem of measuring cohesion including Emerson [7, 8], Lakhotia [18] Troy and Zweben [32] and Selby and Basili [30] success passwd address 3 3 3 procedure LookUp2(A: Table; Size: integer; key: keytype; 1 1 1 var success: boolean; 1 1 var passwd: integer; 1 1 var address: string) begin 2 2 2 i : 1; 2 2 2 success: false; 3 3 3 while not ....

....value mod 10; 2 2 small : false; end end; WFC = 35 42 = 83 A = 15 2 20 3 42 5 = 43 SFC = 0 42 = 0:0 Figure 9: A table lookup procedure arbitrarily composed with a decode procedure. 6. 1 Emerson s work Emerson bases his cohesion measure on a control flow graph representation of a module [7, 8]. The graph contains a node for each statement in the module that contains a variable. After construction of the graph, a reference set is constructed for each variable in the module which indicates the nodes in the control flow graph that reference that variable. A flow subgraph, R , is ....

[Article contains additional citation context not shown here]

T. J. Emerson. A discriminant metric for module cohesion. Proc. 7th Int. Conf. on Software Engineering (ICSE-7), pages 294--303, 1984.

....an interpretation of the informal definitions provided by Constantine and Yourdon. Several attempts have been made to make this subjective concept more precise. These include the suggested use of a decision tree as proposed by Page Jones [11] and attempts to find quantitative cohesion metrics [7, 9]. The aim of this paper is to show that the degree of cohesiveness of a module can be seen by examining slices [13 15] generated from the output variables of the module. In section 2, we will discuss cohesion and provide a simplification of the metric based on examining the relationships among the ....

....temporal, logical and coincidental. In practice, this degree of discrimination is not necessary. For the purposes of this study, we regrouped the seven categories into four levels of cohesion based on similarities seen when using processing element flow graphs [12] Others, e.g. Emerson [7] and Card [2] have used three levels of discrimination in their work. Nodes in a processing element flow graph (PFG) represent the processing elements within a module. Solid edges indicate data flow relationships among the processing elements. Control relationships among the elements are not ....

[Article contains additional citation context not shown here]

T. J. Emerson, A discriminant metric for module cohesion, Proceedings of the 7th international conference on software engineering, Chicago, Il., 1984, 294-303.

....of this, several researchers have attempted to make this concept more tangible. These include the suggested use of a decision tree as proposed by Page Jones [21] relating the cohesiveness of a module to its program dependence graph [13] and earlier attempts to find quantitative cohesion metrics [4, 14]. In this paper, we will build on some of this earlier work, particularly that of Longworth s. Longworth [14] investigated several slice based metrics which were originally proposed by Weiser and found that several of them appear to be related to cohesion. However, he encountered some problems for ....

....not related to the cohesion of the module. Thus, we eliminate the consideration of these statements by restricting our slices to those executable statements and expressions which reference at least one variable. These statements have been called variable referent executable statements (VRES) [4]. Figure 2 shows an example slice profile based on VRES. When computing the metrics, the assumption is that a simple statement, e.g. an assignment statement, is counted as one statement and each variablereferent executable expression, e.g. a conditional expression in an if statement is counted ....

T. J. Emerson. A discriminant metric for module cohesion. In Proc. 7th International Conference on Software Engineering, pages 294--303, 1984.

....and its cohesion as depicted in a slice profile [28] The insights gained from this earlier work were instrumental in developing the data slice model of cohesion and cohesion measures presented here. Other researchers have also examined the problem of measuring cohesion including Emerson [8] [9], Lakhotia [20] Troy and Zweben [34] and Selby and Basili [32] A. Emerson s work Emerson bases his cohesion measure on a control flow graph representation of a module [8] 9] The graph contains a node for each statement in the module that contains a variable. After construction of the ....

....measures presented here. Other researchers have also examined the problem of measuring cohesion including Emerson [8] 9] Lakhotia [20] Troy and Zweben [34] and Selby and Basili [32] A. Emerson s work Emerson bases his cohesion measure on a control flow graph representation of a module [8] [9]. The graph contains a node for each statement in the module that contains a variable. After construction of the graph, a reference set is constructed for each variable in the module which indicates the nodes in the control flow graph that reference that variable. A flow subgraph, R , is computed ....

[Article contains additional citation context not shown here]

T. J. Emerson, "A discriminant metric for module cohesion," in Proc. 7th Int. Conf. Software Eng. (ICSE-7), pp. 294--303, 1984.

....component of this work in other works must be obtained from the IEEE. the measurement 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 ....

T.J. Emerson. A discriminant metric for module cohesion. Proc. 7th Int. Conf. Software Eng. (ICSE-7), pages 294--303, 1984.

No context found.

Emerson, T. J., "A Discriminant Metric for Module Cohesion," 7th International Conference on Software Engineering, March 1984, pp 294303.

No context found.

Emerson, T.J., "A Discriminant Metric for Module Cohesion", Proceedings of the Seventh International Conference on Software Engineering, pp.294--303, 1984. -

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