Model Systems Engineering Documents for Dynamic Message Sign (DMS) Systems
Chapter 4. Verification Plan Guidance
The model Verification Plan can be found in Appendix D. The chapters required for the Verification Plan are:
This verification plan describes the activity of verifying that the system being built satisfies all the requirements set out in the requirements documents.
The verification documents will include:
To ensure that all requirements are verified by this activity, trace each requirement into a verification case, then trace this in turn into a step in the Verification procedure.
The Verification Plan does not need to include verification procedures. These may be prepared by the vendor, but must be reviewed by the agency to ensure each verification case will be tested and appropriate results recorded. In relatively simple cases, the vendor may prepare both the Verification Plan and the procedures. In this situation, the agency must ensure that each requirement is mapped to at least one verification case.
Preparation of a stand-alone verification plan is strongly advised if:
There is also the question of how comprehensive to make the verification effort. It is impossible to validate all possible combinations of actions under all possible operational situations. A good rule of thumb is: if it was important enough to write down as a requirement, then it should be verified, at least once. In-process1 verification performed on the needs and requirements will help ensure that the correct requirements are being verified.
Once the verification plan is completed, use the following checklist to ensure all critical information has been included.
This section identifies the type of verification activity to be performed within this Verification Plan. For instance, this activity may validate the entire system, a sub-system, the deployment at a site, a burn-in, or any other verification activity called for in the Verification Plan.
This section gives a brief description of the planned project and the purpose of the system to be built. This section also describes the environment in which the project operates. It identifies the organization structures that encompass all stakeholders. It also gives a brief description of the role to be played by each stakeholder. This includes ad hoc and existing management work groups and multi-disciplinary technical teams that should be formed to support the project.
This is a list of all documents used in the preparation of this Verification Plan. This usually includes the Project Plan, (if one was written), and the applicable Requirements Documents. Reference to other documents, such as descriptions of external systems, standards, a Concept of Operations, and manuals may also be included.
This section provides details on how verification is accomplished. It defines: who does the verification; when and where it is to be done; the responsibilities of each participant before, during, and after verification; the deployed hardware and software configuration; and the documents to be prepared as a record of the verification activity.
This section also defines how anomalies are to be handled (that is, what to do when an unexpected situation or a failure occurs during verification).
In general, the following information should be included in this section:
This section identifies the specific verification cases to be performed. A verification case is a logical grouping of functions and performance criteria (all from the Requirements Document) that are to be verified together. For instance, a specific verification case may cover all the control capabilities to be provided for control of the DMS System. There may be several individual requirements that define this capability, and they all are verified in one case. The actual grouping of requirements into a verification case is arbitrary; however, the grouping is usually based on the grouping of functional requirements in the Requirements Document. They should be related and easily combined into a reasonable set of procedure actions. Suggested verification cases that may be used in the Verification Plan document are included in the Verification Plan Sample Cases table (Appendix D).
Each case should contain at least the following information:
Each verification case in Appendix D corresponds to the same name of a section of requirements in Section 3 of the Requirements model document. The details of each verification case will need to be added as the system is further defined.
1 In-process verification is reviewing the needs and requirements during the definition stage by the stakeholders to ensure that all the needs have been identified and traced to the appropriate requirements and have been reviewed for completeness for each of the needs. [ Return to Note 1 ]
United States Department of Transportation - Federal Highway Administration