This content is not included in your SAE MOBILUS subscription, or you are not logged in.
Developing Production Software Applications Utilizing a Common Architecture and Complete Model-Based Design
ISSN: 0148-7191, e-ISSN: 2688-3627
Published April 12, 2011 by SAE International in United States
Annotation ability available
The Controls and Software Engineering Team at BorgWarner Drivetrain Systems has successfully employed model-based software development for the past several years. Their drivetrain system control software, developed using MATLAB/Simulink/Stateflow, and autocoded using TargetLink, is on the road in many passenger vehicle applications. Using these tools, BorgWarner has realized the widely recognized benefits of model-based design; such as increased speed to market, improved quality, and reduced complexity. Validating algorithms early through simulation and rapid prototyping, then translating them to production software through automatic code generation has proven very successful for BorgWarner.
When starting with model-based design, the BorgWarner team focused on developing the core application control algorithms in the modeling environment. Lower-level software such as I/O drivers, the task scheduler, and communication logic was still hand-coded. As a result, integration of the application algorithms and lower-level software was also performed manually. To eliminate these manual steps, the BorgWarner team set out to develop complete models consisting of both application and lower-level software. The team accomplished this by building the lower-level logic into SimuQuest QuantiPhi blocks and connecting them to the application algorithms directly in the Simulink/TargetLink model. This allows the entire ECU application to be built in the modeling environment, further reducing iteration times for new revisions and improving quality.
This paper describes the new development process based on the “BorgWarner Core 5” software architecture; characterized by abstraction layers, standardized interfaces, and a model-based implementation of both algorithm and hardware-related software.
CitationGinther, B., Fleischer, D., and Mills, J., "Developing Production Software Applications Utilizing a Common Architecture and Complete Model-Based Design," SAE Technical Paper 2011-01-0054, 2011, https://doi.org/10.4271/2011-01-0054.
- www.mathworks.com MATLAB/Simulink/Stateflow product information, Signal Builder product information, Simulink Model Coverage tool product information CONTACT INFORMATION
- www.dspace.com TargetLink product information
- www.simuquest.com QuantiPhi product information
- Chrissis, Mary Beth Konrad, Mike Shrum, Sandy CMMI Guidelines for Process Integration and Product Improvement Second Addison-Wesley Upper Saddle River, NJ 2006
- Beine, M. Eisemann, U. Fleischer, D. Stamatov, S. “Key Factors for Successful Integration of Automatic Code Generation in Series Production Development,” SAE Technical Paper 2009-01-0154 2009 10.4271/2009-01-0154
- Turin, R. Dagci, O.H. Zhang, R. Brown, A.W. et al. “A Flexible Engine Control Architecture for Model-based Software Development,” SAE Technical Paper 2007-01-1623 2007 10.4271/2007-01-1623
- Moradshahi, Peyman Bellairs, David “Model-Based Development: Realizing Fully Integrated Algorithm & Software Development for Production Automotive Electronic Control Units” 2008 Mathworks Automotive Conference