Experiences with technical debt and management strategies in production systems engineering

Waltersdorfer, Laura; Rinker, Felix; Kathrein, Lukas; Biffl, Stefan

doi:10.1145/3387906.3388627

Cited by 12 publications

(11 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Model transformation and integration require high effort due to custom data formats and implicit model and mapping knowledge, which is not formalised. These processes are not automated and associated with high effort for the data consumers [6], which can lead to error or loss of data.…”

Section: C2 Manual Local Model Mapping and Integration Effortsmentioning

confidence: 99%

“…Model operations, especially model transformations, are another essential measure to achieve the interoperability of domain models. The Model-Driven Engineering (MDE) community has established best-practice concepts and frameworks: the ATLAS Transformation Language (ATL) 5 framework conforms to the Meta Object Facility (MOF) 6 specifications for model transformations and provides the foundations for assuring modelling interoperability [21]. EMF Compare [22] is a framework for model comparison, conflict detection and merging, mainly for technically convergent application contexts.…”

Section: System Modellingmentioning

confidence: 99%

“…Similar to CM in Software Engineering, it should enable a consistent and accurate documentation of various characteristics, such as requirements, design, or testing concerning the actual physical design [5]. However, production systems have reached a high level of complexity that makes conventional approaches to engineering knowledge integration inadequate [3,6]. Therefore, this paper focuses on how to enable improved configuration management and, thus, traceability on the level of data.…”

Section: Introductionmentioning

confidence: 99%

“…Sect. 4.1 and literature [6,8,9]), we have identified several challenges. Figure 1 illustrates how engineers conduct data and model exchange in PSE across workgroup borders, in artefact-based transactions [9].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

et al. 2023

Self Cite

View full text Add to dashboard Cite

Purpose. Agile Production Systems Engineering (PSE) is characterised by parallel and iterative engineering of several disciplines. This multi-view engineering requires capabilities for tracing changes to support configuration management of PSE assets. Yet, traditional model transformation approaches in PSE do not preserve local views and hierarchies on concepts of PSE assets, such as plans and configurations. Thus, tracing multi-view changes to PSE assets is challenging. Method. Following the Design Science approach, we (i) elicit requirements for tracing multi-view changes to PSE assets from a domain analysis in automotive manufacturing; (ii) introduce and evaluate the Traceable Multi-view Model Transformation (TMvMT) process; and (iii) propose the TMvMT pipeline architecture to provide traceable model integration capabilities for agile PSE. Results. In a feasibility study on robot cell models, we evaluate the TMvMT process and architecture regarding the requirements for traceability compared to traditional approaches. Conclusion. The proposed TMvMT approach provides traceability of changes in multi-view modelling as a basis through the separation of modelling transformation steps and provision of clear input and output artefacts to achieve traceable configuration management and validation of system designs for production system assets in agile PSE.

show abstract

Section: C2 Manual Local Model Mapping and Integration Effortsmentioning

confidence: 99%

Section: System Modellingmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

et al. 2023

Self Cite

View full text Add to dashboard Cite

show abstract

“…Some studies such as [20] characterise the current state of practices related to TD payment from the point of view of software practitioners. Other experiences such as [21] analysed potential TD in the engineering data exchange for production system engineering. Recent research studies, such as [22], are focussed on analysing whether TDs are self‐fixed or are propagated to other developers who fix them.…”

Section: Introductionmentioning

confidence: 99%

Towards a privacy debt

2021

View full text Add to dashboard Cite

This study argues the difference between security and privacy and outlines the concept of Privacy Debt as a new Technical Debt. Privacy is gaining momentum in any software system due to mandatory compliance with respect to laws and regulations. There are several types of technical debts within the umbrella of software engineering, and most of them arise during different phases of software development. Several research studies have been focussed on highlighting different types of technical debts. However, authors introduce Privacy Debt as a particular technical debt focussed on privacy management and linked to a perturbative method. Privacy must be considered not only as technical debt requirements but also at design and deployment phases, among others. In addition, this method is illustrated with a use case.

show abstract

Integrating privacy debt and VSE's software developments

Santamaría

Larrucea

Fernández-Gauna

2022

J Software Evolu Process

View full text Add to dashboard Cite

With the advent of regulations protecting users such as the General Data Protection Regulation, security and privacy concerns are playing a new role in small settings such as in very small entities. Their relevance is increasing, and privacy is being considered a Troy horse in software developments. In fact, privacy is a part of software architectural decisions, and they must be considered as a technical debt. The contributions of this paper are the following: a privacy debt definition with a principal and an interest, privacy‐related activities to be considered within the ISO/IEC 29110 basic profile, and the use of the net present value within this context. All these contributions help us to integrate privacy debt and VSE's software developments.

show abstract

Experiences with technical debt and management strategies in production systems engineering

Cited by 12 publications

References 31 publications

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

Traceable Multi-view Model Integration: A Transformation Pipeline for Agile Production Systems Engineering

Towards a privacy debt

Integrating privacy debt and VSE's software developments

Contact Info

Product

Resources

About