With this practice, basic guidance regarding how to develop documentation and training, and more importantly
why, are provided here. The best way to read this practice is to become familiar with its overall structure,
what is in it, and how it is organized.
There are two related parts to this practice: 1) Documentation, and 2) Training. The documentation activity normally
feeds the training effort. There are three basic types of documentation, each of which is meant for a different
audience, and each has its own purpose.
A combination of the Product Documentation and User Documentation, with User Stories and Nonfunctional Requirements,
are used in the development of User Training.
Product Documentation, with the Architecture Notebook and any design artifacts, are used to create Support
Documentation.
Start with the tasks for creating the different types of documentation. Then, review the work products that result from
those tasks. Next, review the tasks of the training activity. Notice that there is only one task that produces two
different types of training materials (end user and support materials), because the process is the same for both
(unlike the process for developing the three types of documentation). There are two tasks for training delivery because
the end user training often is formal in nature and support training usually is informal.
|