Main menu

Pages

Automotive Software Architectures An Introduction Edit By Miroslaw Staron

 Download Automotive Software Architectures An Introduction Edit By Miroslaw Staron 


Contents Civil Engineering :

1- Introduction
2- Software Architectures: Views and Documentation
3- Automotive Software Development
4- AUTOSAR Standard
5- Detailed Design of Automotive Software
6- Evaluation of Automotive Software Architectures 
7- Metrics for Software Design and Architectures
8- Functional Safety of Automotive Software
9- Current Trends in Automotive Software Architectures
10- Summary

Preface Automotive Software Architectures :

Even since I’ve learned how to drive, I’ve been an enthusiast of cars and driving. The ability to “go places” and be in charge of the machine that can take us to these places has always been something that I’ve loved. When I entered the field of computer science and software engineering, the software was present in cars in very few places—basically only to control the ignition of the engine. At least that was the case in the cars I owned at the time. However, I saw a large potential for using computers in cars.

It is the ability to use more software in cars that triggered my interest in automotive software architectures. In 2015 my publisher contacted me and proposed writing a book about topics I like. I managed to convince my colleagues—Darko Durisic from Volvo Car Group, Per Johannessen from AB Volvo and Wilhelm Meding from Ericsson—to help in writing some of the chapters.

In 2017 we managed to finish the book and we hope that it will provide a solid ground for our readers in designing automotive software. We hope that by writing this book we can contribute to a more exciting, yet at the same time safer, cars. We have enjoyed writing the book and we hope that you, our reader, will enjoy reading our book.

The purpose of the book is to introduce the concept of software architecture as one of the cornerstones of software in modern cars. The book is a result of my work in the area of software engineering, with particular focus on safety systems and software measurement. Throughout my research, I’ve worked with multiple companies in the automotive and telecom domains and I have noticed that over time these domains became increasingly similar. The processes and tools for developing software in modern cars became very similar to those used in the development of telecommunication systems. The same is very true about software architectures— initially very different, today they are increasingly similar in terms of architectural styles, programming paradigms and architectural patterns.
reactions

Comments

table of contents title