This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Component Design

1: ES238A_HwAgArbn FDP Design Review Checklist
2: ES238A_HwAgArbn_slwebview
3: ES238A_HwAgArbn_requirements

Component Design

Component Documentation

Reports

ES238A_HwAgArbn_requirements.html

1 - ES238A_HwAgArbn FDP Design Review Checklist

Nexteer_Template_V1.0

Overview

Peer Review Instructions
Technical Review Checklist
Template Change Log

Sheet 1: Peer Review Instructions

Instructions for Functional Design Package Peer Review

PRE-MEETING
	Function Owner	Confirm that requirements are reviewed and approved PRIOR to the FDP peer review
	Function Owner	Start with latest version of the template for any "first reviews" - Continue to use existing temmplate for re-reviews
	Function Owner	Provide the functional design package (changed documents) to the invited attendees 1-2 working days in advance of review
	Function Owner	Notify the assigned peer reviewer and make sure they are prepared to do their function in the meeting
	Function Owner	Identify necessary attendance and invite to meeting
	Function Owner	Complete the "Author" column information for sections 1 through 3 prior to the review
	Function Owner	Complete the attendance invitation list in section 5
	Function Owner	For Re-reviews only: Complete the column "remarks by author" to identify actions taken to address items found in earlier reviews.

DURING MEETING
	Function Owner	Present document changes to the review team
	Peer Reviewer	Capture attendance of the review
	Peer Reviewer	Capture actions and issues in section 4. Identify issue summary, Document type, Reference (Requirement ID, section number, etc), Defect Type and indicate status as "OPEN"

POST MEETING
	Function Owner	Follow up on all "open" items. Update "Summary of Resolution" to indicate what was done or decided.
	Function Owner	Schedule follow up review OR review open items with peer reviewer and obtain agreement to close
	Peer Reviewer	Close change request in system and confirm all associated tasks are complete. Upload peer review checklist (this document) with any FDP updates

Sheet 2: Technical Review Checklist

Technical Review Checklist - Template Version 01.00.05

Product Name

Electric Power Steering

Electrical Arch.

Review Scope

Defect Type

Numbers

Yes

Closed

Function Name

ES238A_HwAgArbn

Baseline

1.0.0

Initial release. Includes arbitration of two channels based on correlation status and signal availability

Requirement

Rejected

FDD

Author

Kushion

Interface

Open

Model

Effort

Design

FMEA

Review Effort(Hrs.)

1.00

Standards

*.m File

Corr+Verf effort(Hrs.)

Documentation

Cal Process

Total Effort (Hrs.)

1.00

Others

Total

Checklist No.

Description of Check

Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. Author

Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. Reviewer

Author: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewer

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

Section 1: TECHNICAL CHECK

1.1

Confirm that all signal inputs into the FDP (Functional Design Package) are contained within and exactly named as the "Available_Nexteer_Signals.m" states.

Yes

1.2

Confirm any removed signal inputs from the design have been removed from the "Available_Nexteer_Signals.m" file.

Yes

1.3

Confirm all signals and parameters (outputs, calibrations, constants, non-volatile memory) used in the *.m file and the design conform to the AutoSAR naming convention documentation.

Yes

1.4

Confirm *.m file has been provided to the "Available_Signal_Names" Author.

Yes

Will be provided when in Synergy per new process

1.5

Confirm Electrical Systems interface map is updated to reflect the FDP (signal IO)

Yes

Map Updated

Section 2: Safety CHECK

Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. Author

Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. Reviewer

Author: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewer

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

2.1

Confirm that the functional DFMEA is up to date based on the design in the current package.

2.2

Confirm that Safety requirements (ASIL A - D) are referenced in the design documents.

Yes

Section 3: Lessons Learned

Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. Author

Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. Reviewer

Author: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewer

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

3.1

Have functions depending upon system state been reviewed for need to be executed at the 2ms rate to avoid system lag issues?

Yes

Function runs in all states, so no concern

3.2

Have all diagnostics (NTCs) been confirmed to show logic to invoke a diagnostic "PASS" for control of the status byte at the customer level.

No NTCs

3.3

Has the requirements traceability steps used the RMI steps as defined in the FDD authoring spec to generate the traceability report?

Yes

3.4

Has the requirements traceability report been verified to only contain ONLY requirements from the FR.

Yes

3.5

Confirm that all PIM that does NOT have an initialization value of zero is initialized in an INIT function.

No PIM initialized to non-zero value

3.6

3.7

Section 4: Issues / Actions Identified

Document

Reference

Summary of resolution

Author: Defect type to be selected. Defect Type

Author: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By Author

Author: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status

4.1

Rename variables with counter to 'Cntr'

Model

Corrected during meeting

Standards

Closed

4.2

Elaborate Long Names

*.m File

Corrected during meeting

Standards

Closed

4.3

Rerun reqmt traceability after FR is baselined

Reran with Review View after baselined

Documentation

Closed

4.4

4.5

4.6

4.7

4.8

4.9

4.10

4.11

4.12

4.13

4.14

4.15

4.16

4.17

4.18

4.19

4.20

4.21

4.22

4.23

4.24

4.25

Section 5: APPROVALS

Role

First Review

Date

Attendance

Approval?

Function Owner*

Kushion

7/14/2015

Yes

Peer Reviewer*

Amberkar

Yes

EPDT Engineer

McCann

ES Engineer

Patel

Yes

Software Lead

Rijvi

Yes

Hardware Lead

Test Lead

Chinchalpet

Yes

Safety Lead

Millsap

Yes

Role

Second Review (if required)

Date

Attendance

Approval?

Function Owner*

Muragesh Asundi

8/14/2015

Yes

Peer Reviewer*

Spandana Balani

Yes

EPDT Engineer

ES Engineer

Software Lead

Hardware Lead

Test Lead

Safety Lead

Role

Third Review (if required)

Date

Attendance

Approval?

Function Owner*

Peer Reviewer*

<Name>

EPDT Engineer

ES Engineer

Software Lead

Hardware Lead

Test Lead

Safety Lead

Role

Fourth Review (if required)

Date

Attendance

Approval?

Function Owner*

Peer Reviewer*

<Name>

EPDT Engineer

ES Engineer

Software Lead

Hardware Lead

Test Lead

Safety Lead

Role

Add more if necessary

Date

Attendance

Approval?

P.S.:

Yes indicates adherence

No indicates non-adherence, reviewer shall provide suitable comments at the end of this document for each point.

NA indicates not applicable

Sheet 3: Template Change Log

Rev	Change	Author
01.00.05	Added lesson learned #3.5	MDK
01.00.06	Added lesson learned #3.6, 3.7 - Structure and writing of NVM in mfiles and models.	MDK

2 - ES238A_HwAgArbn_slwebview

Simulink Web View

3 - ES238A_HwAgArbn_requirements

Requirements Traceability Report for ES238A_HwAgArbn

Table of Contents

1. Model Information for "ES238A_HwAgArbn"
2. Traceability Summary for "ES238A_HwAgArbn"
3. System - HwAgArbnPer1
4. System - Arbitration
5. System - HwAgAAvlChk
6. System - HwAgAAvlChk1

List of Tables

1.1. ES238A_HwAgArbn Version Information
2.1. Artifacts linked in model
3.1. Objects in ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1 that have Requirements Traceability Links
4.1. Objects in ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1/Arbitration that have Requirements Traceability Links
5.1. ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1/HwAgAAvlChk Requirements Traceability Data
6.1. ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1/HwAgAAvlChk1 Requirements Traceability Data

Chapter 1. Model Information for "ES238A_HwAgArbn"

Table 1.1. ES238A_HwAgArbn Version Information

ModelVersion	1.245	ConfigurationManager	None
Created	Thu Mar 19 15:38:41 2015	Creator	rzqy0r
LastModifiedDate	Fri Aug 14 13:53:17 2015	LastModifiedBy	FZG88Y

Chapter 2. Traceability Summary for "ES238A_HwAgArbn"

Table 2.1. Artifacts linked in model

ID	Artifact names stored by RMI	Last modified	# links
DOC1	0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft)	07 July 2015 by Mark Kushion	8
DOC2	0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn)	07 July 2015 by Mark Kushion	4

Chapter 3. System - HwAgArbnPer1

Table 3.1. Objects in ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1 that have Requirements Traceability Links

Linked Object

Requirements Traceability Data

Constant

"REQ: ES238A_35"

DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_35

Constant1

"REQ: ES238A_69"

DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_69

Logical Operator

"REQ: ES238A_35"

DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn), object ES238A_35

Logical Operator1

"REQ: ES238A_69"

DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn), object ES238A_69

Relational Operator

"REQ: ES238A_35"

DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_35

Relational Operator1

"REQ: ES238A_69"

DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_69

Chapter 4. System - Arbitration

Table 4.1. Objects in ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1/Arbitration that have Requirements Traceability Links

Linked Object

Requirements Traceability Data

Arbitrate

1.	"REQ: ES238A_108"	DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_108
--	------------------------------	------------------------------
2.	"REQ: ES238A_84"	DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_84
--	------------------------------	------------------------------
3.	"REQ: ES238A_100"	DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_100
--	------------------------------	------------------------------
4.	"REQ: ES238A_106"	DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn_Draft), object ES238A_106

Chapter 5. System - HwAgAAvlChk

Table 5.1. ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1/HwAgAAvlChk Requirements Traceability Data

Link#	Link Description	Link Target (document name and location ID)
1.	"REQ: ES238A_35"	DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn), object ES238A_35

Chapter 6. System - HwAgAAvlChk1

Table 6.1. ES238A_HwAgArbn/HwAgArbn/HwAgArbnPer1/HwAgAAvlChk1 Requirements Traceability Data

Link#	Link Description	Link Target (document name and location ID)
1.	"REQ: ES238A_69"	DOORS module 0000cf64 (/E-STEER Core/SubSystem Specifications/Electrical Actuator/Control Module/FDD Module Requirements/EA4/ES238A_HwAgArbn), object ES238A_69