TIM—a test improvement model

Ericson, Thomas; Subotic, Anders; Ursing, Stig

doi:10.1002/(sici)1099-1689(199712)7:4<229::aid-stvr149>3.3.co;2-d

Cited by 8 publications

(10 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The model itself does not describe how inspections should be improved, but the assessment process can give an idea about improvement actions that might be useful to take. Similar models have been created for software testing 15, maintenance 16 and project management 17.…”

Section: Related Workmentioning

confidence: 99%

“…Few maturity models, such as TIM 15 and TMM 19, have been presented for software testing. Both the models include reviews as a part of the test process.…”

Section: Related Workmentioning

confidence: 99%

“…Also, the individual maturity levels more or less follow the levels in CMMI. This seems to be a widely adopted way to describe a model for process improvement 6, 15–17.…”

Section: Icmm‐modelmentioning

confidence: 99%

“…ICMM adopts the idea of CMMI and applies it specifically to software inspections. Such models have also been created for software testing 15, maintenance 16 and project management 17.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

ICMM—a maturity model for software inspections

Kollanus

2011

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

Software inspection is widely acknowledged as an important method in software engineering. However, there is a need to better understand how to implement and improve inspection practices. This paper introduces Inspection Capability Maturity Model (ICMM), which provides support for assessment and improvement of software inspection practices in a software organization. The model has been developed iteratively based on a comprehensive literature survey and experiences from eight case organizations. This paper includes a detailed description of the used followed research process, the structure of ICMM and the rationale for the defined criteria. Additionally, the role of this kind of model in inspection process improvement is discussed. Copyright © 2010 John Wiley & Sons, Ltd.

show abstract

Section: Related Workmentioning

confidence: 99%

“…Few maturity models, such as TIM 15 and TMM 19, have been presented for software testing. Both the models include reviews as a part of the test process.…”

Section: Related Workmentioning

confidence: 99%

“…Also, the individual maturity levels more or less follow the levels in CMMI. This seems to be a widely adopted way to describe a model for process improvement 6, 15–17.…”

Section: Icmm‐modelmentioning

confidence: 99%

“…ICMM adopts the idea of CMMI and applies it specifically to software inspections. Such models have also been created for software testing 15, maintenance 16 and project management 17.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

ICMM—a maturity model for software inspections

Kollanus

2011

J. Softw. Maint. Evol.: Res. Pract.

View full text Add to dashboard Cite

show abstract

“…Other CMM-based testing models have been proposed. For example, the Test Improvement Model (TIM) (Ericson et al, 1997) and the Test Process Improvement Model (TPI) (Koomen & Pol, 1999) suggest ways in which testers can improve their work. TIM and TPI identify key areas for the testing process starting from the organization and planning of testing activities to test cases generation, execution, and documentation review.…”

Section: Testing Maturity Modelsmentioning

confidence: 99%

Oss-TMM

Morasca

Taibi

Tosi

2011

International Journal of Open Source Software and Processes

View full text Add to dashboard Cite

Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test & Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.

show abstract

Maintenance of automated test suites in industry: An empirical study on Visual GUI Testing

Alégroth

Feldt

Kolström³

2016

Information and Software Technology

View full text Add to dashboard Cite

Context: Verification and validation (V&V) activities make up 20 to 50 percent of the total development costs of a software system in practice. Test automation is proposed to lower these V&V costs but available research only provides limited empirical data from industrial practice about the maintenance costs of automated tests and what factors affect these costs. In particular, these costs and factors are unknown for automated GUI-based testing.Objective: This paper addresses this lack of knowledge through analysis of the costs and factors associated with the maintenance of automated GUI-based tests in industrial practice.Method: An empirical study at two companies, Siemens and Saab, is reported where interviews about, and empirical work with, Visual GUI Testing is performed to acquire data about the technique's maintenance costs and feasibility.Results: 13 factors are observed that affect maintenance, e.g. tester knowledge/experience and test case complexity. Further, statistical analysis shows that developing new test scripts is costlier than maintenance but also that frequent maintenance is less costly than infrequent, big bang maintenance. In addition a cost model, based on previous work, is presented that estimates the time to positive return on investment (ROI) of test automation compared to manual testing.Conclusions: It is concluded that test automation can lower overall software development costs of a project whilst also having positive effects on software quality. However, maintenance costs can still be considerable and the less time a company currently spends on manual testing, the more time is required before positive, economic, ROI is reached after automation.

show abstract

TIM—a test improvement model

Cited by 8 publications

References 0 publications

ICMM—a maturity model for software inspections

ICMM—a maturity model for software inspections

Oss-TMM

Maintenance of automated test suites in industry: An empirical study on Visual GUI Testing

Contact Info

Product

Resources

About