|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 2.0 | 26-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.
Stabilty Compensator |
| 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.
SF29_002.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Vince Thomas |
| Change Request ID: |
|
|
| SCR 10980 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| X | MDD |
|
|
| X | Source Code |
|
|
|
| X | Data Dictionary |
|
|
| X | 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 2.0 | 26-Aug-13 |
Peer Review Meeting Log (Source Code Review) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Source File Name: |
|
|
|
|
| kzshz2:
Intended Use: Identify which .asm, .c, or .h file is being reviewed
Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form.
Ap_StabilityComp.c |
| Source File Revision: |
|
|
| kzshz2:
Intended Use: Identify which version of the source file is being review.
Rationale: Required for traceability between source code and review. Auditors will likely require this.
16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Module Design Document Name: |
|
|
|
|
| kzshz2:
Intended Use: Identify which version of the MDD this source file was written against.
Rationale: Needed for traceability between source code and MDD
StabilityCompensation_MDD.docx |
| MDD Revision: |
|
|
| kzshz2:
Intended Use: Identify which version of the MDD this source file was written against.
Rationale: Needed for traceability between source code and MDD
13 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Data Dictionary Revision: |
|
|
|
| kzshz2:
Intended Use: Identify which version of the Data Dictionary was referenced for ranges during the source file review.
Rationale: Needed for traceability between source code and DD
17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
| Rationale is required for all answers of No |
|
|
|
|
|
|
|
|
|
|
Pre-review checklist (change owners only) | Analysis performed for divide by zero |
|
|
|
|
| kzshz2:
Intended Use: To confirm this defensive coding strategy has been taken into consideration
Rationale: Necessary since currently there is no place this is documented
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Software Design and Coding Standard followed |
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Software Naming Convention followed |
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All buffered outputs are written in every path |
|
|
|
|
|
|
|
|
| | |
| Comments: |
|
| N/A |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Group-review Checklist (review board) | Telelogic Synergy version matches header |
|
|
|
|
|
| kzshz2:
Intended Use: Indicate that the the versioning was confirmed by the peer reviewer(s).
Rationale: There have been many occassions where versions were not updated in files and as a result Unit Test were referencing wrong versions. This often time leads to the need to re-run of batch tests.
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change log contains detailed description of changes |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Code compared vs requirements (Document or Model) |
|
|
|
|
|
|
|
| kzshz2:
Intended Use: Identify if previous version was compared and only the expected change(s) was present.
Rationale: This is helpful in identifying unapproved (intended or mistaken) changes.
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Global Outputs (RTE/Non-RTE) Initialized |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Global Outputs are limited to the legal range defined |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| in the FDD Data dictionary |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
No Compiler Errors verified |
|
|
| kzshz2:
Intended Use: To confirm the appropriate variable name formats have been used.
Rationale: This is needed to ensure there will be no errors discovered at the time of integration. A Sandox project may be required to confirm there are no errors until the QAC tool has been evaultated to determine if it can automate this check.
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type Casting and Fix Point Macros use reviewed |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Function prototype and passed parameters are |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| consistent |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Vince Thomas |
| Review Date : |
|
| 12/06/13 |
| Group Review Level: |
|
|
| DR4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 2.0 | 26-Aug-13 |
Peer Review Meeting Log (Source Code Review) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Source File Name: |
|
|
|
|
| kzshz2:
Intended Use: Identify which .asm, .c, or .h file is being reviewed
Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form.
Ap_StabilityComp2.c |
| Source File Revision: |
|
|
| kzshz2:
Intended Use: Identify which version of the source file is being review.
Rationale: Required for traceability between source code and review. Auditors will likely require this.
6 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Module Design Document Name: |
|
|
|
|
| kzshz2:
Intended Use: Identify which version of the MDD this source file was written against.
Rationale: Needed for traceability between source code and MDD
StabilityCompensation2_MDD.docx |
| MDD Revision: |
|
|
| kzshz2:
Intended Use: Identify which version of the MDD this source file was written against.
Rationale: Needed for traceability between source code and MDD
6 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Data Dictionary Revision: |
|
|
|
| kzshz2:
Intended Use: Identify which version of the Data Dictionary was referenced for ranges during the source file review.
Rationale: Needed for traceability between source code and DD
17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
| Rationale is required for all answers of No |
|
|
|
|
|
|
|
|
|
|
Pre-review checklist (change owners only) | Analysis performed for divide by zero |
|
|
|
|
| kzshz2:
Intended Use: To confirm this defensive coding strategy has been taken into consideration
Rationale: Necessary since currently there is no place this is documented
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Software Design and Coding Standard followed |
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Software Naming Convention followed |
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All buffered outputs are written in every path |
|
|
|
|
|
|
|
|
| | |
| Comments: |
|
| N/A |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Group-review Checklist (review board) | Telelogic Synergy version matches header |
|
|
|
|
|
| kzshz2:
Intended Use: Indicate that the the versioning was confirmed by the peer reviewer(s).
Rationale: There have been many occassions where versions were not updated in files and as a result Unit Test were referencing wrong versions. This often time leads to the need to re-run of batch tests.
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change log contains detailed description of changes |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Code compared vs requirements (Document or Model) |
|
|
|
|
|
|
|
| kzshz2:
Intended Use: Identify if previous version was compared and only the expected change(s) was present.
Rationale: This is helpful in identifying unapproved (intended or mistaken) changes.
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Global Outputs (RTE/Non-RTE) Initialized |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Global Outputs are limited to the legal range defined |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| in the FDD Data dictionary |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
No Compiler Errors verified |
|
|
| kzshz2:
Intended Use: To confirm the appropriate variable name formats have been used.
Rationale: This is needed to ensure there will be no errors discovered at the time of integration. A Sandox project may be required to confirm there are no errors until the QAC tool has been evaultated to determine if it can automate this check.
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type Casting and Fix Point Macros use reviewed |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Function prototype and passed parameters are |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| consistent |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Vince Thomas |
| Review Date : |
|
| 12/06/13 |
| Group Review Level: |
|
|
| DR4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 2.0 | 26-Aug-13 |
Peer Review Meeting Log (MDD Review) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Module Name: |
|
| kzshz2:
Intended Use: Identify which file is has been reviewed
Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form.
StabilityComp |
|
|
| Module | kzshz2:
Intended Use: Identify how many source files are being reviewed and trace it to the appropriate MDD.
Rationale: Required for traceability between source code and MDD
| 1 | of | 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| MDD Revision: |
|
| kzshz2:
Intended Use: Identify which version of the MDD has been reviewed.
Rationale: Required for traceability between the MDD and review. Auditors will likely require this.
13 |
|
|
| Source File Revision: |
|
|
| kzshz2:
Intended Use: Identify which version of the source file was this MDD written for.
Rationale: Needed for traceability between source code and MDD
16 |
|
| Data Dictionary Revision: |
|
|
|
| kzshz2:
Intended Use: Identify which version of the Data Dictionary was referenced for ranges during the review.
Rationale: Needed for traceability between source code and DD.
Note: Maybe this should be moved to the Summary sheet since there is only one Data Dictionary Version for all changes
17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
| 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: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Changes Highlighted (for Unit Tester) |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
High-level Diagrams have been reviewed (Section 2) |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All Design Exceptions and Limitations are listed |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Design Rationale understood captured appropriately |
|
|
|
|
|
|
|
|
| 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: |
|
| Vince Thomas |
| Review Date : |
|
| 12/06/13 |
| Group Review Level: |
|
|
| DR4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 2.0 | 26-Aug-13 |
Peer Review Meeting Log (MDD Review) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Module Name: |
|
| kzshz2:
Intended Use: Identify which file is has been reviewed
Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form.
StabilityComp |
|
|
| Module | kzshz2:
Intended Use: Identify how many source files are being reviewed and trace it to the appropriate MDD.
Rationale: Required for traceability between source code and MDD
| 2 | of | 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| MDD Revision: |
|
| kzshz2:
Intended Use: Identify which version of the MDD has been reviewed.
Rationale: Required for traceability between the MDD and review. Auditors will likely require this.
6 |
|
|
| Source File Revision: |
|
|
| kzshz2:
Intended Use: Identify which version of the source file was this MDD written for.
Rationale: Needed for traceability between source code and MDD
6 |
|
| Data Dictionary Revision: |
|
|
|
| kzshz2:
Intended Use: Identify which version of the Data Dictionary was referenced for ranges during the review.
Rationale: Needed for traceability between source code and DD.
Note: Maybe this should be moved to the Summary sheet since there is only one Data Dictionary Version for all changes
17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
| 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: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Changes Highlighted (for Unit Tester) |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
High-level Diagrams have been reviewed (Section 2) |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All Design Exceptions and Limitations are listed |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Design Rationale understood captured appropriately |
|
|
|
|
|
|
|
|
| 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: |
|
| Vince Thomas |
| Review Date : |
|
| 12/06/13 |
| Group Review Level: |
|
|
| DR4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 2.0 | 26-Aug-13 |
Peer Review Meeting Log (QAC Review) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Module Name: |
|
| kzshz2:
Intended Use: Identify which .c file is being analyzed
Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form.
Ap_StabilityComp.c |
|
| Source File Revision: |
|
|
| 13 |
|
| Module |
| 1 | of | 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Compliance Document Version: |
|
|
|
|
| Unreleased |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| kzshz2:
Intended Use: Identify specific changes in results (new violation present, previous violation corrected, etc.). Changes to the version of the tool or the way the results were gathered should be described here also. This should be filled out prior to the review by the change owner.
Rationale: Gives reviewers an what needs to be focused on. Forces the change owner to compare with previous results to catch any differences that may otherwise go unoticed
Brief Summary of Changes (In Results or Tool): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
| Rationale is required for all answers of No |
|
|
|
|
|
|
|
|
|
|
Pre-review checklist for change owners | QAC version is correct and did not change (List version) |
|
|
|
|
|
|
|
| kzshz2:
Intended Use: Identify which version of the QAC Subproject was used and if any of the personalities may have changed.
Rationale: Will help ensure this is factored into evaluating the results
| X | |
| Comments: |
|
| ver 8.1.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Contract Folder's header files are appropriate |
|
|
|
|
|
| kzshz2:
Intended Use: Identify that the contract folder contains only the information required for this component. All other variables, constants, function prototypes, etc. should be removed.
Rationale: This will help avoid unit testers having to considers object not used. It will also avoid having other files required for QAC.
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
G Group-review Checklist (review board) | 100% Compliance to the MISRA Compliance Document | 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: |
|
| Vince Thomas |
| Review Date : |
|
| 12/06/13 |
| Group Review Level: |
|
|
| DR4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 2.0 | 26-Aug-13 |
Peer Review Meeting Log (QAC Review) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Module Name: |
|
| kzshz2:
Intended Use: Identify which .c file is being analyzed
Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form.
Ap_StabilityComp2.c |
|
| Source File Revision: |
|
|
| 6 |
|
| Module |
| 1 | of | 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Compliance Document Version: |
|
|
|
|
| Unreleased |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| kzshz2:
Intended Use: Identify specific changes in results (new violation present, previous violation corrected, etc.). Changes to the version of the tool or the way the results were gathered should be described here also. This should be filled out prior to the review by the change owner.
Rationale: Gives reviewers an what needs to be focused on. Forces the change owner to compare with previous results to catch any differences that may otherwise go unoticed
Brief Summary of Changes (In Results or Tool): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
| Rationale is required for all answers of No |
|
|
|
|
|
|
|
|
|
|
Pre-review checklist for change owners | QAC version is correct and did not change (List version) |
|
|
|
|
|
|
|
| kzshz2:
Intended Use: Identify which version of the QAC Subproject was used and if any of the personalities may have changed.
Rationale: Will help ensure this is factored into evaluating the results
| X | |
| Comments: |
|
| ver 8.1.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Contract Folder's header files are appropriate |
|
|
|
|
|
| kzshz2:
Intended Use: Identify that the contract folder contains only the information required for this component. All other variables, constants, function prototypes, etc. should be removed.
Rationale: This will help avoid unit testers having to considers object not used. It will also avoid having other files required for QAC.
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
G Group-review Checklist (review board) | 100% Compliance to the MISRA Compliance Document | 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: |
|
| Vince Thomas |
| Review Date : |
|
| 12/06/13 |
| Group Review Level: |
|
|
| DR4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.1 | 13-Jun-13 |
Peer Review Meeting Log (Unit Test Review) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Review Date : |
|
|
|
| DR Level: |
|
|
|
| Author : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| (DR1, 2, 3, 4) |
|
|
|
|
|
|
|
|
|
|
Module Under Test (Name) : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MDD Revision Level: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source File Revision Level: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unit Test Plan Revision: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Data Dictionary Revision: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Brief Summary of Design Changes: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Invited (check if in attendance) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Lead Peer Reviewer: |
|
|
|
|
|
| Approved By: |
|
|
|
| Date: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Vectors Reviewed (All or list specific periodics and local functions): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unit Test Plan Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
| Rationale is required for all answers of No |
|
|
|
|
|
|
|
|
|
|
|
Test documentation complete and verified correct |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All test vectors have passing results |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
kzshz2:
FDD only gives tolerances for calibrations, not variables
All tolerances are within the limits listed in the DD |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
100 % path coverage |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Calibration and variable ranges match the DD |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Min/Max boundary tested for each input variable |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
and calibration |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Min/Max boundary tested for each output variable |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Valid outputs (generally non-zero, some negative |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
results for signed values, values vary sufficiently) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Calibration tables used in interpolation have unique |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
values for each index when not testing boundary |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Inputs/calibrations that are used as a "defeat" of the |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
output or a portion of code is generally disabled |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
No special code was added to test (i.e. Overflow |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
handling) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Specific Unit Test Guidelines stated within the MDD |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
are followed |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Compiler settings match expected configuration |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
(Compiler version, makefile template, and Float Point) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Call Trace results match VBA's expected stub count |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
EPS Library/Unit Test Tool version is correct (List) |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Floating Point Attribute meets standard and did not |
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
change from previous test (List) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|