4

I've gone through AUTOSAR Layered Software Architecture and understood that it is something like a file structure in which it is defined to have all the hardware abstraction in one directory and called as MCAL, and so on. Am I correct? Does a proper File Structure make a project AUTOSAR Compliant?

If it is a file structure then what should be used as it's build system? shall we use gnu-make?

Improve this question
0

1 Answer 1

Reset to default
6

Autosar is a standardization initiative for software architecture in the automotive industry, and more precisely in the field of Electronic Control Units, which are all theses computing devices involved in the subsystems of a car (e.g. engine, brakes, transmission, etc...).

A reference architecture is not a file format: it‘s primarily a specification. It describes how the software is to be structured, what are the responibilities, functions, or quality attributes expected from the different software components involved. It can also specify some technological building blocks to be used and specify sole common APIs.

The aim of such an architecture is to guarantee interoperability between sub-systems or even parts, which are designed and produced by different suppliers.

Improve this answer
3
  • so if I organize my code as modules specified in the specification according to their functions, will my code be AUTOSAR compliant? Sorry If I understood it in a wrong way. Can you suggest some starting point for me to learn about AUTOSAR from scratch. I need to work on Software Development for ECU's soon.
    – sskartheekadivi
    Commented Sep 24, 2020 at 17:50
  • 1
    @KartheekAssk Imagine you sit in a prototype of a revolutionary self-driving car. You are told that the software is AUTOSAR compliant: would you be reinsured about the quality of the software if it would only about believing in good faith that the developpers organised the code as they understood from reading a spec found on the internet? AUTOSAR is a comprehensive standard. THe layered architecture aim to reduce dependency between components in case of change, the key being to separate hardware dependent and hardware independent parts. (...)
    – Christophe
    Commented Sep 24, 2020 at 18:19
  • 1
    @KartheekAssk but this is only one aspect. You have also API definition, you have coding standards, you have foundation standards, and there are also compliance tests, not to speak about a development process. It's a very comprehensive standard. So the best would be to find some book about the subject.
    – Christophe
    Commented Sep 24, 2020 at 18:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.