|
|
Application module:
Verification and validation |
ISO/TS 10303-1488:2018-11(E)
© ISO
|
This clause specifies the information requirements for the
Verification and validation
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
This clause defines the information requirements to which implementations shall
conform using the EXPRESS language as defined in ISO 10303-11.
The following begins the
Verification_and_validation_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Verification_and_validation_arm;
(*
The following EXPRESS interface statements specify the elements
imported from the ARMs of other application modules.
EXPRESS specification:
*)
USE FROM
Requirement_assignment_arm;
--
ISO/TS 10303-1233
USE FROM
State_observed_arm;
--
ISO/TS 10303-1256
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Requirement_assignment_arm |
ISO/TS 10303-1233 |
| State_observed_arm |
ISO/TS 10303-1256 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM types
for this application module. The ARM types and
definitions are specified below.
The evidence_item type is an
extensible list of alternate data types
that allows for the designation of the data
types
Validation, and Verification.
NOTE
The list of entity data types may be
extended in application modules that use the constructs of
this module.
It is used to identify the data which can be used as evidence in a validation or verification.
The fact that verification and validation are members of this select enables a verification or validation to be used as the
evidence in another verification or validation.
EXPRESS specification:
*)
TYPE
evidence_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
(Validation,
Verification);
END_TYPE;
(*
The evidence_support_item type allows for the designation of the data
types
Validation, and Verification.
EXPRESS specification:
*)
TYPE
evidence_support_item =
SELECT
(Validation,
Verification);
END_TYPE;
(*
The v_and_v_state type is an extension
of the
state_of_item type.
It adds the data
type
evidence_support_item
to the list of alternate data types.
It is used to identify the state of the validation or verification.
EXAMPLE
Example states that may be applied to a verification are "Verified", "Not verified".
EXPRESS specification:
*)
TYPE
v_and_v_state =
SELECT
BASED_ON
state_of_item
WITH
(evidence_support_item);
END_TYPE;
(*
The validation_item type is an
extensible list of alternate data types
that allows for the designation of the data
type
Product_version.
NOTE
The list of entity data types may be
extended in application modules that use the constructs of
this module.
It is used to identify the item to be validated.
EXPRESS specification:
*)
TYPE
validation_item =
EXTENSIBLE
GENERIC_ENTITY
SELECT
(Product_version);
END_TYPE;
(*
This subclause specifies the ARM entities for this
module. Each ARM application entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entities and definitions are specified below.
An Evidence is a collector of items used together to provide a single piece of evidence within a validation or verification. For example
a document and its approval by a customer may be used together to provide evidence of customer acceptance.
EXPRESS specification:
*)
ENTITY Evidence;
supports : evidence_support_item;
items : SET[1:?] OF evidence_item;
END_ENTITY;
(*
Attribute definitions:
supports:
identifies the validation or verification for which this evidence has been related.
items:
the component data items used to support this evidence.
A Validation is a subjective assertion that an item is "fit for purpose".
Evidence used in this validation is identified by the inverse attribute validated_by.
Validation is commonly understood to mean "Have we built the right system?". Validation is concerned with ensuring that the
system will meet the customer’s objectives and expectations. Validation usually includes testing under normal usage conditions.
NOTE
An item may pass validation even though some requirements fail verification.
NOTE
It is assumed that meta data supporting the validation will be applied using assignment entities, such as identification assignment,
person and organization assignment etc..
EXAMPLE
Every flight of every Space Shuttle has been a "Validation" flight to test the new design under actual conditions. No two
shuttles have flown in the same configuration and many systems cannot be validated except under actual conditions.
EXPRESS specification:
*)
ENTITY Validation;
validates : validation_item;
INVERSE
validated_by : SET[0:?] OF Evidence FOR supports;
END_ENTITY;
(*
Attribute definitions:
validates:
identifies the item which is been validated by this entity.
validated_by:
the collection of evidence used in this validation.
A Verification is an objective assertion of a claim that requirement is satisfied by a particular item represented in a Requirement_satisfied_by has been verified. The evidence used in this verification is identified by the inverse attribute verified_by.
Verification is commonly understood to mean "Have we built the system right?". Verification ensures that the specified requirements
have been met. Verification uses the methods of Test, Analysis, Inspection, Demonstration, Similarity.
NOTE
Just because an item is verified does not ensure that it meets all stakeholder needs or expectations, many of these are never
specified are of an un-testable nature e.g. "the car should look sporty".
NOTE
It is assumed that meta data supporting the verification will be applied using assignment entities, such as identification
assignment, person and organization assignment etc..
EXAMPLE
A data type used to represent a vehicle's engine with a power output of 160BHP could be asserted to satisfy a requirement
"the vehicle shall have a maximum power output of at least 150BHP". This assertion may be verified by analysis results on
simulations of the engine. In this case the analysis results would be identified in the items collection of an evidence instance,
possibly including the approval of the analysis. The evidence instance would identify that it is used to support the required
verification.
EXPRESS specification:
*)
ENTITY Verification;
verifies : Requirement_satisfied_by;
INVERSE
verified_by : SET[0:?] OF Evidence FOR supports;
END_ENTITY;
(*
Attribute definitions:
verifies:
the claimed requirement satisfaction by a particular item which is been verified by this entity.
verified_by:
the collection of evidence used in this verification.
A Verification_relationship is an association between two verifications.
NOTE
This relationship may be classified in other modules to provide more specific meanings.
EXPRESS specification:
*)
ENTITY Verification_relationship;
relating : Verification;
related : Verification;
END_ENTITY;
(*
Attribute definitions:
relating:
the first verification in this relationship.
related:
the other verification in this relationship.
*)
END_SCHEMA; -- Verification_and_validation_arm
(*
© ISO 2018 — All rights reserved
