Service Validation and Testing: Difference between revisions

From IT Process Wiki
No edit summary
 
Line 1: Line 1:
{|
<imagemap>
! align="right" width="80%"|
Image:ITIL-Wiki-de-es.jpg|Service Validation and Testing|100px
! style="background:#DDDDDD;" align="right" width="20%"| [https://wiki.de.it-processmaps.com/index.php/Service-Validierung_und_Test_-_Service_Validation_and_Testing diese Seite auf Deutsch]
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/Service-Validierung_und_Test diese Seite auf Deutsch]
|}
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/ITIL_Validacion_y_Pruebas_de_Servicios esta página en español]
desc none
</imagemap>
<br style="clear:both;"/>


'''ITIL Version''': ITIL Version 3 (ITIL V3)
== ITIL Service Validation and Testing: Overview ==


'''Process Objective''': To ensure that deployed releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service.
'''Process Objective''': To ensure that deployed releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service.
Line 10: Line 13:
'''Part of''': [[ITIL V3 Service Transition|Service Transition]]
'''Part of''': [[ITIL V3 Service Transition|Service Transition]]


'''Process Owner''': [[Roles within ITIL V3#ITIL V3 roles and boards within Service Transition|Test Manager]]
'''Process Owner''': [[Service Validation and Testing#ITIL Roles in Service Validation and Testing|Test Manager]]




==ITIL V3 vs. ITIL V2: Service Validation and Testing==
== ITIL Service Validation and Testing: Process Definition ==


* Service Validation and Testing is new process in ITIL V3; ITIL V2 covered some aspects of Release testing within Release Management but ITIL V3 provides considerably enhanced guidance
<imagemap>
* Major additions in ITIL V3 are details on the various testing stages during Service Transition and descriptions of the corresponding testing approaches
Image:overview_service_validation_and_testing_itilv3_thumb.jpg|left|Service Validation and Testing|350px|thumb
default [https://wiki.en.it-processmaps.com/images/pdf/process_overview_service_validation_and_testing_itilv3.pdf Service Validation and Testing (.pdf)]
desc bottom-left
</imagemap>


Service Validation and Testing is new process in ITIL V3; ITIL V2 covered some aspects of Release testing within [[Release Management]] but ITIL V3 provides considerably enhanced guidance. Major additions in ITIL V3 are details on the various testing stages during [[ITIL V3 Service Transition|Service Transition]] and descriptions of the corresponding testing approaches.


==Sub-Processes of Service Validation and Testing (ITIL V3)==
The following sub-processes are part of [[Service Validation and Testing|Service Validation and Testing according to ITIL V3]]:
<br style="clear:both;"/>


[[Image:overview_service_validation_and_testing_itilv3_thumb.jpg|frame|left|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_service_validation_and_testing_itilv3.pdf  Overview of the Service Validation and Testing Process, ITIL V3 (.pdf)]]]
=== Sub-Processes ===


;Test Model Definition
;Test Model Definition
:Process Objective: To specify in detail how the Release will be tested and quality-assured. In particular, this process defines the testing concept and specific test cases to be used during Service Validation.
:Process Objective: To specify in detail how the Release will be tested and quality-assured. In particular, this process defines the [[Service Validation and Testing#Test Model|testing concept]] and specific test cases to be used during Service Validation.


;Service Design Validation
;Service Design Validation
Line 36: Line 44:


;Service Acceptance Testing
;Service Acceptance Testing
:Process Objective: To verify if all conditions are met for the new service to be activated, and to obtain a binding consent from the customer that the new service fulfils the agreed Service Level Requirements.
:Process Objective: To verify if all conditions are met for the new service to be activated, and to obtain a binding consent from the customer that the new service fulfils the agreed [[Service Level Management#SLR|Service Level Requirements]].




==Roles within Service Validation and Testing (ITIL V3)==
=== ITIL Terms: Service Validation and Testing ===


* [[Roles within ITIL V3#ITIL V3 roles and boards within Service Transition|Test Manager]] (Process Owner)
;<span id="Development Installation QA Documentation">Development/ Install. QA Documentation</span>
* [[Roles within ITIL V3#ITIL V3 roles within Service Design|Compliance Manager]]
:A documentation of tests and quality assurance measures applied during the development or installation of applications, systems and other infrastructure components (e.g. component tests, code walk-throughs, ...). A complete Development/ Installation QA Documentation testifies that the required QA measures were applied prior to handing a Release component over to Release Management.
* [[Roles within ITIL V3#ITIL V3 roles outside the IT organization|Customer]]
 
* [[Roles within ITIL V3#ITIL V3 roles within Service Design|IT Security Manager]]
;<span id="Service Design Validation Report">Service Design Validation Report</span>
* [[Roles within ITIL V3#ITIL V3 roles and boards within Service Transition|Release Manager]]
:A report summarizing the results of the Service Design Validation testing activities, documenting that the Service Design Package correctly matches the Service Requirements.
* [[Roles within ITIL V3#ITIL V3 roles within Service Design|Service Level Manager]]
 
* [[Roles within ITIL V3#ITIL V3 roles outside the IT organization|User]]
;<span id="Testing Script">Testing Script</span>
:A detailed set of instructions for testing certain aspects of an application or infrastructure item. The Testing Script essentially defines the activities to be carried out and the expected outcomes.
 
;<span id="Test Model">Test Model</span>
:A Test Model is created during the Release planning phase to specify in detail the testing approach used for deploying a Release into the productive environment. It is an important input for the Project Plan. Most importantly, this document defines the required quality assurance checkpoints during the Release deployment.
 
;<span id="Validation Test Report">Validation Test Report</span>
:A Validation Test Report summarizes the results of testing and assessment activities, documenting that the assessed Release components successfully passed a validation stage.
 
== Additional Information on Service Validation and Testing ==
 
==== ITIL KPIs ====
* [[ITIL KPIs Service Transition#ITIL KPIs Service Validation and Testing|Key Performance Indicators (KPIs) Service Validation and Testing]]
 
 
==== ITIL Roles in Service Validation and Testing ====
 
;Test Manager - Process Owner
:The Test Manager ensures that deployed Releases and the resulting services meet customer expectations, and verifies that IT operations is able to support the new service.
 
;Compliance Manager
:The Compliance Manager's responsibility is to ensure that standards and guidelines is followed, or that proper, consistent accounting or other practices are being employed.
:This includes to make sure that external legal requirements are fulfilled.
 
;Customer
:Someone who buys goods or services.
:The Customer of an IT Service Provider is the person or group who defines and agrees the service level targets.
 
;IT Security Manager
:The IT Security Manager is responsible for ensuring the confidentiality, integrity and availability of an organization’s assets, information, data and IT services.
:He is usually involved in an organizational approach to Security Management which has a wider scope than the IT service provider, and includes handling of paper, building access, phone calls etc., for the entire organization.
 
;Release Manager
:The Release Manager is responsible for planning, scheduling and controlling the movement of Releases to test and live environments. His primary objective is to ensure that the integrity of the live environment is protected and that the correct components are released.
 
;Service Level Manager
:The Service Level Manager is responsible for negotiating Service Level Agreements and ensuring that these are met.
:He makes sure that all IT Service Management processes, Operational Level Agreements and Underpinning Contracts are appropriate for the agreed service level targets.
:The Service Level Manager also monitors and reports on service levels.
 
;User
:The user of an IT service on the business side.
 
 
 
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Transition|Service Validation & Testing]][[Category:Service Validation & Testing|!]]
<!-- --- -->

Revision as of 10:43, 13 October 2010

Service Validation and Testingdiese Seite auf Deutschesta página en español
Service Validation and Testing


ITIL Service Validation and Testing: Overview

Process Objective: To ensure that deployed releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service.

Part of: Service Transition

Process Owner: Test Manager


ITIL Service Validation and Testing: Process Definition

Service Validation and Testing

Service Validation and Testing is new process in ITIL V3; ITIL V2 covered some aspects of Release testing within Release Management but ITIL V3 provides considerably enhanced guidance. Major additions in ITIL V3 are details on the various testing stages during Service Transition and descriptions of the corresponding testing approaches.

The following sub-processes are part of Service Validation and Testing according to ITIL V3:

Sub-Processes

Test Model Definition
Process Objective: To specify in detail how the Release will be tested and quality-assured. In particular, this process defines the testing concept and specific test cases to be used during Service Validation.
Service Design Validation
Process Objective: To ensure that an IT service meets its functionality and quality requirements and that the service provider is ready to operate the new service when it has been deployed.
Release Component Acquisition
Process Objective: To acquire the components of a Release and submit them to an initial assessment. This process ensures that only components which meet stringent quality criteria are allowed to enter the intensive testing phase.
Release Test
Process Objective: To test all Release Components and all tools and mechanisms required for deployment, migration and back out. This process ensures that only components which meet stringent quality criteria are deployed into the live productive environment.
Service Acceptance Testing
Process Objective: To verify if all conditions are met for the new service to be activated, and to obtain a binding consent from the customer that the new service fulfils the agreed Service Level Requirements.


ITIL Terms: Service Validation and Testing

Development/ Install. QA Documentation
A documentation of tests and quality assurance measures applied during the development or installation of applications, systems and other infrastructure components (e.g. component tests, code walk-throughs, ...). A complete Development/ Installation QA Documentation testifies that the required QA measures were applied prior to handing a Release component over to Release Management.
Service Design Validation Report
A report summarizing the results of the Service Design Validation testing activities, documenting that the Service Design Package correctly matches the Service Requirements.
Testing Script
A detailed set of instructions for testing certain aspects of an application or infrastructure item. The Testing Script essentially defines the activities to be carried out and the expected outcomes.
Test Model
A Test Model is created during the Release planning phase to specify in detail the testing approach used for deploying a Release into the productive environment. It is an important input for the Project Plan. Most importantly, this document defines the required quality assurance checkpoints during the Release deployment.
Validation Test Report
A Validation Test Report summarizes the results of testing and assessment activities, documenting that the assessed Release components successfully passed a validation stage.

Additional Information on Service Validation and Testing

ITIL KPIs


ITIL Roles in Service Validation and Testing

Test Manager - Process Owner
The Test Manager ensures that deployed Releases and the resulting services meet customer expectations, and verifies that IT operations is able to support the new service.
Compliance Manager
The Compliance Manager's responsibility is to ensure that standards and guidelines is followed, or that proper, consistent accounting or other practices are being employed.
This includes to make sure that external legal requirements are fulfilled.
Customer
Someone who buys goods or services.
The Customer of an IT Service Provider is the person or group who defines and agrees the service level targets.
IT Security Manager
The IT Security Manager is responsible for ensuring the confidentiality, integrity and availability of an organization’s assets, information, data and IT services.
He is usually involved in an organizational approach to Security Management which has a wider scope than the IT service provider, and includes handling of paper, building access, phone calls etc., for the entire organization.
Release Manager
The Release Manager is responsible for planning, scheduling and controlling the movement of Releases to test and live environments. His primary objective is to ensure that the integrity of the live environment is protected and that the correct components are released.
Service Level Manager
The Service Level Manager is responsible for negotiating Service Level Agreements and ensuring that these are met.
He makes sure that all IT Service Management processes, Operational Level Agreements and Underpinning Contracts are appropriate for the agreed service level targets.
The Service Level Manager also monitors and reports on service levels.
User
The user of an IT service on the business side.