Terms: v | Terminology index |
The terms defined in the terminology dictionary and in the Business DEXs.
valid need for change | |||
Definition: |
Confirmed requirement for configuration change action.
NOTE Note 1: A valid need for change may have one or more proposed solutions, but not all these will be evaluated solutions Note 2: It includes:
|
||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
validation | |||
Definition: |
Confirmation and provision of objective evidence that the requirements for a specific intended use or application have been
fulfilled.
NOTE Note 1: The term validated is used to designate the corresponding status. Note 2: The use conditions may be real or simulated. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.3 | ||
Status: | complete |
validation plan | |||
Definition: | See: Validation, Verification and Audit plans | ||
Synonyms: | validation, verification and audit plans | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
validation, verification and audit plans | |||
Definition: |
The established plans for carrying out activities identified within.
NOTE The plans and schedules enable allocation of resources for the tasks to be carried out and enable monitoring of progress. The plans are based on the decision taken concerning the introduction point and effectivity of the change. They cover both production embodiment and retrospective embodiment, before or after the delivery of the product as appropriate. An approved change is planned and scheduled for implementation in all documents, facilities, hardware and software impacted change. The implementation is carried out in accordance with the plan. Implementation of a change involves the release of new or revised configuration documentation (Assured Product and Support Information (APSI)) including requirements and design information. |
||
Synonyms: | validation, verification, validation plan, audit plan, verification plan | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 1.1 | ||
Status: | in_business_review |
variance | |||
Definition: |
A departure from the design intent as reflected in the Assured product and support information.
NOTE Note 1: Design intent includes the design of the support system, the manufacturing system etc. Acceptance of a Variance does not change the PIF baseline. Note 2: Different organizations have one or more words to describe departures from the design baseline, thus this definition is intended to cover terms such as:
|
||
Synonyms: | APSI | ||
Source: |
[1] PLCS Activity Model, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
verification | |||
Definition: |
Confirmation and provision of objective evidence that specified requirements have been fulfilled.
NOTE Note 1: The term verified is used to designate the corresponding status. Note 2: Confirmation may comprise activities such as:
Note 3 : In the field of metrology, refer to VIM. |
||
Source: |
[1] ISO 9000, Quality Management System - Fundamentals and vocabulary |
||
Version: | 1.2 | ||
Status: | complete |
verification plan | |||
Definition: |
The program of verification tasks.
NOTE See: Validation, verification and audit plans |
||
Synonyms: | validation, verification and audit plans | ||
Source: |
[1] PLCS terminology dictionary, 2000. |
||
Version: | 2.1 | ||
Status: | complete |
Verify releasability | |||
Definition: |
Check that all required release approvals are present.
NOTE Segregates "private and public view" information, common configurations but different customers. These will be placed on different release plans. |
||
Source: | PLCS OASIS | ||
Version: | 1.1 | ||
Status: | in_work |
version | |||
Definition: | A particular form of product which varies from other forms of the product. | ||
Source: |
[1] EIA/ANSI EIA-649-A, National consensus standard for configuration management , 2004. |
||
Version: | 1.1 | ||
Status: | in_business_review |
© OASIS 2010 — All rights reserved