Software development team is dedicated to developing projects for automotive industry, in accordance with AUTOSAR, ASPICE and ISO26262. Focal point is concentrated on development of application software (ASW) and basic software (BSW) for power electronics. The team consists of experts of the areas required to fulfil the V-Cycle process declared in the industry standard ASPICE reference model.
In summary, we deliver turn-key software solutions for automotive OEMs.
Requirement Analysis
Ascertaining and organizing client requirements in accordance with codes and standards.
Architectural Design
Organizing customer requirements into logical operations encapsulating hardware, software, and communication.
Detailed Design and Unit Construction
The creation of software requirements to match the system requirements and the development of service units.
Unit Test Verification
Simulation process of the model-based or software-based model unit testing based on requirements and basic standards.
Integration and Integration Testing
The evaluation of software architecture and whether the service units are still in function.
Software Qualification Testing
Integration process of every services into the full system and testing for functionality and requirement achievement.
Model-based design differs from traditional software design with two key differences; A system model is at the core of development, from requirement analysis through design, implementation, and testing. Many of the time-consuming and error-prone steps in the workflow, such as code generation, traceability, verification, etc. are automated.
Software integration is an integration process to merge different developed software components that operate together and then build the software to generate machine codes from human-readable scripts.
Bench testing & debugging on the evaluation board (SPC58) platform is a system that allows testing/debugging of codes on the SPC58 platform. This system provides the developers to design till ASIL-D safety levels and observe all states and functionalities of code that is engineered for applications to be used in automotive.
Model/Software/Hardware-in-the-loop (MIL-SIL-HIL) simulations are testing and validation processes with a related test bench, model, software and electronic control units, etc. The validation process of the model/software/hardware is executed with the customer requirements to ensure the compatibility of hardware and software. XiL simulations offer great advantages in terms of cost and practicality, by allowing you to use the model to represent the facility.
AUTOSAR is a software architecture development process that is used for automotive ECUs to standardize safety requirements for three-layered software architecture: application, runtime environment (RTE), and basic software (BSW). AUTOSAR increases the quality, reliability, scalability, and maintainability of the system, software, and communication services on the vehicle in the development process between partners.
Functional safety has been standardized as ISO-26262 for safety and functional parts in the integration, verification, and validation process of the embedded automotive software development. This standardization is used to achieve safety goals and safety requirements of the product to prevent system malfunction from predictable errors, problems, and hazards by risk analysis. The software components and units are classified into 5 main levels of risk Quality Managed (QM) and Automotive Safety Integrity Level (ASIL A to D).