Automotive Software Architectures

This book introduces the concept of software architecture as one of the cornerstones of software in modern cars. Following a historical overview of the evolution of software in modern cars and a discussion of the main challenges driving that evolution, Chapter 2 describes the main architectural styles of automotive software and their use in cars’ software. Chapter 3 details this further by presenting two modern architectural styles, i.e. centralized and federated software architectures. In Chapter 4, readers will find a description of the software development processes used to develop software on the car manufacturers’ side. Chapter 5 then introduces AUTOSAR – an important standard in automotive software. Chapter 6 goes beyond simple architecture and describes the detailed design process for automotive software using Simulink, helping readers to understand how detailed design links to high-level design. The new chapter 7 reports on how machine learning is exploited in automotive software e.g. for image recognition and how both on-board and off-board learning are applied. Next, Chapter 8 presents a method for assessing the quality of the architecture – ATAM (Architecture Trade-off Analysis Method) – and provides a sample assessment, while Chapter 9 presents an alternative way of assessing the architecture, namely by using quantitative measures and indicators. Subsequently Chapter 10 dives deeper into one of the specific properties discussed in Chapter 8 – safety – and details an important standard in that area, the ISO/IEC 26262 norm. Lastly, Chapter 11 presents a set of future trends that are currently emerging and have the potential to shape automotive software engineering in the coming years. This book explores the concept of software architecture for modern cars and is intended for both beginning and advanced software designers. It mainly aims at two different groups of audience – professionals working with automotive software who need to understand concepts related to automotive architectures, and students of software engineering or related fields who need to understand the specifics of automotive software to be able to construct cars or their components. Accordingly, the book also contains a wealth of real-world examples illustrating the concepts discussed and requires no prior background in the automotive domain. Compared to the first edition, besides the two new chapters 3 and 7 there are considerable updates in chapters 5 and 8 especially.

This book presents the state of the art, challenges and future trends in automotive software engineering. The amount of automotive software has grown from just a few lines of code in the 1970s to millions of lines in today’s cars. And this trend seems destined to continue in the years to come, considering all the innovations in electric/hybrid, autonomous, and connected cars. Yet there are also concerns related to onboard software, such as security, robustness, and trust. This book covers all essential aspects of the field. After a general introduction to the topic, it addresses automotive software development, automotive software reuse, E/E architectures and safety, C-ITS and security, and future trends. The specific topics discussed include requirements engineering for embedded software systems, tools and methods used in the automotive industry, software product lines, architectural frameworks, various related ISO standards, functional safety and safety cases, cooperative intelligent transportation systems, autonomous vehicles, and security and privacy issues. The intended audience includes researchers from academia who want to learn what the fundamental challenges are and how they are being tackled in the industry, and practitioners looking for cutting-edge academic findings. Although the book is not written as lecture notes, it can also be used in advanced master’s-level courses on software and system engineering. The book also includes a number of case studies that can be used for student projects.

Software Engineering for Automotive Systems: Principles and Applications discusses developments in the field of software engineering for automotive systems. This reference text presents detailed discussion of key concepts including timing analysis and reliability, validation and verification of automotive systems, AUTOSAR architecture for electric vehicles, automotive grade Linux for connected cars, open-source architecture in the automotive software industry, and communication protocols in the automotive software development process. Aimed at senior undergraduate and graduate students in the fields of electrical engineering, electronics and communication engineering, and automobile engineering, this text: Provides the fundamentals of automotive software architectures. Discusses validation and verification of automotive systems. Covers communication protocols in the automotive software development process. Discusses AUTOSAR architecture for electric vehicles. Examines open-source architecture in the automotive software industry.

With the advent of software and electronics, automotive companies are enabling innovation to improve safety, driver experience, and fuel efficiency Increasing use of software over the years, introduced the paradigm shift by requiring automotive companies to develop their systems using architecture and model based techniques The goal of this workshop is to address issues related to the appropriate automotive system software architecture and engineering techniques, which can be accepted by the automotive industry Therefore, to bring together researchers and practitioners in the area of automotive system software architecture and engineering, the international workshop on the Workshop on Automotive Software Architectures (WASA) is organized

A Clear Outline of Current Methods for Designing and Implementing Automotive Systems Highlighting requirements, technologies, and business models, the Automotive Embedded Systems Handbook provides a comprehensive overview of existing and future automotive electronic systems. It presents state-of-the-art methodological and technical solutions in the areas of in-vehicle architectures, multipartner development processes, software engineering methods, embedded communications, and safety and dependability assessment. Divided into four parts, the book begins with an introduction to the design constraints of automotive-embedded systems. It also examines AUTOSAR as the emerging de facto standard and looks at how key technologies, such as sensors and wireless networks, will facilitate the conception of partially and fully autonomous vehicles. The next section focuses on networks and protocols, including CAN, LIN, FlexRay, and TTCAN. The third part explores the design processes of electronic embedded systems, along with new design methodologies, such as the virtual platform. The final section presents validation and verification techniques relating to safety issues. Providing domain-specific solutions to various technical challenges, this handbook serves as a reliable, complete, and well-documented source of information on automotive embedded systems.

Since the early seventies, the development of the automobile has been characterized by a steady increase in the deploymnet of onboard electronics systems and software. This trend continues unabated and is driven by rising end-user demands and increasingly stringent environmental requirements. Today, almost every function onboard the modern vehicle is electronically controlled or monitored. The software-based implementation of vehicle functions provides for unparalleled freedoms of concept and design. However, automobile development calls for the accommodation of contrasting prerequisites – such as higher demands on safety and reliability vs. lower cost ceilings, longer product life cycles vs. shorter development times – along with growing proliferation of model variants. Automotive Software Engineering has established its position at the center of these seemingly conflicting opposites. This book provides background basics as well as numerous suggestions, rare insights, and cases in point concerning those processes, methods, and tools that contribute to the surefooted mastery of the use of electronic systems and software in the contemporary automobile.

This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties. It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts. It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail. It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.

The software development ecosystem is constantly changing, providing a constant stream of new tools, frameworks, techniques, and paradigms. Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. This practical guide ties those parts together with a new way to think about architecture and time.