VerificationValidation::VVCase

Header Image
Content:
VVCase : Public Class VVCase, VerificationValidation, VerificationValidationOrganization, RequirementsRelationships
VVCase represents a V&V effort, i.e. it specifies concrete test subjects and targets and provides stimuli and the expected outcome on a concrete technical level.<br/><br/>Semantics:<br/>VVCase is a grouping element for a set of VVProcedures that together makes up a concrete Verification/Validation effort.<br/><br/>Constraints:<br/>[1] Only a concrete VVCase can have vvLog.<br/>[2] Only a concrete VVCase can have vvTarget.<br/>[3] Only a concrete VVCase can have an abstractVVCase.<br/>
  • Associations
  • Associations From
  • Advanced
  • Other Links
Element Source Role Target Role
VVTarget
Class  
Name:  
 
Name: vvTarget
The VVTargets for this VVCase. See dependency vvSubject for more information.
Details:
 
VVProcedure
Class  
Name:  
 
Name: vvProcedure
The VVProcedures for this VVCase.
Details:
 
VVCase
Class  
Name:  
 
Name: abstractVVCase
An abstract VVCase describes "what" needs to be done and is identified from a concrete VVCase.
Details:
 
VVLog
Class  
Name:  
 
Name: vvLog
The VVLogs captured while executing this ConcreteVVCase.
Details:
 
Element Source Role Target Role
VVCase
Class  
Name:  
 
Name: abstractVVCase
An abstract VVCase describes "what" needs to be done and is identified from a concrete VVCase.
Details:
 
«instanceRef» VVCase_vvSubject
Class  
Name: vvSubject
 
Name:  
 
Details:
 
Verify
Class  
Name:  
 
Name: verifiedByCase
The VVCase that verifies the supplier Requirement
Details:
 
VerificationValidation
Class  
Name:  
 
Name: vvCase
The elements that are being verified and validated by this VVCase. Usually this will be a subset of those elements which are realized by the VVTarget(s) of the VVCase; but this need not always be the case. The difference between the vvSubjects and the entities which are realized by the case's VVTarget(s), is that the vvSubjects are related to the primary, overall objective of the ConcreteVVCase, while the realized entities can comprise more than these. For example: (a) For technical reasons additional entities need to be realized only to permit the testing of the entities of actual interest or (b) If a VVTarget is reused among many ConcreteVVCases and therefore realizes more entities than are actually being tested by any single ConcreteVVCase.
Details:
 
Property Value
isFinalSpecialization: 0
Object Type Connection Direction Notes
VVProcedure Class Weak To  
TraceableSpecification Class Generalization To  
Identifiable Class Dependency To  
«instanceRef» VVCase_vvSubject Class Strong From  
VerificationValidation Class Strong From  
VVLog Class Strong To