User Tools

Site Tools


towards_a_unified_source_code_measurement_framework_supporting_multiple_programming_languages

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
towards_a_unified_source_code_measurement_framework_supporting_multiple_programming_languages [2014/02/04 13:54]
yann
towards_a_unified_source_code_measurement_framework_supporting_multiple_programming_languages [2017/09/06 01:54] (current)
Line 20: Line 20:
 The paper then describes a tool, [[http://​www.unicoen.net/​|UNICOEN]],​ that can parse components in various programming languages and generate UCM models. Using UCM, UNICOEN, and a study of some major metrics, focusing "on size and complexity because they are the most important measurements"​ (McCabe, Halstead'​s,​ CK...), the paper shows the metrics values can be computed on components in Java and JavaScript. The paper then describes a tool, [[http://​www.unicoen.net/​|UNICOEN]],​ that can parse components in various programming languages and generate UCM models. Using UCM, UNICOEN, and a study of some major metrics, focusing "on size and complexity because they are the most important measurements"​ (McCabe, Halstead'​s,​ CK...), the paper shows the metrics values can be computed on components in Java and JavaScript.
  
-However, the paper does not raise the problem of dealing with the dependencies among heterogeneous components, i.e., components written in different programming languages.+The paper does not raise the problem of dealing with the dependencies among heterogeneous components, i.e., components written in different programming languages. Also, it faces the same issues as other works: how to "​provide an easy way to measure a metric",​ "to evaluate the metrics of software written in more than one programming language",​ and to "use the same metric definition standard"​. It solves these issues through the UCM and UNICOEN, as we did with [[PADL]] and its various parsers. Now, the paper does not say, for example, if each UCO (unified code objects, our constituents) keep track of a line start and end, although they are map to statements. It does not consider the presence of "​ghosts",​ i.e., UCO known only be references but not analysed. Finally, it brushes the problem of consistency of the analysis and metric computations for different programming languages, which would be a very nice follow-up for this paper.
towards_a_unified_source_code_measurement_framework_supporting_multiple_programming_languages.1391522059.txt.gz ยท Last modified: 2017/09/06 01:54 (external edit)