This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Component Design

Component Design

Component Documentation

Reports

1 - SF023A_TunSelnAuthy_Design_PeerReviewChkList

Nexteer_Template_V1.0

Overview

Peer Review Instructions
Technical Review Checklist
Template Change Log

Sheet 1: Peer Review Instructions

Instructions for Functional Design Package Peer Review




PRE-MEETING


Function OwnerConfirm that requirements are reviewed and approved PRIOR to the FDP peer review

Function OwnerStart with latest version of the template for any "first reviews" - Continue to use existing temmplate for re-reviews

Function OwnerProvide the functional design package (changed documents) to the invited attendees 1-2 working days in advance of review

Function OwnerNotify the assigned peer reviewer and make sure they are prepared to do their function in the meeting

Function OwnerIdentify necessary attendance and invite to meeting

Function OwnerComplete the "Author" column information for sections 1 through 5 prior to the review

Function OwnerComplete the attendance invitation list in section 7

Function OwnerFor Re-reviews only: Complete the column "remarks by author" to identify actions taken to address items found in earlier reviews.



DURING MEETING


Function OwnerPresent document changes to the review team

Peer ReviewerCapture attendance of the review

Peer ReviewerCapture actions and issues in section 6. Identify issue summary, Document type, Reference (Requirement ID, section number, etc), Defect Type and indicate status as "OPEN"



POST MEETING


Function OwnerFollow up on all "open" items. Update "Summary of Resolution" to indicate what was done or decided.

Function OwnerSchedule follow up review OR review open items with peer reviewer and obtain agreement to close

Peer ReviewerClose change request in system and confirm all associated tasks are complete. Upload peer review checklist (this document) with any FDP updates

Sheet 2: Technical Review Checklist

Technical Review Checklist - Template Version 02.02.00







Product NameElectric Power SteeringElectrical Arch.4Review ScopeDefect TypeNumbers




YesClosedFR
Function IDSF023A_TunSelnAuthy

Added New Input Signals "HwVel'" and "TunSelnRtDi".
Added new configurable Thresholds for Handwheel
Torque & Handwheel Velocity as a function of Vehicle Speed.
Added new Calibration to disable a Tuning Selection.		Requirement0




NoRejectedFDD
Long NameTuning Selection Authority

Interface0




NAOpenModel
Version that you started from. NOT the version you hope to release. If this will be v1.0.0, enter NA. Starting Baseline1.0.0EffortDesign0






FMEA
AuthorSivaReview Effort(Hrs.)1.00Standards0






*.m File


Corr+Verf effort(Hrs.)0.50Documentation0






Cal Process


Total Effort (Hrs.)1.50Others0













Total0







Checklist No.Description of CheckAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1Section 1: Data Dictionary














Is Filename of Data Dictionary in correct format?Yes













Is the FDD.Version property correctly updated?Yes













Is the Data Dictionary Verification report error free?No
E_OK and E_NOT_OK should be added to the "ignore" list in our tools. These are Autosar-defined names, so they do not and should not match our naming convention.
Since the constants were designed as per code they don’t follow the current naming standards.

New tool shall be created to handle this exception.		Open








Does FDD Long Name, Short Name, and Description match requirements?Yes













Are all runnables defined?NA













Do runnables have the correct time step?Yes













Do server runnables correctly define arguments?Yes













Are all clients defined?NA













Do client definitions match the corresponding server runnable?NA













Does name and metadata of every signal match its corresponding interface signal?Yes













Do output signal ranges match requirements (check DOOR min/max attributes too)?Yes













Are calibration tables named correctly (e.g. AssiX and AssiY)?YesNoTunSelnAuthyVehSpdThd should be TunSelnAuthyVehSpdX
TunSelnAuthyHwTqThd should be TunSelnAuthyHwTqThdY
TunSelnAuthyHwVelThd should be TunSelnAuthyHwVelThdY
Fixed in Data DictionaryClosed








Are all data types represented by released Data_Management classes?Yes













Do all calibrations have correct values for all metadata?Yes













Is NVM defined in the appropriate number of blocks?NA













Are constants defined with proper scope (local vs global)?Yes













Are all dependent constants and calibrations included in one file?NA













Does FDD.DesignASIL match requirements?Yes




























2Section 2: ModelAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








Is filename of model in correct format?Yes













Is Top level of model annotated with Requirements Baseline?Yes













Is the Top level of the model annotated with Tool Dependencies?Yes













Is Top level of model annotated with Change Log or History?Yes













Is the 2nd level of model free from subsystems that are not Function-Call Subsystems?Yes













Is the 2nd level of model free from arithmetic and logic operations?Yes













Are the Runnable trigger signals named as "call_<Runnable>"?Yes













Does 2nd level of model have a properly updated annotation with name, description, and intended baseline number?Yes













Are all data flow layers free of Function-Call Subsystems and Memory Store blocks?Yes













Does the Model have the confidentiality and copyright information inside all its Subsystems?Yes













Are all the Memory Store blocks for PIM and Display Variables located on the 2nd level of model?NA













Is each diagnostic (NTC) capable of being set to "PASS"?NA













Does non-zero intialization of PIM occur in the function's Init runnable?NA













Does design properly include Set Ram Block Status when NVM RAM values change?NA













Does model include appropriate logic for dealing with missing or corrupted NVM data?NA













Does model execute without errors/warnings after loading NxtrMBDConfig configuration set?Yes




























3Section 3: Requirements LinkingAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








Are all requirements links of the format <FDDNumber>_<ObjectID>?Yes













Does requirements HTML report reference only the DOORS module of this component for all links in the design?Yes













Are linked blocks linked to the correct requirements(s)? (watch for problems due to copy/pasted blocks)Yes













Is the list of unlinked blocks acceptable?Yes




























4Section 4: Model AdvisorAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








Was Model Advisor run with the correct configuration settings?Yes













Is the Model Advisor rerport free from "Fails".Yes













Are Model Advisor report "Warnings" acceptable?Yes




























5Section 5: Delivery PackageAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








Does Design folder contain only the model, data dictionary, and (optionally) a simulation setup script?Yes













Does Doc folder contain a zipped HTML webview model?Yes













Was webview model created without requirements highlighted?Yes













Does Reports folder contain only the data dictionary verification report, Model Advisor report, and zipped requirements traceability report?Yes




























4Section 6: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1Close tabs, set each level to proper zoom, have model open at top layer.



Fixed in Model.Closed







4.2TunSelnRtDi.Description is too specific to one architecture. Should be generalized a bit.



Fixed n Data Dictionary.Closed







4.3TunSelnRtDi.EngInit is currently 1. Must be 0.



Fixed n Data Dictionary.Closed







4.4Table datatypes are u16. VehSpd table should be u9p7.



Fixed in Data Dictionary.Closed







4.5Table datatypes are u16. HwTq table should be u4p12.



Fixed in Data Dictionary.Closed







4.6Table datatypes are u16. HwVel table should be u6p10.



Fixed in Data Dictionary.Closed







4.7Model is missing datatype conversion blocks before and after interpolations.



Updated Model.Closed







4.8














4.9














4.10














4.11














4.12














4.13














4.14














4.15














4.16














4.17














4.18














4.19














4.20














4.21














4.22














4.23














4.24














4.25














5Section 7: APPROVALS













RoleFirst ReviewDateAttendanceApproval?










Function Owner*<Owner Name>6/14/2016YesYes










Peer Reviewer*KevinYesNo










Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleSecond Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleThird Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleFourth Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleAdd more if necessaryDateAttendanceApproval?










































P.S.:Yes indicates adherence














No indicates non-adherence, reviewer shall provide suitable comments at the end of this document for each point.














NA indicates not applicable













Sheet 3: Template Change Log

RevChangeAuthor
01.00.05Added lesson learned #3.5MDK
01.00.06Added lesson learned #3.6, 3.7 - Structure and writing of NVM in mfiles and models.MDK
02.00.00Combined ESG and Systems into one, compatible with Data_Management 2.13.0 of CreateDD and VerifyDD.K. Derry
02.01.00Added: Does FDD.DesignASIL match requirements?
Added: Was webview model created without requirements highlighted?
Removed: Redundant row in Data Dictionary section.
Formatting: Column C now consistently center-justified.		K. Derry
02.02.00Added: Are all data types represented by released Data_Management classes?
Removed: Are all runnables defined? Rationale: Automated tools checking.
Removed: Does the Component shortname match data dictionary FDD metadata?
Removed: "Data store name must resolve to Simulink signal object"
Edited: Model Advisor report should now be left unzipped.		K. Derry











































































2 - SF023A_TunSelnAuthy_ModelAdvisor_Report

Model Advisor Report for 'SF023A_TunSelnAuthy'
Model Advisor Report - SF023A_TunSelnAuthy.slx
Simulink version: 8.2Model version: 1.261
System: SF023A_TunSelnAuthyCurrent run: 14-Jun-2016 16:00:39
 Model Advisor configuration: ...NxtrModelAdvisorConfig.mat

Run Summary
PassFailWarningNot RunTotal
   53   0   14   292359


Model Advisor

    By Product

        Simulink

        Simulink Coder

        Embedded Coder

        Simscape

        Simulink Verification and Validation

            Modeling Standards

                DO-178C/DO-331 Checks

                IEC 61508, ISO 26262, and EN 50128 Checks

                MathWorks Automotive Advisory Board Checks

            Requirements Consistency

        Simulink Control Design

    By Task

        Code Generation Efficiency

 Check optimization settings

You should turn on the following optimization(s):

  • Block reduction
  • Remove code from floating-point to integer conversions that wraps out-of-range values
  • Inline invariant signals
  • The Simulation range checking diagnostic is enabled. Because this diagnostic can increase the time it takes to simulate your model, you should consider turning it off, by setting its value to none.
  • Ignore testpoints when generating code
  • Pass reusable subsystem outputs as individual arguments



    •         Frequency Response Estimation

            Managing Data Store Memory Blocks

            Managing Library Links And Variants

            Model Referencing

            Modeling Guidelines for MISRA-C:2004

            Modeling Physical Systems

            Modeling Signals and Parameters using Buses

     Check bus usage

    Mux blocks used to create bus signals
    Identify Mux blocks in the model that are creating bus signals. For guidelines about changes that you might need to make to models, callbacks, scripts, or tests after running the check, see     Compatibility Issues.

    Passed
    The model uses Mux blocks properly. Model is configured to detect future changes that might result in improper Mux block usage.
    _________________________________________________________________________________________

    Bus signal treated as vector
    Identify bus signals in the model that are treated as vectors by the Simulink software.

    Passed
    The model uses bus signals properly. Model is configured to detect future changes that might result in improper bus signal usage.



            Modeling Single-Precision Systems

            Modeling Standards for DO-178C/DO-331

            Modeling Standards for EN 50128

            Modeling Standards for IEC 61508

            Modeling Standards for ISO 26262

     Display model metrics and complexity report

    Display number of elements and name, level, and depth of subsystems for the model or subsystem

    Model metrics information
    Display number of elements for Simulink blocks and Stateflow constructs


    Summary

    Element TypeCount
    Inport21
    Outport16
    SubSystem24


    Simulink

    Block TypeCount
    SubSystem24
    Inport21
    Constant17
    Outport16
    S-Function8
    From7
    Goto5
    ActionPort4
    TriggerPort3
    Math3
    Logic3
    RelationalOperator3
    Abs2
    UnaryMinus2
    If2
    DataTypeConversion2
    Width2
    Merge2
    Step1
    Sum1
    EnablePort1
    ∧ Less

    Model complexity information
    Display name, level, and depth of subsystems


    Maximum Subsystem Depth: 5

    Subsystem Depth

    Subsystem NameLevelDepth
    CopyRight211
    TunSelnAuthy14
    TunSelnAuthy/CopyRight221
    TunSelnAuthy/RtCalChgReq23
    TunSelnAuthy/RtCalChgReq/CopyRight231
    TunSelnAuthy/RtCalChgReq/FixdToFloat_f32_u131
    TunSelnAuthy/RtCalChgReq/FixdToFloat_f32_u1631
    TunSelnAuthy/RtCalChgReq/FloatToFixd_u16_f3231
    TunSelnAuthy/RtCalChgReq/LnrIntrpn_u16_u16VariXu16VariY31
    TunSelnAuthy/RtCalChgReq/LnrIntrpn_u16_u16VariXu16VariY131
    TunSelnAuthy/RtCalChgReq/RtnNotOK32
    TunSelnAuthy/RtCalChgReq/RtnNotOK/CopyRight241
    TunSelnAuthy/RtCalChgReq/RtnOK32
    TunSelnAuthy/RtCalChgReq/RtnOK/CopyRight241
    TunSelnAuthy/TunSelnAuthyInit122
    TunSelnAuthy/TunSelnAuthyInit1/CopyRight231
    TunSelnAuthy/XcpCalChgReq23
    TunSelnAuthy/XcpCalChgReq/CopyRight231
    TunSelnAuthy/XcpCalChgReq/RtnNotOK32
    TunSelnAuthy/XcpCalChgReq/RtnNotOK/CopyRight241
    TunSelnAuthy/XcpCalChgReq/RtnOK32
    TunSelnAuthy/XcpCalChgReq/RtnOK/CopyRight241
    call_TunSelnAuthyInit112
    call_TunSelnAuthyInit1/CopyRight221
    ∧ Less


     Check for model objects that do not link to requirements

    Check Simulink blocks and Stateflow objects that do not link to a requirements document

    Warning
    The following blocks do not link to a requirement document:

    ∧ Less
    Recommended Action
    For each object in the list, in the Model Editor, right-click the block, select Requirements, and specify a requirement.



            Modeling Standards for MAAB

                Naming Conventions

     Check file names

    Identify file names with incorrect characters or formatting.

    See Also

    Warning
    The following files have incorrect file names:

    File NameIncorrect Character or Format
    SF023A Tuning Select Authority.rtfFile name contains incorrect characters. Correct characters are a-z, A-Z, 0-9, and underscore (_).


    Recommended Action
    Rename the above files to remove incorrect characters and formatting.

     Check character usage in block names

    Identify block names that use characters that are not correct in C code.

    See Also

    Warning
    The following block names use characters that are not correct for C code:

    Error typeBlock
    Name contains incorrect characters...../Function-Call Generator


    Recommended Action
    Rename the block using correct characters.



                Model Architecture

     Check for mixing basic blocks and subsystems

    Identify levels in the model that include basic blocks and subsystems. Each level of a model must be designed with blocks of the same level (for example, only subsystems or only basic blocks).

    See Also

    Warning
    The following level(s) in the model include basic blocks and subsystems:

    SystemBlock path
    SF023A_TunSelnAuthySF023A_TunSelnAuthy/CopyRight2
    SF023A_TunSelnAuthySF023A_TunSelnAuthy/Step
    SF023A_TunSelnAuthy/TunSelnAuthy..../TunSelnAuthy/CopyRight2
    ..../TunSelnAuthy/RtCalChgReq..../TunSelnAuthy/RtCalChgReq/Abs
    ..../TunSelnAuthy/RtCalChgReq..../TunSelnAuthy/RtCalChgReq/Abs1
    ..../TunSelnAuthy/RtCalChgReq..../TunSelnAuthy/RtCalChgReq/Constant2
    ..../TunSelnAuthy/RtCalChgReq..../TunSelnAuthy/RtCalChgReq/CopyRight2
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/FixdToFloat_f32_u1
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/FixdToFloat_f32_u16
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/FloatToFixd_u16_f32
    ..../TunSelnAuthy/RtCalChgReq..../LnrIntrpn_u16_u16VariXu16VariY
    ..../TunSelnAuthy/RtCalChgReq..../LnrIntrpn_u16_u16VariXu16VariY1
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/Logical Operator
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/Logical Operator1
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/Logical Operator2
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/Relational Operator
    ..../TunSelnAuthy/RtCalChgReq..../RtCalChgReq/Relational Operator1
    ..../TunSelnAuthy/XcpCalChgReq..../TunSelnAuthy/XcpCalChgReq/Add
    ..../TunSelnAuthy/XcpCalChgReq..../TunSelnAuthy/XcpCalChgReq/Constant4
    ..../TunSelnAuthy/XcpCalChgReq..../TunSelnAuthy/XcpCalChgReq/CopyRight2
    ..../TunSelnAuthy/XcpCalChgReq..../XcpCalChgReq/Relational Operator1
    ..../TunSelnAuthy/XcpCalChgReq..../TunSelnAuthy/XcpCalChgReq/VehSpdThd
    ∧ Less


    Recommended Action
    If possible, replace blocks at the identified level of the model hierarchy with basic blocks. Move nonvirtual blocks into the identified subsystem.



                Model Configuration Options

                Simulink

     Check for Simulink diagrams using nonstandard display attributes

    Identify nonstandard display attributes in Simulink diagrams.

    See Also

    _________________________________________________________________________________________

    Check format settings
    Identify incorrect model-level format options.

    Warning
    The following format display options are incorrect.

    Display AttributeRecommended ValueActual Value
    Display > Signals & Ports > Wide Nonscalar Linesonoff
    Display > Signals & Ports > Signal Dimensionsoffon
    View > Model Browser Options > Model Browseroffon
    Display > Library Links > Allnonedisabled


    Recommended Action
    Set the format options to the recommended value.
    _________________________________________________________________________________________

    Check block colors
    Identify blocks using nonstandard colors.

    Warning
    The following blocks use nonstandard colors:

    ∧ Less
    Recommended Action
    Set the block foreground color to black and the background color to white.
    _________________________________________________________________________________________

    Check canvas colors
    Identify canvases that are not white.

    Passed
    All diagrams use a white canvas.
    _________________________________________________________________________________________

    Check diagram zoom
    Identify diagrams that do not have zoom factor set to 100 %.

    Warning
    The following diagrams do not have zoom factor set to 100 percent:

    Recommended Action
    For each listed diagram, select View > Zoom > Normal View (100%).

     Check font formatting

    Identify inconsistent formatting of text.

    See Also

    Warning
    Font formatting is not consistent.

    The following font characteristics are used in the model/subsystem. Font characteristics are sorted by number of occurrences. The most common characteristics are bold.
    Font NameFont SizeFont Style

    Helvetica
    Arial

    10
    14
    9

    normal



    Recommended Action
    To have consistent font formatting, click Modify All Fonts to apply the font formatting selected in the input parameters above to all objects.

    Input Parameters Selection
    NameValue
    Font NameCommon
    Font SizeCommon
    Font StyleCommon

     Check positioning and configuration of ports

    Identify input and output ports with incorrect positioning and configurations.

    See Also

    _________________________________________________________________________________________

    Check Inport blocks position
    Identify Inport blocks that result in left-flowing signals.

    Passed
    There are no Inport blocks in the model that result in left-flowing signals.
    _________________________________________________________________________________________

    Check Outport block position
    Identify Outport blocks that result in left-flowing signals.

    Passed
    There are no Outport blocks in the model that result in left-flowing signals.
    _________________________________________________________________________________________

    Check port orientation
    Identify port blocks with nondefault orientation.

    Passed
    All ports use the default orientation.
    _________________________________________________________________________________________

    Check for duplicate Inports blocks
    Identify duplicate Inport blocks.

    Passed
    All Inport blocks in the model are used once.

     Check visibility of block port names

    Identify port block names that are not uniformly displayed. The block names must all be displayed or none displayed. Library blocks are an exception to this rule. This check ignores masked and subsystem blocks.

    See Also

    _________________________________________________________________________________________

    Check for incorrect port name display
    Identify ports that are incorrectly displaying names.

    Passed
    Subsystem blocks are correctly displayed.
    _________________________________________________________________________________________

    Check for incorrect subsystem port name display
    Identify subsystems that are incorrectly displaying names.

    Passed
    Subsystem blocks are correctly displayed.

    Input Parameters Selection
    NameValue
    Display all port names (Diagram > Format > Show Block Name).true

     Check the display attributes of block names

    Identify whether to display block names.

    See Also

    _________________________________________________________________________________________

    Check for blocks with hidden names and obvious function
    Identify block names that are displayed but can be hidden due to obvious behavior.

    Passed
    All blocks with obvious behavior have hidden names.
    _________________________________________________________________________________________

    Check for non-descriptive displayed block names
    Identify block names that are displayed but should be hidden due to a lack of a descriptive name.

    Passed
    All displayed names provide descriptive information.
    _________________________________________________________________________________________

    Check for missing block names
    Identify block names that are hidden but should be displayed to show a descriptive name.

    Warning
    The following blocks have descriptive names, however, the names are hidden:

    Recommended Action
    Modify the blocks to show the block name (Diagram > Format > Show Block Name).

     Check position of Trigger and Enable blocks

    Identify Trigger and Enable blocks that are not centered in the upper third of the model diagram.

    See Also

    Warning
    The following Trigger and Enable blocks are not centered in the upper third of the model diagram:Recommended Action
    Move the above Trigger or Enable blocks such that it is centered in the upper third of the model diagram.

     Check signal line labels

    Identify blocks that require labeled signals. A subset of source and destination blocks require labeled signals.

    See Also

    _________________________________________________________________________________________

    Check source block labels
    The following source blocks require labeled signals; Inport, From, Data Store Read, Constant, Bus Selector, Demux, Selector. If the signal name is visible on the block, this rule is considered met.

    Warning
    The following signals have no label:

    ∧ Less
    Recommended Action
    Add a new or propagated label to the signal line.
    _________________________________________________________________________________________

    Check destination block labels
    The following destination blocks require labeled signals; Outport, Goto, Data Store Write, Bus Creator, Mux, Subsystem, Chart. If the signal name is visible on the source block, this rule is considered met.

    Warning
    The following signals have no label:

    ∧ Less
    Recommended Action
    Add a new or propagated label to the signal line.

     Check for propagated signal labels

    Identify propagated labels on signal lines.

    See Also

    _________________________________________________________________________________________

    Check subsystem input labels
    Identify subsystem inputs that are labeled and display propagated signals.

    Passed
    All inputs to the subsystem have labels and display propagated signals.
    _________________________________________________________________________________________

    Check subsystem output labels
    Identify outputs from subsystems that are labeled and display signal propagation.

    Passed
    All outputs from the subsystem have labels and display propagated signals.
    _________________________________________________________________________________________

    Signal propagation for nonsubsystem blocks
    Identify the signal propagation status for both transformative and nontransformative blocks.

    Passed
    All outputs from non subsystem blocks correctly use labels and display propagated signals.



                Stateflow

     Check usage of exclusive and default states in state machines

    Identify Stateflow charts and substates that incorrectly use or define exclusive and default states.
    Note: This check does not support charts that use MATLAB as the action language.

    See Also

    _________________________________________________________________________________________

    Check Stateflow charts for exclusive states
    Identify Stateflow charts that have singular exclusive (OR) states.

    Passed
    The Stateflow charts do not have singular exclusive (OR) states.
    _________________________________________________________________________________________

    Check Stateflow charts for undefined default states
    Identify Stateflow charts that do not define default states.

    Passed
    Each Stateflow chart defines a default state.
    _________________________________________________________________________________________

    Check for multiple states assigned as the default state
    At the root level in the Stateflow hierarchy only one state should be assigned as the default.

    Passed
    The root level of the chart has only one default state assigned.
    _________________________________________________________________________________________

    Check for substates with singular OR states
    States configured as OR should always be part of a group of states.

    Passed
    No singular OR states were detected.
    _________________________________________________________________________________________

    Check for substates without default states defined
    At every level in the Stateflow hierarchy a default state should be assigned.

    Passed
    All substates have default states assigned.
    _________________________________________________________________________________________

    Check for substates with multiple default states defined
    At every level in the Stateflow hierarchy only one state should be assigned as the default.

    Passed
    All levels of the chart have only one default state assigned.

     Check transition orientations in flowcharts

    Identify transitions in Stateflow flowcharts that are drawn incorrectly.

    See Also

    _________________________________________________________________________________________

    Check for conditions drawn vertically
    Condition expressions should be drawn on the horizontal segments of flowcharts.

    Passed
    All conditions expressions were drawn horizontally.
    _________________________________________________________________________________________

    Check for action transitions drawn vertically
    Transition actions should be drawn on the vertical segments of flowcharts.

    Passed
    All transitions actions where drawn vertically.
    _________________________________________________________________________________________

    Check for junctions for default transitions
    All Junctions in a flow chart should have a default exit transition.

    Passed
    All Junctions have a default exit transition.
    _________________________________________________________________________________________

    Check for transitions that combine condition and action
    Flowcharts should not combine condition evaluations and action expressions in a single transition.

    Passed
    No combined expressions where found in the chart.



                MATLAB Functions

            Requirements Consistency Checking

            Simulation Accuracy

            Simulation Runtime Accuracy Diagnostics

            Simulink Model File Integrity

            Upgrading to the Current Simulink Version