PDA

View Full Version : Pointers for Industry standards


Sri
09-11-2003, 12:46 AM
Hi All,

I am looking for some information on measurements and comparing it
with standards/benchmarks.

This is what I am looking for:
1. How much % of time is spent on dev vs. QA (ours is 60:40; how does
this
compare with industry standards?)
2. Within development how much time is spent on design vs. coding vs.
reviews vs. testing( ours is 12:48:3:37; how does this compare with
industry standards?)
3. Defects per LoC (ours is 1:114 c++ code; how does this compare with
industry standards?)
4. Test cases per Loc (not yet calculated; does not whether this is of
any
worth)
5. Review effectiveness: Say, 10% of the bugs were found during code
reviews. Is this good/bad/satisfactory??

Offhand information is welcome but I am looking for some literature /
website / source which I can refer in my report.

Thanks,
~Sri

Mon
09-11-2003, 01:21 PM
3 books for reference.
Even if you don't want to use FPA, they provide percentages which will hold
true for effort expended. (Mind you, they used FPA to ensure they got a
standard measure of size on which to base the percentages ;-))

Software Sizing and Estimating - MkII FPA Charles Symons - published by
Wiley Professional Computing ISBN 0 471 92985 9
Sizing and Estimating Software in Practice Stephen Treble & Neil
Douglas publisher McGraw-Hill ISBN 0 07 707620 6
Practical Implementation of Software Metrics Paul Goodman publisher
McGraw-Hill ISBN 0 07 707665 6
M. O'Neill
Software Management Methods
Dublin
Sri <sri_adiga@yahoo.com> wrote in message
news:191e4e3e.0309110046.28e73a3f@posting.google.com... Hi All, I am looking for some information on measurements and comparing it with standards/benchmarks. This is what I am looking for: 1. How much % of time is spent on dev vs. QA (ours is 60:40; how does this compare with industry standards?) 2. Within development how much time is spent on design vs. coding vs. reviews vs. testing( ours is 12:48:3:37; how does this compare with industry standards?) 3. Defects per LoC (ours is 1:114 c++ code; how does this compare with industry standards?) 4. Test cases per Loc (not yet calculated; does not whether this is of any worth) 5. Review effectiveness: Say, 10% of the bugs were found during code reviews. Is this good/bad/satisfactory?? Offhand information is welcome but I am looking for some literature / website / source which I can refer in my report. Thanks, ~Sri


MyLounge.com Site Map
Forum: Cars, Cell Phone, Database, Games, Home Improvement, IT, Music, School, Sports, Web Design, Web Server, Weight Loss

The MyLounge.com forum is intended for informational use only and should not be relied upon and is not a substitute for any advice. The information contained on MyLounge.com are opinions and suggestions of members and is not a representation of the opinions of MyLounge.com. MyLounge.com does not warrant or vouch for the accuracy, completeness or usefulness of any postings or the qualifications of any person responding. Please consult a expert or seek the services of an attorney in your area for more accuracy on your specific situation. Please note that our forums also serve as mirrors to Usenet newsgroups. Many posts you see on our forums are made by newsgroup users who may not be members of MyLounge.com Term of Service