Some
considerations involved in determining software quality:
·
Robustness
o
Crash-proof?
o
Gives correct
results?
o
Improper inputs
detected?
·
User friendliness
o
Meaning of output is
self-explanatory?
o
Features are clear without having to read
the code?
=>FIND SIMILAR
o
User
interface is not confusing?
o
User
input is convenient?
o
Response to improper inputs includes
instructions for proper inputs?
o
Default behavior exists when
appropriate?
·
Style
o
Comments are frequent and
appropriate?
=>FIND SIMILAR
o
Every method and class has an
introductory comment?
o
Comment format is neat and
readable?
o
Indentations are 2-4 spaces except when
another value is better?
o
Symbol names are mnemonic?
=>FIND SIMILAR
o
Symbol names comply with Java
custom?
o
Coding structure is
good?
o
Variable and object types and classes are
well chosen?
o
Neatness: is it clear what assignment it
is, who did it, etc.?
=>FIND SIMILAR
·
Effort and Attention to
detail
o
Output format shows careful
craftsmanship?
o
How
do teammates assess each other’s contribution?
o
Does
the size of a team positively affect the result quality?
=>FIND SIMILAR
o
Is
authorship stated?
o
Is
source code significantly different from code written by others?
·
Elaborateness
o
How
much functionality is provided? Often more is better when specs allow.
=>FIND SIMILAR
Does
it run on different Java platforms? (Appletviewer, IE, and Netscape, for
example.) In industry, this matters.