Loading [MathJax]/extensions/MathMenu.js

Best practices for technical aspects of software testing in enterprises | IEEE Conference Publication | IEEE Xplore

- Donate
- Personal Sign In

ADVANCED SEARCH

Conferences >2010 International Conference...

Best practices for technical aspects of software testing in enterprises

Download PDF
Download References
Request Permissions
Save to
Alerts

Abstract:

Software testing is essential for the creation of high quality software products. Since it is an expensive task and hard to manage, its organizational implementation has ...Show More

Metadata

Abstract:

Software testing is essential for the creation of high quality software products. Since it is an expensive task and hard to manage, its organizational implementation has to be well founded. We worked with regional companies in order to learn about their distinct weaknesses and strengths in software development. Eventually, we deduced best practices for software testing. In this paper we sketch the research methodology used. We present four important best practices focusing on technical aspects of testing in organizations. For each of the four recommendations we give implementation advice based on a categorization framework.

Published in: 2010 International Conference on Information Society

Date of Conference: 28-30 June 2010

Date Added to IEEE Xplore: 15 September 2011

ISBN Information:

DOI: 10.1109/i-Society16502.2010.6018823

Conference Location: London, UK

References is not available for this document.

1. Introduction

The strive to improve software quality is no new emergence. The idea to optimize technical aspects respectively to use technology to achieve this aim is known for decades. Unsurprisingly, the term software engineering [20] has been coined in the 1960s and the software crisis is known – and unfortunately still lasting – since the 1970s [8].

Select All

1.

R. Black. Pragmatic Software Testing. Wiley, Indianapolis, 2007.

2.

R. Black. Managing the Testing Process. Wiley, Indianapolis, 3rd edition, 2009.

3.

J. Bloch. Effective Java. Prentice Hall, Upper Saddle River, 2nd edition, 2008.

4.

F. P. Brooks, Jr. The mythical man-month (anniversary ed.). Addison-Wesley, Boston, 1995.

5.

Y. E. Chan and B. H. Reich. IT alignment: what have we learned? Journal of Information Technology, 22, 2007.

CrossRef Google Scholar

6.

R. N. Charette. Why software fails. IEEE Spectrum, 42(9):42-49, 2005.

7.

M. F. Cowlishaw. Lexx - a programmable structured editor. IBM J. of Research and Development, 31(1):73-80, 1987.

8.

E. Dijkstra. The humble programmer. Communications of the ACM, 15:859-866, 1972.

CrossRef Google Scholar

9.

Eclipse marketplace. Online: http://marketplace.eclipse.org/ (Access date: 09 March 2010).

10.

T. Groetker, U. Holtmann, H. Keding, and M. Wloka. The Developer's Guide to Debugging. Springer, 2008.

11.

A. R. Hevner, S. T. March, J. Park, and S. Ram. Design science in information systems research. MIS Quarterly, 28(1), 2004.

CrossRef Google Scholar

12.

IEEE. IEEE Std 829-2008: IEEE standard for software and system test documentation. New York, 2008.

13.

D. Kopec and S. Tamang. Failures in complex systems: case studies, causes, and possible remedies. SIGCSE Bulletin, 39(2):180-184, 2007.

CrossRef Google Scholar

14.

W. E. Lewis. Software Testing and Continuous Quality Improvement. Auerbach, Boston, 3rd edition, 2008.

CrossRef Google Scholar

15.

T. A. Majchrzak. Best practices for the organizational implementation of software testing. In Proc. of the 43th Annual Hawaii Int. Conf. on System Sciences (HICSS-43). IEEE Computer Society, 2010.

16.

T. A. Majchrzak and H. Kuchen. Handlungsempfehlungen für erfolgreiches Testen von Software in Unternehmen. In J. Becker, H. Grob, B. Hellingrath, S. Klein, H. Kuchen, U. Müller-Funk, and G. Vossen, editors, Arbeitsbericht Nr. 127. Inst. für WI, WWU Münster, 2010.

17.

S. Meyers. Effective C++: 55 Specific Ways to Improve Your Programs and Designs. Addison-Wesley, 3rd edition, 2005.

18.

M. D. Myers. Qualitative research in information systems. MIS Quarterly, 21(2):241-242, 1997.

CrossRef Google Scholar

19.

NASA. Mars climate orbiter mishap investigation board phase I report, 1999.

20.

P. Naur and B. Randell. Software Engineering: Report of a conf. spon. by the NATO Science Committee, Garmisch, Germany. Scientific Affairs Division, NATO, 1969.

21.

T. Parveen, S. Tilley, and G. Gonzalez. A case study in test management. In ACM-SE 45: Proceedings of the 45th annual southeast regional conference, pages 82-87, New York, 2007. ACM. (Pubitemid 46737709)

CrossRef Google Scholar

22.

H. A. Simon. The sciences of the artificial. MIT Press, Cambridge, 3 edition, 1996.

23.

Sun Microsystems, Inc. Code Conventions for the Java Programming Language. Online: http://java.sun.com/docs/codeconv/ (Access date: 09 March 2010).

24.

H. Sutter and A. Alexandrescu. C++ Coding Standards. Addison-Wesley, 2004.

25.

J. Watkins. Testing IT: an off-the-shelf software testing process. Cambridge University Press, New York, 2001.

CrossRef Google Scholar

26.

R. K. Yin. Case Study Research: Design and Methods. Sage Publications, London, 3rd edition, 2002.

References is not available for this document.