testing process improvement

29
Testing Process Improvement

Upload: api-3699222

Post on 13-Nov-2014

126 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Testing Process Improvement

Testing Process Improvement

Page 2: Testing Process Improvement

2

Goal with this Presentation

Need for process improvement.Present an idea, TMM and TPI.Describe the process which build up TMMDifference between the TMM and TPI

Page 3: Testing Process Improvement

3

Test Process Improvement: Why?

Increasing importance and size of software in society as a whole

Testing often takes 30 - 40% of project costs.How do we improve the efficiency of software testing, and

at the same time reduce the cost of testing? In other words, how do we make software testing both better and cheaper? The answer of course is process improvement.

Page 4: Testing Process Improvement

4

Purpose of TMM

The purpose of the TMM is to assist software organizations with assessing and improving their software testing processes.

Page 5: Testing Process Improvement

5

TMM’s development History

Developed by IIT (Illinois Institute of Technology). Component CMM on areas of interest. Any organization that wishes to improve its testing process

by use of the TMM first commit to improving its overall software development process by application of the CMM. (Testing process is a subset of the overall software development process; therefore, its maturity growth needs support from the KPAs associated with general process growth )

Page 6: Testing Process Improvement

6

What is TMM

A maturity model with focus on following pointsDescribes the processes, which are the basic in order to

ensure a well planned and controlled test part of a project.5 level of maturity in testing.Inspired by CMMThe model aims at raising through the 5 levels of maturity.The higher the level of maturity, higher is the quality of

software being developed.

Page 7: Testing Process Improvement

7

TMM – usability

The TMM can be used by: . Internal teams to evaluate the current testing maturity . Management to launch specific improvement initiatives . Development projects to improve a specific test . Users and contractors to define their roles in testing

Page 8: Testing Process Improvement

8

Process Flow of Test Process Improvement.

Page 9: Testing Process Improvement

9

TMM’s 2 Main ComponentA Set of LevelsTMM consist of 5 levels each level represents a stage in evaluation to a

mature testing process.A set of maturity goals for each level and activities, task and

responsibilities needed to support them.For each maturity level, a number of process areas are defined. A

process area is a cluster of related activities within the test process, e.g. test planning or test training.

An Assessment ModelsA set of maturity related goal questions. They will help determine to

what extent the organization has mechanisms in place to achieve those goals and for resolving the maturity issues.

An assessment methodA training program design to select and instruct the evaluation team.

Page 10: Testing Process Improvement

10

TMM Maturity Goals By Level

Page 11: Testing Process Improvement

11

Maturity Goals Level 1- Initial

There are no maturity goals at this level.Tests are developed in an ad hoc way after coding is done.Testing and debugging activities go hand-in-hand to get the

defects out of the software.The objective of testing is to show that the software works/

runs.

Page 12: Testing Process Improvement

12

Maturity Goals Level 2-Phase Definition

Develop Testing and Debugging goalsA life cycle phase that follows codingInitiate a Test planning processBasic testing techniques and methods are used during

testing.No reviews to address early defectsThe objective of testing is to show that the software meets

its specification

Page 13: Testing Process Improvement

13

Maturity Goals Level 3- Integration

Software Test OrganizationTechnical Training ProgramIntegrate Testing into Software LifecycleControl and Monitor Testing Process.Objective : to provide insight into the quality of the product,

Page 14: Testing Process Improvement

14

Monitoring and Control

Test Project

Plan Monitorplanplan

deviations

deviationschanges

changes

RiskRisk Project DataProject Data

Product qualityProduct qualityExit criteriaExit criteria

DeliverablesDeliverables

EffortEffortCostCost

ScheduleScheduleControl

Page 15: Testing Process Improvement

15

Maturity Goals Level 4- Management & Measurement

Establish Review ProgramEstablish a Test Measurement Program.Software Quality Evaluation

Page 16: Testing Process Improvement

16

Level 5- Optimization, Defect Prevention and Quality Control

Application of process data for defect prevention.Quality ControlTest Process Optimization The objective of testing is to prevent defects from re-

occurring in the future

Page 17: Testing Process Improvement

17

Support for TMM maturity levels

TMMTMM CMMCMM

2 2 Requirements management, project planning and Requirements management, project planning and software configuration managementsoftware configuration management

3 2 Project tracking SQAProject tracking SQA

3 3 Organization process focus, organization process definition and training Organization process focus, organization process definition and training programsprograms

4 3 Intergroup coordination, Peer reviewsIntergroup coordination, Peer reviews

4 4 Software quality management and Quantitative process managementSoftware quality management and Quantitative process management

5 5 Process change management, technology changeProcess change management, technology changemanagement and defect preventionmanagement and defect prevention

Supporting Key Process AreasSupporting Key Process Areas

Page 18: Testing Process Improvement

18

TMM Summary

Baseline the current testing process level of maturityIdentify areas that can be improved identify testing

processes that can be adopted organization-wideProvide a road map for implementing the improvementsProvide a method for measuring the improvement results

Page 19: Testing Process Improvement

19

TPI (Test Process Improvement)

The Test Process Improvement (TPI®)-model offers insight in the 'maturity' of test processes within your organization.

The TPI has been developed by Sogeti, a wholly owned subsidiary of the international Capgemini organization. It goes hand in hand with the Test Management Approach (TMap) which is also a testing methodology from Sogeti.

This model has four basic components - 1. Key Areas 2. Levels 3. Checkpoints 4. Improvement Suggestions

Page 20: Testing Process Improvement

20

Model Description

Each of the above key areas is assessed at various levels like A, B, C and D.

The number of levels for all the key areas is not the same. For e.g. ‘Static Testing Techniques’ key area has only two levels – A and B. However, ‘Test Strategy’ has 4 levels – A, B, C and D.

Each level has certain checkpoints for each of the key areas.

The test process under assessment should satisfy these checkpoints to be certified for that level.

The model also includes improvement suggestions to assist the organizations in achieving higher levels of maturity.

Page 21: Testing Process Improvement

21

TPI Model

Page 22: Testing Process Improvement

22

Key AreasLife cycle 1. Test Strategy 2. Lifecycle Model 3. Moment of involvementTechniques 4. Estimating and Planning 5. Test Specification Techniques 6. Static Test Techniques 7. MetricsInfrastructure 8. Test Automation 9. Test Environment 10. Office EnvironmentOrganization 11. Commitment and Motivation 12. Testing Functions and Trainings 13. Scope of Methodology 14. Communication 15. Reporting 16. Defect Management 17. Test ware Management 18. Test Process ManagementAll Cornerstones 19. Evaluation 20. Low-level Testing

Page 23: Testing Process Improvement

23

Page 24: Testing Process Improvement

24

Page 25: Testing Process Improvement

25

Test Maturity Matrix

The Test Maturity Matrix relates Levels to Key Areas.It does so by expressing the internal priorities and

dependencies between Levels and Key Areas.It illustrates the strong and weak points of the current test

process. This aids the prioritizing of actions for improvement.

In the matrix each level is related to a certain scale of test maturity. This results in 13 scales of test maturity.

The open cells between different levels have no meaning in themselves, but indicate that achieving a higher maturity for a key area is related to the maturity of other key areas

Page 26: Testing Process Improvement

26

Test Maturity Matrix

Page 27: Testing Process Improvement

27

Test Maturity Matrix

Indicates the level of maturity of each key area .As we go from left to right in the matrix, our testing process

becomes more and more sophisticated from Controlled to Efficient to Optimizing.

For example, to start with static testing techniques (at level A), the moment of involvement must be at level A also. Due to this dependency, the level A of moment of involvement is earlier than level A of the Static testing techniques.

The blanks in the test matrix essentially mean nothing and are present to take care of the dependencies.

Level 0 indicates that the key area does not exist in the current testing process.

Page 28: Testing Process Improvement

28

TPI Summary

The TPI model offers objective procedures for classifying the current situation of the test process. Additionally, the model offers assistance for test process improvement in the form of key areas, levels and improvement suggestions.

means of checkpoints it is possible to determine the levels of key areas that a test process is on.

The different maturity levels and key areas and their dependencies are presented in the Test Maturity Matrix.

Page 29: Testing Process Improvement

29

Comparison of TMM and TPI

TMM TPI

Complements CMMi Associated closely with TMap

Includes all levels of testing Focus on high level tests

Research Product Commercial Product

Contains 5 levels Contains 13 scales of maturity

Follows staged progress Follows continuous process