INTRODUCTION

$($NOTE $1$: THE SOFTWARE IEST PLAN GUIDELINES WERE DERIVED AND DEVELOPED FROM IEEE STANDARD FOR SOFTWARE TEST DOCUMENTATION$)$

$($Note $2$: The Software Test Plan elements is not meant to imply that the sections or subsections must be developed or presented in that order. The order of presentation is intended for ease of use, not as a guide to preparing the various elements of the Software Test Plan. If some or allof the content of a section is in another document, then a reference to that material may be listed in place of the corresponding content.$)$

The Introduction section of the Software Test Plan $($STP$)$ provides an overview of the project and the product test strateg, a list of testing deliverables, the plan for development and evolution of the STP$,$ reference material, and agency definitions and acronyms used in the STP$.$

The Software Test Plan $($STP$)$ is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.

$1\mathrm{.}1$ Objectives