1. Tips

2.  Your system should be robust and easy to use.  Display meaningful text, mention units & assumptions (maybe as a tool-tip).  Use meaningful error messages. What’s wrong, how to fix.  User should be aware of the outcome of an operation.

3. Tips  Try to make wrong inputs impossible.  Separate internal and external representations  i.e. use id internally and name externally.  Allow the users the review their status. What is the id of this item? Why should I care?

4. Tips  Documentation should be clear and concise. Use table of contents, page numbering, titles.  Don’t forget to mention how to run your system.  Often test-plan is written before the system is fully ready. Before submission verify that:  The existing tests are still relevant.  No tests are missing.  All the tests pass.  Install and run your system on a new machine.