AUTOSAR is an open and standardized framework for automotive electronics. It enables the establishment of a common ECU software architecture by supporting standardized interfaces between application software and basic vehicular functions. Standardization has significantly changed how software is developed in the automotive industry. A turning point, to be sure, but one that also introduced new challenges as AUTOSAR is known to be complex to handle. So, the question is, can only experts with specific training be in the position to design components for an AUTOSAR environment? Are there any technologies that can simplify its approach and protocols? The answer is yes, thanks to our SodiusWillert solutions, deployed in your IBM Rhapsody Model-Driven Development environment.
I. AUTOSAR: when standardization leads to a certain level of complexity
II. The challenges of AUTOSAR standard in the daily routine of engineers
III. So, does rigorous training and extensive AUTOSAR experience make a difference?
IV. How do we work on reducing AUTOSAR complexity?
V. Conclusion
AUTOSAR: when standardization leads to a certain level of complexity
It's worth considering AUTOSAR as a common vendor-independent framework facilitating some benefits, including reusability, transferability, and flexibility.
In this light, standardization seems to have solved all the problems experienced by software and systems engineers, vehicle architects, configuration managers, and all relevant parts of the automotive industry. However, it's not as simple as it sounds, and standardization comes with its own set of complexity. Engineers are now expected to follow extended and highly rigorous guidelines and to master them in the blink of an eye.
To help you appreciate the level of complexity, let's draw an analogy with learning a foreign language. Assimilating a new one, without specific help or tools, can be a long and tedious process - especially when syntax, semantics, and characters are radically different from those you speak and write fluently. Back to the AUTOSAR context, engineers are required to know how to comprehend and delve into a specific (layered) architecture, with its own components and elements. In the same logic, it doesn’t happen overnight!
The challenges of AUTOSAR standard in the daily routine of engineers
Software engineers need to stay focused on their core activities, which are the creation and development of new features and reliable components. Overly complex protocols, different architectures, and extensive guidelines make them lose sight of their objectives, and waste extremely valuable time.
They also have multiple other questions to consider if they want to perform their tasks in the best conditions. These are the most recurrent sources of concern:
- Finding the right and clearest documentation
- Gathering in one model, the multiple architectures resulting from the coexistence of Classic and Adaptive AUTOSAR
- Converting their SysML and UML models without reinventing the wheel
- Developing components without starting from scratch
- Make sure that their current design, modeling, and development solutions are compatible with AUTOSAR enabling tools
All this, at a time when the race to innovate and compete is more aggressive than ever and where release cycles are constantly shrinking....
So, does rigorous training and extensive AUTOSAR experience make a difference?
End of the suspense: despite its apparent complexity and numerous challenges, you don’t need to have an extensive AUTOSAR background or be certified in the field to develop AUTOSAR-compliant modules and interfaces. Of course, some initial knowledge can help, but it is not an essential prerequisite. And this is where engineering tools and their wide range of capabilities enter the picture.
SodiusWillert's solutions for AUTOSAR support the seamless conversion of your SysML environment into AUTOSAR-compliant models and further to UML.
Technologies such as automatization capabilities ensure that no in-depth AUTOSAR expertise and knowledge is required. It also enables your engineers to work more peacefully and to focus on their key strengths and tasks.
Now, let's take a closer look at the specific capabilities of our solutions and how we work on reducing complexity.
How do we work on reducing AUTOSAR complexity?
1. Seamless integration of AUTOSAR standard in IBM Rhapsody’s environment
- Seamless modeling
IBM's AUTOSAR Extension for IBM Engineering Systems Design Rhapsody (developed by SodiusWillert) seamlessly integrates AUTOSAR standard with IBM's Rhapsody Model-Driven Development (MDD) tool. Navigating the intricacies of model-driven is already no mean feat. By enabling Rhapsody to support AUTOSAR, developers can streamline their workflow and reduce the complexities associated with integrating disparate tools and standards.
This IBM’s technology is here to provide a unified environment where software engineers and developers can switch from the modeling phase to implementation without manually translating their model to the right code. The risk of errors is very low, and they progress considerably faster.
- Import and export models more easily
The System Authoring tool enhances the import of your ARXML models into Rhapsody. It integrates a SysML modeler and a suite of valuable views, so you can seamlessly edit your AUTOSAR-compliant models. In addition, it also facilitates the export of your Electronic Control Unit (ECU) and manifests to ARXML format.
2. Source Code Generation
RXF for AUTOSAR Classic allows the automatic generation of AUTOSAR compliant code from IBM Rhapsody models, ensuring consistency, reducing human errors, and improving development speed.
Considering Classic AUTOSAR and its layered architecture, our solution generates executable code that enables communication of your AUTOSAR application with the Runtime Environment (RTE). The executable framework we are working in allows developers to verify and validate the consistency of a model before moving to the implementation stage.
Indeed, guidance throughout the validation and verification processes is achieved by instrumenting the runtime performance and behavior while you are doing component integration. Therefore, it ensures a highly valuable consistency between your AUTOSAR software specification and component implementation.
Download our RXF for AUTOSAR Classic product sheet
3. Model-to-Model Transformation (M2M)
M2M is a rule-based model transformation tool that allows seamless import/export of entire models or specific subparts across a wide range of domains. It enhances modeling workflows with automated, comprehensive, flexible rules features, preventing you from manually transforming models. You are no longer overwhelmed by numerous modules and details.
Instead, you can develop and implement your component from a software designer’s point of view, no more no less. This approach helps you to focus only on the elements you need. Plus, you can transition between different modeling tools at any phase of your MBSE process, allowing a great deal of interoperability.
Learn more about M2M Transformation for Rhapsody
4. Complete AUTOSAR support
Our solutions integrate both AUTOSAR Classic and Adaptive platforms. Indeed, we provide a code generation and execution framework allowing Rhapsody UML models to operate within a Classic AND an Adaptive AUTOSAR environment. You ensure compatibility with a wide range of existing systems and, above all, with the latest and most innovative technology in the industry.
5. Rigorous validation and verification protocols
We provide built-in validation and verification tools, allowing developers to spot and resolve errors early in the process. Not only does this reduce development costs, but it also means you get higher-quality software. Step-by-step guidelines and processes help you see the bigger picture.
Learn more about Embedded UML Studio and Embedded UML RXF.
6. Extensibility
SodiusWillert’s AUTOSAR solutions are designed to be easily extended and customized to your specific needs. Software engineers, developers, and the teams involved can smoothly add new features or tailor the tool.
Conclusion
It's now clear that engineering tool improvements, particularly automation, will play a major role in the engineering team's understanding of AUTOSAR. The need for software solutions and tools will continue to increase. For developers, these tools are invaluable, as they let them stay focused on what they do best and release their full potential. They can work with greater peace of mind without the burden of navigating a complex environment.
Find out more about our AUTOSAR solutions or contact us.
Leave us your comment