This post is number 6 in a series of 8 video blogs, walking through the fundamentals of Model-Based Design. When taken as a whole, these videos provide the foundation stones for understanding and implementing Model-Based Design workflows I will be using a simple Home A/C system for my example; however the principals apply to everything from chase Avoidance controllers featuring to Zig and Zag dodging. ⁽¹⁾

Having a clear refining and elaboration process is key to an organized development process. The “test-as-you-go” methodology (also known as test-driven development) that I describe here provides a natural framework for ensuring that the system is in alignment with requirements throughout the development process.

1. Requirements
   1. Requirements Management
   2. Writing clear requirements
   3. What I’m expecting: writing requirements
2. System Architecture
   1. Modeling architecture: Fundamentals
   2. Model architecture decomposition for hardware and close loop testing
   3. Is your system architecture “Lego Legal”?
3. Initial (shell) models
   1. Modeling architecture with room to grow
   2. The Model-Based Design Workflow…
   3. Defining your initial Model-Based Design workflow
   4. Plants resting on a table
4. Defining and managing data
   1. Managing Data
   2. Understanding Data Usage in Model-Based Design Part I
      and
   3. Understanding Data Usage in Model-Based Design Part II
   4. The Simulink Data Dictionary
5. V&V
   1. The 8 commandments of V&V
   2. Levels of testing
   3. Modular testing environments
6. Refining the models
   1. Defining your initial Model-Based Design workflow
   2. Best Practices for Establishing a Model-Based Design Culture
7. Code generation
   1. https://www.mathworks.com/solutions/embedded-code-generation.html
8. The grab bag…
   1. A road map for Model-Based Design
   2. The next generation of Model-Based Design

Footnotes

1. Zig/Zag dodging being the preferred method for not getting tagged in the game of “tag.”