Database Reference
In-Depth Information
Figure 3-3.
An example of a “Solution Development Plan” document
When you look over the documents shown in Figure
3-3
, you see it has several sections. (You can also find
this document in the Chapter 3 folder of the downloadable content files for a clearer view.)
At the top, it identifies the name of the solution, the owner, and the date the document started. Of course,
there are other items that could be added, but in an effort to keep things simple, we have reduced this content to
just these three items.
Beneath that is a section for recording changes to the document. This area is used after your initial writing of
the document, which at this point will not take place until other steps are completed first.
The “Change Log” section is followed by the summary of the solutions you are going to build. This is a
parenthetical description of the solution.
Following that is an outline of expectations. It is important to list what will satisfy the client once the solution is
completed. You will compare the success or failure of the solution against these expectations once it is completed.
Reviewing your successes and failures will allow you to plan for future solutions, allowing you to avoid the same
mistakes. This is also a section used by testers to verify that your solution has accomplished its goal.
In Figure
3-4
, you can see that the document includes open and closed issues sections. Developers, testers,
and managers can use these sections to track questions about the solution and the answers that go with them.
