Java Runtime Libraries Comparison: Difference between revisions

From Istlab
Jump to navigationJump to search
Content deleted Content added
Bkarak (talk | contribs)
New page: == General == '''Main Concept''': The main idea is to compare the three most complete implementation of the 1.6 Java Platform Specification JSR. The libraries will be compared in the term...
 
Bkarak (talk | contribs)
No edit summary
Line 12: Line 12:


Nice and proven, the problem with that, it is done before in various contexts.
Nice and proven, the problem with that, it is done before in various contexts.

=== Mathematical Approach (Vs Public Interface) ===

Maybe we can find (observing our data ofc) a mathematical equation or a theorem of some sort, that will describe certain relations between the metrics.

=== External Characteristics ===

* Micro-benchmarking (maybe in collections etc).
* Number of Bugs ('''update''': cannot find data for [http://java.sun.com/ OpenJDK]

=== Requirements Drives Quality ===

Examine if Requirements dictates quality or the design of code, since in our case we have a specification that guides the implementation.

* Clustering by public class + non-public dependencies

=== Threats of Validity ===

* The three systems are not directly comparable
** [http://java.sun.com/ OpenJDK] implements 1.6 JSR,
** [http://harmony.apache.org/ Jakarta Harmony] implements 1.6 JSR (beta)
** [http://www.gnu.org/software/classpath/ GNU Classpath] implements part of 1.5 so far (updated 9/9/2008)

Revision as of 11:36, 9 September 2008

General

Main Concept: The main idea is to compare the three most complete implementation of the 1.6 Java Platform Specification JSR. The libraries will be compared in the terms of software complexity metrics (CK suite and some others).

Participants: OpenJDK, GNU Classpath, Jakarta Harmony.

Brainstorming

Various ideas that can be evolved in the process of this paper.

Open Source Vs Closed Source Development

Nice and proven, the problem with that, it is done before in various contexts.

Mathematical Approach (Vs Public Interface)

Maybe we can find (observing our data ofc) a mathematical equation or a theorem of some sort, that will describe certain relations between the metrics.

External Characteristics

  • Micro-benchmarking (maybe in collections etc).
  • Number of Bugs (update: cannot find data for OpenJDK

Requirements Drives Quality

Examine if Requirements dictates quality or the design of code, since in our case we have a specification that guides the implementation.

  • Clustering by public class + non-public dependencies

Threats of Validity

  • The three systems are not directly comparable