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 条

[21] Lessons learned from the human genome project
Nebert, DW
DRUG METABOLISM REVIEWS, 2002, 34 : 1 - 1
[22] Lessons learned from an eXtremely distributed project
Hogan, Ben
AGILE 2006, Proceedings, 2006, : 321 - 326
[23] LESSONS LEARNED FROM THE MACHACOS PROJECT IN KENYA
VANGINNEKEN, JK
OMONDIODHIAMBO
POPULATION INDEX, 1985, 51 (03) : 385 - 385
[24] Lessons learned from a Hospital Intranet Project
Helland, O
Oyri, K
MEDICAL INFOBAHN FOR EUROPE, PROCEEDINGS, 2000, 77 : 900 - 903
[25] Lessons learned from Lake Shiwha Project
Cho, DO
COASTAL MANAGEMENT, 2005, 33 (03) : 315 - 334
[26] Lessons learned from the Joint Project INGe
Richter, H.
Piontkowski, E.
Roller, G.
Brockmann, S.
Nill, F.
Joggerst, B.
Stengele, U.
Schaefer, P.
Braun, P.
Wolfers, K.
Minkwitz, S.
Joos, S.
Rieger, M. A.
Haeske, D.
GESUNDHEITSWESEN, 2024, 86 : S166 - S167
[27] Lessons learned from multiphase reconstruction project
Krizek, RJ
Lo, W
Hadavi, A
JOURNAL OF CONSTRUCTION ENGINEERING AND MANAGEMENT-ASCE, 1996, 122 (01): : 44 - 54
[28] Introducing Agile Software Development: Lessons Learned from the First Scrum Project in a Slovenian Company
Zabkar, N.
Hovelja, T.
Urevc, J.
Mahnic, V.
INTERNATIONAL CONFERENCE ON ADVANCES IN MANAGEMENT ENGINEERING AND INFORMATION TECHNOLOGY (AMEIT 2015), 2015, : 841 - 851
[29] The development of SAOImage DS9: Lessons learned from a small but successful software project
Joye, WA
Mandel, E
Astronomical Data Analysis Software and Systems XIV, Proceedings, 2005, 347 : 110 - 113
[30] Assessment of design patterns during software reengineering: Lessons learned from a large commercial project
Wendorff, P
FIFTH EUROPEAN CONFERENCE ON SOFTWARE MAINTENANCE AND REENGINEERING, PROCEEDINGS, 2001, : 77 - 84

← 1 2 3 4 5 →