• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • 1
    CommentGo Back
Download
 
 
Using the Testing Maturity Model
SM
 in practical test-planningand post-evaluation
 
Author
 
Klaus Olsen Poul Staal Vinje
Consultant ConsultantSoftwaretest.dk VR PartnersDenmark Denmark Email: Email:klaus@softwaretest.dk  psv@ddf.dk   Tel: +45 4615 5012 Tel: +45 4615 5012
Abstract
We have used the Testing Maturity Model (TMM
SM
 ), as the basis for an evaluation of real-worldtesting.We have found that in addition to being useful in the overall maturity improvement in anorganisation, the TMM is useful in the planning process of testing activities. Futhermore the TMMis useful in the post-evaluation of the testing process.TMM is so far lacking a formal assessment model, but the levels and recommended practices areuseful in the evaluation.
SM
Testing Maturity Model, registered service marks of Illinois Institute of Technology.
SM
TMM, registered service marks of Illinois Institute of Technology.
 
Author Klaus Olsen and Poul Staal Vinje EuroSTAR ‘98 Page 2 of 6
Improving the Software Testing Process
The task
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. Klaus Olsen and Poul Staal Vinje work with software testing at anoperational level, but in addition to this they work with some of the various models available forSoftware Process Improvements (SPI).
The need
The need for efficient software testing has always existed, because the users expect software thatworks. The need for process improvement is apparent, due to the number of defects delivered, andthe time and money consumed in testing.We expect that the future will present even more extensive demands to the testing process. Webelieve that users will demand better technical quality, and we expect development organisations todemand less expensive testing.
The solution
The solution is not more people equipped with more tools. As already mentioned, the solution isprocess improvement. The ’Testing Maturity Model’ (TMM) [1] is developed with this purpose. Itis an extension to CMM
SM
 and SPICE. Choosing the TMM is a perfectly good choice, and we willwork with this and other SPI-models in the future.
The history
TMM has been developed by Ilene Burnstein, et al. at Computer Science Department at IllinoisInstitute of Technology. It reflects the maturity growth through 5 levels well known from SoftwareEngineering Institute’s Capability Maturity Model (CMM) [2]. Burnstein also refers to the fiveperiods in the evolution of testing model proposed by Gelperin and Hetzel [3], and the parallel toBeizers' five-phase model of an individual tester's maturity growth [4]. To sum up, we see TMM asthe result of many people’s work during the last decade on defining useful process improvementswhich also will be useful in testing.
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
TMM – the model
TMM consist of 5 levels of testing maturity, each level with maturity goals identifying testingimprovements that must be addressed to achieve the next level. See figure 1.
SM
CMM, registered service marks of Carnegie Mellon University.
 
Author Klaus Olsen and Poul Staal Vinje EuroSTAR ‘98 Page 3 of 6
Level 5: Optimization, Defect
 
Prevention, and Quality Control
•
Test process optimization
•
Quality control
•
Application of process data for defectprevention
 
Level 4: Management and
 
Measurement
•
Software quality evaluation
•
Establish a test measurement program
•
Establish an organization-wide reviewprogram
 
Level 3: Integration
•
Control and monitor the testing process
•
Integrate testing into the software lifecycle
•
Establish a technical training program
•
Establish a software test organization
 
Level 2: Phase Definition
•
Institutionalize basic testing techniquesand methods
•
Initiate a test planning process
•
Develop testing and debugging goals
 
Level 1: Initial
 
Figure 1, Testing Maturity Model with maturity goals at each level.
More information
You will find detailed information in the two article “Developing a Testing Maturity Model: Part Iand II” [1] which were publicised in U.S. Air force magazine Crosstalk, August and September1996.
Our experiment
What we have done is to try to take advantage of the TMM in terms of predicting the cause of atesting process. The background is that our clients typically is at level 1 or 2. Advancing one levelusually means working with SPI for 1-2 years. This is acceptable, and most of them work withimprovements.But if the model addresses the correct issues, it should be possible to use it as an instrument forprediction. We use other models for prediction the success of testing. They are “home-made” in thesense that they build on practical experience and observations. If the TMM refers to relevant, and
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
narayanmoorthy

hi sumit: can u help me find info tech professional for an overseas posting with the following skills please: my email id is narayanhk@gmail.com Automation Test Engineer Job Description: (QTP with BPT Frame work) u Analysis and planning of test cases u Plan automation u Automation of test cases. u Defect logging u Regression testing. u Effort Estimation u Reporting Requirement:

reply02 / 01 / 2010
You must be to leave a comment.
Submit
Characters: ...