Table of Contents
Internal Block Diagram of the sub-projection 6.4.
The purpose of this sub-projection is to define Validation Campaigns (VC) which consists of one DUT, one VM and Operations related to the Tests previously allocated to Requirements under DUTs. The Figure 1 below shows a drop-down list, in the main toolbar, which gives access to the sub-projection 6.4.
Figure 1: Drop-down list to access the sub-proj. “6.4. Define Validation Campaigns”
In this sub-projection, by a drag and drop of the Objects from the palette (see Figure 2) or adding existing ones, we can:
- create some VCs:
- on the Root if it concerns an “integration VC” : the System in its environment (possibly involving some external systems),
- in the System, for internal VCs,
- allocate one existing DUT and one existing VM to the VC,
- create Operations under VC:
- manually (not really ergonomics! Prefer the tabular view “b. Determine Operations” presented below),
- automatically by Right-clicking on the VC -> Initialize Validation Campaign. This action creates automatically suitable Operations as explained on Figure 5 below,
- fill each Operation result by editing its attribute “Result” (see Figure 4)
Figure 2: Palette of Objects in the sub-proj. “6.4. Define Validation Campaigns”
Similarly to the other Objects, we can fill the tables of the properties for the Validation Campaigns (VC) and Operations. As shown on Figure 3 and Figure 4, VC’s and Operation’s attributes are almost all common attributes (already discussed in sub-projection 6.1.) such as Name, desc, etc.
Figure 3: Properties table of a VC
The VC’s attribute Initialize Validation Campaign, is the script (discussed below) run when generating automatically Operations, as stated above. You can edit or run it by clicking on “Edit…”.
Figure 4: Properties table of an Operation
The Operation’s attribute Result can be: (empty), NA (Not Available), In Work, NOK or OK.
The script “Initialize Validation Campaign”
It creates automatically suitable Operations in a VC, according to the DUT and VM allocated to the VC. In other words, it filters suitable Tests and allocate them to Operations corresponding to the Reqs under DUT which are concerned by the VM.
The mechanism of the script is illustrated (steps 1 to 4 for two Reqs: red and blue arrows on Figure 5) below for two VCs one the same DUT validated through two VMs:
- In a given DUT, for each Requirement, the script identifies its Test in the sub-projection 6.2.,
- It verifies whether the Validation Mean of the identified Test (defined in the sub-projection 6.2.) is the same as the Validation Mean in the VC (sub-projection 6.4.).
DUT: Charging system, Requirement: Battery Heating, Test: Launch several apps, Validation Mean: Software,
- If yes, it adds a new Operation in the VC (sub-projection 6.4),
- It puts the Test in the Operation.
Figure 5: Mechanism generating suitable Operations in sub-proj. “6.4. Define Validation Campaigns”
Note: Figure 5 shows the sub-projection 6.4. for the Laptop example.
Tabular View of the sub-projection 6.4.
Figure 6 shows the actions in the Tabular View of the sub-projection 6.4.
Figure 6: Tabular View of the sub-proj. “6.4. Define Validation Campaigns” in Project Tools
a. Define Validation Campaigns
In the table illustrated in Figure 7 below, you can define a new Validation Campaign which is allocated to the Object specified in “parent id” column (empty = Root). On the same line you can allocate one DUT and one Validation Mean to the Validation Campaign.
Figure 7: Define VC through Tabular View (sub-proj. “6.4. Define Validation Campaigns”)
b. Determine Operations
In the table illustrated in Figure 8 you can define Operations under Validation Campaigns. For each new Operation, you must specify the VC, DUT and Test related to it, and then specify also the Operation’s attributes.
The columns of this table allow also to:
- affect Tests to Validation Campaigns
- fill the Operations’ Results
Figure 8: Define Operations under VCs through Tabular View (sub-proj. “6.4. Define Validation Campaigns”)
c. Matrix Test results
In this tabular view, you can fill Operations’ results with the values stated above. For each Operation (line), you can specify its result in each VC (column) as illustrated in Figure 9.
- OK: the operation is successfully performed,
- NOK: the operation failed,
- Not Available (NA): the result is not known,
- In Work: the operation is currently run,
- (Empty): the VC is not concern by the Test.
Figure 9: Filling Operations’ results through Tabular View (sub-proj. “6.4. Define Validation Campaigns”)