TmplMon Design Review

Overview

Summary Sheet
Data Dictionary
Integration Manual

Sheet 1: Summary Sheet
























Rev 2.026-Aug-13

Peer Review Summary Sheet



























Component Name:


kzshz2: Intended Use: Identify which component is being reviewed. This should be the Module Short Name from Synergy Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. CBD_TmprlMon
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 9.4





























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Rijvi Ahmed
Change Request ID:


11297





























kzshz2: Intended Use: Intended to identify at a high level to the reviewers which areas of the component have been changed. Rationale: This will be good information to know when ensuring appropriate reviews have been completed. Modified File Types:
















































































































































kzshz2: Intended Use: Identify who where the reviewers, what they reviewed, and if the reviewed changes have been approved to release the code for testing. Comments here should be at a highlevel, the specific comments should be present on the specific review form sheet. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. ADD DR Level Move reviewer and approval to individual checklist form Review Checklist Summary:






















































Reviewed:































MDD


Source Code



XData Dictionary


QAC



































Integration Manual


Davinci Files








































































Comments:






























































































General Guidelines:
- The reviews should be performed over the portions of the component that were modified as a result of the Change Request. (Note: If this peer review form was not
completed for pervious versions of this component, the Change Owner should review the entire component and complete the checklist in its entirety prior and check
the form into Syngery. This should be done prior to reviewing the modifications for this Change Result)
- The Change Owner is responsible for completing the entire checklist (Pre and Group review items) prior holding the initial group review.
- New components should include FDD Owner and Intergator as apart of the Group Review Board (Source Code, Integration Manual, and Davinci Files)
- Select "Yes" and add "N/A" to the comments for checklist items that are not applicable for this change














Sheet 2: Data Dictionary






















Rev 2.026-Aug-13
Peer Review Meeting Log (Data Dictionary Review)


























Data Dictionary Revision:



kzshz2: Intended Use: Identify which version of the file is being reviewed Rationale: Required for traceability. 8









































kzshz2: Intended Use: Indicate to the reviewers the type of variable changes. This should be filled out prior to the review by the change owner. Rationale: This will be good information to know to both reviewers and post reviewers of the change. Variables:



























Newly Added


Name Changes


Range Changes


Deleted
































NVM Changes


Other:


































































kzshz2: Intended Use: Indicate to the reviewers the type of calibration changes. This should be filled out prior to the review by the change owner. Rationale: This will be good information to know to both reviewers and post reviewers of the change. Calibrations:



























Newly Added


Name Changes


Range Changes


Default Value Changes
































Deleted


XOther:



Tuning sets are changed from P to N





























































Quality Check Items:

































YesNo
Rationale is required for all answers of No









Group-review Checklist (review board)Telelogic Synergy version matches header








X
Comments:










































Change log contains detailed description of changes








X
Comments:










































All Changes Identified (for Unit Tester)








X
Comments:










































Calibration and NVM names, ranges, and default values








X
Comments:

Only for changes

compared against FDD




































Global variables names, ranges, and default values








X
Comments:

Only for changes

compared against FDD Data Dictionary






























































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Rijvi Ahmed
Review Date :

3-Feb-14
Group Review Level:


DR4



























Lead Peer Reviewer:


Selva Sengottaiyan

Approved by Reviewer(s):



Yes































Other Reviewer(s):









































































Sheet 3: Integration Manual






















Rev 2.026-Aug-13
Peer Review Meeting Log (Integration Manual Review)


























Integration Manual Name:



kzshz2: Intended Use: Identify which file is being reviewed Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form. Temporal Monitor_Integration_Manual

Integration Manual Revision:



kzshz2: Intended Use: Identify which version of the integration manual has been reviewed. Rationale: Required for traceability between the MDD and review. Auditors will likely require this. 1























Quality Check Items:

































YesNo
Rationale is required for all answers of No









Group-review Checklist (review board)Telelogic Synergy version matches header








X
Comments:










































Latest template used








X
Comments:










































Change log contains detailed description of changes








X
Comments:










































Changes Highlighted (for Integrator)








X
Comments:











































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Rijvi Ahmed
Review Date :

3-Feb-14
Group Review Level:


DR4



























Lead Peer Reviewer:


Selva Sengottaiyan

Approved by Reviewer(s):



Yes































Other Reviewer(s):









































































Last modified October 12, 2025: Initial commit (0347a62)