From their web profiles:

Yanja Dajsuren is a program director of the PDEng Software Technology program and assistant professor at the Software Engineering and Technology (SET) group, Eindhoven University of Technology (TU/e).... Mark van den Brand is a graduate school dean at the Department of Mathematics and Computer Department and a full professor at SET group of the TU/e.

TU/e offers an automotive technology master’s program. From their backgrounds, one can conclude that they are knowledgeable and qualified to edit a book in such a broad and complex field.

I call this field very broad and complex because, to start with, software engineering itself is a very broad area. In fact, software engineering is sometimes called “the queen of the technology,” similar to the quote attributed to mathematician Carl Friedrich Gauss: “Mathematics is the queen of the sciences.” The ubiquitous nature of software in all our technological advancements is astounding and continuously growing. If we add to this technologies associated with transportation, the size and complexity becomes exponential. Two major standardization efforts tackle these problems: MISRA C and ISO 26262 (“Road vehicles--Functional safety”).

Since the book does not have a universal index, I could not systematically check which chapters cover these standards. However, I noticed coverage of ISO 26262 in several parts.

Part 1’s overview chapter ably states the difficulties of the area and ways to tackle the problems.

The next three chapters constitute Part 2, “Automotive Software Development.” “Requirements Engineering for Automotive Embedded Systems,” by Miroslaw Staron, provides background on requirements and mapping to ISO 26262. “Status Report on Automotive Software Development,” by Bock et al., gives a comprehensive survey of challenges and remedies. “State-of-the-Art Tools and Methods Used in the Automotive Industry,” by Harald Altinger, presents a high-level overview of the tools and methods used in the field.

In the interest of brevity, I will refrain from explaining every chapter after this point; the titles are self-explanatory. The book’s 16 chapters, grouped into six parts, can be viewed online (https://www.springer.com/us/book/9783030121563).

In conclusion, this book could be useful to people who wish to explore, and who excel in, this area; however, it will not be helpful to experts. I presume that it will be useful to readers who need a detailed overview of the subjects associated with automotive software systems engineering.