The following paragraphs briefly summarize some of the key challenges and their solutions addressed in the video.
Firstly, unreasonable resource allocation can lead to poor project management. In the progress of development, as the complexity of the project increases, improper resource allocation can overwhelm developers and eventually lead to delivery delays.
To deal with this situation, accurate workload estimation can help developers overcome such dilemmas.
As one of its many features, MXAM‘s Global Complexity calculation can check the size and the volume of the model in an objective and comprehensive way. The Global Complexity numbers can be used to the allocation of resources for development, testing and review. MXAM enables precise measurement of complexity metrics, helping developers making appropriate decisions and timely adjustments, thereby ensuring the smooth and on-time delivery of the product.
Secondly, overly complex models can affect the on-time delivery of the software. If the structure of the model is too complex, it becomes a significant challenge to deliver the product on time. Even with the best initial design, models can still become overly incomprehensible as errors are fixed and new features are added. Statistically, the greater the complexity of a part of the model becomes, the higher the possibility of errors.
To meet this challenge, reducing model complexity can help minimize errors, and make it easier for developers to review and fix the errors.
MXAM supports this by precisely identifying the most complex part of the model, while also helping to make appropriate decisions.
In addition, inconsistent modeling styles can hinder software development progress. In developing control algorithms, Simulink provides many implementation methods for one given question. If different teams need to use this model at different stages of development, the inconsistent modeling style can lead to difficulties in understanding the model between teams, resulting in more time and effort.
At this point, following a consistent modeling style becomes an effective solution.
MXAM can identify and adjust all model parts that do not conform to modeling guidelines, ensuring consistency in the modeling process.
At the same time, the error-prone modeling styles increase the difficulty of later fixes, and can also lead to unexpected behavior. The features of Simulink are very broad for many domains. Many of these are error-prone, so guidelines require the selection of certain reliable language subsets.
Again, MXAM can assist here: MXAM‘s guideline checks ensure the reinforcement of defensive implementation techniques, the use of modeling language subsets, and consistent data and control flows that are recommended mehods by the functional safety standard ISO 26262.
Finally, whether the development process complies with the ISO 26262 standard should also be considered. It has already been considered as a necessity that the development process should align with ISO 26262 requirements.
MES also offers consulting services for the deployment of ISO 26262 complaint development processes. From analyzing current development processes to implementations, the MES process and quality service team provides professional support, introduction and software development optimization related to ISO 26262, ASPICE and AUTOSAR. Tailored consulting services include MBD process, safety development, and ASPICE fundamental practices.
