Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geclipse-dev] Quality metrics

Hi *,

from my point of view, this sounds like a good approach: Starting with ONE 
SIMPLE metric and enhance this one step-by-step. We don't have to reimplement 
everything from scratch: Most (if not all) metrics are already implemented.

It is most important to give the developers feedback of the code quality in a 
timely manner and to automate the process. This means that I vote for an 
integration in the nightly build process. When we have such a solution 
running we get information if we are getting better or worse over time.

That said, a first step must be the integration of the JUnit tests in the 
build process. The PDE build output and the log files could also be taken to 
count the numbers of errors and warnings very easily every night.

On the other hand there are many metrics available from the Eclipse Foundation 
or can extracted from their databases: Number of open bugs, time to solve a 
bug, number of repository check-ins, ... These are not code metrics, but they 
give a pretty good view about the liveliness of a project.

Markus

On Thursday 03 May 2007 08:44, Kornmayer, Harald wrote:
> HI all
>
> I propose to start with the implementations of the system to measure the
> metrics. We need the measurements soon. If we do NOT adress quality with
> metrics in the first year report, We will run in problems at the review.
>
> So be pragmatic, start with the implementation of the first metrics. And
> then we will enhance the System step by step.
>
> Harald
>
> >>-----Ursprüngliche Nachricht-----
> >>Von: geclipse-dev-bounces@xxxxxxxxxxx
> >>[mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von
> >>Stuempert, Mathias IWR
> >>Gesendet: Mittwoch, 2. Mai 2007 17:44
> >>An: Developer mailing list
> >>Betreff: AW: [geclipse-dev] Quality metrics
> >>
> >>
> >>Hi All,
> >>
> >>As I mentioned also in the meeting today a metric measuring
> >>the coverage of the code by tests would also be very important.
> >>
> >>Cheers, Mathias
> >>
> >>-----Ursprüngliche Nachricht-----
> >>Von: geclipse-dev-bounces@xxxxxxxxxxx
> >>[mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im >>Auftrag von Tao,
> >>Jie
> >>Gesendet: Mittwoch, 2. Mai 2007 16:12
> >>An: Developer mailing list
> >>Betreff: [geclipse-dev] Quality metrics
> >>
> >>Dear all,
> >>
> >>As mentioned in the audio meeting this afternoon, I give you a brief
> >>description of the metrics I thought about. Please give me suggestions
> >>of novel ones.
> >>
> >>1. Size: code size (statements, blank, comments, executable), method
> >>size (number of lines) (! 30% of comments is regarded as efficient)
> >>2. Class: number of methods (two large means many children and high
> >>inheritance-->prevent reuse)
> >>3. Messages: number of methods which can be invoked in response to a
> >>message (measuring complexity)
> >>4. Cohesion: is defined as the degree that methods in a class are
> >>related to one another. It is measured with "how methods use the same
> >>data field in a class"
> >>5. Coupling: measured by "number of classes on which a class depends"
> >>6. Inheritance: measured by "number of ancestors and children of a
> >>class"
> >>
> >>Cheers,
> >>
> >>Jie
> >>_______________________________________________
> >>geclipse-dev mailing list
> >>geclipse-dev@xxxxxxxxxxx
> >>https://dev.eclipse.org/mailman/listinfo/geclipse-dev
> >>_______________________________________________
> >>geclipse-dev mailing list
> >>geclipse-dev@xxxxxxxxxxx
> >>https://dev.eclipse.org/mailman/listinfo/geclipse-dev
>
> _______________________________________________
> geclipse-dev mailing list
> geclipse-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/geclipse-dev

-- 
Markus Knauer
INNOOPRACT Informationssysteme GmbH
###   phone: +49 721 664 733 44
###     fax: +49 721 664 733 29
###     web: www.innoopract.com

========================= Legal Disclaimer =================================
According to Section 80 of the German Corporation Act 
Innoopract Informationssysteme GmbH must indicate the following information:
Address: Stephanienstrasse 20, 76133 Karlsruhe Germany 
General Manager: Jochen Krause, Eric von der Heyden
Registered Office: Karlsruhe, Commercial Register Karlsruhe HRB 7883
============================================================================


Back to the top