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

In the multi-disciplinary 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

[1]  D. Winkler,et al.  Introducing Engineering Data Logistics for Production Systems Engineering , 2019 .

[2]  Peng Liang,et al.  A systematic mapping study on technical debt and its management , 2015, J. Syst. Softw..

[3]  Stefan Biffl,et al.  Efficient Engineering Data Exchange in Multi-disciplinary Systems Engineering , 2019, CAiSE.

[4]  Richard Mordinyi,et al.  Integrating heterogeneous engineering knowledge and tools for efficient industrial simulation model support , 2015, Adv. Eng. Informatics.

[5]  Xiaoqing Frank Liu,et al.  Software Architecture Rationale Capture through Intelligent Argumentation , 2014, SEKE.

[6]  Birgit Vogel-Heuser,et al.  Cross-disciplinary and cross-life-cycle-phase Technical Debt in automated Production Systems: two industrial case studies and a survey , 2018 .

[7]  Marta Sabou,et al.  Semantic Modelling and Acquisition of Engineering Knowledge , 2016, Semantic Web Technologies for Intelligent Engineering Applications.

[8]  Rainer Drath,et al.  AutomationML - the glue for seamless automation engineering , 2008, 2008 IEEE International Conference on Emerging Technologies and Factory Automation.

[9]  Wolfgang Marquardt,et al.  OntoCAPE - A (re)usable ontology for computer-aided process engineering , 2009, Comput. Chem. Eng..

[10]  Roel Wieringa,et al.  Design Science Methodology for Information Systems and Software Engineering , 2014, Springer Berlin Heidelberg.

[11]  Aldo Gangemi,et al.  Ontology Design Patterns , 2005 .

[12]  Stefan Biffl,et al.  Ontology-Based Data Integration in Multi-Disciplinary Engineering Environments: A Review , 2017, Open J. Inf. Syst..

[13]  D. Winkler,et al.  Process Analysis for Communicating Systems Engineering Workgroups , 2019 .

[14]  Jürgen Jasperneite,et al.  Requirements and concept for Plug-and-Work , 2015, Autom..

[15]  Lida Xu,et al.  The internet of things: a survey , 2014, Information Systems Frontiers.

[16]  Flávio Oquendo,et al.  An Approach for Capturing and Documenting Architectural Decisions of Reference Architectures , 2014, SEKE.

[17]  Stefan Biffl,et al.  Production-Aware Analysis of Multi-disciplinary Systems Engineering Processes , 2019, ICEIS.

[18]  Marta Indulska,et al.  Improving the quality of process reference models: A quality function deployment-based approach , 2009, Decis. Support Syst..

[19]  Rafael H. Bordini,et al.  A Knowledge Engineering Process for the Development of Argumentation Schemes for Risk Management in Software Projects , 2017, SEKE.

[20]  Anton Strahilov,et al.  Engineering Workflow and Software Tool Chains of Automated Production Systems , 2017, Multi-Disciplinary Engineering for Cyber-Physical Production Systems.

[21]  Alexander Fay,et al.  Zusätzliche Wertschöpfung mit digitalem Modell , 2018, atp magazin.

[22]  Elena García Barriocanal,et al.  Ontologies of engineering knowledge: general structure and the case of Software Engineering , 2009, The Knowledge Engineering Review.

[23]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[24]  Robert L. Nord,et al.  Reducing Friction in Software Development , 2016, IEEE Software.

[25]  Jan Bosch,et al.  Technical Debt tracking: Current state of practice: A survey and multiple case study in 15 large organizations , 2018, Sci. Comput. Program..

[26]  Stefan Biffl,et al.  Multi-Disciplinary Engineering for Cyber-Physical Production Systems, Data Models and Software Solutions for Handling Complex Engineering Projects , 2017 .

[27]  Stefan Feldmann,et al.  Semantics to the Shop Floor: Towards Ontology Modularization and Reuse in the Automation Domain , 2014 .