Model-Based Design Terminology

This page attempts to define terms in common use in Model-Based Design.  For the most part, I will attempt to stay with generic definitions however some of the information will reflect my standard working environment of MATLAB and Simulink.

Child model: A model referenced inside of an integration model.  Normally child models are sized so that a single developer can have ownership of the model.

Control model: A model used to represent all or part of a controls system.

Data-driven modeling: A paradigm where data is used to configure the models’ behavior through the use of parameter sets.  The parameter sets change the functional behavior of the model.

Integration model: A model comprised of 2 or more child models used to integrate components into a larger system.  In best practice the integration model does not perform any calculations it is used simply for connecting and scheduling child models.

Parameter set:  A group, set, of data that defines an instance of a model; related to data-driven modeling.

Plant model: A model used to represent a physical system such as the lift produced by an aircraft wing dependent on speed and angle of attack.

Process adoption team:  A group of people who have responsibility for implementing the process change.  The group should have representation from Management (project and senior), controls engineers, system engineers, test engineers.  There should be a core group that is consistent throughout the adoption process, some roles will cycle on and off depending on the phase and tasks that are active.

Model: A software artifact used to represent all or part of a system such as a Simulink .slx file.

Shell model: A model that only has inports and outports but no functional code.  Shell models are used early in the development process to provide defined interfaces in the system level model.  Inports and outports for the shell model should be defined with respect to the data type and dimension.

System level model: See Integration model