The recent discussion(s) about quality goals and metrics got me to
thinking about what CPANTS is trying to do vs. what it's actually
doing. As a brainstorming exercise, I wrote down all of the software
quality goals I could think of quickly. For each existing CPANTS
metric, I decided which of those goals the test was trying to solve.
Then I tossed in some other possible (or impossible?) metrics that
have been mentioned on this list or which occurred to me as I was
brainstorming.
I posted all of my thoughts on the Perl-QA wiki here:
http://perl-qa.yi.org/index.php/CPANTS_Quality_Goals
I'd be thrilled if others would look at what I wrote and improve it
or tear it apart. :-) I hope this isn't too much wheel re-invention...
Chris
--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1435 E Main St, Madison WI 53703
vCard: http://www.chrisdolan.net/ChrisDolan.vcf
Clotho Advanced Media, Inc. - Creators of MediaLandscape Software
(http://www.media-landscape.com/) and partners in the revolutionary
Croquet project (http://www.opencroquet.org/)
