Technologies

Software Development for Automotive Industry Expert.

Both in Engineering Services And Engineering Consultancy.

Introduction to AUTOSAR

AUTOSAR is an abbreviation of Automotive Open System Architecture and it is not just a set of technical specification but also a framework of how a software development of an electronic control unit (ECU) should be done. It describes how the data among the stakeholders should be exchanged including the exchange format. Furthermore, the software architecture is also standardized and the interfaces among the modules are specified. 

AUTOSAR defines the software as three layers, i.e. Application, Runtime Environment (RTE) and Basic Software (BSW): 

 

Figure 1: Three layers of AUTOSAR architecture 

The BSW layer is divided into Services, ECU Abstraction, Mictrocontroller Abstraction Layer (MCAL) and Complex Drivers: 

Figure 2: Major Layers of the BSW 

Then the BSW layers are further segregated into modules as follows: 

Figure 3: Major components of the BSW layers 

These modules communicated with each other via interfaces specified by the AUTOSAR standards: 

Figure 4: AUTOSAR interfaces 

Advantages of using AUTOSAR 

  1. Software sharing can be possible between different companies 
  2. Reusability of software component 
  3. The basic software architecture is layered. 
  4. Consistency of interfaces 
  5. Interoperability 
  6. Software code can be reused. 
  7. Design flexibility is more 
  8. Less time to market 
  9. Cost efficiency over long product lifecycle 
  10. Efficiency can be increased within functional development 
  11. Transparency & distinct interfaces will allow new business models. 

Disadvantages of using AUTOSAR 

  1. Require more resources than legacy (controller optimized) architecture 
  2. Learning curve 
  3. Initial cost for tooling and licensing 
  1. Design and configuration of the Software Components (SWC) on the Application layer 
  2. AUTOSAR-conform implementation of the Application SWCs using hand-coding or MBD methodologies 
  3. Configuration of the BSW layer (OS, COM, BSW, NVM, CRYPTO, IO and DIAG) 
  4. Integration of AUTOSAR conform architectures into PowerPC and TriCore architectures 
  5. Using tools from Vector Informatik or dSPACE 

Introduction To Model-Based Software Development (MBD) ​

Model-Based Software Development or short MBD is a tool aided software development which simplified the way embedded software is developed and along the way also improves it significantly. From the name itself, an application model is developed using a graphical programming tool e.g. SIMULINK or ASCET and then the code will be generated based on the designed model. 

 

Figure 5: SIMULINK model example 

Figure 6: ASCET model example 

Usually MBD follows the V model software development process. 

Advantages of MBD

  1. Leverage graphical model to improve understandability of the logic 
  2. Using tool automations and code generator to improve multiple aspects of the software developments 
  3. Increase readability 
  4. Reduce time-to code 
  5. Reduce time-to-market 
  6. Remove human errors 
  7. Increase software quality 
  8. Increase testability 
  9. Increase reliability 

Disadvantages of MBD 

  1. High initial tool cost and licensing 
  2. Learning curve 
  1. Toolchain design of the MBD process according to V model and ASPICE from design until verification. 
  2. Application software development using TargetLink from dSPACE or Embedded Coder from Mathworks. 
  3. AUTOSAR conform SWC development using MBD methods. 

Introduction To SAP BASIS

SAP BASIS stands for Business Application Software Integrated Solution. It is a set of tools that will work as a bridge between your operating system, communication protocols, the various business applications, and database. SAP BASIS also includes different administration activities. These are load balancing, installation, and also maintaining the performance of the SAP systems that are being executed on SAP ABAP or Java stack. You can say that BASIS is an operating system for ABAP and SAP applications. 

The SAP BASIS system is divided into Presentation Layer, Application Layer and Database Layer. 

Figure 8: Layers of SAP BASIS 

  1. Design of the SAP system. 
  2. Installation of the database system. 
  3. Upgrade and maintenance of each of the SAP BASIS layers.