| Menu | |
|
: Home |
|
| Search | |
|
|
Definitions and Terminology
A
B C
D E
F G
H I
J K
L M
N O
P Q
R S
T U
V W
X Y
Z
Version
(Service Transition) A Version is used to identify a specific Baseline of a Configuration Item. Versions typically use a naming convention that enables the sequence or date of each Baseline to be identified. For example Payroll Application Version 3 contains updated functionality from Version 2.
source: ITIL v3, Service Operation, 2007
(Service Transition) A Version is used to identify a specific Baseline of a Configuration Item. Versions typically use a naming convention that enables the sequence or date of each Baseline to be identified. For example Payroll Application Version 3 contains updated functionality from Version 2.
source: ITIL v3, Service Design, 2007
(Service Transition) A Version is used to identify a specific Baseline of a Configuration Item. Versions typically use a naming convention that enables the sequence or date of each Baseline to be identified. For example, Payroll Application Version 3 contains updated functionality from Version 2.
source: ITIL v3, Service Transition, 2007
(Service Transition) A Version is used to identify a specific Baseline of a Configuration Item. Versions typically use a naming convention that enables the sequence or date of each Baseline to be identified. For example Payroll Application Version 3 contains updated functionality from Version 2.
source: ITIL v3, Continual Service Improvement, 2007
(Service Transition) A Version is used to identify a specific Baseline of a Configuration Item. Versions typically use a naming convention that enables the sequence or date of each Baseline to be identified. For example Payroll Application Version 3 contains updated functionality from Version 2.
source: ITIL v3, Service Strategy, 2007
| Copyright 2006-2008. All Rights Reserved. | Something missing on this page? Let us know |