London software testing news UK


Posted in Software testing by testing in London on December 17, 2009

From Akrim Online

Validation and test management Plan and design test Verify test plan and test design Prepare test environment Perform tests Evaluate exit criteria and report Test clean up and closure

It should be noted that when implementing these activities for ITIL software testing they will not be undertaken in sequence. In fact, several activities should be done in parallel.

While ITIL does mention many different approaches to testing, one of the main objectives of Service Testing and Validation is to provide quality assurance and establish that the project will deliver a product that is fit for purpose and use. Risk Based test approaches support these objectives and, in particular, reinforce the Project Wide Risk Policy established during the Strategy phase. By determining and populating the appropriate Risk Matrix for an organisation or project, the Risk Policy can be better enforced through the Testing Process. Using a Risk Based approach, ITIL can provide a systematic method to: evaluate requirements; improve test effectiveness and efficiency; report progress; and gain consensus on high risk requirements, can only further support these overall objectives.

One Response to 'QA and ITIL'

Subscribe to comments with RSS or TrackBack to 'QA and ITIL'.

  1. plannetplc said,

    On the subject of moving from v2 to v3, you might find this interesting:

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: