This is a truly excellent writeup. There are a couple of points I wish to add for completeness:
Don't forget documentation. The production of online help and manuals may be the responsibility of the UI designer, but I see this as a distinct role. Often software houses have come unstuck by neglecting this aspect of their product. It may me the best software in the world, but who will be able to use it without instructions in plain English (or French, Japanese, etc.).
Who is the customer? With any project of a reasonable size, it is doomed to failure if the customer is not involved at an early stage (remember the classic swing diagram). Even if the customer is merely involved in signing off the requirements document, that is better than nothing, and saves much legal heartache when it comes to project delivery time.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] |