I think this excerpt explains it pretty good: Metrics are not indications of bugs or poor design, but high metric numbers often indicate how complex, fragile, or sensitive to regressions a class may be. Classes or methods with high metric values may be good candidates for refactoring. It is therefore useful for a developer to monitor project metrics and investigate those metrics which seem out of line.
Like a car's dashboard warning lights, the metrics module flags classes and methods which cross various metric thresholds with a yellow (warning) or red (error) light next to their icons in the Explorer. A developer has the choice of refactoring the class or method, or approving the current metric value; in either case, the warning light goes out. The metrics module is therefore useful as a guide during class creation and maintenance to encourage the development of lighter weight classes which are loosely coupled. Taken from: http://metrics.netbeans.org/ PS! You'll notice that my original email mentioned "Stats", but the correct term appears to be "metrics". Regards, Enrico -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 11 April 2006 08:01 AM To: CTJUG Forum Subject: [CTJUG Forum] Re: Stats Hi, I don't know of any other tools but I'm curious why you need these stats? Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CTJUG Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/CTJUG-Forum -~----------~----~----~----~------~----~------~--~---
