T-engineering has always focused on model-based development, utilising the MathWorks Simulink environment to develop algorithms and produce reliable C code. Our drive for higher quality and shorter time-to-production has led to T-engineering adopting the model-based approach to systems engineering as well in order to remain competitive and improve customer satisfaction.
When embracing model-based systems engineering we are in effect creating a set of interconnected models that capture knowledge and then presents it in different ways. By doing so we assist our engineers in finding problems early on and identifying correlations and insights that can lead to new solutions. By combining MBSE with a quality-orientated approach we can then deliver full-fledged, safe and reliable solutions to our customers, minimising development time, and doing so at competitive prices. This is key when developing for increasingly more complex vehicle technology.
Adopting MBSE does pose several challenges; for example, how to ensure that value is added, that the objectives are met and how standards like ISO26262 are fulfilled whilst remaining competitive and flexible. But as we’ve said before, where others see challenges, we find opportunities instead.
To meet these challenges, we are not only applying a model-based systems engineering approach to our software systems, but we are also applying it to the entire development process. Model-based process engineering, if you will.
By doing so, we fully understand the connections between activities, roles, and outcomes. Procedures are written with a clear role in mind, data is presented in a way that assists the engineer instead of hindering them and thus tools are selected or developed to fit our needs and not the other way around.
