russ@motto.UUCP (Russell Crook) (10/29/88)
.
I am looking for references (both practical and theoretical) on
metrics that can be applied to software quality. I have
no idea what research has been done on such things; I imagine
that things like number of bugs found per [module, line, program,
system], number of reported problems, average time taken to correct a
given problem, ratio of design time expended to coding time ... whatever
has been done (or even proposed to be done) could be used. Reports on
language issues (i.e., certain languages make it easier to write "high
quality" programs than others, general availability of certain software
tools in certain environments (e.g., "lint" for C, PFORT for profiling
Fortran-66)) are also of interest.
Please send e-mail; if there is enough information, I will post
a summary of what is found.
advTHANKSance ...
--
Russell Crook (UUCP: ...!uunet!mnetor!motto!russ)
Disclaimer: "...we're all mad here. I'm mad. You're mad."
"How do you know I'm mad?" said Alice.
"You must be", said the Cat, "or you wouldn't have come here."