Computing Reviews
Today's Issue Hot Topics Search Browse Recommended My Account Log In
Review Help
Search
Improving software testing by observing practice
Taipale O., Smolander K.  International symposium on empirical software engineering (Proceedings of the 2006 ACM/IEEE International Symposium on Empirical Software Engineering, Rio de Janeiro, Brazil, Sep 21-22, 2006)262-271.2006.Type:Proceedings
Date Reviewed: Jun 18 2007

Taipale and Smolander report on an extensive qualitative study of software testing. They conducted 41 interviews with development and testing managers, testers, and system analysts. In total, 946 pages of transcribed interview data were analyzed, using the grounded theory approach and ATLAS.ti software. The analysis yielded seven dimensions that were used to distinguish five representative organizational units (called cases). For example, the dimension “level of business orientation” varied from purely service oriented (case E), to purely product oriented (case D).

The authors discuss various cause and effect pairs. For example, greater use of software components creates a demand for components that are more testable. The authors also list five process improvement propositions. Proposition 1 states that testing should be adjusted according to business orientation. Proposition 2 calls for enhanced testability of software components. Proposition 3 calls for efficient communication and interaction between development and testing. Proposition 4 calls for the early involvement of testing and planning for testing. Proposition 5 calls for the use of risk-based testing.

The authors ambitiously set out to establish a theory of software testing from the ground up. Disappointingly, the emergent five propositions are largely already well understood. In addition, the authors should have critically reflected on the qualitative methodology they used, since analyzing 946 pages of transcripts is far from light work. To establish a theory of software testing, building a business simulation model based on the existing extensive literature on software testing might have been more productive. This paper will be of passing interest, only to those involved in software process improvement.

Reviewer:  Andy Brooks Review #: CR134425 (0805-0484)
Bookmark and Share
  Featured Reviewer  
 
Productivity (D.2.9 ... )
 
 
Software Management (K.6.3 )
 
 
Software/ Program Verification (D.2.4 )
 
 
Testing And Debugging (D.2.5 )
 
Would you recommend this review?
yes
no
Other reviews under "Productivity": Date
Productivity sand traps and tar pits
Walsh M., Dorset House Publ. Co., Inc.,  New York, NY, 1991. Type: Book (9780932633217)
Jun 1 1992
Effects of individual characteristics, organizational factors and task characteristics on computer programmer productivity and job satisfaction
Cheney P. Information and Management 7(4): 209-214, 1984. Type: Article
Jan 1 1986
Managing programming productivity
Jeffery D. (ed), Lawrence M. Journal of Systems and Software 5(1): 49-58, 1985. Type: Article
Sep 1 1985
more...

E-Mail This Printer-Friendly
Send Your Comments
Contact Us
Reproduction in whole or in part without permission is prohibited.   Copyright 1999-2024 ThinkLoud®
Terms of Use
| Privacy Policy