Exploring the Mysteries of System-Level Test

System-level test, or SLT, is an increasingly important process step in today's integrated circuit testing flows. Broadly speaking, SLT aims at executing functional workloads in operational modes. In this paper, we consolidate available knowledge about what SLT is precisely and why it is used despite its considerable costs and complexities. We discuss the types or failures covered by SLT, and outline approaches to quality assessment, test generation and root-cause diagnosis in the context of SLT. Observing that the theoretical understanding for all these questions has not yet reached the level of maturity of the more conventional structural and functional test methods, we outline new and promising directions for methodical developments leveraging on recent findings from software engineering.Comment: 7 pages, 2 figure

Lessons Learned in a Complex Software Safety Program

Development of a system software safety program was required as part of an effort to secure government safety certification of a complex and intrinsically hazardous software-controlled system under development by several contributing companies. The author was part of a team of software safety support engineers reporting to one of the contributing companies. This paper summarizes some of the highlights of the lessons learned during development of this program

Conformance Testing for the AUTOSAR Standard

International audienceThe paper presents why AUTOSAR conformance tests are required, what has been achieved, and how 3 car manufacturers will use conformance tests as part of their vehicle E/E engineering process. Important topics covered are the need for conformance testing when developing a standard, the relationship between conformance and interoperability, the need for interoperability of ECUs in a vehicle, and the need to avoid diverging implementation of a standard

Dealing With Ambiguous and Fluctuating Requirements of Embedded System Development: A Case-Study

This paper presents the findings of a case study that investigates how developers and managers deal with ambiguous and fluctuating requirements during an embedded system development in a structured process management environment. In particular, this paper focuses on improvisation and bricolage actions as a coping strategy by software developers and managers. This research adopts an interpretive approach that involves the collection and analysis of qualitative data. In this study, we observed a turbulent environment with situated improvisational and bricolage responses from developers and managers. The organizational structured process management framework was not sophisticated enough to deal with the existing challenges. Moreover, some improvisational and bricolage activities became institutionalized and, hence, became organizational routines of developers and managers. This paper indicates the value of reflexive practices as vital issues for strategic conduct in the event that improvisational and bricolage activities were deployed as a coping strategy

2021 URS Abstract Booklet

Complete Schedule of Events for the 23rd Annual Undergraduate Research Symposium at Minnesota State University, Mankato

Towards Automotive Embedded Systems with Self-X Properties

With self-adaptation and self-organization new paradigms for the management of distributed systems have been introduced. By enhancing the automotive software system with self-X capabilities, e.g. self-healing, self-configuration and self-optimization, the complexity is handled while increasing the flexibility, scalability and dependability of these systems. In this chapter we present an approach for enhancing automotive systems with self-X properties. At first, we discuss the benefits of providing automotive software systems with self-management capabilities and outline concrete use cases. Afterwards, we will discuss requirements and challenges for realizing adaptive automotive embedded systems