Automotive Development Projects Research Articles

Model‐based analysis and specification of functional requirements and tests for complex automotive systems

AbstractThe specification of requirements and tests are crucial activities in automotive development projects. However, due to the increasing complexity of automotive systems, practitioners fail to specify requirements and tests for distributed and evolving systems with complex interactions when following traditional development processes. To address this research gap, we propose a technique that starts with the early identification of validation concerns from a stakeholder perspective, which we use to systematically design tests that drive a scenario‐based modeling and analysis of system requirements. To ensure complete and consistent requirements and test specifications in a form that is required in automotive development projects, we develop a Model‐Based Systems Engineering (MBSE) methodology. This methodology supports system architects and test designers in the collaborative application of our technique and in maintaining a central system model, in order to automatically derive the required specifications. We evaluate our methodology by applying it at KOSTAL (Tier1 supplier) and within student projects as part of the masters program Embedded Systems Engineering. Our study corroborates that our methodology is applicable and improves existing requirements and test specification processes by supporting the integrated and stakeholder‐focused modeling of product and validation systems, where the early definition of stakeholder and validation concerns fosters a problem‐oriented, iterative and test‐driven requirements modeling.

Sizing tool for rapid optimisation of pack configuration at early-stage automotive product development

The specifications that define an automotive development project are established at an early point in the process and define the direction of such a development, and changing these decisions becomes more costly the further the project progresses. Tools to enable better consideration of choice can help prevent this. The tool presented is designed to aid with the decisions needed when embarking on the development of a vehicle that incorporates electric-vehicle technologies and the important choices made regarding the battery pack required by such a vehicle. The tool incorporates a sizing model for determining the number of cells and the configuration required to meet a specified battery requirement. The tool then uses a 1-d model to determine some of the basic thermal and power characteristics that can then be used to inform other parts of the design specification. When attached to a database containing cell information, the tool can pre-select candidate cells to meet the requirement, and rapid execution time of the tool means that it can be used to quickly compare between cell choices, at a level understandable by all stakeholders in the decision making process.

Innovation of Engineering Education via Global Automotive Development Project

Innovation of Engineering Education via Global Automotive Development Project

Information hiding in product development: the design churn effect

Execution of a complex product development project is facilitated through its decomposition into an interrelated set of localized development tasks. When a local task is completed, its output is integrated through an iterative cycle of system-wide integration activities. Integration is often accompanied by inadvertent information hiding due to the asynchronous information exchanges. We show that information hiding leads to persistent recurrence of problems (termed the design churn effect) such that progress oscillates between being on schedule and falling behind. The oscillatory nature of the PD process confounds progress measurement and makes it difficult to judge whether the project is on schedule or slipping. We develop a dynamic model of work transformation to derive conditions under which churn is observed as an unintended consequence of information hiding due to local and system task decomposition. We illustrate these conditions with a case example from an automotive development project and discuss strategies to mitigate design churn.

Information Hiding in Product Development: The Design Churn
 Effect

Execution of a complex product development project is facilitated through its decomposition into an interrelated set of localized development tasks. When a local task is completed, its output is integrated through an iterative cycle of system-wide integration activities. Integration is often accompanied by inadvertent information hiding due to the asynchronous information exchanges. We show that information hiding leads to persistent recurrence of problems (termed as the design churn effect) such that progress oscillates between being on schedule and falling behind. The oscillatory nature of the PD process confounds progress measurement and makes it difficult to judge whether the project is on schedule or slipping. We develop a dynamic model of work transformation to derive conditions under which churn is observed as an unintended consequence of information hiding due to local and system task decomposition. We illustrate these conditions with a case example from an automotive development project and discuss strategies to mitigate design churn.