Engineering Data Logistics for Agile Automation Systems Engineering

Biffl, Stefan; Lüder, Arndt; Rinker, Felix; Waltersdorfer, Laura; Winkler, Dietmar

doi:10.1007/978-3-030-25312-7_8

Cited by 10 publications

(4 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several initiatives have developed industry standards that have been increasingly used to model and specify domainspecific contexts: For instance, modelling languages are Systems Modelling Language (SysML) 8 and Automa-tionML (AML) 9 for engineering data exchange, the Business Process Model and Notation (BPMN) 10 for generic process description in use cases, or Simulink 11 for control and signal processing. However, data exchange in PSE settings still concerns the exchange of documents [34] with highly heterogeneous data formats, hindering seamless model integration and transformation.…”

Section: Domain-specific Modelling Technologiesmentioning

confidence: 99%

See 1 more Smart Citation

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: Domain-specific Modelling Technologiesmentioning

confidence: 99%

“…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]. Furthermore, the figure shows the challenges marked with labels in red.…”

Section: Introductionmentioning

confidence: 99%

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

“…Martini et al [18] show how architectural TD accumulates during development in a project until reaching a crisis point that makes refactoring inevitable, increasing business value as the short-term sins are repaid adequately. Case studies by Biffl et al [4][5] and Kathrein et al [12][13] investigated engineering processes of EOs with a focus on the structure of collaborations between workgroups [13] and how data is exchanged [4] [5]. These works represent building blocks for this paper, as they define a coherent context with basic concepts needed for TD investigations.…”

Section: Technical Debt In Pse Knowledgementioning

confidence: 99%

“…In a typical PSE process, the domain experts work in parallel in discipline-specific workgroups that exchange engineering artifacts for iterative improvement. For making informed design decisions, industrial automation and software engineers depend on the high quality of input artifacts that contain software requirements as well as results and rationale of system design decisions [4] [5].…”

Section: Introductionmentioning

confidence: 99%

Software Engineering Risks from Technical Debt in the Representation of Product/ion Knowledge

Biffl¹,

Kathrein²,

Lüder³

et al. 2019

International Conferences on Software Engineering and Knowledge Engineering

Self Cite

View full text Add to dashboard Cite

In the multidisciplinary production systems engineering (PSE) process, software engineers depend on requirements and design rationales coming from product and production process planning, summarized as product/ion knowledge. Unfortunately, the engineering artifacts coming from product/ion planning often represent important product/ion knowledge incompletely and not well integrated, leading to risks regarding software engineering quality. In this paper, we report on a case study at a large industrial PSE organization, investigating Technical Debt (TD) effects, items, and causes in PSE process documentation and configuration management according to the VDI guideline 3695 Part 2. We focus on requirements for and issues in the representation of product/ion knowledge in the engineering data provided to software engineers. Based on data elicited from PSE domain experts, we model TD concepts based on the Quality Function Deployment method as foundation for TD analysis and risk management. The initial validation with domain experts revealed how software engineers could benefit from improved product/ion knowledge modeling as foundation for better understanding the rationale of engineering design decisions.

show abstract

Multi-view FMEA Re-validation: Efficient Risk and Engineering Knowledge Integration in Agile Production Systems Engineering

Rinker

Kropatschek²,

Steuer³

et al. 2023

Communications in Computer and Information Science

View full text Add to dashboard Cite

Engineering Data Logistics for Agile Automation Systems Engineering

Cited by 10 publications

References 21 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

Software Engineering Risks from Technical Debt in the Representation of Product/ion Knowledge

Multi-view FMEA Re-validation: Efficient Risk and Engineering Knowledge Integration in Agile Production Systems Engineering

Contact Info

Product

Resources

About