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

来源：

PRODUCT-FOCUSED SOFTWARE PROCESS IMPROVEMENT (PROFES 2017) | 2017年 / 10611卷

关键词：

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 条

[41] Lessons learned from incorporation of commercial computer aided software engineering tools in a flight critical software test environment
Hagar, J
15TH DASC - AIAA/IEEE DIGITAL AVIONICS SYSTEMS CONFERENCE, 1996, : 125 - 130
[42] Lessons learned from infrastructure operation in the CUTE project
Stolzenburg, K.
Tsatsami, V.
Grubel, H.
INTERNATIONAL JOURNAL OF HYDROGEN ENERGY, 2009, 34 (16) : 7114 - 7124
[43] @Baycrest - Lessons learned from an Intranet development project
Crockford, S
Phillips, J
JOURNAL OF THE AMERICAN MEDICAL INFORMATICS ASSOCIATION, 2001, : 815 - 815
[44] Lessons learned from an overambitious undergraduate research project
Trethewey, Samuel P.
CLINICAL TEACHER, 2019, 16 (02): : 168 - 168
[45] Lessons learned from a nationwide CBD promotion project
Kim, SD
COMMUNICATIONS OF THE ACM, 2002, 45 (10) : 83 - 87
[46] Lessons learned from an emergency bridge replacement project
Bai, Y
Burkett, WR
Nash, PT
JOURNAL OF CONSTRUCTION ENGINEERING AND MANAGEMENT-ASCE, 2006, 132 (04): : 338 - 344
[47] Lessons learned from the Case Study Zagreb Project
Skanata, D
Subasic, D
INTERNATIONAL JOURNAL OF ENVIRONMENT AND POLLUTION, 1996, 6 (4-6) : 662 - 682
[48] Architecture and ageing: lessons learned from a cohousing project
Schaff, Gwendoline
Vanrie, Jan
Courtejoie, Fabienne
Elsen, Catherine
Petermans, Ann
JOURNAL OF HOUSING AND THE BUILT ENVIRONMENT, 2023, 38 (04) : 2345 - 2371
[49] Lessons learned from the Hospital Without Walls project
Dadd, M
Doyle, B
Wilson, L
Gunaratnam, M
JOURNAL OF TELEMEDICINE AND TELECARE, 2002, 8 : 11 - 14
[50] Lessons learned from the prospective pravastatin pooling project
Byington R.P.
Sacks F.M.
Current Atherosclerosis Reports, 2004, 6 (5) : 366 - 374

← 1 2 3 4 5 →