Explore the vast range of titles available.

One problem in incremental product development is that geometric models are limited in their ability to explore radical alternative design variants. In this publication, a function modeling approach is suggested to increase the amount and variety of explored alternatives, since function models (FM) provide greater model flexibility. An enhanced function-means (EF-M) model capable of representing the constraints of the design space as well as alternative designs is created through a reverse engineering process. This model is then used as a basis for the development of a new product variant. This work describes the EF-M model's capabilities for representing the design space and integrating novel solutions into the existing product structure and explains how these capabilities support the exploration of alternative design variants. First-order analyses are executed, and the EF-M model is used to capture and represent already existing design information for further analyses. Based on these findings, a design space exploration approach is developed. It positions the FM as a connection between legacy and novel designs and, through this, allows for the exploration of more diverse product concepts. This approach is based on three steps – decomposition, design, and embodiment – and builds on the capabilities of EF-M to model alternative solutions for different requirements. While the embodiment step of creating the novel product's geometry is still a topic for future research, the design space exploration concept can be used to enable wider, more methodological, and potentially automated design space exploration.

Product development companies strive to provide their customers with high quality products, more quickly than their competitors, using as few resources as possible. One way of managing all three aspects at the same time is to reuse old, quality assured designs and knowledge in new products. A common way to do that is to create a platform with designs that are reusable in many different products. Traditionally, research on platforms has focused on finding ways to provide manufacturing with a low number of parts to be able to increase utilization of expensive production equipment. However, reuse of parts does not benefit all businesses, especially those where customer requirements continuously change. To cut development lead-time, other types of reuse are necessary. The use of platforms based on core technologies and re-configurable systems as platform elements may provide the necessary support. They enable reuse on a more abstract level, reusing technologies, requirements and concepts rather than ready designed parts. This thesis elaborates on support for working with the type of platforms that are integrated across the lifecycle of a product.The studies in this thesis show that platform approaches in literature today do not cover the need to support holistic platform development across all stages of a lifecycle. As a solution, configurable system elements are used to model platforms and the links between the lifecycles. The development processes and models may be further infused with set-based concurrent engineering to provide a framework for efficient development. These principles are integrated into the models and the processes to enhance the ability to manage the complex relationships within and between parts of the platform throughout the lifecycle.Further, development platforms may be supported by a Product Lifecycle Management (PLM) architecture for engineering-to-order configuration, but it can also serve as a tool to learn about the knowledge gaps that need to be filled to get a product that meets requirements.

Product developing companies strive to provide their customers with high quality products, more quickly than their competitors, using as few resources as possible. One way of managing all three aspects at the same time is to reuse old, quality assured designs and knowledge in new products. A common way to do that is to create a platform with designs that are reusable in many different products.Traditionally, research on platforms has focused on finding ways to provide manufacturing with a low number of parts to be able to increase utilization of expensive production equipment. However, a designer needs more information than just the physical form of a design in order to reuse the design to cut development lead-time. The use of platforms based on core technologies and re-configurable systems as platform elements may on the other hand give the needed support. These types of platforms are here referred to as development platforms. This thesis elaborates on support for working with development platforms that are integrated across the lifecycle of a product.The studies in this thesis show that platform approaches in literature today do not cover the need to support holistic platform development across all stages of a lifecycle. As a solution, configurable system elements may be used as a bridge between abstract descriptions of platforms (e.g. technology platforms) and concrete descriptions (e.g. part-based and module-based platforms).Further, development platforms may be supported by a Product Lifecycle Management (PLM) architecture for engineering-to-order configuration, but it can also serve as a tool to learn about the knowledge gaps that need to be filled to get a product to meet requirements. However, there is a great risk in trying to support design reuse with IT-applications alone. In order to fully support platform-based development, an organization needs to consider business objectives, processes, information architecture and application architecture.

Deep Neural Networks (DNN) will emerge as a cornerstone in automotive software engineering. However, developing systems with DNNs introduces novel challenges for safety assessments. This paper reviews the state-of-the-art in verification and validation of safety-critical systems that rely on machine learning. Furthermore, we report from a workshop series on DNNs for perception with automotive experts in Sweden, confirming that ISO 26262 largely contravenes the nature of DNNs. We recommend aerospace-to-automotive knowledge transfer and systems-based safety approaches, e.g., safety cage architectures and simulated system test cases.