|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
 | Component Integration Review Sheet |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| Change Request ID: |
|
|
| Many, see individual tabs |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Integration Steps |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| # | Name | Version | Approved |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| AR350A | ImcArbn | 1.0.1 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CM200C | DmaCfgAndUse | 1.1.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CM475A | TSG31CfgAndUse | 1.4.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CM620C | MotAg0Meas | 1.2.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CM640C | MotAg1Meas | 1.2.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CM745A | Sci30CfgAndUse | 1.1.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DF003A | McuErrInj | 1.0.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ES011A | DualEcuIdn | 1.0.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ES238B | HwAgArbn | 1.0.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ES239B | HwArCorrln | 1.0.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ES999A | ElecGlbPrm | 6.2.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| MM000B | SerlComInProxy | 1.0.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| MM500B | SerlComOupProxy | 1.1.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SF009A | DutyCycThermProtn | 3.0.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SF011A | EotLrng | 3.0.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SF029A | StabyCmp | 1.2.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SF031A | CurrReasbnDiagc | 1.0.0 | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SF042A | HwAgSnsrls | 1.4.0 | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SF102A | MotCtrlPrmEstimn | 2.0.0 | 0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Comments: |
|
| The calibration section was altered from the approved review checklist to better suit the process used by EA4.
Tab Colors:
Green: Reviewed and passing for this release
Gray: Reviewed and pssing on previous release |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Guidelines: |
|
| - The reviews should be performed over the steps taken to integrate each of the SWC.
- If a section does not apply, select "N/A" in the Yes column and state why it did not apply. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Abbreviations and Acronyms
|
|
| - CIG: Component Integration Guidlines. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| References |
|
|
| Document Title | Version | Applicable Sections |
|
| [1] | Component Integration Guidelines | Version 1.2 | All |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for AR000A Integration Project |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Hari Mattupalli |
| 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.
07.00.02 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8020, EA4#8024 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Integration project is not a component |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Latest RTE files were generated due to calibration changes. |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| Cal component was generated due to calibration changes. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Not a SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| EA4#8020: Integrate latest tool for Tuning Select feature, Re-connected DesRtIdx to Message 232, Fixed EotProtnHwDegDampgX calibration mapping from CalRegion1 to CalRegion0 |
|
| EA4#8024: Fault Injection Integration Configuration updates |
|
| Software Version changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Hari Mattupalli |
| Review Date : |
|
| 10/14/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Jared Julien |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for AR300A MotCtrlMgr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7773 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No additional considerations |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for AR350A ImcArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9584 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/03/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for AR999A ArchGlbPrm |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5161 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update only, no source files changed |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF009A GmOvrlStMgr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
4.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7201 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF010A GmTqArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6509 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF012A GmStrtStop |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6500 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Initial integration was from 1.2.0 to 1.3.0 which changed the names of the outputs |
|
| Update from 1.3.0 to 1.4.0 was a source only change from unit testing issue |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF016A GmVehSpdArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
3.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#2175 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 05/06/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF017A GmVehPwrMod |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
3.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4261 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configurations |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF018A GmRoadWhlInQlfr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7763 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF025A GmFctDiArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6553 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CF010A GmT1xxMcuCfg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
3.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6572 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| This component is implemented directly in the integration project |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| This component is implemented directly in the integration project |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| This component is implemented directly in the integration project |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No client/server ports |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Updates for ADC diagnosics changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM100A StrtUpSeq |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7075 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer component |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer component |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer component |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer component |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer component |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer component |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Adjusted ordering of EcuM init functions in EcuM_Callout_Stubs.c |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM101A ExcpnHndlg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
4.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7356 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| None |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM102A FlsMem |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
5.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7355 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM103A RamMem |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
3.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7205 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Required removal of SPI double bit ecc error interrupt notification |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM104A EcmOutpAndDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
4.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7072 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM106A McuCoreCfgAndDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5361 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Source-only update |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This was a source only update that did not require any changes beyond using the newest version in Synergy |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/18/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM107A GuardCfgAndDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
3.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5156 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Using latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No RTE changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only change - no integration work required other than to update component version |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM108A DataAndAdrPar |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5157 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Only version available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No RTE changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only change - no integration work required other than to update component version |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM111A VrfyCritReg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5512 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for CM200C DmaCfgAndUse |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available / Removed CM200A |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| New ISR interruption |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM300A Adc0CfgAndUse |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7714 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM320A Adc1CfgAndUse |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7715 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM340A AdcDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7215 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM455A Tauj0CfgAndUse |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4876 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| None |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This was a source only update that required no changes to the integration project |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 03/24/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM460A Tauj1CfgAndUse |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4877 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| None |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This was a source only update that required no changes to the integration project |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 03/24/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for CM475A TSG31CfgAndUse |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No developer updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| I hacked the Rte_TSG31CfgAndUse_MemMap.h file in order to declare all necessary macros to enable the ISR. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for CM620C MotAg0Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9362 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No change to NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No change to NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/02/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for CM640C MotAg1Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9362 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/02/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM650A HwTq0Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.7.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5140 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No interface changes - only PIM updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM660A HwTq1Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.6.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5141 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM670A HwAg1Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.8.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6453 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration files changed |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration files changed |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM680A HwTq2Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA46584 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch files |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update from unit testing |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/18/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM690A HwAg0Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.8.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6453 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration files changed |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration files changed |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for CM700A HwTq3Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6585 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch files |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update from unit testing |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/18/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for CM745A Sci30CfgAndUse |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9586 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch files |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update from unit testing |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/03/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for DF001A FltInj |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7707 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for DF003A McuErrInj |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES002A McuDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7886 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| Co changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES004A PwrUpSeq |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6603 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES005A TmplMonr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6460 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration setting changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES006A Nvm |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7935 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Updated NvM MultiBlkCallBack to match new name |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES008A PwrSply |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7739 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for ES011A DualEcuIdn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9585 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Changes to Port and Dio. |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/03/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES100A SysStMod |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5155 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No appicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Only change to source was two name changes on inputs - both were mapped back to the same outputs from CF017A |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES101A DiagcMgr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
4.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| . |
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7888 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No changes to configurations |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS Settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES102A PolarityCfg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.0.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5632 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 05/06/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES104A XcpIf |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.0.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7345 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES105A StHlthSigNorm |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Hari Mattupalli |
| 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.
3.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8027 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No changes to groups |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Hari Mattupalli |
| Review Date : |
|
| 10/14/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Jared Julien |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES106A StHlthSigStc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7884 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable fot T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES200A CurrMeas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
4.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7897 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No changes to NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No changes to NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES208A CurrMeasArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.6.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4889 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS changes |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This was a source only update that required no changes to the integration project |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 03/24/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES209A CurrMeasCorrln |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.5.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7708 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES210A EcuTMeas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5657 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No devloper changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No devloper changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No devloper changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No devloper changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No devloper changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No devloper changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only change |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 05/06/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES229A HwTqCorrln |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Hari Mattupalli |
| 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.
3.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8019 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Hari Mattupalli |
| Review Date : |
|
| 10/14/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Jared Julien |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for ES238B HwAgArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for ES239B HwAgCorrln |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES241A MotAg2Meas |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.5.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7738 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No devloper changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES248A MotAgArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.0.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6586 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS Settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/18/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES249A MotAgCorrln |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
4.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5398, EA4#5429 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| New outputs are provided for SoH updates that are not yet integrated so outputs were intentionally left disconnected |
|
| Discovered an implementation issue while reviewing the integration of version 4.0.0 that was quickly resolved for version 4.1.0 of component |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES250A BattVltg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.0.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7122 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS Settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update only |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES259A BattVltgCorrln |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6513 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS Settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Added new NTC 0x03D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES300A SinVltgGenn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.5.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6587 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/18/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES311A GateDrv0Ctrl |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7747 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch files |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES312A GateDrv1Ctrl |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7748 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch files |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration changes |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES320A MotDrvDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.5.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5469, EA4# |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Outputs were added for state of health which is not integrated yet so they were left disconnected |
|
| A minor issue was observed during integration of 1.4.0 that was repaired and rolled in as 1.5.0. This was a source only change so the review from 1.4.0 |
|
| was retained above. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for ES400A TunSelnMgmt |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7346 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for ES999A ElecGlbPrm |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo Nunes |
| 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.
6.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8878 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/02/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for GM001A ChkPt |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.7.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7926 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No new server runnables |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for GM002A PartNr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.7.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7924 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No additional considerations |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| New Init1 runnable |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No change |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for GM003A CustDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.12.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7774 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Added new non-trusted function calls for enable/disable of DTC update |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No additional considerations |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for MM000B SerlComInpProxy |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9675 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/06/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM001A GmMsg0C5BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4# |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/16/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willy Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM005A GmMsg180BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Only PIM changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM006A GmMsg1E9BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Only PIM changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM007A GmMsg1F1BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5845 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 06/14/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM008A GmMsg1F5BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Only PIM changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM009A GmMsg214BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM017A GmMsg180BusChassisExp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM018A GmMsg182BusChassisExp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM019A GmMsg337BusChassisExp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for MM500B SerlComOutpProxy |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9774 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No RTE changes. |
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No RTE changes. |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No RTE changes. |
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/09/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM501A GmMsg148BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6567 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM502A GmMsg184BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7331 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM503A GmMsg1E5BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.7.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7332 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM504A GmMsg778BusHiSpd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7885 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM505A GmMsg1CABusChassisExp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7333 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM506A GmMsg1E5BusChassisExp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.7.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7335 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for MM507A GmMsg335BusChassisExp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7334 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS configuration |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/01/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for NM001A CmnMfgSrv |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.18.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6654 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration change |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/22/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for NM002A CmnMfgSrvIf |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6578 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvMs |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for NM004A NxtrCalIds |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5278 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/18/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for NM010A ProgMfgSrv |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
0.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5821 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibrations |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 06/14/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for NM100A MotVelCtrl |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6798 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/12/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF001A Assi |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.5.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7199 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF002A Rtn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7750 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF005A StOutpCtrl |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5467 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF007A SysFricLrn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7883 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No additional considerations |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 10/07/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for SF009A DutyCycThermProtn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
3.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8651 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS setttings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| Missing updates to other components to connect all the ports and Price's model is also outdated. |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 02/06/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF011A EotLrng |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
3.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8653 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Co configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF012A HysCmp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5159 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Just a design update - no source changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF013A PullCmpActv |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6554 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF014A InertiaCmpVel |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.10.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8654 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No changes in the component. Only in the design. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/06/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF015A WhlImbRejctn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Hari Mattupalli |
| 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.
1.8.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8025 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| Latest SW component integrated |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No additional considerations |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes in runnables |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes in ports |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source and developer changes. Reviewed 1.7.0 and 1.8.0 integration. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Hari Mattupalli |
| Review Date : |
|
| 10/14/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Jared Julien |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF016A VehSpdLimr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5588 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only change |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 05/06/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF018A EotProtn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Hari Mattupalli |
| 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.
1.7.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8015 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Design only updates |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design only updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Hari Mattupalli |
| Review Date : |
|
| 10/14/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Jared Julien |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF019B PwrLimr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5162 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No client/server ports |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Only initial value changes - nothing needed except to import the latest DCF |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/08/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Lucas Wendling |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF020A HwAgTrakgServo |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.5.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7741 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF021A HwAgTrajGen |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5472 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF023A TunSelnAuthy |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6517 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM change for this update |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF027A EotProtnFwl |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7751 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for SF029A StabyCmp |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8656 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No TunningSets for G2KCA yet. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/02/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for SF031A CurrReasbnDiagc |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| | X |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| The include "MotCtrl_Data.h" was supposed to be "CDD_MotCtrl_Data.h" |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| The include "MotCtrl_Data.h" was supposed to be "CDD_MotCtrl_Data.h" |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
| No |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF032A MotTqCmdSca |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7753 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS Settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF033A VehSigCdng |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7746 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM change for this update |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer updates |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No cal changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No cal changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No cal changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF040A MotVel |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7757 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch files |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| Design-only change |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for SF042A HwAgSnsrls |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8657 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration |
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NVM changes |
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NVM changes |
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| Missing connection for input MotAgCumvAlgndVld. Need update of ES247A MotAGCmp to lastest version. |
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| Changes don't impact StdDef definitions |
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No changes |
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
| 02/06/17 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF043A TqOscn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5470 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF044A HowDetn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7196 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NVM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NVM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF045A HwAgSysArbn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7186 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NVM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NVM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Devloper changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF048A TqLoa |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7752 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF049A LoaMgr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
2.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6505 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM change for this update |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No cal changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No cal changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No cal changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF050A MotTqTranlDampg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5474 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 04/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF051A SnsrOffsLrng |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7198 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable to T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No change to existing block |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM change for this update |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 08/26/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF053A HwAgVehCntrTrim |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.3.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7713 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM changes |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF054A PwrpkCmpbltyChk |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.0.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7754 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available version |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| << |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
|
| SWC Integration Review for SF102A MotCtrlPrmEstimn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
2.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF103A MotRefMdl |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
2.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8453 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| No configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF104A MotCurrRegCfg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6504 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Co configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Design-only update to 1.3.1 |
|
| Source only update from 1.3.1 to 1.4.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF105A MotCurrRegVltgLimr |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.6.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7744 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| X |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Made motor control manager updates to support signal renaming |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 09/28/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Hari Mattupalli |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF106A MotRplCoggCfg |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6575 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Co configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF107A MotRplCoggCmd |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6578 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Co configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
| No Developer changes |
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| General Notes / Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Source only update |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 07/19/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Willie Haywood |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF108A MotCurrPeakEstimn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Jared Julien |
| 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.
1.2.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5584 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Co configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Jared Julien |
| Review Date : |
|
| 05/06/16 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
| Kevin Smith |
|
| Approved by Reviewer(s): |
|
|
|
| Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Rev 1.0 | 3/10/2014 |
| SWC Integration Review for SF109A ElecPwrCns |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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.
Gustavo M Nunes |
| 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.
1.0.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Change Request ID: |
|
|
| Smith, Kevin:
Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Quality Check Items: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
| Configurator Changes (Group Review) | SWC downloaded from Synergy and version matches |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the required component version to be integrated. |
|
|
|
|
|
|
|
|
|
|
|
| Latest available |
|
| CIG Section 4.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| If available, run the integrate batch file in the tools folder |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| of the SWC. |
|
|
|
|
|
|
|
|
|
|
|
| No batch file |
|
| CIG Section 4.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Smith, Kevin:
Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer.
Any comments/questions shall be documented below and followed up before completeing the integration task.
All conifguration settings reviewed for the SWC to |
|
|
|
|
|
|
|
|
| N/A |
|
| Comments: |
|
|
|
|
|
|
|
|
|
|
| meet program needs and requirements. |
|
|
|
|
|
|
|
|
|
|
|
| Co configuration settings |
|
| CIG Section 4.2, SWC Integration guide. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| OS: If required, the changes made in the OS files are |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| reviewed. |
|
|
|
|
|
|
|
|
|
|
|
| No OS settings |
|
| CIG Section 5.2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If required, NvM blocks are conifgured to meet |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| the requirements of the SWC and program. |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Ea: | If applicable, Ea configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for T1xx |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| FEE: | If applicable, FEE configured with the new SWC |
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
| NvM blocks. CRC's and other checks are applied |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| as required. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 7.2.2.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Developer Changes (Group Review) | Import the SWC that is required to integrate into |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| Developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Per the integration guidelines for the SWC, all additional |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| considerations required have been performed and reviewed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.3.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Imported Std_Workspace that meets or exceeds the |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| version used for the SWC. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 4.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| All runnables of the SWC mapped to the correct |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| application, task, and order within the task. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 5.1, SWC FDD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| SWC Service and Client/Server ports mapped to |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| required ports |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 6.2, SWC FDD/Integration Guide |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: If applicable, create NvM block mapping for |
|
|
|
|
|
|
|
| Smith, Kevin:
If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
| N/A | |
| Comments: |
|
|
|
|
| per-instance memory items in the SWC |
|
|
|
|
|
|
|
|
|
|
|
| Not applicable for EA4 |
|
| CIG Section 7.1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| NvM: Import generated component descriptions for the |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| NvM created by Configurator |
|
|
|
|
|
|
|
|
|
|
|
| No NvM |
|
| CIG Section 7.2.4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| RTE Generated an all file changes were compared and |
|
|
|
|
|
|
|
|
| X | |
| Comments: |
|
|
|
|
| changes were in line with the changes made by the SWC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CIG Section 8 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration Changes (Group Review) | CalComponent.arxml regenerated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Developer project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| TuningSets.arxml generated and imported into |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
| Configurator project. |
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Calibration ports linked properly in Developer. |
|
|
|
|
|
|
|
|
| N/A | |
| Comments: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| No calibration changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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: |
|
| Gustavo M Nunes |
| Review Date : |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Lead Peer Reviewer: |
|
|
|
|
|
| Approved by Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Other Reviewer(s): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|