Component-Based Software Development for Embedded Systems – An Introduction

Atkinson, Colin; Bunse, Christian; Peper, Christian; Groß, Hans-Gerhard

doi:10.1007/11591962_1

Cited by 10 publications

(6 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the late 1960s, component-based software engineering (CBSE) [9] started becoming popular, which presented the idea of componentization and the consequent focus on interface specification. The components communicate with each other through the interfaces [6]. The communication follows the software specification which states the order and timings of the messages [43].…”

mentioning

confidence: 99%

Interface protocol inference to aid understanding legacy software components

et al. 2020

View full text Add to dashboard Cite

High-tech companies are struggling today with the maintenance of legacy software. Legacy software is vital to many organizations as it contains the important business logic. To facilitate maintenance of legacy software, a comprehensive understanding of the software’s behavior is essential. In terms of component-based software engineering, it is necessary to completely understand the behavior of components in relation to their interfaces, i.e., their interface protocols, and to preserve this behavior during the maintenance activities of the components. For this purpose, we present an approach to infer the interface protocols of software components from the behavioral models of those components, learned by a blackbox technique called active (automata) learning. To validate the learned results, we applied our approach to the software components developed with model-based engineering so that equivalence can be checked between the learned models and the reference models, ensuring the behavioral relations are preserved. Experimenting with components having reference models and performing equivalence checking builds confidence that applying active learning technique to reverse engineer legacy software components, for which no reference models are available, will also yield correct results. To apply our approach in practice, we present an automated framework for conducting active learning on a large set of components and deriving their interface protocols. Using the framework, we validated our methodology by applying active learning on 202 industrial software components, out of which, interface protocols could be successfully derived for 156 components within our given time bound of 1 h for each component.

show abstract

mentioning

confidence: 99%

Interface protocol inference to aid understanding legacy software components

et al. 2020

View full text Add to dashboard Cite

show abstract

“…Components of the autonomous robot are executed in a safety bag, where all interactions of components are analyzed according to the states and evaluated using rules formalized as ordered binary decision diagrams. Finally, a component-based approach to embedded software in general is supported in [3], especially addressing issues of the specification, verification and dealing with the non-functional properties.…”

Section: Safe Robot Softwarementioning

confidence: 99%

A multilayer software architecture for safe autonomous robots

Gribov

Voos

2014

Proceedings of the 2014 IEEE Emerging Technology and Factory Automation (ETFA)

View full text Add to dashboard Cite

In this paper a safety-oriented model based software architecture for robotic solutions is proposed. The main focus herein is to consider aspects such as real-time, heterogeneity, deployment, modeling and analysis of emerging effects as well as functional safety and to combine all aspects into an overall development approach. The architecture shall capture the complexity caused by the autonomy and mobility of the robot and support the developer with a suitable chain of evidence especially suited for the safety relevant functions. A use case comprising a lightweight robotic manipulator which will be integrated in a mobile service robot underlines the feasibility of this approach.

show abstract

“…Such groups comprise typically different stakeholders, such as real-time system experts, hardware experts, safety manager and domain experts. This fact can be exploited similar to the approach in component-based approaches [31], [2]. The responsibility for different aspects of the code generation functionality can be assigned to dedicated experts.…”

Section: Requirements On the Toolmentioning

confidence: 99%

FTOS: Model-driven development of fault-tolerant automation systems

Buckl

Sojer

Knoll

2010

2010 IEEE 15th Conference on Emerging Technologies &Amp; Factory Automation (ETFA 2010)

View full text Add to dashboard Cite

Abstract-The design of fault-tolerant automation systems is a complex task. These systems must not only satisfy real-time requirements but they must also deliver the specified functionality in the presence of both software and hardware faults. To achieve fault-tolerance, systems have to use redundancy. This redundancy is usually achieved by replicating hardware units and executing the application within a distributed system.Model-based design tools promise to reduce the complexity of the design process by raising the abstraction level. However, most of the existing tools focus only on functional aspects. Code realizing extra-functional requirements such as fault-tolerance mechanisms, communication, and scheduling is not targeted. However, this type of code makes up the majority of the code of a fault-tolerant real-time system. This paper presents FTOS, a model-based development tool for the design of fault-tolerant automation systems that focuses on code generation of extrafunctional requirements and therefore complements existing tools.

show abstract

Component-Based Software Development for Embedded Systems – An Introduction

Cited by 10 publications

References 0 publications

Interface protocol inference to aid understanding legacy software components

Interface protocol inference to aid understanding legacy software components

A multilayer software architecture for safe autonomous robots

FTOS: Model-driven development of fault-tolerant automation systems

Contact Info

Product

Resources

About