Towards Model-and-Code Consistency Checking

Riedl-Ehrenleitner, Markus; Demuth, Andreas; Egyed, Alexander

doi:10.1109/compsac.2014.91

Cited by 21 publications

(8 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The next research step towards assumptions documentation within DesignSpace (Riedl-Ehrenleitner et al, 2014) is to investigate the benefit of such documentation to the individual. The final goal of this research -once such a benefit has been verified -is industrial application of a data management network handling assumptions.…”

Section: Discussionmentioning

confidence: 99%

The influence of documenting assumed values of product properties on the number of iterations in the design process - first observations

Sadlauer

Hehenberger

Zeman

2017

IJITM

View full text Add to dashboard Cite

Abstract:Iterations are an integral part of the product design process and can become necessary when there are inconsistencies between the requirements and the solution at hand. However, not all iterations are beneficial -some are unnecessary, for example, those arising from inappropriate return points. The identification of potentially wrong assumptions about product properties can indicate promising iteration return points. This paper presents the results of survey of product development engineers about iterations and assumed values of properties in their work. Additionally, we conducted a design experiment to further analyse the influence of documenting assumed values of properties on the number of iterations, the ratio of unnecessary to useful iterations and task success. Based on the results, we recommend a network-based documentation of assumptions with meta-information about confidence in the assumptions to aid identification and prioritisation of potential iteration return points.Keywords: product property assumptions; design iterations; assumptions management; iteration return points.Reference to this paper should be made as follows: Sadlauer, A., Hehenberger, P. and Zeman, K. (2017) A. Sadlauer et al.Klaus Zeman is Full Professor and the Head of the IMDP. He obtained his Diploma degree in Mechanical Engineering in 1979 at the Vienna Technical University, where in 1984 he also finished his PhD thesis on dynamical systems, bifurcation theory and structural stability. His actual research fields are modelling and simulation of specific manufacturing processes, model-based mechatronic design, design science and machine dynamics.

show abstract

Section: Discussionmentioning

confidence: 99%

The influence of documenting assumed values of product properties on the number of iterations in the design process - first observations

Sadlauer

Hehenberger

Zeman

2017

IJITM

View full text Add to dashboard Cite

show abstract

“…Projects ranged from small, like an implementation of the "Game of Life" [44], to big multi-developer projects like the ArgoUML tool 2 . The evaluation was based on 14 consistency rules, which can be found in [75]. We validated the computational scalability of our approach by systematically applying changes to all elements of our projects and by capturing the time required to re-evaluate all rule evaluation artifacts.…”

Section: Empirical Studymentioning

confidence: 99%

“…While a multitude of consistency checking approaches exist in the current landscape of engineering solutions (e.g., [37,38,72,74,76,94]) most of them do not consider the core aspect of this work, which is the multifaceted application of the mechanism on a varied set of different engineering artifacts. Nevertheless, individual concepts of this work have been the focus of various research efforts in the past.…”

Section: Related Workmentioning

confidence: 99%

“…One major problem in this regard is, that inconsistencies -which are bound to arise, due to the heavily interdependent nature of engineering artifacts -become very hard to detect, before the integration of an engineer's work with the work of others. There have been various attempts at tackling consistency checking in general (e.g., [37,38,66,74,76,94]), but the issue described beforehand makes it clear to us, that a mechanism providing more immediate feedback is required. There is a need for consistency checking enhanced by a collaborative environment and while some approaches have gone into that direction (e.g., [51,77]) they mostly consider only homogeneous engineering artifacts or require costly merging operations.…”

Section: Paper B Collaboratively Enhanced Consistency Checking In a Cloud-based Engineering Environment 1 Introductionmentioning

confidence: 99%

“…While a regular engineering project may share its engineering artifacts among engineers in a multitude of different ways, this is not a sufficient solution to overcome the increasing complexity of the artifacts and their interdependencies. Despite its major industrial importance and constant reminders by the research community (e.g., [37,38,72,74,76,89,94]), maintaining consistency among artifacts is treated as an afterthought.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Instant distribution of consistency-relevant change information in a hierarchical multi-developer engineering environment

Tröls

Mashkoor

Egyed

2021

Proceedings of the 36th Annual ACM Symposium on Applied Computing

Self Cite

View full text Add to dashboard Cite

Ensuring safe and consistent coengineering of cyber‐physical production systems: A case study

Tröls

Mashkoor

Demuth

et al. 2020

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

In today's engineering projects, companies continuously have to adapt their systems to changing customers or dynamic market requirements. This requires a flexible, iterative development process in which different parts of the system under construction are built and updated concurrently. However, concurrent engineering becomes quite challenging in domains where different engineering artifacts from different disciplines come into play, such as safety‐critical cyber‐physical systems, where the involved engineering artifacts are quite heterogeneous in nature. In such systems, it is of utmost importance that different artifacts remain consistent in order to guarantee a correctly functioning end product. In this article, we discuss our experiences (with a leading company working in the areas of production automation and product processing) in maintaining the consistency between electrical models and the corresponding software controller, when both are subject to continuous changes. The article discusses how we let engineers describe the relationships between electrical models and the corresponding software controller code in the form of links and consistency rules. Additionally, we demonstrate that how our approach, through a process of continuous consistency checking, notifies engineers about the erroneous impact of their changes in various engineering artifacts.

show abstract

Towards Model-and-Code Consistency Checking

Cited by 21 publications

References 20 publications

The influence of documenting assumed values of product properties on the number of iterations in the design process - first observations

The influence of documenting assumed values of product properties on the number of iterations in the design process - first observations

Instant distribution of consistency-relevant change information in a hierarchical multi-developer engineering environment

Ensuring safe and consistent coengineering of cyber‐physical production systems: A case study

Contact Info

Product

Resources

About