You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Experiments with Component Tests to Improve Software Quality

Fulltext:


Authors:

Sigrid Eldh, Sasikumar Punnekkat, Hans Hansson

Publication Type:

Conference/Workshop Paper

Venue:

ISSRE (Industrial Track)

Publisher:

IEEE

Abstract

In commercial systems, time to market pressure often result in short cuts in the design phase where component test is most vulnerable. It is hard to define how much testing is cost effective by the individual developers, and hard to judge when testing is enough. Verification activities constitute a major part of the product cost. Failures unearthed during later phases of product development escalate the cost substantially. To reduce cost in later stages of testing by reducing failures is important not only for Ericsson, but for any software producer. At Ericsson, we created a scheme, Software Quality Rank (SQR). SQR is a way to improve quality on components. SQR consists of five steps, where the first is where the actual “ranking” of components takes place. Then a selection of components is targeted for improvement in five levels. Most components are targeted for rank 3, which is the cost-efficient quality level. Rank 5 is the target for safety-critical code. The goal of SQR was to provide developers with a tool that prioritizes what to do before delivery to next system test phase. SQR defines a stepwise plan, which describes how much and what to test on component level for each rank. It gives the process for how to prioritize components; re-introduces reviews; requires usage of static analysis tools and defines what coverage to be achieved. The scheme has been used with great success at different design organizations within and outside Ericsson and we believe it supports industry in defining what cost-efficient component test in a time to market situation.

Bibtex

@inproceedings{Eldh1092,
author = {Sigrid Eldh and Sasikumar Punnekkat and Hans Hansson},
title = {Experiments with Component Tests to Improve Software Quality},
month = {November},
year = {2007},
booktitle = {ISSRE (Industrial Track)},
publisher = {IEEE},
url = {http://www.es.mdu.se/publications/1092-}
}