Peer Review Checklist - Design

Peer Review Meeting Log (Design Review)

FDD Module Name:

Siva: Intended Use: Mention the FDD module being reviewed. SF004B_AssiSumLim

Exisiting Synergy Baselined Version Number

Siva: Intended Use: Mention the version of FDD module which was already baselined in Synergy database. 1.1.0

(Before changes were made to FDD)

Quality Check Items:

Yes

Rationale is required for all answers of No

General

Are the right version of tools being used for the development process?

Comments:

Is the correct verison of FDD being checked out from Synergy reporsitory?

Comments:

Data Dictionary

Is Filename of Data Dictionary in correct format?

Comments:

Are all the Signals & Parameters present in the FDD covered in the Data Dictionary?

Comments:

Do all the Signals & Parameters have the right Data Dictionary Objects?

Comments:

Do all the Signals and Parameters have the correct meta information?

Comments:

Does the Data Dictionary has all the necessary NTC and Dependancy information?

Comments:

Is the FDD model simulating (updating) without any warnings or errors with the updated Data Dictionary?

Comments:

Is the Data Dictionary Verification report error free?

Comments:

Model Variables associated with Manual Torque Command as well as parameters for its Server Runnable give errors of parts missing. Input signals does not match name to list of known Nexteer signals.

Design

Does the FDD model file name follow the naming conventions ex: <FDD No>_<FDD Short Name>.slx?

Comments:

Is Top level of model annotated with Requirements Baseline?

Comments:

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

Comments:

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

Comments:

Is Top level of model annotated with File Dependencies like Common Calibration information m-file?

Comments:

Does the model being developed follow all the architectural design requirements mentioned in section 6.1.1 of the FDD Standards?

Comments:

Does the Structure level of model only contain Function-Call Subsystems and Data Store Memory Blocks?

Comments:

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

Comments:

Does the Component shortname match between model, data dict, & requirements?

Comments:

Is the FDD description updated according to the latest version of FDD?

Comments:

Are all the library blocks linked to the correct versions of Nexteer Utilities blocks?

Comments:

Are there any Function call subystems inside the model's Data Flow Layer?

Comments:

No function call subsystems inside model data flow layer

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

Comments:

Is the PDF version of FDD model placed in the Doc folder of delivery package?

Comments:

Is the HTML version of FDD model placed in the Doc folder of Delivery package?

Comments:

Delivery

Is the Delivery folder structure correct (e.x. Reports, Design, Doc folders)?

Comments:

Does the Delivery folder have all the necessary artifacts?

Comments:

Is the component Data Dictionary included in the Design folder?

Comments:

Is the Traceability report present in the Reports folder?

Comments:

Does this FDD have one or more NTC's? If so is the NTC One pager included in the Doc folder?

Comments:

NTC one pager is not included in the Doc folder

General Notes / Comments:

Siva: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved or declined. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Review Board:

Change Owner:

Chris Wheatley

Review Date :

07/15/15

Lead Peer Reviewer:

Sudeep Shankar

Approved by Reviewer(s):

Sudeep Shankar

Other Reviewer(s):

Last modified October 12, 2025: Initial commit (1fadfc4)