Samsung recently introduced a new smartphone display with increased breaking resistance, which will probably be relevant for future cars as well. This example shows that subsystems, in general artefacts from former development processes can be relevant for subsequent projects. Their integration has to be planned, i.a. even before the original product is in the market and across branches. The research on supporting methods requires a suitable description model for this phenomenon. Research in design reuse and PGE – product generation engineering addresses this only partially yet. Design reuse focuses on the informational aspect, PGE refers primarily to reference products. This contribution aims at closing this gap as a basis for future research. Two case studies from industry projects by the authors and an example from foresight and product planning show the role of artefacts from former development processes in running projects. It is described which artefacts are used as a reference, why they are used and when. Based on these findings the authors propose the term “reference system” to depict the whole set of artefacts, which serves as a basis for every product development project.

No abstract

No abstract

The development of mechatronic systems has always been characterized by continuous handling of uncertainties. This challenge, which is associated with dynamic changes in the development context, is increasingly met by companies in the development of physical systems with the implementation of agile approaches in their development processes. However, since established approaches have their origin in software development, they reach various limits in the context of the development of mechatronic systems, e.g. due to the physical properties of the systems. Other features, such as transparent and flexible project management or targeted and early involvement of customers and users in development processes, can also be implemented in mechatronic system development. In order to derive the potentials and limits of existing agile approaches for the context of mechatronic system development, the present paper compares existing approaches with regard to relevant factors from the context of mechatronic system development. The aim is to create a basis for the targeted development, adaptation and use of agile approaches in the field of mechatronic system development.

More than 15 years after the publication of the agile manifesto of software development, agile development approaches have also reached the processes of physical product development. Because of the boundary conditions and requirements here, which differ strongly from those of pure software development, these approaches often reach their limits. However, research and practice have quickly recognized that hybrid approaches integrate the strengths of agile and plan-driven development. This paper presents 25 hybrid development approaches that have been identified in a Systematic Literature Review.