Robbert Jongeling

Robbert Jongeling

Auto-generated profile, based on publicly available information

Robbert Jongeling

Mälardalen University

Research Focus & Metrics

Academic Career Length

8Years (2019-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
13 April 2022 in Software and Systems Modeling
Verified
Journal Article
Open access
PDF file
RJRobbert Jongeling
Robbert Jongeling
FCFederico Ciccozzi
Federico Ciccozzi
JCJan Carlson
Jan Carlson
ACAntonio Cicchetti
Antonio Cicchetti
This article presents the state of practice of consistency management in thirteen industrial model-based development settings. Our analysis shows a tight coupling between adopting shorter development cycles and increasingly pressing consistency management challenges. We find that practitioners desire to adopt shorter development cycles, but immature modeling practices slow them down. We describe the different patterns that emerge from the various industrial settings. There is an opportunity for researchers to provide practitioners with a migration path toward practices that enable more automated consistency management, and ultimately, continuous model-based development.

19 October 2020
Verified
Conference Paper
Open access
MAMuhammad Abbas
Muhammad Abbas
RJRobbert Jongeling
Robbert Jongeling
CLClaes Lindskog
Claes Lindskog
Eduard EnoiuEduard Enoiu
Eduard Enoiu
MSMehrdad Saadatmand
Mehrdad Saadatmand
DSDaniel Sundmark
Daniel Sundmark
The software system controlling a train is typically deployed on various hardware architectures and must process various signals across those deployments. The increase of such customization scenarios and the needed adherence of the software to various safety standards in different application domains has led to the adoption of product line engineering within the railway domain. This paper explores the current state-of-practice of software product line development within a team developing industrial embedded software for a train propulsion control system. Evidence is collected using a focus group session with several engineers and through inspection of archival data. We report several benefits and challenges experienced during product line adoption and deployment. Furthermore, we identify and discuss improvement opportunities, focusing mainly on product line evolution and test automation.

17 October 2020
Verified
Book Chapter
Closed access
PDF file
RJRobbert Jongeling
Robbert Jongeling
JFJohan Fredriksson
Johan Fredriksson
FCFederico Ciccozzi
Federico Ciccozzi
ACAntonio Cicchetti
Antonio Cicchetti
JCJan Carlson
Jan Carlson

9 September 2022
Verified
Book Chapter
Closed access
PDF file
RJRobbert Jongeling
Robbert Jongeling
FCFederico Ciccozzi
Federico Ciccozzi
ACAntonio Cicchetti
Antonio Cicchetti
JCJan Carlson
Jan Carlson

1 January 2019 in The Journal of Object Technology
Verified
Journal Article
Closed access
RJRobbert Jongeling
Robbert Jongeling
FCFederico Ciccozzi
Federico Ciccozzi
ACAntonio Cicchetti
Antonio Cicchetti
JCJan Carlson
Jan Carlson

3 July 2024 in Software Quality Journal
Verified
Journal Article
Open access
PDF file
SKStefan Karlsson
Stefan Karlsson
RJRobbert Jongeling
Robbert Jongeling
AČAdnan Čaušević
Adnan Čaušević
DSDaniel Sundmark
Daniel Sundmark
A common way of exposing functionality in contemporary systems is by providing a Web-API based on the REST API architectural guidelines. To describe REST APIs, the industry standard is currently OpenAPI-specifications. Test generation and fuzzing methods targeting OpenAPI-described REST APIs have been a very active research area in recent years. An open research challenge is to aid users in better understanding their API, in addition to finding faults and to cover all the code. In this paper, we address this challenge by proposing a set of behavioural properties, common to REST APIs, which are used to generate examples of behaviours that these APIs exhibit. These examples can be used both (i) to further the understanding of the API and (ii) as a source of automatic test cases. Our evaluation shows that our approach can generate examples deemedrelevantfor understanding the system and for a source of test generation by practitioners. In addition, we show that basing test generation on behavioural properties provides tests that are less dependent on the state of the system, while at the same time yielding a similar code coverage as state-of-the-art methods in REST API fuzzing in a given time limit.