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 - SF042A_HwAgSnsrls_Design_PeerReviewChkList

Nexteer_Template_V1.0

Overview

Project Info
Process
Safety
Software
Apps
SME
Master
Template Change Log

Sheet 1: Project Info

Peer Review Checklist - Component DesignTemplate Version: 3.0.0
Product NameElectric Power SteeringReview Scope
Component IDSF042A_HwAgSnsrlsAdded a new method Corrected Pinion Angle of the Handwheel AngleOffset with Pinion angle and Pinion Angle Confidence and update the logic in the Arbitrator subsystem.
Component Long NameHandwheel Angle Sensorless
Component OwnerFei Yuan
Version that you started from. NOT the version you hope to release. If this will be v1.0.0, enter NA. Starting Baseline1.5.0
The number that will be used when package is baselined in Synergy. For example, the first one will be 1.0.0. Intended Baseline1.6.0
Electrical ArchitectureEA4
CR Number8284
Author: The person who edited the design. Usually the Resolver of a CR. AuthorFei Yuan
Review TypeMinimal



Author's Quality Statement:Author must provide an explanation of any deviation from an ideal Instpection process. This field may be used for analysis of anomalies. Corrected Pinion Angle method is added for Handwheel Angle Offset.




Meeting DateAttendeesExamples: Initial Mtg, Follow-up. Reason for Meeting
11/7/2016Carl Tarum, Hari Mattupalli, Matthew TompkinsRequirements, Design, MIL Review









Sheet 2: Process

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Process Reviewer:Fei Yuan






NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for Runnables: .ContextYes













Are the following values correct for Runnables: .TimeStepYes













Are the following values correct for SrvRunnables: .ReturnYes













Are the following values correct for SrvRunnables: .ArgumentsYes













Are the following values correct for all Ip/Op/IrvSignals: .EngDTYes













Are the following values correct for all Ip/Op/IrvSignals: .DocUnitYes













Are the following values correct for all Ip/Op/IrvSignals: .EngInitYes













Are the following values correct for all Ip/Op/IrvSignals: .EngMinYes













Are the following values correct for all Ip/Op/IrvSignals: .EngMaxYes













Are the following values correct for all Ip/Op/IrvSignals: .ReadIn/WrittenInYes













Are the following values correct for all Ip/Op/IrvSignals: .ReadType/WriteTypeYes













Are the following values correct for all Calibrations: .DocUnitYes













Are the following values correct for all Calibrations: .PortNameYes













Are the following values correct for all NVM: .DocUnitYes













Are the following values correct for all PIM: .DocUnitYes













Are the following values correct for all Constants: .DocUnitYes













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













Do output signal ranges match requirements?Yes













Are all clients from model defined in dictionary?Yes













Do client definitions match their corresponding server runnable?Yes













Is NVM defined in the appropriate number of blocks (separate for EOL vs saved at power-off)?Yes













Is NVM with multiple values defined as a structure?Yes













Are NVM structure members arranged largest-to-smallest datatype?Yes













Are local Constants unique from global constants available in xx999A dictionaries?Yes













Are calibration tables named correctly (e.g. AssiX and AssiY)?Yes













Are Constant names abbreviated properly (ALLCAPS are not checkable by tools)?Yes













Is the Data Dictionary Verification report error free?No
Output singal name and NTC number, which are acceptable at this time.











Are all data types represented by released Data_Management classes?Yes



























































































































































































2
Section 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









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













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













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













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













Are NTCs set only outside an IRQ (not related to the typical periodic OS)?NA













Are NTCs set and read only at periodic steps no less than 2 ms?NA













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













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 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













Was Model Advisor run with the correct configuration settings?Yes













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













Does the model execute?Yes













If model has ADC input, is failure boolean input and appropriate fault response been included?NA













Do cal ranges & logic ensure no incompatible values for their datatype?Yes













Are "magic numbers" acceptable?Yes













Do IF..ELSEIF blocks also contain an ELSE condition?Yes













Do SWITCH CASE blocks also contain a DEFAULT condtion?Yes











3
Are ELSE and DEFAULT branching conditions reachable when dependent on internal variables?Author: 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does review meet 'inspection' criteria?Yes













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 Doc folder contain appropriate number of NTC Summary sheets?Yes













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



























































4
Section 4: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1
The initial value of the calibration HwAgSnsrlsCorrdPinionAgHwConf is wrong.*.m File
Change the value to 1.Change the value to 1.Closed







4.2
The logic for CorrdPinionAgHwOffs is wrong.Model
The handwheel angle offset is equal to Relative Handwheel Angle minus Pnion Angle.Use Relative Handwheel Angle minus Pinion Angle to get the handwheel angle offset.Closed







4.3














4.4














4.5














4.6














4.7














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






























Sheet 3: Safety

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Safety Reviewer:Carl Tarum






NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for all Calibrations: .ImpactYes













Are the following values correct for all Calibrations: .TuningOwnerYes













Are the following values correct for all Calibrations: .OnlineYes













Does the FDD .DesignASIL property match requirements?Yes













Are lookup tables using compatible table dimensions?Yes











































































































































































































































































































































































































































































































































































2
Section 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Are Model Advisor report ISO26262 warnings acceptable?Yes













Is model free from dynamic array size allocation?Yes













Is model free from data type conversion blocks that do not explicitly state desired data type?Yes













Does model refrain from using Display Variable values in downstream operations?Yes













Are all GOTO/FROM blocks restricted in scope to their own subystem level?Yes













If model has ADC input, is failure boolean input and appropriate fault response been included?Yes













Does design include output limiting blocks?Yes













Do cal ranges & logic ensure freedom from divide-by-zero?Yes













Are the following values correct for all NTC: .NtcTypYes













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



























































































































































































































































































3
Section 3: 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does review meet 'inspection' criteria?Yes











































































































































4
Section 4: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














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






























Sheet 4: Software

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Software Reviewer:Hari Mattupalli






NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for Runnables: .ContextYesYesNo changes in Runnables: .Context











Are the following values correct for SrvRunnables: .ReturnYesYesNo changes in SrvRunnables: .Return











Are the following values correct for SrvRunnables: .ArgumentsYesYesNo changes in SrvRunnables: .Arguments











Are the following values correct for all Calibrations: .PortNameYesYesNo changes in Calibrations: .PortName











Are the following values correct for all NVM: .EngInitYesYesNo changes in NVM: .EngInit











Are the following values correct for all NVM: .AliasNANA












Are the following values correct for all NVM: .InitRowColYesYesNo changes in NVM: .InitRowCol











Are the following values correct for all Display Variables: .EngMinYesYesNo changes in Display Variables: .EngMin











Are the following values correct for all Display Variables: .EngMaxYesYesNo changes in Display Variables: .EngMax











Are the following values correct for all Display Variables: .InitRowColYesYesNo changes in Display Variables: .InitRowCol











Are the following values correct for all PIM: .EngMinYesYes












Are the following values correct for all PIM: .EngMaxYesYes












Are the following values correct for all PIM: .InitRowColYesYes












Are lookup tables using compatible table dimensions?YesYesNo changes in look up table dimensions











Are all clients from model defined in dictionary?YesYes












Do client definitions match their corresponding server runnable?YesYes












Is NVM defined in the appropriate number of blocks (separate for EOL vs saved at power-off)?YesYesNo changes in NVM











Is NVM with multiple values defined as a structure?YesYesNo changes in NVM











Are NVM structure members arranged largest-to-smallest datatype?YesYesNo changes in NVM











Are local Constants unique from global constants available in xx999A dictionaries?YesYesNo changes in local and global constants



























































































































































































































































































































Section 2: ModelAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist.
Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist.
Author: Detailed Description of the finding shall be provided by the reviewer.
Corrective Action: What action is taken to fix the issue?
Author: Data in this column shall be filled by reviewer after checking whether the rework is completed.










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












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












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












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












Are NTCs set only outside an IRQ (not related to the typical periodic OS)?NANA












Are NTCs set and read only at periodic steps no less than 2 ms?NANA












Is model free from dynamic array size allocation?YesYes












Is model free from data type conversion blocks that do not explicitly state desired data type?YesYes












Does model refrain from using Display Variable values in downstream operations?YesYes












Are all GOTO/FROM blocks restricted in scope to their own subystem level?YesYes












Does design calculate PIM values only within their defined range?YesYes












Does design include output limiting blocks?YesYes












Do cal ranges & logic ensure freedom from divide-by-zero?YesYes












Do cal ranges & logic ensure no incompatible values for their datatype?YesYes












Are Model Advisor report MISRA warnings acceptable?YesYes












Is design free of unreachable logic?YesYes












Do state machines provide exits of all non-latch states?NANA












Is design free from recursive logic that could cause indefinate waits?YesYes












Does design maintain data size consistency?YesYes












Are "magic numbers" acceptable?YesYes












Is design of a managable size and easy to understand?YesYes












Is Stateflow used only for state machines not easily represented in Simulink?YesYes












Is model free from over-nested IF logic or redundant IF..ELSEIF..ELSEIF.. Conditions?YesYes












Is model free from arithmetic operations on Boolean values?YesYes


























































3
Section 3: 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status























































































































































4

DocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














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






























Sheet 5: Apps

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Applications Reviewer:







NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for Runnables: .TimeStep














Are the following values correct for all Calibrations: .DocUnit














Are the following values correct for all Calibrations: .EngMax














Are the following values correct for all Calibrations: .Cardinality














Are the following values correct for all Calibrations: .CustomerVisible














Are the following values correct for all Calibrations: .Impact














Are the following values correct for all Calibrations: .GraphLink














Are the following values correct for all Calibrations: .Monotony














Are the following values correct for all NVM: .DocUnit














Are the following values correct for all Display Variables: .DocUnit














Are the following values correct for all Calibrations: .EngVal














Are the following values correct for all Calibrations: .EngMin














Are the following values correct for all Calibrations: .TuningOwner














Are the following values correct for all Calibrations: .Online














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














Do output signal ranges match requirements?














Do signal and parameter names accurately describe their purpose?














Do all .Description properties provide useful information?














Are calibration tables named correctly (e.g. AssiX and AssiY)?












































































































































































































































































































































2
Section 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









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














Does model include adequate annotation throughout?














Are the following values correct for all NTC: .NtcTyp














Are display variables appropriately placed?














Does design provide appropriate tuning flexibility?














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














Is the list of unlinked blocks acceptable?














Does design account for all requirements?














Is design of a managable size and easy to understand?














Is design easily disabled via calibration?














Does design either work with global signal units or contain necessary unit-conversion logic?












































































































































































































































































3
Section 3: 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does NTC Summary sheet adequately describe NTC usage?












































































































































4
Section 4: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














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






























Sheet 6: SME

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

SME Reviewer:







NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for all Calibrations: .EngDT














Are the following values correct for all NVM: .EngDT














Are the following values correct for all Display Variables: .EngDT














Are the following values correct for all PIM: .EngDT














Are the following values correct for all Constants: .EngDT














Has Static Register evaluation has been completed and updated for any register data that is written to?




























































































































































































































































































































































































































































































































































2
Section 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









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














Does design either work with global signal units or contain necessary unit-conversion logic?














Does the design prevent Integrator drifting?














Does design make proper use of limiters to prevent integrator windup and runaway values?














Are all IIR filters free of potential instability over their defined calibration ranges?












































































































































































































































































































































































3

Author: 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 reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Has author performed basic simulations to screen for problems?












































































































































4

DocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














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






























Sheet 7: Master

This is the master list of questions.


ADVANCED FILTER CRITERIA

A macro is used to filter and populate separate spreadsheets for each engineering discipline.

ArtifactDomain1Domain2















NumberArtifactChecklist ItemDomain1Domain2



1dictIs Filename of Data Dictionary in correct format?Processnone



2dictIs the FDD.Version property correctly updated?Processnone



3dictAre the following values correct for Runnables: .ContextProcessSoftwareShould be Architect


4dictAre the following values correct for Runnables: .TimeStepProcessAppsShould be Architect


5dictAre the following values correct for SrvRunnables: .ReturnProcessSoftwareShould be Architect


6dictAre the following values correct for SrvRunnables: .ArgumentsProcessSoftwareShould be Architect


7dictAre the following values correct for all Ip/Op/IrvSignals: .EngDTProcessnoneShould be Architect


8dictAre the following values correct for all Ip/Op/IrvSignals: .DocUnitProcessnoneShould be Architect


9dictAre the following values correct for all Ip/Op/IrvSignals: .EngInitProcessnoneShould be Architect


10dictAre the following values correct for all Ip/Op/IrvSignals: .EngMinProcessnoneShould be Architect


11dictAre the following values correct for all Ip/Op/IrvSignals: .EngMaxProcessnoneShould be Architect


12dictAre the following values correct for all Ip/Op/IrvSignals: .ReadIn/WrittenInProcessnone



13dictAre the following values correct for all Ip/Op/IrvSignals: .ReadType/WriteTypeProcessnone



14dictAre the following values correct for all Calibrations: .EngDTSMEnone



15dictAre the following values correct for all Calibrations: .DocUnitAppsProcess



16dictAre the following values correct for all Calibrations: .EngMaxAppsnone



17dictAre the following values correct for all Calibrations: .CardinalityAppsnone



18dictAre the following values correct for all Calibrations: .CustomerVisibleAppsnone



19dictAre the following values correct for all Calibrations: .ImpactAppsSafety



20dictAre the following values correct for all Calibrations: .GraphLinkAppsnone



21dictAre the following values correct for all Calibrations: .MonotonyAppsnone



22dictAre the following values correct for all Calibrations: .PortNameSoftwareProcess



23dictAre the following values correct for all NVM: .EngDTSMEnone



24dictAre the following values correct for all NVM: .DocUnitProcessApps



25dictAre the following values correct for all NVM: .EngInitSoftwarenone



26dictAre the following values correct for all NVM: .AliasSoftwarenone



27dictAre the following values correct for all NVM: .InitRowColSoftwarenone



28dictAre the following values correct for all Display Variables: .EngDTSMEnone



29dictAre the following values correct for all Display Variables: .DocUnitAppsnone



30dictAre the following values correct for all Display Variables: .EngMinSoftwarenone



31dictAre the following values correct for all Display Variables: .EngMaxSoftwarenone



32dictAre the following values correct for all Display Variables: .InitRowColSoftwarenone



33dictAre the following values correct for all PIM: .EngDTSMEnone



34dictAre the following values correct for all PIM: .DocUnitProcessnone



35dictAre the following values correct for all PIM: .EngMinSoftwarenone



36dictAre the following values correct for all PIM: .EngMaxSoftwarenone



37dictAre the following values correct for all PIM: .InitRowColSoftwarenone



38dictAre the following values correct for all Constants: .EngDTSMEnone



39dictAre the following values correct for all Constants: .DocUnitProcessnone



40dictAre the following values correct for all Calibrations: .EngValAppsnone



41dictAre the following values correct for all Calibrations: .EngMinAppsnone



43dictAre the following values correct for all Calibrations: .TuningOwnerSafetyApps



47dictAre the following values correct for all Calibrations: .OnlineSafetyApps



44dictDoes the FDD .DesignASIL property match requirements?Safetynone



45dictDoes FDD Long Name, Short Name, and Description match requirements?AppsProcess



46dictDo output signal ranges match requirements?AppsProcess



42dictAre lookup tables using compatible table dimensions?SafetySoftware



48dictDo signal and parameter names accurately describe their purpose?Appsnone



49dictDo all .Description properties provide useful information?Appsnone



50dictHas Static Register evaluation has been completed and updated for any register data that is written to?SMEnone



51dictAre all clients from model defined in dictionary?ProcessSoftware



52dictDo client definitions match their corresponding server runnable?ProcessSoftware



53dictIs NVM defined in the appropriate number of blocks (separate for EOL vs saved at power-off)?ProcessSoftware



54dictIs NVM with multiple values defined as a structure?ProcessSoftware



55dictAre NVM structure members arranged largest-to-smallest datatype?ProcessSoftware



56dictAre local Constants unique from global constants available in xx999A dictionaries?ProcessSoftware



57dictAre calibration tables named correctly (e.g. AssiX and AssiY)?ProcessApps



58dictAre Constant names abbreviated properly (ALLCAPS are not checkable by tools)?Processnone



59dictIs the Data Dictionary Verification report error free?Processnone



60dictAre all data types represented by released Data_Management classes?Processnone



61modelAre all the Memory Store blocks for PIM and Display Variables located on the 2nd level of model?ProcessSoftware



62modelIs each diagnostic (NTC) capable of being set to "PASS"?ProcessSoftware



63modelDoes non-zero intialization of PIM occur in the function's Init runnable?ProcessSoftware



64modelDoes design properly include Set Ram Block Status when NVM RAM values change?ProcessSoftware



65modelAre NTCs set only outside an IRQ (not related to the typical periodic OS)?ProcessSoftware



66modelAre NTCs set and read only at periodic steps no less than 2 ms?ProcessSoftware



67modelDoes model execute without errors/warnings after loading NxtrMBDConfig configuration set?ProcessApps



68modelIs filename of model in correct format?Processnone



69modelIs Top level of model annotated with Requirements Baseline?Processnone



70modelIs the Top level of the model annotated with Tool Dependencies?Processnone



71modelIs Top level of model annotated with Change Log or History?Processnone



72modelIs the 2nd level of model free from subsystems that are not Function-Call Subsystems?Processnone



73modelIs the 2nd level of model free from arithmetic and logic operations?Processnone



74modelAre the Runnable trigger signals named as "call_<Runnable>"?Processnone



75modelDoes 2nd level of model have a properly updated annotation with name, description, and intended baseline number?Processnone



76modelAre all data flow layers free of Function-Call Subsystems and Memory Store blocks?Processnone



77modelDoes the Model have the confidentiality and copyright information inside all its Subsystems?Processnone



78modelAre all requirements links of the format <FDDNumber>_<ObjectID>?Processnone



79modelDoes requirements HTML report reference only the DOORS module of this component for all links in the design?Processnone



80modelWas Model Advisor run with the correct configuration settings?Processnone



81modelIs the Model Advisor rerport free from "Fails".Processnone



82modelDoes the model execute?Processnone



83modelAre Model Advisor report ISO26262 warnings acceptable?Safetynone



84modelIs model free from dynamic array size allocation?SafetySoftware



85modelDoes model include adequate annotation throughout?Appsnone



86modelIs model free from data type conversion blocks that do not explicitly state desired data type?SafetySoftware



87modelDoes model refrain from using Display Variable values in downstream operations?SafetySoftware



88modelAre all GOTO/FROM blocks restricted in scope to their own subystem level?SafetySoftware



89modelIf model has ADC input, is failure boolean input and appropriate fault response been included?SafetyProcess



90modelDoes design calculate PIM values only within their defined range?Softwarenone



91modelDoes design include output limiting blocks?SoftwareSafety



92modelDo cal ranges & logic ensure freedom from divide-by-zero?SoftwareSafety



93modelDo cal ranges & logic ensure no incompatible values for their datatype?SoftwareProcess



94modelAre Model Advisor report MISRA warnings acceptable?Softwarenone



95modelIs design free of unreachable logic?Softwarenone



96modelDo state machines provide exits of all non-latch states?Softwarenone



97modelIs design free from recursive logic that could cause indefinate waits?Softwarenone



98modelDoes design maintain data size consistency?Softwarenone



99modelAre "magic numbers" acceptable?ProcessSoftware



100modelAre the following values correct for all NTC: .NtcTypAppsSafety



101modelAre display variables appropriately placed?Appsnone



102modelDoes design provide appropriate tuning flexibility?Appsnone



103modelAre blocks linked to the correct requirements? (watch for problems due to copy/pasted blocks)Appsnone



104modelIs the list of unlinked blocks acceptable?Appsnone



105modelDoes design account for all requirements?Appsnone



106modelIs design of a managable size and easy to understand?AppsSoftware



107modelIs design easily disabled via calibration?Appsnone



108modelDoes model include appropriate logic for dealing with missing or corrupted NVM data?SMESafety



109modelDoes design either work with global signal units or contain necessary unit-conversion logic?SMEApps



110modelDoes the design prevent Integrator drifting?SMEnone



111modelDoes design make proper use of limiters to prevent integrator windup and runaway values?SMEnone



112modelAre all IIR filters free of potential instability over their defined calibration ranges?SMEnone



113modelIs Stateflow used only for state machines not easily represented in Simulink?Softwarenone



114modelDo IF..ELSEIF blocks also contain an ELSE condition?Processnone



115modelDo SWITCH CASE blocks also contain a DEFAULT condtion?Processnone



116modelAre ELSE and DEFAULT branching conditions reachable when dependent on internal variables?Processnone



117modelIs model free from over-nested IF logic or redundant IF..ELSEIF..ELSEIF.. Conditions?Softwarenone



118modelIs model free from arithmetic operations on Boolean values?Softwarenone



119modelIs model optimized to minimize redundant calculations?Processnone



120packageDoes NTC Summary sheet adequately describe NTC usage?Appsnone



121packageDoes review meet 'inspection' criteria?SafetyProcess



122packageDoes Design folder contain only the model, data dictionary, and (optionally) a simulation setup script?Processnone



123packageDoes Doc folder contain a zipped HTML webview model?Processnone



124packageWas webview model created without requirements highlighted?Processnone



125packageDoes Doc folder contain appropriate number of NTC Summary sheets?Processnone



126packageDoes Reports folder contain only the data dictionary verification report, Model Advisor report, and zipped requirements traceability report?Processnone



127packageHas author performed basic simulations to screen for problems?SMEnone



Sheet 8: 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
3.0.0New concept of discipline-specific checklists.
New sheets for Project Info, Safety, Software, Apps, SME, and Master.
New VBA code to distribute master list onto appropriate discipline sheets.
Major reformatting, many line item checks added/deleted/modified.		K. Derry








































































2 - SF042A_HwAgSnsrls_ModelAdvisor_Report

Model Advisor Report for 'SF042A_HwAgSnsrls'
Model Advisor Report - SF042A_HwAgSnsrls.slx
Simulink version: 8.2Model version: 1.633
System: SF042A_HwAgSnsrlsCurrent run: 09-Nov-2016 08:16:06
 Model Advisor configuration: ...NxtrModelAdvisorConfig.mat

Run Summary
PassFailWarningNot RunTotal
   49   0   18   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

            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
    Inport164
    Outport106
    SubSystem183


    Simulink

    Block TypeCount
    SubSystem183
    Inport164
    Constant117
    Outport106
    DataStoreWrite55
    ActionPort50
    Product48
    DataStoreRead42
    Sum38
    From36
    DataStoreMemory35
    Merge28
    If26
    RelationalOperator23
    Goto23
    S-Function17
    DataTypeConversion8
    Rounding8
    Math5
    TriggerPort4
    Logic4
    Terminator2
    UnaryMinus2
    Clock1
    Demux1
    SwitchCase1
    ∧ Less

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


    Maximum Subsystem Depth: 10

    Subsystem Depth

    Subsystem NameLevelDepth
    CopyRight211
    HwAgSnsrls19
    HwAgSnsrls/CopyRight221
    HwAgSnsrls/FSnsrlsHwCentr22
    HwAgSnsrls/FSnsrlsHwCentr/CopyRight231
    HwAgSnsrls/HwAgSnsrlsInit123
    HwAgSnsrls/HwAgSnsrlsInit1/CaseNotValid32
    HwAgSnsrls/HwAgSnsrlsInit1/CaseNotValid/CopyRight241
    HwAgSnsrls/HwAgSnsrlsInit1/CaseValid32
    HwAgSnsrls/HwAgSnsrlsInit1/CaseValid/CopyRight241
    HwAgSnsrls/HwAgSnsrlsInit1/CopyRight231
    HwAgSnsrls/HwAgSnsrlsInit1/Enumerated Constant231
    HwAgSnsrls/HwAgSnsrlsInit1/Enumerated Constant431
    HwAgSnsrls/HwAgSnsrlsInit1/FiltersInit32
    HwAgSnsrls/HwAgSnsrlsInit1/FiltersInit/CopyRight241
    HwAgSnsrls/HwAgSnsrlsInit1/FiltersInit/PinionTqFilInit41
    HwAgSnsrls/HwAgSnsrlsInit1/FiltersInit/RelHwAgFil1Init41
    HwAgSnsrls/HwAgSnsrlsInit1/FiltersInit/RelHwAgFil2Init41
    HwAgSnsrls/HwAgSnsrlsInit1/FiltersInit/YawRateFilInit41
    HwAgSnsrls/HwAgSnsrlsInit1/GetNtcQlfrSts32
    HwAgSnsrls/HwAgSnsrlsInit1/GetNtcQlfrSts/CopyRight241
    HwAgSnsrls/HwAgSnsrlsInit1/GetRefTmr100MicroSec32bit32
    HwAgSnsrls/HwAgSnsrlsInit1/GetRefTmr100MicroSec32bit/CopyRight241
    HwAgSnsrls/HwAgSnsrlsInit1/Set Ram Block Status31
    HwAgSnsrls/HwAgSnsrlsPer128
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator35
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf43
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem52
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem152
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem1/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem252
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem2/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem352
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem3/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem452
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem4/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem552
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem5/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem652
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem6/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem752
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf/If Action Subsystem7/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf44
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln53
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/CorrectedPinionAg62
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/CorrectedPinionAg/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/ForcedCenter62
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/ForcedCenter/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/StordLastPosn62
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/StordLastPosn/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/VehicleDynamic62
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/VehicleDynamic/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/WheelSpeed62
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln/WheelSpeed/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/PrevHwAgConf42
    HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/PrevHwAgConf/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/Case Invalid32
    HwAgSnsrls/HwAgSnsrlsPer1/Case Invalid/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/Case Valid32
    HwAgSnsrls/HwAgSnsrlsPer1/Case Valid/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/CopyRight231
    HwAgSnsrls/HwAgSnsrlsPer1/CorrdPinionAg32
    HwAgSnsrls/HwAgSnsrlsPer1/CorrdPinionAg/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/FCentr33
    HwAgSnsrls/HwAgSnsrlsPer1/FCentr/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/FCentr/If Action Subsystem42
    HwAgSnsrls/HwAgSnsrlsPer1/FCentr/If Action Subsystem/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/FixdToFloat_f32_s3231
    HwAgSnsrls/HwAgSnsrlsPer1/LimStat_f131
    HwAgSnsrls/HwAgSnsrlsPer1/LimStat_f231
    HwAgSnsrls/HwAgSnsrlsPer1/LimStat_f3231
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn34
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/LimStat_f3241
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/Set to 042
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/Set to 0/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/UseMotAg43
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/UseMotAg/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/UseMotAg/GetMotAgOffs52
    HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/UseMotAg/GetMotAgOffs/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/Smoothing33
    HwAgSnsrls/HwAgSnsrlsPer1/Smoothing/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/Smoothing/If Action Subsystem42
    HwAgSnsrls/HwAgSnsrlsPer1/Smoothing/If Action Subsystem/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/Smoothing/If Action Subsystem142
    HwAgSnsrls/HwAgSnsrlsPer1/Smoothing/If Action Subsystem1/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr37
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne43
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne/If Action Subsystem152
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne/If Action Subsystem1/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne/If Action Subsystem252
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne/If Action Subsystem2/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne/If Action Subsystem2/FilLpUpdOutp61
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna46
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/FilLpUpdOutp51
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr155
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan164
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan1/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan1/GetTiSpan100MicroSec32bit73
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan1/GetTiSpan100MicroSec32bit/CopyRight281
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan1/GetTiSpan100MicroSec32bit/No wrapping82
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan1/GetTiSpan100MicroSec32bit/No wrapping/CopyRight291
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan1/GetTiSpan100MicroSec32bit/Wrapping82
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/GetTiSpan1/GetTiSpan100MicroSec32bit/Wrapping/CopyRight291
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/If Action Subsystem363
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/If Action Subsystem3/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/If Action Subsystem3/GetRefTmr100MicroSec32bit72
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/If Action Subsystem3/GetRefTmr100MicroSec32bit/CopyRight281
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/Set to 063
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/Set to 0/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/Set to 0/GetRefTmr100MicroSec32bit72
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOneEna/VehDynTmr1/Set to 0/GetRefTmr100MicroSec32bit/CopyRight281
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo43
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo/If Action Subsystem352
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo/If Action Subsystem3/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo/If Action Subsystem452
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo/If Action Subsystem4/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo/If Action Subsystem4/FilLpUpdOutp61
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna46
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr255
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan264
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan2/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan2/GetTiSpan100MicroSec32bit73
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan2/GetTiSpan100MicroSec32bit/CopyRight281
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan2/GetTiSpan100MicroSec32bit/No wrapping82
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan2/GetTiSpan100MicroSec32bit/No wrapping/CopyRight291
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan2/GetTiSpan100MicroSec32bit/Wrapping82
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/GetTiSpan2/GetTiSpan100MicroSec32bit/Wrapping/CopyRight291
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/If Action Subsystem462
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/If Action Subsystem4/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/Set to 063
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/Set to 0/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/Set to 0/GetRefTmr100MicroSec32bit72
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwoEna/VehDynTmr2/Set to 0/GetRefTmr100MicroSec32bit/CopyRight281
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/PinionTqCalc42
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/PinionTqCalc/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/VehDynAutoCentr/PinionTqCalc/FilLpUpdOutp51
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr37
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/CopyRight241
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlFrqNotVld42
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlFrqNotVld/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd46
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/CopyRight251
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/If Action Subsystem52
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/If Action Subsystem/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/If Action Subsystem153
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/If Action Subsystem1/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/If Action Subsystem1/If Action Subsystem362
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/If Action Subsystem1/If Action Subsystem3/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/Output 052
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/Output 0/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk55
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/CopyRight261
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan64
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan /CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan /GetTiSpan100MicroSec32bit73
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan /GetTiSpan100MicroSec32bit/CopyRight281
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan /GetTiSpan100MicroSec32bit/No wrapping82
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan /GetTiSpan100MicroSec32bit/No wrapping/CopyRight291
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan /GetTiSpan100MicroSec32bit/Wrapping82
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/GetTiSpan /GetTiSpan100MicroSec32bit/Wrapping/CopyRight291
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/Set to 063
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/Set to 0/CopyRight271
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/Set to 0/GetRefTmr100MicroSec32bit72
    HwAgSnsrls/HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd/VehSpdChk/Set to 0/GetRefTmr100MicroSec32bit/CopyRight281
    HwAgSnsrls/RstSnsrlsHwCentr22
    HwAgSnsrls/RstSnsrlsHwCentr/CopyRight231
    ∧ Less


     Check for root Inports with missing properties

    Identify Inport blocks in the top-level of the model with missing or inherited sample times, data types, or port dimensions

    Warning
    The following Inport blocks have undefined or inherited sample times, data types or port dimensions

    InportLinkConditions
    1SF042A_HwAgSnsrls/WhlLeFrqMissing port dimension
    Missing signal data type
    Missing port sample time
    2SF042A_HwAgSnsrls/WhlRiFrqMissing port dimension
    Missing signal data type
    Missing port sample time
    3SF042A_HwAgSnsrls/VehSpdMissing port dimension
    Missing signal data type
    Missing port sample time
    4SF042A_HwAgSnsrls/VehSpdVldMissing port dimension
    Missing signal data type
    Missing port sample time
    5SF042A_HwAgSnsrls/MotVelCrfMissing port dimension
    Missing signal data type
    Missing port sample time
    6SF042A_HwAgSnsrls/HwTqMissing port dimension
    Missing signal data type
    Missing port sample time
    7SF042A_HwAgSnsrls/MotTqCmdCrfMissing port dimension
    Missing signal data type
    Missing port sample time
    8SF042A_HwAgSnsrls/VehYawRateMissing port dimension
    Missing signal data type
    Missing port sample time
    9SF042A_HwAgSnsrls/MotAgCumvAlgndCrfMissing port dimension
    Missing signal data type
    Missing port sample time
    10SF042A_HwAgSnsrls/CmplncErrMotToPinionMissing port dimension
    Missing signal data type
    Missing port sample time
    11SF042A_HwAgSnsrls/PinionAgMissing port dimension
    Missing signal data type
    Missing port sample time
    12SF042A_HwAgSnsrls/PinionAgConfMissing port dimension
    Missing signal data type
    Missing port sample time
    13SF042A_HwAgSnsrls/WhlFrqVldMissing port dimension
    Missing signal data type
    Missing port sample time
    14SF042A_HwAgSnsrls/MotAgCumvAlgndVldMissing port dimension
    Missing signal data type
    Missing port sample time
    ∧ Less


    Recommended Action
    Explicitly define all missing Inport block properties identified in the results
    • Missing port dimension: Model contains Inport blocks with inherited port dimension (-1). Specify port dimension for the listed Inport blocks.
    • Missing signal data type: Model contains Inport blocks with inherited data type. Specify a data type for the listed Inport blocks.
    • Missing port sample time: Model contains Inport blocks with inherited sample time (-1). Specify sample time information for the listed Inport blocks. Note: The sample time of root Inports with bus type must match the sample times specified at the leaf elements of the bus object.

     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 subsystem names

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

    See Also

    Warning
    The following subsystem names contain incorrect characters:

    ErrorSubsystem block
    Name contains incorrect characters...../Arbitrator/MaxHwConf/If Action Subsystem
    Name contains incorrect characters...../MaxHwConf/If Action Subsystem1
    Name contains incorrect characters...../MaxHwConf/If Action Subsystem2
    Name contains incorrect characters...../MaxHwConf/If Action Subsystem3
    Name contains incorrect characters...../MaxHwConf/If Action Subsystem4
    Name contains incorrect characters...../MaxHwConf/If Action Subsystem5
    Name contains incorrect characters...../MaxHwConf/If Action Subsystem6
    Name contains incorrect characters...../MaxHwConf/If Action Subsystem7
    Name contains incorrect characters...../HwAgSnsrls/HwAgSnsrlsPer1/Case Invalid
    Name contains incorrect characters...../HwAgSnsrls/HwAgSnsrlsPer1/Case Valid
    Name contains incorrect characters...../FCentr/If Action Subsystem
    Name contains incorrect characters...../HwAgSnsrlsPer1/RelHwAgCalcn/Set to 0
    Name contains incorrect characters...../Smoothing/If Action Subsystem
    Name contains incorrect characters...../Smoothing/If Action Subsystem1
    Name contains incorrect characters...../LpFilOne/If Action Subsystem1
    Name contains incorrect characters...../LpFilOne/If Action Subsystem2
    Name contains incorrect characters...../VehDynTmr1/If Action Subsystem3
    Name contains incorrect characters...../LpFilOneEna/VehDynTmr1/Set to 0
    Name contains incorrect characters...../LpFilTwo/If Action Subsystem3
    Name contains incorrect characters...../LpFilTwo/If Action Subsystem4
    Name contains incorrect characters...../VehDynTmr2/If Action Subsystem4
    Name contains incorrect characters...../LpFilTwoEna/VehDynTmr2/Set to 0
    Name contains incorrect characters...../WhlSpd/If Action Subsystem
    Name contains incorrect characters...../WhlSpd/If Action Subsystem1
    Name contains incorrect characters...../If Action Subsystem3
    Name contains incorrect characters...../WhlSpdAutoCentr/WhlSpd/Output 0
    Name contains incorrect characters...../WhlSpd/VehSpdChk/GetTiSpan
    Name contains incorrect characters...../WhlSpd/VehSpdChk/Set to 0
    ∧ Less


    Recommended Action
    Rename the subsystem blocks using correct characters.

     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
    SF042A_HwAgSnsrlsSF042A_HwAgSnsrls/Clock
    SF042A_HwAgSnsrlsSF042A_HwAgSnsrls/CopyRight2
    SF042A_HwAgSnsrlsSF042A_HwAgSnsrls/Data Store Write
    SF042A_HwAgSnsrls/HwAgSnsrlsSF042A_HwAgSnsrls/HwAgSnsrls/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrls/HwAgSnsrlsInit1/Constant1
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrls/HwAgSnsrlsInit1/Constant2
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrls/HwAgSnsrlsInit1/Constant5
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrls/HwAgSnsrlsInit1/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Read
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write1
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write2
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write3
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write4
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write5
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write6
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write7
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Data Store Write8
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Enumerated Constant2
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Enumerated Constant4
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrls/HwAgSnsrlsInit1/GetNtcQlfrSts
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../GetRefTmr100MicroSec32bit
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrls/HwAgSnsrlsInit1/NtcStsChk
    ..../HwAgSnsrls/HwAgSnsrlsInit1..../HwAgSnsrlsInit1/Set Ram Block Status
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrls/HwAgSnsrlsPer1/Constant1
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrls/HwAgSnsrlsPer1/Constant2
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrls/HwAgSnsrlsPer1/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrlsPer1/Data Store Write
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrlsPer1/FixdToFloat_f32_s32
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrls/HwAgSnsrlsPer1/LimStat_f1
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrls/HwAgSnsrlsPer1/LimStat_f2
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrls/HwAgSnsrlsPer1/LimStat_f32
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrlsPer1/Relational Operator1
    ..../HwAgSnsrls/HwAgSnsrlsPer1..../HwAgSnsrlsPer1/Relational Operator2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../HwAgSnsrlsPer1/Arbitrator/Add1
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../HwAgSnsrlsPer1/Arbitrator/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../Arbitrator/Data Store Read
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../Arbitrator/Data Store Read1
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../Arbitrator/Data Store Write
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../Arbitrator/Data Store Write1
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../Arbitrator/Data Store Write3
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../Arbitrator/Relational Operator3
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../Arbitrator/Relational Operator4
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator..../HwAgSnsrlsPer1/Arbitrator/Unary Minus
    ..../HwAgSnsrlsPer1/Arbitrator/MaxHwConf..../Arbitrator/MaxHwConf/CopyRight2
    ..../HwAgSnsrlsPer1/Arbitrator/MaxHwConf..../Arbitrator/MaxHwConf/Data Store Read4
    ..../HwAgSnsrlsPer1/Arbitrator/MaxHwConf..../Arbitrator/MaxHwConf/Relational Operator
    ..../HwAgSnsrlsPer1/Arbitrator/MaxHwConf..../MaxHwConf/Relational Operator1
    ..../HwAgSnsrlsPer1/Arbitrator/MaxHwConf..../MaxHwConf/Relational Operator2
    ..../HwAgSnsrlsPer1/Arbitrator/MaxHwConf..../MaxHwConf/Relational Operator3
    ..../HwAgSnsrlsPer1/Arbitrator/NewHwAgConf..../Arbitrator/NewHwAgConf/CopyRight2
    ..../Arbitrator/NewHwAgConf/HwAgOffsSeln..../NewHwAgConf/HwAgOffsSeln/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/FCentr..../HwAgSnsrlsPer1/FCentr/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/FCentr..../HwAgSnsrlsPer1/FCentr/Data Store Read
    ..../HwAgSnsrls/HwAgSnsrlsPer1/FCentr..../HwAgSnsrlsPer1/FCentr/Data Store Read2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn..../HwAgSnsrlsPer1/RelHwAgCalcn/Add
    ..../HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn..../HwAgSnsrlsPer1/RelHwAgCalcn/Add1
    ..../HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn..../HwAgSnsrlsPer1/RelHwAgCalcn/Constant
    ..../HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn..../HwAgSnsrlsPer1/RelHwAgCalcn/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn..../RelHwAgCalcn/Data Store Read2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn..../HwAgSnsrlsPer1/RelHwAgCalcn/Divide
    ..../HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn..../HwAgSnsrlsPer1/RelHwAgCalcn/LimStat_f32
    ..../HwAgSnsrlsPer1/RelHwAgCalcn/UseMotAg..../RelHwAgCalcn/UseMotAg/CopyRight2
    ..../HwAgSnsrlsPer1/RelHwAgCalcn/UseMotAg..../RelHwAgCalcn/UseMotAg/Data Store Read2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../HwAgSnsrlsPer1/Smoothing/Abslt_f32_f32
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing/Add3
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../HwAgSnsrlsPer1/Smoothing/Constant
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../HwAgSnsrlsPer1/Smoothing/CopyRight2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../HwAgSnsrlsPer1/Smoothing/Data Store Read
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../Smoothing/Data Store Read1
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../Smoothing/Data Store Write2
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../Smoothing/Logical Operator1
    ..../HwAgSnsrls/HwAgSnsrlsPer1/Smoothing..../Smoothing/Relational Operator
    ..../HwAgSnsrlsPer1/VehDynAutoCentr..../VehDynAutoCentr/CopyRight2
    ..../HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne..../VehDynAutoCentr/LpFilOne/CopyRight2
    ..../HwAgSnsrlsPer1/VehDynAutoCentr/LpFilOne..../LpFilOne/Data Store Write
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/Abslt_f32_f1
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/Abslt_f32_f2
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/Abslt_f32_f3
    ..../VehDynAutoCentr/LpFilOneEna..../LpFilOneEna/Abslt_f32_f32
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/Constant
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/Constant1
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/Constant2
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/Constant3
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/CopyRight2
    ..../VehDynAutoCentr/LpFilOneEna..../VehDynAutoCentr/LpFilOneEna/FilLpUpdOutp
    ..../VehDynAutoCentr/LpFilOneEna..../LpFilOneEna/Logical Operator
    ..../VehDynAutoCentr/LpFilOneEna..../LpFilOneEna/Relational Operator
    ..../VehDynAutoCentr/LpFilOneEna..../LpFilOneEna/Relational Operator1
    ..../VehDynAutoCentr/LpFilOneEna..../LpFilOneEna/Relational Operator2
    ..../VehDynAutoCentr/LpFilOneEna..../LpFilOneEna/Relational Operator3
    ..../VehDynAutoCentr/LpFilOneEna/VehDynTmr1..../LpFilOneEna/VehDynTmr1/Constant1
    ..../VehDynAutoCentr/LpFilOneEna/VehDynTmr1..../LpFilOneEna/VehDynTmr1/Constant3
    ..../VehDynAutoCentr/LpFilOneEna/VehDynTmr1..../LpFilOneEna/VehDynTmr1/CopyRight2
    ..../VehDynAutoCentr/LpFilOneEna/VehDynTmr1..../LpFilOneEna/VehDynTmr1/Data Store Read1
    ..../VehDynAutoCentr/LpFilOneEna/VehDynTmr1..../LpFilOneEna/VehDynTmr1/Product
    ..../VehDynAutoCentr/LpFilOneEna/VehDynTmr1..../VehDynTmr1/Relational Operator1
    ..../HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo..../VehDynAutoCentr/LpFilTwo/CopyRight2
    ..../HwAgSnsrlsPer1/VehDynAutoCentr/LpFilTwo..../LpFilTwo/Data Store Write1
    ..../VehDynAutoCentr/LpFilTwoEna..../VehDynAutoCentr/LpFilTwoEna/Abslt_f32_f3
    ..../VehDynAutoCentr/LpFilTwoEna..../VehDynAutoCentr/LpFilTwoEna/Add
    ..../VehDynAutoCentr/LpFilTwoEna..../VehDynAutoCentr/LpFilTwoEna/Constant5
    ..../VehDynAutoCentr/LpFilTwoEna..../VehDynAutoCentr/LpFilTwoEna/CopyRight2
    ..../VehDynAutoCentr/LpFilTwoEna..../LpFilTwoEna/Logical Operator1
    ..../VehDynAutoCentr/LpFilTwoEna..../LpFilTwoEna/Relational Operator3
    ..../VehDynAutoCentr/LpFilTwoEna/VehDynTmr2..../LpFilTwoEna/VehDynTmr2/Constant1
    ..../VehDynAutoCentr/LpFilTwoEna/VehDynTmr2..../LpFilTwoEna/VehDynTmr2/Constant3
    ..../VehDynAutoCentr/LpFilTwoEna/VehDynTmr2..../LpFilTwoEna/VehDynTmr2/CopyRight2
    ..../VehDynAutoCentr/LpFilTwoEna/VehDynTmr2..../LpFilTwoEna/VehDynTmr2/Data Store Read1
    ..../VehDynAutoCentr/LpFilTwoEna/VehDynTmr2..../LpFilTwoEna/VehDynTmr2/Product
    ..../VehDynAutoCentr/LpFilTwoEna/VehDynTmr2..../VehDynTmr2/Relational Operator1
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr..../WhlSpdAutoCentr/CopyRight2
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr..../WhlSpdAutoCentr/Data Store Write2
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Abslt_f32_f1
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Abslt_f32_f2
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Abslt_f32_f32
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Constant
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Constant1
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/CopyRight2
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Data Store Read
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Data Store Read2
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpdAutoCentr/WhlSpd/Logical Operator
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpd/Relational Operator
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpd/Relational Operator1
    ..../HwAgSnsrlsPer1/WhlSpdAutoCentr/WhlSpd..../WhlSpd/Relational Operator2
    ..../WhlSpd/If Action Subsystem1..../WhlSpd/If Action Subsystem1/Abslt_f32_f1
    ..../WhlSpd/If Action Subsystem1..../WhlSpd/If Action Subsystem1/Add1
    ..../WhlSpd/If Action Subsystem1..../WhlSpd/If Action Subsystem1/Constant2
    ..../WhlSpd/If Action Subsystem1..../WhlSpd/If Action Subsystem1/Constant3
    ..../WhlSpd/If Action Subsystem1..../WhlSpd/If Action Subsystem1/Constant4
    ..../WhlSpd/If Action Subsystem1..../WhlSpd/If Action Subsystem1/CopyRight2
    ..../WhlSpd/If Action Subsystem1..../WhlSpd/If Action Subsystem1/Product
    ..../WhlSpd/If Action Subsystem1..../Relational Operator2
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpd/VehSpdChk/Abslt_f32_f3
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpd/VehSpdChk/Constant1
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpd/VehSpdChk/Constant3
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpd/VehSpdChk/Constant4
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpd/VehSpdChk/CopyRight2
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpdAutoCentr/WhlSpd/VehSpdChk/Product
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpd/VehSpdChk/Relational Operator4
    ..../WhlSpdAutoCentr/WhlSpd/VehSpdChk..../WhlSpd/VehSpdChk/Relational Operator5
    ∧ 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
    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:

    ∧ Less
    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.

    Warning
    The following blocks have a name displayed, however, the name is not descriptive:

    Recommended Action
    Modify the block name to provide descriptive information, or hide the block name by deselecting (Diagram > Format > Show Block Name).
    _________________________________________________________________________________________

    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:

    ∧ Less
    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:∧ Less
    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 signals originating in Subsystem blocks to verify that the signals have labels.

    Warning
    The following signal labels are not propagated. Propagate signals coming from Subsystem blocks.

    Recommended Action
    Add labels to the output 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

     Identify selection-based links having description fields that do not match their requirements document text

    Inconsistencies:

    The following selection-based links have descriptions that differ from their corresponding selections in the requirements documents. If this reflects a change in the requirements document, click Update to replace the current description in the selection-based link with the text from the requirements document (the external description).
     
    Block 

    		Current description External description  

    SF042A_HwAgSnsrls/HwAgSnsrls/MotAgCumvAlgndVld

    		REQ:SF042A_92REQ: SF042A_92

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/If3

    		REQ:SF042A_80REQ: SF042A_80

    		Update
    REQ:SF042A_90REQ: SF042A_90

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/MaxHwConf

    		REQ:SF042A_80REQ: SF042A_80

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/Merge1

    		REQ:SF042A_90REQ: SF042A_90

    		Update
    REQ:SF042A_80REQ: SF042A_80

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/Merge2

    		REQ:SF042A_90REQ: SF042A_90

    		Update
    REQ:SF042A_80REQ: SF042A_80

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/Merge6

    		REQ:SF042A_90REQ: SF042A_90

    		Update
    REQ:SF042A_80REQ: SF042A_80

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf

    		REQ:SF042A_80REQ: SF042A_80

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/PrevHwAgConf

    		REQ:SF042A_90REQ: SF042A_90

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/Relational Operator3

    		REQ:SF042A_80REQ: SF042A_80

    		Update
    REQ:SF042A_90REQ: SF042A_90

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/MotAgCumvAlgndCrf

    		REQ:SF042A_66REQ: SF042A_66

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/Add1

    		REQ:SF042A_66REQ: SF042A_66

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/Data Store Read2

    		REQ:SF042A_66REQ: SF042A_66

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/If

    		REQ:SF042A_66REQ: SF042A_66

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/Merge

    		REQ:SF042A_66REQ: SF042A_66

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/Set to 0

    		REQ:SF042A_66REQ: SF042A_66

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/RelHwAgCalcn/UseMotAg

    		REQ:SF042A_66REQ: SF042A_66

    		Update

    SF042A_HwAgSnsrls/HwAgSnsrls/HwAgSnsrlsPer1/Arbitrator/NewHwAgConf/HwAgOffsSeln

    		REQ:SF042A_80REQ: SF042A_80

    		Update


            Simulation Accuracy

            Simulation Runtime Accuracy Diagnostics

     Check if Read/Write diagnostics are enabled for Data Store blocks

    Note: These runtime diagnostics may slow down simulation considerably. You should set them back to Disable all once you have verified that they do not cause any warnings or errors during simulation.



            Simulink Model File Integrity

            Upgrading to the Current Simulink Version