As indicated in the INCOSE System Engineering Handbook 2006, "the purpose of the Validation Process is to confirm that the realized system complies with the stakeholder requirements." The Validation Plan view of arKItect offers an interactive interface to create Validation Campaigns (VCs) and to ensure that all Requirements are fulfilled. To achieve this goal, the Validation Plan projection includes four sub-projections wherein we can progressively:
- Sub-projection "6.1. Define Validation Means":
- Sub-projection "6.2. Define Tests":
- Sub-projection "":
- Sub-projection "6.4. Define Validation Campaigns":
We explain this projection with an example called “LapTop”. Figure 1 shows the final result of the sub-projection 6.4. for this example.
Figure 1: Final behavior of Validation Plan (sub-proj. 6.4.)
The table below summarizes the Objects and parent-child relations allowed in each of the sub-projections.
Parent -> child relations
6.1. Define Validation Means
Validation Mean (VM)
VM (-> VM ->…)
6.2. Define Tests
Requirement -> Test -> VM
6.3. Define Device under Tests
Device Under Test (DUT)
DUT -> (DUT ->…) -> Requirement
6.4. Define Validation Campaigns
Validation Campaign, Operation
(System -> ) VC -> DUT, VM, Operation
Note: In sub-projection “6.4. Define Validation Campaigns”, other Objects (less often used) can be allocated to Tests: Observed signals and Stimuli signals (in which VP flows, Data and Physical flows can be allocated).
In the next sections, we explain the sub-projections of the projection 6 which allow to create the VP progressively. In each section, there are two parts that explain how to create the VP in two manners:
Figure 2: Main views of Validation Plan sub-projections