Control strategy model modeling specification (general)

1. Introduction

1.1. Purpose

This modeling specification is suitable for the development and maintenance of the rapid prototype model in the XXXXX control strategy development phase.
This specification is mainly used to constrain the modeling behavior of XXXX control strategy of XXXXX Department.

1.2. Reference documents

CONTROL ALGORITHM MODELING GUIDELINES USING MATLAB, Simulink, and Stateflow（Ver. 3.0） 
CONTROL ALGORITHM MODELING GUIDELINES USING MATLAB, Simulink, and Stateflow（Ver. 4.01）
Modeling Guidelines for MATLAB/Simulink/Stateflow and TargetLink
1.3. 缩写及术语

MAAB: MathWorks Automotive Advisory Board
RCP: Rapid Control Prototyping
HILS: Hardware-in-the-Loop Simulation Hardware-in-the-Loop Simulation
SF: Stateflow

2. Overview

This specification refers to the part of the model building style in the "Guide to Modeling Control Systems Using Matlab, Simulink and Stateflow" issued by the Automotive Advisory Committee of Mathwork. The expected readers are: professionals who are familiar with the structure of the controlled object, have strong Simulink/Stateflow modeling capabilities, and are familiar with XXXX control ideas.

2.1. Naming Convention

Module	Block(s) / Module(s)	The basic functional unit constituting the Simulink model
model	Model	A collection of modules ( files with suffix .mdl or .slx )
mode	Mode	Exclusive(OR) 和 Parallel(AND)
SF module	SF module / type	Chart in Simulink model
SF state machine	SF State-Machine	The collective name of all SF models in Simulink model
SF block diagram	SF Diagram	What the SF module contains
SF state diagram	State Charts	SF diagrams comprising S partial graph tate (s) of
SF flow chart	Flow Charts	Does not contain any SF block diagram with only connected nodes and transitions

2.2. MATLAB version

This specification should be followed in MATLAB 2009b/2010b/2015b/2016a, unless it is impossible to achieve or comply.
The model will eventually automatically generate embedded code through RTW and apply it to RCP testing.

2.3. Purpose

By restricting the modeling behavior, the following characteristics of the model can be improved or improved:
• Readability: facilitate the understanding of the graphical module architecture, function analysis, and prevent easy errors;
• Modeling efficiency: easy to modify and maintain , Strong reusability, clear interface;
• Simulation and testing: easy to analyze, monitor and test, strong traceability, convenient testing;
• Code efficiency: improve the time efficiency and space efficiency of RTW code, and enhance robustness.