As we outlined with the road map and in the defining the initial Model-Based Design workflow upon the completion of the initial the validation phase begins. To review, with the completion of the initial phase, the following basic concepts have been explored and a base level of mastery established.
- Model architecture: defines the interface of individual models and how model hierarchies are built.
- Data management: data for both models and tests are defined and stored.
- Baseline testing: the fundamentals of a test as you go workflow.
What is next?
In the Initial Adoption phase, a small, well-defined system is selected for the evaluation of the process. In this, the second phase, both the scope and the nature of the algorithm(s) and Model-Based Design processes are expanded.
Expanding scope
What does it mean to expand 
the scope of an algorithm? Basically, there are three components.
- Expand the working group: The initial project consisted of a small working group generally from a few groups. The validation project should include developers from new groups to ensure that issues unique to each group are exposed.
- Increase the complexity: The initial project, intentionally, used a simplified test model. The objective was to validate the Model-Based Design fundamentals, not complex control problems. With the second phase, more complex problems should be tackled; this both exposes issues in the MBD process and the limits of the understanding of the tools.
- Expanding the process: The initial phase focused on the core technologies. The validation phase provides an opportunity to expand the scope of tools used in the Model-Based Design process. Note caution should still be taken to not overload on tools at this still early phase in the adoption process.
Expanding nature
If there are three things that define the
scope of the algorithms, what then defines the nature of your algorithm and Model-Based Design process?
- Systems, not models: With the validation project the designers start designing systems comprised of multiple models and integrating the generated code with existing text-based code (either incorporating the text-based code into the model or the code generated from the model into the text based code)
- Automation of processes: In the initial phase most processes were performed manually. In the validation phase, the working group should look at methods for automating verification and validation processes. This is critical as new developers on-board.
Final thoughts
This post is an introduction to the validation phase; in subsequent posts, I will go into depth on the recommended expanded processes and architectural recommendations for this phase.