Documentation

This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

na_0007: Guidelines for use of Flow Charts, Truth Tables and State Machines

ID: Title

na_0007: Guidelines for use of Flow Charts, Truth Tables and State Machines

Priority

Strongly recommended

Scope

MAAB

MATLAB Versions

All

Description

Within Stateflow, the choice of whether to use a flow chart or a state chart to model a given portion of the control algorithm functionality should be driven by the nature of the behavior being modeled.

  • If the primary nature of the function segment is to calculate modes of operation or discrete-valued states, use state charts. Some examples are:

    • Diagnostic models with pass, fail, abort, and conflict states

    • Model that calculates different modes of operation for a control algorithm

  • If the primary nature of the function segment involves if-then-else statements, use flow charts or truth tables.

Specifics

If the primary nature of a function segment is to calculate modes or states, but if-then-else statements are required, add a flow chart to a state within the state chart. (See Flow Chart Patterns.)

Rationale

  • Readability

  • Workflow

  • Simulation

  • Verification and Validation

  • Code Generation

Last Changed

V2.0

Model Advisor Check

Not applicable

Introduced in R2010a

Was this topic helpful?