A first step in the testing path can be the generation of a document called test plan, which is the blueprint to conduct software testing. This document describes the objective, scope, approach, focus, and distribution of the testing efforts. The process of preparing such document is a useful way to think about the needs to verify of a software system. Again, this document is especially useful when the size of the SUT and the involved team is large, due to the fact that the separation of work in different roles makes the communication a potential deterrent for the success of the project.
A way to create a test plan is to follow the IEEE 829 Standard for Test Documentation. Although this standard might be too much formal for the most of software projects, it might be worth to review the guidelines proposed in this standard, and use the parts needed (if any) in our...