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 - SF044A_HowDetn_Peer Review Checklist Design

Nexteer_Template_V1.0

Overview

Peer Review Instructions
Technical Review Checklist
Template Change Log

Sheet 1: Peer Review Instructions

Instructions for Functional Design Package Peer Review




PRE-MEETING


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

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

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

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

Function OwnerIdentify necessary attendance and invite to meeting

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

Function OwnerComplete the attendance invitation list in section 5

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



DURING MEETING


Function OwnerPresent document changes to the review team

Peer ReviewerCapture attendance of the review

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



POST MEETING


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

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

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

Sheet 2: Technical Review Checklist

Technical Review Checklist - Template Version 02.00.00







Product NameElectric Power SteeringElectrical Arch.4Review ScopeDefect TypeNumbers




YesClosedFR
Function IDSF044A_HowDetn

Data dictionaryRequirement0




NoRejectedFDD
Long NameHands on wheel Detection

Interface0




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






FMEA
AuthorSneha SinghReview Effort(Hrs.)0.50Standards0






*.m File


Corr+Verf effort(Hrs.)1.20Documentation0






Cal Process


Total Effort (Hrs.)1.70Others0













Total0







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







1Section 1: Data Dictionary














Is Filename of Data Dictionary in correct format?Yes













Is the FDD.Version property correctly updated?Yes













Is the Data Dictionary Verification report error free?No
1. There are some warnings which is causing errors in the report. Refer 'Verify_DD_warnings.txt' present in the doc folder.

2. Since singal names consists of component names errors exists. But since there wont be any change in the signal names, these errors can be ignored.

Closed








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













Are all runnables defined?Yes













Do runnables have the correct time step?Yes













Do server runnables correctly define arguments?Yes













Are all clients defined?Yes













Do client definitions match the corresponding server runnable?Yes













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













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













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













Do all calibrations have correct values for all metadata?Yes













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













Is NVM defined in the appropriate number of blocks?NA
No NVM defined











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













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




























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








Is filename of model in correct format?Yes













Is Top level of model annotated with Requirements Baseline?Yes













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













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













Does the Component shortname match data dictionary FDD metadata?Yes













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













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












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













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













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













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













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













Do all Memory Store blocks for PIM and Display Variables have the "Data store name must resolve to Simulink signal object" setting checked to true?Yes













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











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?NA
No NVM defined











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













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




























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








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













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













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













Is the list of unlinked blocks acceptable?Yes




























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








Was Model Advisor run with the correct configuration settings?Yes













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













Are Model Advisor report "Warnings" acceptable?Yes




























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








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













Does Doc folder contain a zipped HTML webview model?Yes













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




























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







6.1














6.2














6.3














6.4














6.5














6.6














6.7














6.8














6.9














6.10














6.11














6.12














6.13














6.14














6.15














6.16














6.17














6.18














6.19














6.20














6.21














6.22














6.23














6.24














6.25














7Section 7: APPROVALS













RoleFirst ReviewDateAttendanceApproval?










Function Owner*Sneha Singh (Author)8/12/2016Yes











Peer Reviewer*Qi WangYesYes










Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleSecond Review (if required)DateAttendanceApproval?










Function Owner*<Name - if invited>













Peer Reviewer*<Name - if invited>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleThird Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleFourth Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleAdd more if necessaryDateAttendanceApproval?










































P.S.:Yes indicates adherence














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














NA indicates not applicable













Sheet 3: Template Change Log

RevChangeAuthor
01.00.05Added lesson learned #3.5MDK
01.00.06Added lesson learned #3.6, 3.7 - Structure and writing of NVM in mfiles and models.MDK
02.00.00Combined ESG and Systems into one, compatible with Data_Management 2.13.0 of CreateDD and VerifyDD.K. Derry

















































































2 - SF044A_HowDetn_PeerReviewChkList Requirements

Nexteer_Template_V1.0

Overview

Peer Review Instructions
Technical Review Checklist
Action Item List
Template Change Log

Sheet 1: Peer Review Instructions

Instructions for conducting a Requirements Peer Review




PRE-MEETING





Function OwnerProvide the Review Moderator with the latest version of the requirements to be reviewed




Review ModeratorStart with the latest version of the template for any "first reviews" - Continue to use the existing template for re-reviews

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

Review ModeratorComplete the attendance invitation list in section 7

Review Moderator/Function OwnerIdentify necessary attendance and invite them to the meeting. Provide the requirements to the invited attendees 2 or more working days in advance of the review. Include a copy of the Peer Review Checklist for them to note any anomalies found.

AttendeesReview the provided artifacts, record issues on the Peer Review Checklist, record your name in the top left block as the Reviewer, and return the Peer Review Checklist to the Review Moderator 1 day prior to the review for collation. Any design issues should be resolved with the Function Owner prior to the review.

Review ModeratorPrior to the review, collate all Peer Review Checklists. Identify each reviewer's comments with their initials at the beginning of the "Description of finding by reviewer" section. The Collated file shall be used to create a Review copy of the issues.

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



DURING MEETING


Function OwnerPresent document changes to the review team

Review ModeratorCapture attendance of the review

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



POST MEETING


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

Review ModeratorSchedule follow up review OR review open items with peer reviewer and obtain agreement to close

Review ModeratorClose change request in system and confirm all associated tasks are complete. Upload peer review checklist (this document) with any FDP updates. Contact the Function Owner and Attendees and provide the location of the completed Peer Review Checklist; do not distribute the Peer Review Checklist via email.

Sheet 2: Technical Review Checklist

Component Requirements Review Checklist - Template Version 3







Product NameElectric Power Steering

Review ScopeDefect TypeNumbers




YesClosedFR
Function IDSF044A_HOW

Requirements Review for SF044A, Hands On Wheel Detection.Requirement0




NoRejectedFDD
Long NameHands on Wheel Detection

Interface0




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






FMEA
AuthorQi WangReview Effort(Hrs.)
Standards0






*.m File
ModeratorDavid LytzCorr+Verf effort(Hrs.)
Documentation0






Cal Process
Reviewer
Total Effort (Hrs.)0.00Others0













Total0







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







1Section 1: System Function Description














Does Function ID follow correct pattern: AAnnnA (e.g. ES999A)?YesYes












Does Long Name use only Autosar-approved keywords?YesYes












Does ShortName match Long Name and use Autosar abbreviations?YesYes



























































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








Are all signal names in the form of Capitalized Long Names?YesYes












Are callable routines given names that will likely be unique in a system?NANA



























































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








Are requirements appropriately categorized into major feature categories?YesYes












Are intermediate calculations introduced in proper order for readability?YesYes












Are output ranges properly defined?YesYes












Are output resolutions defined to an appropriate number of decimal?YesYes












Is execution rate information defined?YesYes












Is ASIL allocation defined?YesYes












Is NTC information properly defined?NANA











































































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








Do object IDs have appropriate prefix (e.g. "SF001A_")?YesYes












Are all "Reqt" attributes (T/F) filled in properly?YesYes












Are all ".EA?" attributes (EA3, EA4, Both) filled in propertly?YesYes












Do all requirements contain "shall"?YesYes












Is module based on latest template?YesYes












Has traceability been performed in DOORS (if possible)?NoNo

Traceability to model will be performed. Bilateral traceability shall be performed upon artifact creation requiring the traceability.
























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







5.1Scott Milsap - not HOW specific, but, we need to start fault injection logic requirements in the component requirement documents













5.2














5.3














5.4














5.5














5.6














5.7














5.8














5.9














5.10














5.11














5.12














5.13














5.14














5.15














5.16














5.17














5.18














5.19














5.20














6Section 6: APPROVALS













RoleFirst ReviewDateAttendanceApproval?










Function Owner*Qi Wang, Sneha Singh5/20/2016YesYes










Moderator*David LytzYesYes










SafetyScott MilsapYesYes










SoftwareKrishna AnneYesYes










ESG / SystemsPrice LeflerYesYes










EPDT / CSE













Hardware













Test













RoleSecond Review (if required)DateAttendanceApproval?










Function Owner*














Peer Reviewer*













Safety













Software













ESG / Systems













EPDT / CSE













Hardware













Test













RoleThird Review (if required)DateAttendanceApproval?










Function Owner*














Peer Reviewer*













Safety













Software













ESG / Systems













EPDT / CSE













Hardware













Test













RoleFourth Review (if required)DateAttendanceApproval?










Function Owner*














Peer Reviewer*













Safety













Software













ESG / Systems













EPDT / CSE













Hardware













Test













RoleAdd more if necessaryDateAttendanceApproval?










































P.S.:Yes indicates adherence














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














NA indicates not applicable













Sheet 3: Action Item List

ACTION ITEM LIST















ITEM #



DESCRIPTION




ASSIGNEE



DUE DATE

Sheet 4: Template Change Log

RevChangeAuthor
1Initial Release, based on Excel sheet created by Venkata SivanandV. Sivanand
2Revised the Peer Review Instructions sheet to provide the revised procedureLytz
3Update for traceabilityLytz

















































































3 - SF044A_HowDetn_modeladvisor

Model Advisor Report for 'SF044A_HowDetn'
Model Advisor Report - SF044A_HowDetn.slx
Simulink version: 8.2Model version: 1.379
System: SF044A_HowDetnCurrent run: 12-Aug-2016 09:42:04
 Model Advisor configuration: ...NxtrModelAdvisorConfig.mat

Run Summary
PassFailWarningNot RunTotal
   51   0   16   133200


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
    Inport79
    Outport49
    SubSystem78


    Simulink

    Block TypeCount
    Constant91
    Inport79
    SubSystem78
    Outport49
    Sum30
    DataStoreWrite28
    Product27
    S-Function22
    Math19
    DataStoreMemory11
    DataStoreRead10
    From8
    DataTypeConversion7
    Width6
    UnaryMinus5
    ActionPort4
    Goto3
    TriggerPort2
    If2
    Merge2
    RelationalOperator2
    Step2
    EnablePort2
    Sqrt1
    ∧ Less

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


    Maximum Subsystem Depth: 6

    Subsystem Depth

    Subsystem NameLevelDepth
    CopyRight211
    HowDetn15
    HowDetn/CopyRight221
    HowDetn/HowDetnInit122
    HowDetn/HowDetnInit1/CopyRight231
    HowDetn/HowDetnInit1/EstimLpFil31
    HowDetn/HowDetnInit1/FinalLpFil31
    HowDetn/HowDetnInit1/IniLpFil131
    HowDetn/HowDetnInit1/IniLpFil231
    HowDetn/HowDetnInit1/IniLpFil331
    HowDetn/HowDetnInit1/StLpFil31
    HowDetn/HowDetnInit1/TqHpFil31
    HowDetn/HowDetnPer124
    HowDetn/HowDetnPer1/Calculate HOW Estimate33
    HowDetn/HowDetnPer1/Calculate HOW Estimate/CalcEstimn42
    HowDetn/HowDetnPer1/Calculate HOW Estimate/CalcEstimn/CopyRight251
    HowDetn/HowDetnPer1/Calculate HOW Estimate/CopyRight241
    HowDetn/HowDetnPer1/Calculate HOW Estimate/FilLpUpdOutp41
    HowDetn/HowDetnPer1/Calculate HOW Estimate/High-Frequency Lookup Table42
    HowDetn/HowDetnPer1/Calculate HOW Estimate/High-Frequency Lookup Table/BilnrIntrpnWithRound_s16_u16MplXs16MplY51
    HowDetn/HowDetnPer1/Calculate HOW Estimate/High-Frequency Lookup Table/CopyRight251
    HowDetn/HowDetnPer1/Calculate HOW Estimate/High-Frequency Lookup Table/FixdToFloat_f32_s1651
    HowDetn/HowDetnPer1/Calculate HOW Estimate/High-Frequency Lookup Table/FloatToFixd_u16_f151
    HowDetn/HowDetnPer1/Calculate HOW Estimate/High-Frequency Lookup Table/FloatToFixd_u16_f3251
    HowDetn/HowDetnPer1/Calculate HOW Estimate/LimDyn_f141
    HowDetn/HowDetnPer1/Calculate HOW Estimate/LimDyn_f3241
    HowDetn/HowDetnPer1/Calculate HOW Estimate/Low-Frequency Lookup Table42
    HowDetn/HowDetnPer1/Calculate HOW Estimate/Low-Frequency Lookup Table/BilnrIntrpnWithRound_s16_u16MplXs16MplY51
    HowDetn/HowDetnPer1/Calculate HOW Estimate/Low-Frequency Lookup Table/CopyRight251
    HowDetn/HowDetnPer1/Calculate HOW Estimate/Low-Frequency Lookup Table/FixdToFloat_f32_s1651
    HowDetn/HowDetnPer1/Calculate HOW Estimate/Low-Frequency Lookup Table/FloatToFixd_u16_f151
    HowDetn/HowDetnPer1/Calculate HOW Estimate/Low-Frequency Lookup Table/FloatToFixd_u16_f3251
    HowDetn/HowDetnPer1/Calculate HOW Estimate/RateLimDyn_f3241
    HowDetn/HowDetnPer1/Calculate HOW Estimate/default42
    HowDetn/HowDetnPer1/Calculate HOW Estimate/default/CopyRight251
    HowDetn/HowDetnPer1/CopyRight231
    HowDetn/HowDetnPer1/Determine HOW State33
    HowDetn/HowDetnPer1/Determine HOW State/CopyRight241
    HowDetn/HowDetnPer1/Determine HOW State/FilLpUpdOutp141
    HowDetn/HowDetnPer1/Determine HOW State/HOW State Look up Table42
    HowDetn/HowDetnPer1/Determine HOW State/HOW State Look up Table/CopyRight251
    HowDetn/HowDetnPer1/Determine HOW State/HOW State Look up Table/FloatToFixd_u16_f151
    HowDetn/HowDetnPer1/Determine HOW State/HOW State Look up Table/LnrIntrpn_s16_u16VariXs16VariY51
    HowDetn/HowDetnPer1/Determine HOW State/Pass42
    HowDetn/HowDetnPer1/Determine HOW State/Pass/CopyRight251
    HowDetn/HowDetnPer1/Determine HOW State/Zero42
    HowDetn/HowDetnPer1/Determine HOW State/Zero/CopyRight251
    HowDetn/HowDetnPer1/Filter HwTq32
    HowDetn/HowDetnPer1/Filter HwTq/CopyRight241
    HowDetn/HowDetnPer1/Filter HwTq/FilHpUpdOutp41
    HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp41
    HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp141
    HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp241
    HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp341
    HowDetn/HowDetnPer1/Filter HwTq/FixdToFloat_f32_u1641
    HowDetn/HowDetnPer1/Filter HwTq/FloatToFixd_u16_f3241
    HowDetn/HowDetnPer1/Filter HwTq/LnrIntrpn_u16_u16VariXu16VariY41
    HowDetn/HowDetnPer1/LimStat_f3231
    HowDetn/HowDetnPer1/LimStat_s0831
    call_HowDetnInit112
    call_HowDetnInit1/CopyRight221
    call_HowDetnPer112
    call_HowDetnPer1/CopyRight221
    ∧ Less


     Check for model objects that do not link to requirements

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

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

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



        Modeling Standards for MAAB

            Naming Conventions

     Check 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
    Name contains incorrect characters...../call_HowDetnPer1/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
    SF044A_HowDetnSF044A_HowDetn/CopyRight2
    SF044A_HowDetnSF044A_HowDetn/Step
    SF044A_HowDetnSF044A_HowDetn/Step1
    SF044A_HowDetn/HowDetnSF044A_HowDetn/HowDetn/CopyRight2
    SF044A_HowDetn/HowDetn/HowDetnPer1..../HowDetn/HowDetnPer1/CopyRight2
    SF044A_HowDetn/HowDetn/HowDetnPer1..../HowDetn/HowDetnPer1/LimStat_f32
    SF044A_HowDetn/HowDetn/HowDetnPer1..../HowDetn/HowDetnPer1/LimStat_s08
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Constant1
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Constant2
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Constant3
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Constant4
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Constant5
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/CopyRight2
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Data Store Read
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Data Store Write6
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/FilLpUpdOutp
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/LimDyn_f1
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/LimDyn_f32
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Product1
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Product2
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/RateLimDyn_f32
    ..../HowDetnPer1/Calculate HOW Estimate..../Relational Operator
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Subtract1
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Subtract2
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Subtract3
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/TimerValue1
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/TimerValue4
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/TimerValue8
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Unary Minus
    ..../HowDetnPer1/Calculate HOW Estimate..../Calculate HOW Estimate/Unary Minus1
    ..../HowDetn/HowDetnPer1/Determine HOW State..../Determine HOW State/Constant1
    ..../HowDetn/HowDetnPer1/Determine HOW State..../Determine HOW State/CopyRight2
    ..../HowDetn/HowDetnPer1/Determine HOW State..../Determine HOW State/FilLpUpdOutp1
    ..../HowDetn/HowDetnPer1/Determine HOW State..../Determine HOW State/Relational Operator
    ∧ Less


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



            Model Configuration Options

            Simulink

     Check for Simulink diagrams using nonstandard display attributes

    Identify nonstandard display attributes in Simulink diagrams.

    See Also

    _________________________________________________________________________________________

    Check format settings
    Identify incorrect model-level format options.

    Warning
    The following format display options are incorrect.

    Display AttributeRecommended ValueActual Value
    Display > Signals & Ports > Wide Nonscalar Linesonoff
    Display > Signals & Ports > Storage Classoffon
    View > Model Browser Options > Model Browseroffon


    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

    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:

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

     Check signal line labels

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

    See Also

    _________________________________________________________________________________________

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

    Warning
    The following signals have no label:

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

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

    Warning
    The following signals have no label:

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

     Check for propagated signal labels

    Identify propagated labels on signal lines.

    See Also

    _________________________________________________________________________________________

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

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

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

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

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

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



            Stateflow

     Check usage of exclusive and default states in state machines

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

    See Also

    _________________________________________________________________________________________

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

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

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

    Passed
    Each Stateflow chart defines a default state.
    _________________________________________________________________________________________

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

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

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

    Passed
    No singular OR states were detected.
    _________________________________________________________________________________________

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

    Passed
    All substates have default states assigned.
    _________________________________________________________________________________________

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

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

     Check transition orientations in flowcharts

    Identify transitions in Stateflow flowcharts that are drawn incorrectly.

    See Also

    _________________________________________________________________________________________

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

    Passed
    All conditions expressions were drawn horizontally.
    _________________________________________________________________________________________

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

    Passed
    All transitions actions where drawn vertically.
    _________________________________________________________________________________________

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

    Passed
    All Junctions have a default exit transition.
    _________________________________________________________________________________________

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

    Passed
    No combined expressions where found in the chart.



            MATLAB Functions

        Requirements Consistency Checking

     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  

    SF044A_HowDetn/HwTq

    		REQ:SF044A_67REQ: SF044A_67

    		Update

    SF044A_HowDetn/VehSpd

    		REQ:SF044A_68REQ: SF044A_68

    		Update

    SF044A_HowDetn/HowDetnEstimn

    		REQ:SF044A_69REQ: SF044A_69

    		Update

    SF044A_HowDetn/HowDetnSt

    		REQ:SF044A_70REQ: SF044A_70

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/LimStat_f32

    		REQ:SF044A_86REQ: SF044A_86

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/LimStat_s08

    		REQ:SF044A_87REQ: SF044A_87

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/Constant1

    		REQ:SF044A_9REQ: SF044A_9

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/Constant2

    		REQ:SF044A_9REQ: SF044A_9

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/Constant5

    		REQ:SF044A_11REQ: SF044A_11

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/FilLpUpdOutp

    		REQ:SF044A_9REQ: SF044A_9

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/From2

    		REQ:SF044A_11REQ: SF044A_11

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/If

    		REQ:SF044A_11REQ: SF044A_11

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/LimDyn_f32

    		REQ:SF044A_9REQ: SF044A_9

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/Relational Operator

    		REQ:SF044A_11REQ: SF044A_11

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/Subtract3

    		REQ:SF044A_9REQ: SF044A_9

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/TimerValue1

    		REQ:SF044A_21REQ: SF044A_21

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/Unary Minus1

    		REQ:SF044A_9REQ: SF044A_9

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/default

    		REQ:SF044A_11REQ: SF044A_11

    		Update
    REQ:SF044A_10REQ: SF044A_10

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Calculate HOW Estimate/HowDetnEstimn

    		REQ:SF044A_83REQ: SF044A_83

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/HowDetnEstimn

    		REQ:SF044A_22REQ: SF044A_22

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/VehSpd

    		REQ:SF044A_15REQ: SF044A_15

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/Constant1

    		REQ:SF044A_15REQ: SF044A_15

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/FilLpUpdOutp1

    		REQ:SF044A_22REQ: SF044A_22

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/HOW State Look up Table

    		REQ:SF044A_13REQ: SF044A_13

    		Update
    REQ:SF044A_16REQ: SF044A_16

    		Update
    REQ:SF044A_17REQ: SF044A_17

    		Update
    REQ:SF044A_18REQ: SF044A_18

    		Update
    REQ:SF044A_19REQ: SF044A_19

    		Update
    REQ:SF044A_22REQ: SF044A_22

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/If

    		REQ:SF044A_15REQ: SF044A_15

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/Relational Operator

    		REQ:SF044A_15REQ: SF044A_15

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/Zero

    		REQ:SF044A_14REQ: SF044A_14

    		Update
    REQ:SF044A_15REQ: SF044A_15

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Determine HOW State/HowDetnSt

    		REQ:SF044A_12REQ: SF044A_12

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/HwTq

    		REQ:SF044A_80REQ: SF044A_80

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/VehSpd

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Abslt_f32_f1

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Abslt_f32_f32

    		REQ:SF044A_80REQ: SF044A_80

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Constant

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Constant1

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Data Store Write1

    		REQ:SF044A_80REQ: SF044A_80

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Data Store Write6

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/FilHpUpdOutp

    		REQ:SF044A_81REQ: SF044A_81

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp

    		REQ:SF044A_80REQ: SF044A_80

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp1

    		REQ:SF044A_80REQ: SF044A_80

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp2

    		REQ:SF044A_80REQ: SF044A_80

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/FilLpUpdOutp3

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/FixdToFloat_f32_u16

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/FloatToFixd_u16_f32

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/LnrIntrpn_u16_u16VariXu16VariY

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Product

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/AbsHiFreqTq

    		REQ:SF044A_82REQ: SF044A_82

    		Update

    SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/AbsLoFreqTq

    		REQ:SF044A_80REQ: SF044A_80

    		Update


        Simulation Accuracy

        Simulation Runtime Accuracy Diagnostics

     Runtime diagnostics for S-functions

    This model contains the following C-MEX S-functions:

    IDS-FunctionBlock
    1C:\Users\xzb1db\Desktop\Sneha_Work\04. FDD_Tools\Nexteer_Utilities v4.7.0\EA4_Library\Math\Abslt_f32_f32.mexw64SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Abslt_f32_f1
      SF044A_HowDetn/HowDetn/HowDetnPer1/Filter HwTq/Abslt_f32_f32

    Consider setting Solver data inconsistency [?] to either error or warning (currently set to none) to validate whether S-functions adhere to the ODE solver consistency rules that Simulink applies to its built-in blocks.

    Consider setting ArrayBounds exceeded [?]to either error or warning (currently set to none) to check if S-functions are writing outside array boundaries.

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

     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