Boundary Objects and their Use in Agile Systems Engineering

Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders, but also makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation, but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design-science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry

Combined automotive safety and security pattern engineering approach

Automotive systems will exhibit increased levels of automation as well as ever tighter integration with other vehicles, traffic infrastructure, and cloud services. From safety perspective, this can be perceived as boon or bane - it greatly increases complexity and uncertainty, but at the same time opens up new opportunities for realizing innovative safety functions. Moreover, cybersecurity becomes important as additional concern because attacks are now much more likely and severe. However, there is a lack of experience with security concerns in context of safety engineering in general and in automotive safety departments in particular. To address this problem, we propose a systematic pattern-based approach that interlinks safety and security patterns and provides guidance with respect to selection and combination of both types of patterns in context of system engineering. A combined safety and security pattern engineering workflow is proposed to provide systematic guidance to support non-expert engineers based on best practices. The application of the approach is shown and demonstrated by an automotive case study and different use case scenarios.EC/H2020/692474/EU/Architecture-driven, Multi-concern and Seamless Assurance and Certification of Cyber-Physical Systems/AMASSEC/H2020/737422/EU/Secure COnnected Trustable Things/SCOTTEC/H2020/732242/EU/Dependability Engineering Innovation for CPS - DEIS/DEISBMBF, 01IS16043, Collaborative Embedded Systems (CrESt

Problem Based Learning and its use on the Automotive Engineering Design Course at Coventry University

The Automotive Engineering Design course at Coventry University has been in operation since October 1989 and has earned a reputation for creating able engineers well prepared for industry. When originally conceived, a problem led approach to learning was adopted across the course. This approach best enables the course objectives to be satisfied. However, there is nothing new about problem-based learning for engineering design educators but for our engineering science colleagues a degree of novelty has been encountered by this approach. But is the success of the course purely down to this teaching and learning approach? This paper will discuss the opportunities, benefits and limitations of the problem-led approach being extended across a whole course. The paper also will address how the use of industrially defined problems in engineering design projects has been critical to the development of the course. The paper will then attempt to identify the key factors that lie behind the success of the Automotive Engineering Design course. Finally, a set of best practice guidelines for engineering design education will be presented based upon my experiences as the Course Tutor and a teacher of engineering design on this course

Set-Based Concurrent Engineering Model for Automotive Electronic/Software Systems Development

Organised by: Cranfield UniversityThis paper is presenting a proposal of a novel approach to automotive electronic/software systems development. It is based on the combination of Set-Based Concurrent Engineering, a Toyota approach to product development, with the standard V-Model of software development. Automotive industry currently faces the problem of growing complexity of electronic/software systems. This issue is especially visible at the level of integration of these systems which is difficult and error-prone. The presented conceptual proposal is to establish better processes that could handle the electronic/software systems design and development in a more integrated and consistent manner.Mori Seiki – The Machine Tool Compan

Assisted assignment of automotive safety requirements

ISO 26262, a functional-safety standard, uses Automotive Safety Integrity Levels (ASILs) to assign safety requirements to automotive-system elements. System designers initially assign ASILs to system-level hazards and then allocate them to elements of the refined system architecture. Through ASIL decomposition, designers can divide a function & rsquo;s safety requirements among multiple components. However, in practice, manual ASIL decomposition is difficult and produces varying results. To overcome this problem, a new tool automates ASIL allocation and decomposition. It supports the system and software engineering life cycle by enabling users to efficiently allocate safety requirements regarding systematic failures in the design of critical embedded computer systems. The tool is applicable to industries with a similar concept of safety integrity levels. © 1984-2012 IEEE

Why and How Your Traceability Should Evolve: Insights from an Automotive Supplier

Traceability is a key enabler of various activities in automotive software and systems engineering and required by several standards. However, most existing traceability management approaches do not consider that traceability is situated in constantly changing development contexts involving multiple stakeholders. Together with an automotive supplier, we analyzed how technology, business, and organizational factors raise the need for flexible traceability. We present how traceability can be evolved in the development lifecycle, from early elicitation of traceability needs to the implementation of mature traceability strategies. Moreover, we shed light on how traceability can be managed flexibly within an agile team and more formally when crossing team borders and organizational borders. Based on these insights, we present requirements for flexible tool solutions, supporting varying levels of data quality, change propagation, versioning, and organizational traceability.Comment: 9 pages, 3 figures, accepted in IEEE Softwar

Machine Design Experiments Using Gears to Foster Discovery Learning

Machine Design Experiments Using Gears to Foster Discovery Learning For the typical undergraduate engineering student the topic of gears is introduced and discussed in several courses. Early exposure may be in a physics course or in a first dynamics course,where gear pairs are presented as an idealized means to change speed ratios and torque ratios.They are used for mechanical advantage or to achieve desired speed, and the focus is usually on kinematics. Since gears have inertia they store kinetic energy and are part of the dynamic equations of motion of mechanisms and machines. For mechanical engineering students, gears are a core component studied in courses such as \u27kinematics and dynamics of mechanisms\u27 and \u27machine design\u27, where the nomenclature and design equations are developed for various types of gears. There may be exposure to real gears in a mechanical engineering laboratory; more often, students may see gears passed around in class and as part of demonstrations.In this paper we describe new experiments that were designed to provide mechanical engineering students with discovery learning experiences with gears and mechanical systems using gears.The suite of practical experiments presents students with a range of challenges that require them to analyze, measure, design, and fabricate gears. Activities in the experiments include: (1) Identifying gear types (spur, helical, bevel, etc.) and appropriate applications (automotive transmissions and differentials, drills, gear head motors). (2) Disassembling and re-assembling a kitchen mixer (with design and manufacturing questions related to its gears). (3) Disassembling and re-assembling an automotive HVAC baffle sub-assembly (with measurement of train ratios, and design and manufacturing questions related to its gears). (4) Designing the gear mechanism for driving the minute and hour hands of a gear clock given a known yet arbitrary drive speed. Fabricating the gears of the clock via rapid prototyping (3D printing), assembling the clock, and then testing the timing accuracy.In addition to reporting the details of the experiments, we share experiences of students and teaching assistants in their use and effectiveness. We provide insights into how well students became familiar with types and nomenclature of gears and understood the applicability of different gears to actual real-world problems. The intent of the experiments is to effectively enhance mechanical engineering students\u27 awareness of gears and expand their knowledge and confidence in the use of gears in machine and mechanism design

Systematic pattern approach for safety and security co-engineering in the automotive domain

Future automotive systems will exhibit increased levels of automation as well as ever tighter integration with other vehicles, traffic infrastructure, and cloud services. From safety perspective, this can be perceived as boon or bane - it greatly increases complexity and uncertainty, but at the same time opens up new opportunities for realizing innovative safety functions. Moreover, cybersecurity becomes important as additional concern because attacks are now much more likely and severe. Unfortunately, there is lack of experience with security concerns in context of safety engineering in general and in automotive safety departments in particular. To remediate this problem, we propose a systematic pattern-based approach that interlinks safety and security patterns and provides guidance with respect to selection and combination of both types of patterns in context of system engineering. The application of a combined safety and security pattern engineering workflow is shown and demonstrated by an automotive use case scenario

Enhancing the EAST-ADL error model with HiP-HOPS semantics

EAST-ADL is a domain-specific modelling language for the engineering of automotive embedded systems. The language has abstractions that enable engineers to capture a variety of information about design in the course of the lifecycle — from requirements to detailed design of hardware and software architectures. The specification of the EAST-ADL language includes an error model extension which documents language structures that allow potential failures of design elements to be specified locally. The effects of these failures are then later assessed in the context of the architecture design. To provide this type of useful assessment, a language and a specification are not enough; a compiler-like tool that can read and operate on a system specification together with its error model is needed. In this paper we integrate the error model of EAST-ADL with the precise semantics of HiP-HOPS — a state-of-the-art tool that enables dependability analysis and optimization of design models. We present the integration concept between EAST-ADL structure and HiP-HOPS error propagation logic and its transformation into the HiP-HOPS model. Source and destination models are represented using the corresponding XML formats. The connection of these two models at tool level enables practical EAST-ADL designs of embedded automotive systems to be analysed in terms of dependability, i.e. safety, reliability and availability. In addition, the information encoded in the error model can be re-used across different contexts of application with the associated benefits for cost reduction, simplification, and rationalisation of dependability assessments in complex engineering designs

Summary results of the DOE flywheel development effort

The technology and applications evaluation task focuses on defining performance and cost requirements for flywheels in the various areas of application. To date the DOE program has focused on automotive applications. The composite materials effort entails the testing of new commercial composites to determine their engineering properties. The rotor and containment development work uses data from these program elements to design and fabricate flywheels. The flywheels are then tested at the Oak Ridge Flywheel Evaluation Laboratory and their performance is evaluated to indicate possible areas for improvement. Once a rotor has been fully developed it is transferred to the private sector