Is 100% Test Coverage a Reasonable Requirement? Lessons Learned from a Space Software Project

被引:9
|
作者
Prause, Christian R. [1 ]
Werner, Juergen [2 ]
Hornig, Kay [2 ]
Bosecker, Sascha [2 ]
Kuhrmann, Marco [3 ]
机构
[1] German Aerosp Ctr, Bonn, Germany
[2] Test Spacecom GmbH, Backnang, Germany
[3] Tech Univ Clausthal, Inst Appl Software Syst Engn, Goslar, Germany
关键词
Validation and verification; Software quality; Unit testing; Test coverage; Expert interviews; Spaceflight; Software criticality; Process requirements;
D O I
10.1007/978-3-319-69926-4_25
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
To ensure the dependability and safety of spaceflight devices, rigorous standards are defined. Among others, one requirement from the European Cooperation for Space Standardization (ECSS) standards is 100% test coverage at software unit level. Different stakeholders need to have a good knowledge of the implications of such a requirement to avoid risks for the project that this requirement might entail. In this paper, we study if such a 100% test coverage requirement is a reasonable one. For this, we interviewed the industrial developers who ran a project that had the sole goal of achieving 100% unit test coverage in a spaceflight software. We discuss costs, benefits, risks, effects on quality, interplay with surrounding conditions, and project management implications. We distill lessons learned with which we hope to support other developers and decision makers when considering a 100% unit test coverage requirement.
引用
收藏
页码:351 / 367
页数:17
相关论文
共 50 条
  • [1] Lessons Learned from a Scientific Software Development Project
    Morris, Chris
    Segal, Judith
    IEEE SOFTWARE, 2012, 29 (04) : 9 - 12
  • [2] Software project failure lessons learned
    Chisham, D
    COMMUNICATIONS OF THE ACM, 1999, 42 (11) : 22 - 23
  • [3] Software Engineering Team Project lessons learned
    Hnatkowska, Bogumila
    E-INFORMATICA SOFTWARE ENGINEERING JOURNAL, 2013, 7 (01) : 77 - 85
  • [4] Software project failure lessons learned - Response
    Glass, R
    COMMUNICATIONS OF THE ACM, 1999, 42 (11) : 24 - 24
  • [5] Automatic recall of software lessons learned for software project managers
    Abdellatif, Tamer Mohamed
    Capretz, Luiz Fernando
    Ho, Danny
    INFORMATION AND SOFTWARE TECHNOLOGY, 2019, 115 : 44 - 57
  • [6] Clinical software development for the Web: lessons learned from the BOADICEA project
    Alex P Cunningham
    Antonis C Antoniou
    Douglas F Easton
    BMC Medical Informatics and Decision Making, 12
  • [7] Project risk management: lessons learned from software development environment
    Kwak, YH
    Stoddard, J
    TECHNOVATION, 2004, 24 (11) : 915 - 920
  • [8] Clinical software development for the Web: lessons learned from the BOADICEA project
    Cunningham, Alex P.
    Antoniou, Antonis C.
    Easton, Douglas F.
    BMC MEDICAL INFORMATICS AND DECISION MAKING, 2012, 12
  • [9] Results and Lessons Learned From Nanosatellite Space Environment Test
    Kim, Hae-Dong
    Choi, Won-Sub
    Kim, Min-Ki
    Kim, Jin-Hyung
    Kim, KiDuck
    Kim, Ji-Seok
    Cho, Dong-Hyun
    JOURNAL OF THE KOREAN SOCIETY FOR AERONAUTICAL AND SPACE SCIENCES, 2021, 49 (11) : 919 - 931
  • [10] Lessons learned and not learned from the SUPPORT project
    Teno, JM
    PALLIATIVE MEDICINE, 1999, 13 (02) : 91 - 93