Technical Review Checklist - Template Version 02.00.00 |
|
|
|
|
|
|
|
|
Product Name | Electric Power Steering | Electrical Arch. | 4 | Review Scope | Defect Type | Numbers |
|
|
|
|
| Yes | Closed | FR |
Function ID | SF045A_HwAgSysArbn |
|
| Generic design is now simplfied considering only Pinion coordinates to arbitrate the HwAg signals instead of flexibility to choose between Handwheel, Pinion and MotorAg coordinates. This resulted in removing the cals used to apply compilance error compensation and priority selection. - Kinematic Integrity diagonstic added - HwAg to MotAg Correlation diagonstic added - Logic added to arbitrate HwAg signal going to EOT when HwAg sensor signals not available. | Requirement | 0 |
|
|
|
|
| No | Rejected | FDD |
Long Name | Loa Manager |
|
| Interface | 0 |
|
|
|
|
| NA | Open | Model |
Version that you started from.
NOT the version you hope to release.
If this will be v1.0.0, enter NA.
Starting Baseline | 1.1.0 | Effort | Design | 8 |
|
|
|
|
|
|
| FMEA |
Author | Sudeep Shankar | Review Effort(Hrs.) |
| Standards | 2 |
|
|
|
|
|
|
| *.m File |
|
| Corr+Verf effort(Hrs.) |
| Documentation | 4 |
|
|
|
|
|
|
| Cal Process |
|
| Total Effort (Hrs.) | 0.00 | Others | 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Total | 15 |
|
|
|
|
|
|
|
|
Checklist No. | Description of Check | Author:
This column is for Self review. Author shall fill Yes/No/NA against each point in checklist.
Author | Author:
This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist.
Reviewer | Author:
Detailed Description of the finding shall be provided by the reviewer.
Description of finding by reviewer | Author:
Defect type to be selected.
Defect Type | Author:
What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author | Author:
Data in this column shall be filled by reviewer after checking whether the rework is completed. Status |
|
|
|
|
|
|
|
|
1 | Section 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 |
| Special cases are shown as error | Others | Tools issue | 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? | NA |
| No Server runnables |
|
|
|
|
|
|
|
|
|
|
|
| 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)? | NA |
| No cal tables |
|
|
|
|
|
|
|
|
|
|
|
| Do all calibrations have correct values for all metadata? | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Are calibration tables named correctly (e.g. AssiX and AssiY)? | NA |
| No cal tables |
|
|
|
|
|
|
|
|
|
|
|
| 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2 | Section 2: Model | Author:
This column is for Self review. Author shall fill Yes/No/NA against each point in checklist.
Author | Author:
This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist.
Reviewer | Author:
Detailed Description of the finding shall be provided by the reviewer.
Description of finding by reviewer | Author:
Defect type to be selected.
Defect Type | Author:
What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author | Author:
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"? | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3 | Section 3: Requirements Linking | Author:
This column is for Self review. Author shall fill Yes/No/NA against each point in checklist.
Author | Author:
This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist.
Reviewer | Author:
Detailed Description of the finding shall be provided by the reviewer.
Description of finding by reviewer | Author:
Defect type to be selected.
Defect Type | Author:
What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author | Author:
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>? | NA |
|
|
| No baseline requirements |
|
|
|
|
|
|
|
|
|
| Does requirements HTML report reference only the DOORS module of this component for all links in the design? | NA |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Are linked blocks linked to the correct requirements(s)? (watch for problems due to copy/pasted blocks) | NA |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Is the list of unlinked blocks acceptable? | NA |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4 | Section 4: Model Advisor | Author:
This column is for Self review. Author shall fill Yes/No/NA against each point in checklist.
Author | Author:
This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist.
Reviewer | Author:
Detailed Description of the finding shall be provided by the reviewer.
Description of finding by reviewer | Author:
Defect type to be selected.
Defect Type | Author:
What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author | Author:
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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5 | Section 5: Delivery Package | Author:
This column is for Self review. Author shall fill Yes/No/NA against each point in checklist.
Author | Author:
This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist.
Reviewer | Author:
Detailed Description of the finding shall be provided by the reviewer.
Description of finding by reviewer | Author:
Defect type to be selected.
Defect Type | Author:
What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author | Author:
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? | No |
|
|
| No requirement traceability report |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6 | Section 6: Other Issus/Actions Identified | Document | Reference | Summary of resolution | Author:
Defect type to be selected.
Defect Type | Author:
What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author | Author:
Data in this column shall be filled by reviewer after checking whether the rework is completed. Status |
|
|
|
|
|
|
|
|
6.1 | Change the order of inputs fed to Periodic | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1 | Changed the input order | Documentation | Implemented | Closed |
|
|
|
|
|
|
|
|
6.2 | HwAgSnsrls can be removed from If and Else block as in both blocks it is just a pass through | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/VldtSnsrlsData | Updated as per comment | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.3 | Change the name of the HwAgSysArbnHwAgSnsrlsThd to a meaningful name representing Kinematic in the name. | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/VldtSnsrlsData | Name changed | Documentation | Implemented | Closed |
|
|
|
|
|
|
|
|
6.4 | Latch the confidence to 0 when Kinematic integrity fault is set to TRUE. | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/VldtSnsrlsData | Fault latched | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.5 | Change the design to compare sensor and sensorless confidence signals against correlation confidence thershold cals to determine whether to perform correlation check. And also simplify the design to select between sensor and sensorless signal | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln | Design in simplified | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.6 | Simplify the correlation logic. Substract one signal from another and take the absolute value of it. | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/VrfyHwAgCorrln | Updated as per comment | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.7 | Store the flag to a PIM to indicate whether correlation is true or not | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/VrfyHwAgCorrln/SetNtcPass | PIM updated | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.8 | Set the NTC to "Prepass" instead of "Pass" when Correlation is true with debounce step | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/VrfyHwAgCorrln/SetNtcPass | NTC state updated | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.9 | NtcNr1.NTCNR_0X0A6 NTC definition in data dictionary must indicate that the NTC uses debounce step | *.m File |
| Changed in DD | Standards | Implemented | Closed |
|
|
|
|
|
|
|
|
6.10 | Change the block name "DftCal" to a meaningful name | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/TestHwAgSrcChg | change the name to be more meaningful | Documentation | Implemented | Closed |
|
|
|
|
|
|
|
|
6.11 | Move Reference timer and calibrations inside block. ( If, else and other) block | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/TestHwAgSrcChg | Moved the calibrations inside the blocks | Standards | Implemented | Closed |
|
|
|
|
|
|
|
|
6.12 | Port name "Tmr" to the "ApplyRateLim" block to be updated to more meaningful name so that design is readable. | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/TestHwAgSrcChg | change the name to be more meaningful | Documentation | Implemented | Closed |
|
|
|
|
|
|
|
|
6.13 | Add Correlation Status flag to else and elseif logic | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln | Added correlation flag after simplifying the design | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.14 | Add a cal to to restrict the duration of sensorless HwAg signal to be transmitted on Serial Com sincel last correlated also set the calibration to duration equivalent to one day | Model | SF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/SnsrlsDataToSerlCom | updated design to add timer logic | Design | Implemented | Closed |
|
|
|
|
|
|
|
|
6.15 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.18 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.19 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.20 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.21 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.22 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.23 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.24 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6.25 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7 | Section 7: APPROVALS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Role | First Review | Date | Attendance | Approval? |
|
|
|
|
|
|
|
|
|
|
|
Function Owner* | Sudeep Shankar | 6/13/2016 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
Peer Reviewer* | Kevin Derry | Yes | No |
|
|
|
|
|
|
|
|
|
|
|
Safety | Carl Tarum | No |
|
|
|
|
|
|
|
|
|
|
|
|
Software | Spandana Balani | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
ESG / Systems | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
EPDT / CSE | Matthew Tompkins | Yes | No |
|
|
|
|
|
|
|
|
|
|
|
Hardware | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
Test | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
Role | Second Review (if required) | Date | Attendance | Approval? |
|
|
|
|
|
|
|
|
|
|
|
Function Owner* | <Name - if invited> | 6/15/2016 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Peer Reviewer* | Kevin Derry | Yes | Yes |
|
|
|
|
|
|
|
|
|
|
|
Safety | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
Software | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
ESG / Systems | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
EPDT / CSE | Matthew Tompkins | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
Hardware | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
Test | <Name - if invited> |
|
|
|
|
|
|
|
|
|
|
|
|
|
Role | Third Review (if required) | Date | Attendance | Approval? |
|
|
|
|
|
|
|
|
|
|
|
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> |
|
|
|
|
|
|
|
|
|
|
|
|
|
Role | Fourth Review (if required) | Date | Attendance | Approval? |
|
|
|
|
|
|
|
|
|
|
|
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> |
|
|
|
|
|
|
|
|
|
|
|
|
|
Role | Add more if necessary | Date | Attendance | Approval? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|