Architecture-Based Unit Testing of the Flight Software Product Line

Ganesan, Dharmalingam; Lindvall, Mikael; McComas, David; Bartholomew, Maureen; Slegel, Steve; Medina, Barbara F.

doi:10.1007/978-3-642-15579-6_18

Cited by 18 publications

(21 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, especially in the context of highly-configurable systems and software product lines, the preprocessor is still the standard tool [Jepsen and Beuche, 2009;Ganesan et al, 2009], and several researchers work on improved versions that avoid many of the pitfalls [Kästner et al, 2008b;Favre, 1997;Erwig and Walkingshaw, 2011;McCloskey and Brewer, 2005;Weise and Crew, 1993], on tools to migrate to alternative implementations [Adams et al, 2009;Kumar et al, 2012;Tomassetti and Ratiu, 2013;McCloskey and Brewer, 2005], and on tools to cope with existing cpp implementations [Vo and Chen, 1992;Krone and Snelting, 1994;Feigenspan et al, 2013;Kullbach and Riediger, 2001;Singh et al, 2007;Ribeiro et al, 2011].…”

Section: Related Workmentioning

confidence: 99%

“…cpp supports conditional compilation through preprocessor directives (e.g., #ifdef), which enable the programmer to include or exclude parts of the code base by providing a corresponding configuration. cpp is widely used for the implementation of highly-configurable systems both in the open-source and the industrial world [Liebig et al, 2010;Ernst et al, 2002;Baxter and Mehlich, 2001;Ganesan et al, 2009;Pech et al, 2009;Jepsen and Beuche, 2009;Pearse and Oman, 1997]. One of the most prominent examples is the Linux kernel, which uses the preprocessor to allow the developer to choose among 12 000 distinct options or features at build time [Tartler et al, 2011;Berger et al, 2010].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Preprocessor-based variability in open-source and industrial software systems: An empirical study

et al. 2015

View full text Add to dashboard Cite

Almost every sufficiently complex software system today is configurable. Conditional compilation is a simple variability-implementation mechanism that is widely used in open-source projects and industry. Especially, the C preprocessor (cpp) is very popular in practice, but it is also gaining (again) interest in academia. Although there have been several attempts to understand and improve cpp, there is a lack of understanding of how it is used in open-source and industrial systems and whether different usage patterns have emerged. The background is that much research on configurable systems and product lines concentrates on open-source systems, simply because they are available for study in the first place. This leads to the potentially problematic situation that it is unclear whether the results obtained from these studies are transferable to industrial systems. We aim at lowering this gap by compar- * This author published previous work as Janet Feigenspan. ing the use of cpp in open-source projects and industry-especially from the embedded-systems domain-based on a substantial set of subject systems and well-known variability metrics, including size, scattering, and tangling metrics. A key result of our empirical study is that, regarding almost all aspects we studied, the analyzed open-source systems and the considered embedded systems from industry are similar regarding most metrics, including systems that have been developed in industry and made open source at some point. So, our study indicates that, regarding cpp as variability-implementation mechanism, insights, methods, and tools developed based on studies of open-source systems are transferable to industrial systems-at least, with respect to the metrics we considered.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Preprocessor-based variability in open-source and industrial software systems: An empirical study

et al. 2015

View full text Add to dashboard Cite

show abstract

“…32. Each layer masks the specifics of its underlying operation and can be changed without impacting the other layers.…”

Section: Viiib Cfs Structure and Control Loop Setupmentioning

confidence: 99%

On TTEthernet for Integrated Fault-Tolerant Spacecraft Networks

Loveless

2015

AIAA SPACE 2015 Conference and Exposition

View full text Add to dashboard Cite

There has recently been a push for adopting integrated modular avionics (IMA) principles in designing spacecraft architectures. This consolidation of multiple vehicle functions to shared computing platforms can significantly reduce spacecraft cost, weight, and design complexity. Ethernet technology is attractive for inclusion in more integrated avionic systems due to its high speed, flexibility, and the availability of inexpensive commercial off-the-shelf (COTS) components. Furthermore, Ethernet can be augmented with a variety of quality of service (QoS) enhancements that enable its use for transmitting critical data. TTEthernet introduces a decentralized clock synchronization paradigm enabling the use of time-triggered Ethernet messaging appropriate for hard real-time applications. TTEthernet can also provide two forms of event-driven communication, therefore accommodating the full spectrum of traffic criticality levels required in IMA architectures. This paper explores the application of TTEthernet technology to future IMA spacecraft architectures as part of the Avionics and Software (A&S) project chartered by NASA's Advanced Exploration Systems (AES) program.

show abstract

“…Despite this criticism, practitioners implement many software product lines with preprocessors. Examples are HP's product line Owen for printer firmware [Pearse and Oman 1997], Danfoss' product line of frequency converters [Jepsen and Beuche 2009], the NASA's product line of flight control systems [Ganesan et al 2009], and the Linux kernel [Tartler et al 2009;She et al 2010].…”

Section: Software-product-line Implementationmentioning

confidence: 99%

Type checking annotation-based product lines

Kästner

Apel

Thüm

et al. 2012

ACM Trans. Softw. Eng. Methodol.

148

133

View full text Add to dashboard Cite

Software-product-line engineering is an efficient means to generate a family of program variants for a domain from a single code base. However, because of the potentially high number of possible program variants, it is difficult to test them all and ensure properties like type safety for the entire product line. We present a product-line-aware type system that can type check an entire software product line without generating each variant in isolation. Specifically, we extend the Featherweight Java calculus with feature annotations for product-line development and prove formally that all program variants generated from a well-typed product line are well-typed. Furthermore, we present a solution to the problem of typing mutually exclusive features. We discuss how results from our formalization helped implementing our own product-line tool CIDE for full Java and report of experience with detecting type errors in four existing software-product-line implementations.

show abstract

Architecture-Based Unit Testing of the Flight Software Product Line

Cited by 18 publications

References 2 publications

Preprocessor-based variability in open-source and industrial software systems: An empirical study

Preprocessor-based variability in open-source and industrial software systems: An empirical study

On TTEthernet for Integrated Fault-Tolerant Spacecraft Networks

Type checking annotation-based product lines

Contact Info

Product

Resources

About