I can't remember who created this list, but this is what
i was taught in college. This is a very generic list of
qualities, but one that should be reflected upon often:
- does the software behave as specified?
- can we depend upon this software?
- how well does software behave beyond
what it is required to do?
- is the software efficient? scalable?
- user friendliness
- human-computer interaction
- test test test!!
- be sure that whomever takes over your code does not
know where you live
- can others use this wheel for their needs?
- does it run on other platforms? will a lot of changes be
required to do so?
- can others understand your code? did you try to ensure
that others can understand it?
- how well does this software work with other
- measurement of the development process, not necessarily
how productive the software itself is
- ability to meet your deadline
- is the documentation clear to internal and external
users of the software?
(the triplet paradiddle with high-hat)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||