Software product assurance at the German space agency

@article{Prause2016SoftwarePA,
  title={Software product assurance at the German space agency},
  author={Christian R. Prause and Markus Bibus and Carsten Dietrich and Wolfgang Jobi},
  journal={Journal of Software: Evolution and Process},
  year={2016},
  volume={28},
  pages={744 - 761}
}
The DLR Space Administration designs and implements the German space program. While project management rests with the agency, suppliers are contracted for building the space devices and their software. As opposed to many other domains, these are often unique devices with uncommon and custom‐built peripherals. Its software is specifically developed for a single mission only and controls critical functionality. A small coding error can mean the loss of a mission. For this reason, customer and… 
Evaluating Automated Software Verification Tools
TLDR
Questions regarding effectiveness and efficiency of different tools and their combinations, what the best tool is, if it makes sense at all to apply automated software verification to well-tested software, and whether tools with many or few reports are preferable are investigated are investigated.
MeLa: A Programming Language for a New Multidisciplinary Oceanographic Float
TLDR
A seismic P wave detection and a blue whales D call detection algorithm with the MeLa language are implemented, which are the first efforts toward multidisciplinary monitoring of the oceans, which can extend beyond acoustic applications.

References

SHOWING 1-10 OF 39 REFERENCES
Tailoring process requirements for software product assurance
TLDR
A customer's perspective on lessons and management tools for influencing suppliers' processes and product quality: standards, single-source tailoring and cross-company product assurance is reported on.
Scoping Software Process Models - Initial Concepts and Experience from Defining Space Standards
TLDR
Requirement and concepts for determining the scope of process standards based on a characterization of the potential products to be produced in the future, the projects expected for thefuture, and the respective process capabilities needed are described.
Successful software development 2nd edition
TLDR
Successful Software Development proceeds from the fact that there is no one way to develop software systems and introduces a model for a mature software development process that accommodates flexibility, the Systems Engineering Environment (SEE).
Introducing ECSS software-engineering standards within ESA: Practical approaches for space- and ground-segment software
TLDR
The ECSS softwareengineering standard ECSS-E-40, which first appeared in 1999, is based on ISO 12207, which is now the leading standard in this field.
Empirical Study of Tool Support in Highly Distributed Research Projects
TLDR
An empirical study involving more than 50 transnational, multi-million Euro projects of the Sixth Framework Programme shows which tools are accepted by developers and used in practice in the respective phases of the software process.
NASA Study on Flight Software Complexity
TLDR
This report examines complexity throughout the engineering lifecycle—from requirements definition through design, development, verification, and operations—and presents sixteen findings and associated recommendations.
Reuse of software in distributed embedded automotive systems
TLDR
A framework is proposed to deal with the specific problems of reuse of software in the automotive domain and the application of this framework is shown in a realistic application example.
Get Ready for Agile Methods, with Care
TLDR
Although many of their advocates consider the agile and plan-driven software development methods polar opposites, synthesizing the two can provide developers with a comprehensive spectrum of tools and options, and a combined approach is feasible and preferable in some circumstances.
Criteria for software process tailoring: a systematic review
TLDR
This paper presents a collection of 49 tailoring criteria for the tailoring of software processes as the outcomes of a systematic literature review and analyzes the impact of these criteria by relating them to a set of 20 exemplary tailoring actions, which affect the project-specific software process.
...
...