1 - SF003A_Dampg

document1

3 - SF003A_Dampg_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 IDSF03A_Dampg

Initial Baseline in EA4Requirement0




NoRejectedFDD
Long NameDamping

Interface4




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






FMEA
AuthorSudeep ShankarReview Effort(Hrs.)2.00Standards2






*.m File


Corr+Verf effort(Hrs.)3.00Documentation10






Cal Process


Total Effort (Hrs.)5.00Others0













Total16







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
Error due to update needed in VerifyDD tool

Closed








Does FDD Long Name, Short Name, and Description match requirements?NA
No Baseline requirements available

Closed








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)?NA
No Baseline requirements available

Closed








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?NA
No Baseline requirements available

Closed








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











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











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>?NA
No baseline requirements available

Closed








Does requirements HTML report reference only the DOORS module of this component for all links in the design?NA
No baseline requirements available

Closed








Are linked blocks linked to the correct requirements(s)? (watch for problems due to copy/pasted blocks)NA
No baseline requirements available

Closed








Is the list of unlinked blocks acceptable?NA
No baseline requirements available

Closed























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?No
Requirement traceability report does not exists as requirement linking is not created due to non availability of baseline requirements

Closed























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.1Update the change log with the information "Initial release based on EA3 version #'ModelChange logUpdated the change log to refer EA3 versionDocumentationupdated as per findingClosed







6.2Instead of QuadDampgCmd use QuadDampgScaModelEnhd_Quad_Dampg blockChanged QuadDampgCmd to QuadDampgSca. Updated the Memory block and signal names as wellDocumentationupdated as per findingClosed







6.3Provide annotation about using Global Vehicle Speed Bilinear selection table used in linear intrepolationModelHydPwrSteerDampgCmdAdded annotation regarding use of Global Vehicle speed Bilinear Selection in linear interpolationDocumentationupdated as per findingClosed







6.4Suggestion : DampgFilMotVelCrfLpFrq can be changed to DampgMotVelLpFilFrq. Similar to other Filter calibration as well.*.m FileSF003A_Dampg_DataDictChanged in DD and modelDocumentationupdated as per findingClosed







6.5Gain block '-1' to be changed to unary minusModelHydPwrSteerDampgCmd\AssiLimScaleChanged Gain block ' -1' with Unary minusStandardsupdated as per findingClosed







6.6Instead of 'Dampg Force' use 'Dampg Command'ModelHydPwrSteerDampgCmdOutput port name is renamed as 'HydDampg'Documentationupdated as per findingClosed







6.7In the Long name of Calibration, remove 'Damping'*.m FileSF003A_Dampg_DataDictRemoved 'Damping' from long name of CalibrationsDocumentationupdated as per findingClosed







6.8MotVelCrf can be changed to 'MotVel' wherever applicable*.m FileSF003A_Dampg_DataDictChanged from MotVelCrf to MotVel wherever applicableDocumentationupdated as per findingClosed







6.9Following changes are to be done on the calibration attributes
1. DampgHwTqX: Cardinality = 'R', CustomerVisible = 'True' , Online = 'True'
2. DampgHwTqY: Cardinality = 'R', CustomerVisible = 'True' , Online = 'True'
3. DampgHydAssiLim : Cardinality = 'I', CustomerVisible = 'false' , Online = 'True'
4. DampgHydCoeff1ScaY : Cardinality ='R', CustomerVisible = 'true', Online = 'true'
5. DampgHydCoeff2ScaY : Cardinality ='R', CustomerVisible = 'true', Online = 'true'
6. DampgHydCoeff3ScaY : Cardinality ='R', CustomerVisible = 'true', Online = 'true'
7. DampgHydCoeff4ScaY : Cardinality ='R', CustomerVisible = 'true', Online = 'true'
8. DampgMotVelCrfX : Cardinality ='R', CustomerVisible = 'true', Online = 'true'
9. DampgMotVelCrfY : Cardinality ='R', CustomerVisible = 'true', Online = 'true'
10. DampgQuadHwTqBacklsh: Cardinality = 'N'
11. DampgQuadMotVelCrfBacklsh : Cardinality = 'N'
12. DampgTScaX = Cardinality ='I', CustomerVisible = 'true', Online = 'true'
13. DampgTScaY = Cardinality ='I', CustomerVisible = 'true', Online = 'true'
*.m FileSF003A_Dampg_DataDictChanged the attributes of the calibrations as given in the commentInterfaceupdated as per findingClosed







6.10DampgHydCoeff1ScaY EngVal to be changed to 1*.m FileSF003A_Dampg_DataDictUpdated the Coefficient values of DampgHydCoeff1ScaY to 1Interfaceupdated as per findingClosed







6.11Change 'DampgHydOutLim' to DampgHydOutpLim*.m FileSF003A_Dampg_DataDictupdated to 'DampgHydOutpLim' both in model and DDDocumentationupdated as per findingClosed







6.12Simplify the DampgMotVelX and DampgMotVelY table values.*.m FileSF003A_Dampg_DataDictSimplied the table values to nearest 3 digit precisionStandardsupdated as per findingClosed







6.13Add annotation to backlash logic in the model*.m FileSF003A_Dampg_DataDictAdded annotation of the backlash logicDocumentationupdated as per findingClosed







6.14dDampgQuadHwTqBacklsh.Description = to be updated to say that the lashed output is captured in the display variable.*.m FileSF003A_Dampg_DataDictDescription updatedDocumentationupdated as per findingClosed







6.15For the filter logic, instead of removing the datastore check box, change the initialization in the model.*.m FileSF003A_Dampg_DataDictUpdated in the modelInterfaceupdated as per findingClosed







6.16Following PIM are to be verified for the Min, max and units
1. MotVelCrfLpFil : Doc units to be ' '
2. PrevHwTqBacklshOutp : Min , Max values to be corrected
3. PrevHydOutLim : Min, Max values to be corrected
4. PrevMotVelCrfBacklshOutp : Min, Max values to be corrected
5. QuadDampgCmdLpFil : Doc units to be ' '
6. QuadDampgHwTqLpFil : Doc Units to be ' '
7. QuadDampgMotVelCrfLpFil : Doc units to be ' '
*.m FileSF003A_Dampg_DataDictUpdated the Doc units , Min and Max values for the display variables given in the commentInterfaceupdated as per findingClosed







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*Klein6/24/2015No











Peer Reviewer*Kevin Derry, Chris Wheatly, Fei YuanYes











SafetyScott WeissNo











Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSEMatthew TompkinsYes











Hardware<Name - if invited>












Test<Name - if invited>












RoleSecond Review (if required)DateAttendanceApproval?










Function Owner*Klein6/26/2015No











Peer Reviewer*Fei YuanYesYes










Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSEMatthew TompkinsYesYes










Hardware<Name - if invited>












Test<Name - if invited>












RoleThird Review (if required)DateAttendanceApproval?










Function Owner*Klein7/7/2015No











Peer Reviewer*Fei YuanYesYes










Safety<Name - if invited>












SoftwareSankardu VaradapureddiYesYes










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

















































































4 - SF003A_Dampgs