Taming the Beast – How to Manage Large Software Models
|Jul 17-18, 2019||English||Troy (Detroit), MI, U.S.|
|Sep 12-13, 2019||German||Berlin, Germany|
Models are the core artifacts in automotive software development. Over time – within a single development project or even across multiple evolution steps – models grow as they capture more and more functionality. As a result, models become hard to maintain, rarely understandable, and the risk of errors due to unexpected behavior increases. The technical debt of the model demands proper countermeasures. This training class addresses deficits caused by large models and shows ways to overcome their risks.
Also available as an in-house training class worldwide on request.
In this case, our instructors can tailor the curriculum to meet your specific needs.
"The seminars provide insight and ideas on how to approach handling large software projects in a systematic way with useful suggestions and quantitative metrics."
This training class is targeted towards modelers, developers, testers, quality managers, project managers, and team leaders, whose focus is model-based development of embedded software based on MATLAB®/Simulink® for serial projects.
- Basic concepts of software architectures
- Assessing architectural design principles in models
- Refactoring Simulink® models
- Layered application architectures
- Representing architectures in models
|10 a.m.||Welcome and introduction round|
|10:30 a.m.||Overview: Model-based development and quality assurance with Simulink®
|12 p.m.||Lunch break and open dialog|
|1 p.m.||Analysis and evaluation of model structure
|2:45 p.m.||Software architecture
|4:30 p.m.||Implementing software architectures in models
|5:15 p.m.||Integrated models and distributed modeling
|6 p.m.||End of day|
|9 a.m.||Refactoring Simulink® models and their structure
→Hands-on using MES's latest refactoring tool
|10:45 a.m.||Refactoring Stateflow® charts
→Hands-on with participant models
|12:15 p.m.||Lunch break and open dialog|
|1:15 p.m.||Regression testing of models
|3 p.m.||Process concerns regarding refactoring
|4:30 p.m.||Summary and conclusion|
|5 p.m.||End of training class|