Database Reference
In-Depth Information
Figure 19-6. Comparing the Solution Development Plan to the dev specs
When each version of the solution is complete and you start work on the next version, properly written
dev specs will get your team up to speed. Portions of this document can also be included as part of the SDK
document, because the audience for the two documents are complementary.
some companies fly employees in from all over the world to be trained to create these types of files. You do
not have to go that far, but documents of this type are an important indication of your level of professionalism.
Tip
Dev specs are a blueprint to what was created and are given to the customer much like a car manual is
included with a new car. The SDK is given to other developers who will work with your solution, much like
a repair manual is used by mechanics. (You may not want to refer to your SDK as a repair manual! Hot-rod
customization tool kit sounds much better.)
User Documentation
With all the documentation that needs to be included, we cannot forget that we have new users who have never
seen your BI solution before and need to be instructed on how to use your program.
Just as there is more than one way to peel an apple, there is more than one way to train a user. Some methods
include the following:
Developing a video demo for online training
Training the managers who in turn are responsible for teaching it to their employees
Sending someone from your team to set up one or more training sessions
 
 
 
Search WWH ::




Custom Search