system design description -凯发k8网页登录

main content

system design description

predefined standard reports

from the simulink® toolstrip, you can generate two predefined, standard simulink report generator™ reports called:

  • system design description

  • system requirements traceability

the system design description report provides summary or detailed information about a system design represented by a model. you can choose report options using the report dialog, or you can create a customized version using the report explorer. for details, see generate system design description reports.

you can use the system design description report setup file as a starting point for creating a setup file for your own report. for more information, see .

the system requirements traceability report requires that you have requirements toolbox™ installed. the system requirements traceability report includes information about all the requirements associated with the model and its objects.

follow these steps to generate the system requirements traceability report from the simulink toolstrip:

  1. if the requirements tab is not available, on the apps tab, in the model verification, validation, and test section, click requirements manager.

  2. on the requirements tab, in the share section, click share > generate model traceability report.

what is the system design description?

the system design description is a prebuilt simulink report generator report that describes the system design represented by a simulink model.

by default, the simulink report generator generates the report for the model from which you invoke the system design description report option.

what you can do with the report

you can use the system design description to

  • review a system design without having the model open

  • generate summary and detailed descriptions of the design

  • assess compliance with design requirements

  • archive the system design in a format independent of the modeling environment

  • build a customized version of the report, using the report explorer

report contents

you can specify what kinds of information to include in the report, in terms of:

  • what elements of a model to include in the report (for example, whether to include subsystems from custom libraries)

  • whether to generate a summary version or a detailed version of the system design description report.

for details, see generate system design description reports.

summary version

sectioninformation
report overview

model version

root system
  • block diagram representing the algorithms that compute root system outputs

  • description (if available from model)

  • interface: name, data type, and other properties of the system input and output signals

  • subsystems: the path and a block diagram for each subsystem

  • state charts

  • requirements (optional)

subsystems
  • path

  • block diagram

system design variables
  • design variables

  • functions in design variable expressions

detailed version

the detailed version of the report includes all the information that is in the summary form of the report, as well as more information about the system components. the atomic subsystem information is more detailed than virtual subsystem information.

sectioninformation
report overview

model version

root system
  • block diagram representing the algorithms that compute root system outputs

  • description (if available from model)

  • interface: name, data type, and other properties of the root system input and output signals

  • block parameters

    • includes detailed information about matlab function blocks

  • block execution order for root system and atomic subsystems

  • look-up tables

  • simulink workspace variables

  • model configuration sets

  • state charts

  • requirements (optional)

subsystems

the same type of information as the information for the root system, as well as:

  • path of the subsystem in the model

  • (for atomic subsystems) checksum that indicates whether the version of an atomic subsystem that generates the report differs from other versions of the subsystem

  • referenced models (optional)

  • subsystems from custom libraries (optional)

state charts
  • state chart

  • states

  • transitions between the states

  • junctions

  • events that trigger state transitions

  • data types

  • targets

  • truth tables

report captures documentation included in a model

the system design description reports documentation included in a model, including:

  • the model description (from the model properties)

  • the block property description

  • docblock model documentation blocks

to enrich the generated system design description, add corresponding information in the model.

网站地图