TABLE OF CONTENTS System verification planning should start way back with the development of the system specification. The V diagram illustrates this very well. As noted in Figure 4.1-1, the content of the system specification should drive system test requirements crafted at the same time as the specification is written. Ideally, these requirements will be included in Section 4 (in a DoD specification) of the specification. Some organizations place these requirements elsewhere or fail to go through this step, and the result is a poorer specification and unnecessary program risk. If you have to write the verification requirement as the product requirements are being written, you will write better product requirements. There will not be any requirements statements like "shall work well and last a long time" in the specification because one cannot craft a way to test or analyze whether or not the final product satisfies this kind of requirement, thus encouraging the writer to realize that they cannot write the verification requirement because they have written an unverifiable product requirement.
All of those system requirements mapped to test in the system specification verification traceability matrix should come to rest in the hands of the person responsible for creating the system test plan. These may be augmented by verification requirements, or verification strings in the context of top-tier...
