Search Results

Using a Model-based approach to the embedded software development process contributed significantly in reducing the development time while also supporting a high quality level of the software code implementation. However, based on our experience with CNH Industrial application scenarios, involving multiple suppliers from vehicle ECU to the engine ECU, it only addressed the need of the implementation phase without any consistent influence in other software development life-cycle phases such as requirements and specification. Mandatory functional safety requirements, new complex functionalities, and reducing time to delivery while maintaining high quality level of software are driving factors in our new software development projects. Ideally the adoption of international standards, as for example the ISO 12007, and the safety standards, as the ISO 26262, ISO 25119 and ISO 13849, should represent a consistent guide to develop software.

In the last Years, there is the awareness that the migration to Model-based approach, allowing to System engineers and the Software engineers the use of the same executable model as working paper throughout the development process from requirements capture and specification to coding and test, is the only possibility to address the real needs of the Sw Embedded development Process (continue Specification changes, unrealistic schedule, cost reduction). Besides, in today's commercial vehicle development process, the enhancement of the vehicle or the realization of new line is obtained through the introduction of Safety critical electronics Systems. The ISO 26262 aims to ensure the functional safety related electronics systems in the Road Vehicles. Other side, the ISO 12207 describes the processes that should occur during the life cycle of a software development process from its conceptualization through its retirement.

The implementation of CAN messages has been a critical aspect of the ECU development process in recent years. The traditional approach generates more inconsistencies between the specification and the software coding (implementation), probably coding errors, and variable reproducibility of the implementation, depending on the ECU platform. Therefore in order to achieve an efficient development, the use of a high abstraction level of the CAN protocol is essential. The IVECO Electronics (IE) approach places emphasis on integrating various phases of the traditional Sw development process for the CAN Interface, hence leading to faster production of quality code and minimizing the cost associated with fixing the problems.

The implementation of CAN messages has been a critical aspect of the ECU development process in recent years. The traditional approach generates more inconsistencies between the specification and the software coding (implementation), probably coding errors, and variable reproducibility of the implementation, depending on the ECU platform. Therefore in order to achieve an efficient development, the use of a high abstraction level of the CAN protocol is essential. The Eltrac approach places emphasis on integrating various phases of the traditional Sw development process for the CAN Interface, hence leading to faster production of quality code and minimizing the cost associated with fixing the problems.