instruction
stringlengths 29
35k
| input
stringclasses 1
value | output
stringlengths 29
35k
|
|---|---|---|
[BSW_Test][SW: 1.7.1.55]: Issue with DID DD0C Requirement: SSDS
/ IBC/ Customer/ Geely/ Lotus_EPA/ 01_Requirements/ 04_SW/ 02_Diag/ SSDS/ BCM/ BCM Brake Control Module (VDS) 8891363492 A.xlsx
Comments provided in SSDS for DID DD0C:
"Only need to receive value on BUS, then map to DID DD0C, when fault detected, record to snapshot is engough. The Two signals are: VehModMngtGlbSafe1PwrElecMai(high half-byte), VehModMngtGlbSafe1PwrElecSubtyp(Low half-byte)"
Procedure:
1. Set signal
VehModMngtGlbSafe1PwrElecMai = 1
VehModMngtGlbSafe1PwrElecSubtyp = 1
2. Simulate fault WSS_HS_SHORT_LS_FRONT_LEFT
3. Read snapshot record 19 04 40 31 19 20
4. Set signal
VehModMngtGlbSafe1PwrElecMai = 1
VehModMngtGlbSafe1PwrElecSubtyp = 3
2. Simulate fault WSS_HS_SHORT_GND_FRONT_LEFT
3. Read snapshot record 19 04 40 31 11 20
Expected Response:
At step 3: 59 04 40 31 19 2F 20 18 xx xx...DD 0C 11..xx xx
At step 3: 59 04 40 31 11 2F 20 18 xx xx...DD 0C 13..xx xx
Expected Response:
At step 3: 59 04 40 31 19 2F 20 18 xx xx...DD 0C 01..xx xx
At step 3: 59 04 40 31 11 2F 20 18 xx xx...DD 0C 03..xx xx
Only the signal value VehModMngtGlbSafe1PwrElecSubtyp is considered.
Logs attached
Please do change as related action analyzed. Brief investigation comment:
Based on the attached SSDS, 1 byte 0xDD0C value is from below signals:
VehModMngtGlbSafe1PwrElecMai(high half-byte), VehModMngtGlbSafe1PwrElecSubtyp(Low half-byte).
Data length from each signal is of only 4 bits in Comms. So, to make the 2 signals as U8, below change to be made in software:
Data[FM_ZERO] = MAKE_U8(powerlevel_main, powerlevel_subtype);
In current software, implementation is as below:
Data[FM_ZERO] = MAKE_U8(GET_HIGHER_NIBBLE(powerlevel_main), GET_LOWER_NIBBLE(powerlevel_subtype));
Proposal of next steps (incl. effort / h and verifier):
Please create a task to update implementation as mentioned in investigation comments.
Analysis Completed by:
Krishna Kishore
Impacted Components:
FaultManagerArWrapper
Estimated Efforts: 5hrs
Planned Completion date:29-07-2021 | [BSW_Test][SW: 1.7.1.55]: Issue with DID DD0C Requirement: SSDS
/ IBC/ Customer/ Geely/ Lotus_EPA/ 01_Requirements/ 04_SW/ 02_Diag/ SSDS/ BCM/ BCM Brake Control Module (VDS) 8891363492 A.xlsx
Comments provided in SSDS for DID DD0C:
"Only need to receive value on BUS, then map to DID DD0C, when fault detected, record to snapshot is engough. The Two signals are: VehModMngtGlbSafe1PwrElecMai(high half-byte), VehModMngtGlbSafe1PwrElecSubtyp(Low half-byte)"
Procedure:
1. Set signal
VehModMngtGlbSafe1PwrElecMai = 1
VehModMngtGlbSafe1PwrElecSubtyp = 1
2. Simulate fault WSS_HS_SHORT_LS_FRONT_LEFT
3. Read snapshot record 19 04 40 31 19 20
4. Set signal
VehModMngtGlbSafe1PwrElecMai = 1
VehModMngtGlbSafe1PwrElecSubtyp = 3
2. Simulate fault WSS_HS_SHORT_GND_FRONT_LEFT
3. Read snapshot record 19 04 40 31 11 20
Expected Response:
At step 3: 59 04 40 31 19 2F 20 18 xx xx...DD 0C 11..xx xx
At step 3: 59 04 40 31 11 2F 20 18 xx xx...DD 0C 13..xx xx
Expected Response:
At step 3: 59 04 40 31 19 2F 20 18 xx xx...DD 0C 01..xx xx
At step 3: 59 04 40 31 11 2F 20 18 xx xx...DD 0C 03..xx xx
Only the signal value VehModMngtGlbSafe1PwrElecSubtyp is considered.
Logs attached
Please do change as related action analyzed. Brief investigation comment:
Based on the attached SSDS, 1 byte 0xDD0C value is from below signals:
VehModMngtGlbSafe1PwrElecMai(high half-byte), VehModMngtGlbSafe1PwrElecSubtyp(Low half-byte).
Data length from each signal is of only 4 bits in Comms. So, to make the 2 signals as U8, below change to be made in software:
Data[FM_ZERO] = MAKE_U8(powerlevel_main, powerlevel_subtype);
In current software, implementation is as below:
Data[FM_ZERO] = MAKE_U8(GET_HIGHER_NIBBLE(powerlevel_main), GET_LOWER_NIBBLE(powerlevel_subtype));
Proposal of next steps (incl. effort / h and verifier):
Please create a task to update implementation as mentioned in investigation comments.
Analysis Completed by:
Krishna Kishore
Impacted Components:
FaultManagerArWrapper
Estimated Efforts: 5hrs
Planned Completion date:29-07-2021 |
|
[XQA][PA2123][ASPICE][SYS.5][CL1][BP.7]_System Qualification Test_Inconsistency in cumulative number of planned and excuted tests During the last MQB48-W audit it turned out that sums in the test data were inconsistent.
Due to the big number of test cases/requirements human mistakes cannot be excluded.
To avoid such inconsistencies an (partly) automated test center report will help.
Source: [ASPICE] Assessment CW 2123
Finding:
Overall test report shows inconsistent in the documentation about cumulative number of planned test to executed and not testable test, to passed and failed tests.
Evidence:
Test summary report
Impact / Risk:
Monitoring, completeness and coverage may be incorrect.
Lowered "Trust" in report-
Important aspects may not be sufficiently tested.
Type:
Project and Process
Recommended Actions:
- Analyze why issue happened.
- Check tool supported solution:
- data should be single source (unified metrics)
- or in same format which can be imported consistently (without manual work)
- Update template to calculate values rather than entering all of them manually
- Add review in case as short-term solution ADBY43 will follow the approach from ADTY with the automized tooling. | [XQA][PA2123][ASPICE][SYS.5][CL1][BP.7]_System Qualification Test_Inconsistency in cumulative number of planned and excuted tests During the last MQB48-W audit it turned out that sums in the test data were inconsistent.
Due to the big number of test cases/requirements human mistakes cannot be excluded.
To avoid such inconsistencies an (partly) automated test center report will help.
Source: [ASPICE] Assessment CW 2123
Finding:
Overall test report shows inconsistent in the documentation about cumulative number of planned test to executed and not testable test, to passed and failed tests.
Evidence:
Test summary report
Impact / Risk:
Monitoring, completeness and coverage may be incorrect.
Lowered "Trust" in report-
Important aspects may not be sufficiently tested.
Type:
Project and Process
Recommended Actions:
- Analyze why issue happened.
- Check tool supported solution:
- data should be single source (unified metrics)
- or in same format which can be imported consistently (without manual work)
- Update template to calculate values rather than entering all of them manually
- Add review in case as short-term solution ADBY43 will follow the approach from ADTY with the automized tooling. |
|
[SWE.5 IAT][FCA WS][FBP3] Interaction testing mismatch between sw implementation and architecture model This CR is created to resolve the architecture diagram / connectivity issues for the OP's 5465622 and 5431253 2021-11-10 HoughtoB:
The Issues captured in the referenced OPs span both the foundation architecture and the WS project architecture.
Foundation Architecture (2 tasks)
1 task required to make corrections to static and dynamic architecture diagrams based on finding in OP 5465622
ex:
- diagrams for calculateFrictionCompensationTorqueDemand should no longer reference the AssistBoostCurvesData (associated data sender receiver port should be removed from all components that reference it)
- determineColumnVelocity diagram columnVelocity data flow to determineAssistState runnable should be corrected to show consumption by overuseDetection runnable entity.
- correct sequence representation of FrictionCompensation.calculateDemand to be place before ActiveReturn.calculateDemand to match execution order found in task mapping table.
- Dual lane system specific interaction blocks need to be introduced to a number of diagrams (using correct EPP_C1 / EPP_C1+ condition)
- determineMotorTorqueDemand
- determineMotorTorquePositionAndVelocity
- determineSupplyCapability
- monitorAssistTorque
1 task required to merge change to foundation mainline
Project Architecture (2 tasks)
1 task required to make correction to static and dynamic architecture diagrams base on findings in OP 5465622 as well as correct issues found based on static interface testing referenced in OP 5431253.
- A number of duplicate unique IDs are found representing a conflict between foundation diagrams and VMSpecialisation diagrams.
- Ensure diagram settings are set properly to help prevent future issues when testing control flows that reference blueprint components that are varied at the project level.
- Remove duplicate links found in model resulting in duplicate RteConnectivity.csv file entries
- add missing links in model resulting in missing entries in RteConnectivity.csv file
1 task required to merge change to foundation mainline. | [SWE.5 IAT][FCA WS][FBP3] Interaction testing mismatch between sw implementation and architecture model This CR is created to resolve the architecture diagram / connectivity issues for the OP's 5465622 and 5431253 2021-11-10 HoughtoB:
The Issues captured in the referenced OPs span both the foundation architecture and the WS project architecture.
Foundation Architecture (2 tasks)
1 task required to make corrections to static and dynamic architecture diagrams based on finding in OP 5465622
ex:
- diagrams for calculateFrictionCompensationTorqueDemand should no longer reference the AssistBoostCurvesData (associated data sender receiver port should be removed from all components that reference it)
- determineColumnVelocity diagram columnVelocity data flow to determineAssistState runnable should be corrected to show consumption by overuseDetection runnable entity.
- correct sequence representation of FrictionCompensation.calculateDemand to be place before ActiveReturn.calculateDemand to match execution order found in task mapping table.
- Dual lane system specific interaction blocks need to be introduced to a number of diagrams (using correct EPP_C1 / EPP_C1+ condition)
- determineMotorTorqueDemand
- determineMotorTorquePositionAndVelocity
- determineSupplyCapability
- monitorAssistTorque
1 task required to merge change to foundation mainline
Project Architecture (2 tasks)
1 task required to make correction to static and dynamic architecture diagrams base on findings in OP 5465622 as well as correct issues found based on static interface testing referenced in OP 5431253.
- A number of duplicate unique IDs are found representing a conflict between foundation diagrams and VMSpecialisation diagrams.
- Ensure diagram settings are set properly to help prevent future issues when testing control flows that reference blueprint components that are varied at the project level.
- Remove duplicate links found in model resulting in duplicate RteConnectivity.csv file entries
- add missing links in model resulting in missing entries in RteConnectivity.csv file
1 task required to merge change to foundation mainline. |
|
GAC A39 Variant1 A39-I-2wd LA.LKAS_FAILED_TEMPORARY_TIME_OVER change from 500 to 5000 Activity Description:
This working package deal with a final interation of all realized W150j and W210j1&j2 tasks as SW Architecure and SWCs to be integrated to a completed executable SW build which shall matches this release defined change scope, fucnitons and requirements defined in SW Engineering Traceability Matrix and Software Release Plan.
It follows ZF Level 3 WI C_040_3_SSE_063_EN GenC Software Integration Work Instruction and breakdown as below activities:
Before any of below activities, Gate 2 - Software Design Freeze must be reviewed and passed! (Refer to W130j Software Reelase Gate Review Activities)
4.1.Project Initiation
4.2.Composite Component Integration
4.3.Configure Repository
4.4.Configure Integration Model
4.5.Update of the Memory Configuration
4.6.AUTOSAR ECU Model Configuration
4.7.Build Configuration Updates
Below Activities (4.8-4.12) directly lead by SWPM during SWPM performing Gate 3 - Software Freeze Review:
4.8.Baseline Check
4.9.Software Build
4.10.Tune Generation for Test
4.11.Software Confidence Test
4.12.Approval of Software Build (This is responsed by SWPM and performed before Jenkins formal build)
Below activities is repsonsible by SWPM and performed within W130j Software Release Gate Review Activities as Gate 3 Software Freeze and/or in Gate 4 Software Release, however it supported from SW Integrator and LSE:
4.13.Configuration of Delivery
4.14.Acceptance of Delivery for Release
4.15.Documentation of Software Delivery
4.16.Delivery of Software Release
4.17.Review and Update of Software Tune
Input of this WP are:
1. SW Architecture
2. SW Component Source
3. Configured AutoSAR Stack
4. SW Component Integration Status Report
4. SW Requirement and Baseline
5. SW Engineering Traceability Matrix
6. SW Release Plan
7. SW BOM
8. Approved SW Gate 2 Software Design Freeze Reiew Checklist (same as SW Engineering Checklist)
9. Prepared Jenkins Task
Output of this WP are:
1. SW Assemble Build in Jenkins (S1,2,3...)
2. Confidence Test Report per assemble
Responsible: SW Integrator, SWPM (4.12-4.17)
Support: SW Requirement Engineer, SW FM Developer, LSE
Reviewer: SW Integrator Supervisor This is cluster CR. | GAC A39 Variant1 A39-I-2wd LA.LKAS_FAILED_TEMPORARY_TIME_OVER change from 500 to 5000 Activity Description:
This working package deal with a final interation of all realized W150j and W210j1&j2 tasks as SW Architecure and SWCs to be integrated to a completed executable SW build which shall matches this release defined change scope, fucnitons and requirements defined in SW Engineering Traceability Matrix and Software Release Plan.
It follows ZF Level 3 WI C_040_3_SSE_063_EN GenC Software Integration Work Instruction and breakdown as below activities:
Before any of below activities, Gate 2 - Software Design Freeze must be reviewed and passed! (Refer to W130j Software Reelase Gate Review Activities)
4.1.Project Initiation
4.2.Composite Component Integration
4.3.Configure Repository
4.4.Configure Integration Model
4.5.Update of the Memory Configuration
4.6.AUTOSAR ECU Model Configuration
4.7.Build Configuration Updates
Below Activities (4.8-4.12) directly lead by SWPM during SWPM performing Gate 3 - Software Freeze Review:
4.8.Baseline Check
4.9.Software Build
4.10.Tune Generation for Test
4.11.Software Confidence Test
4.12.Approval of Software Build (This is responsed by SWPM and performed before Jenkins formal build)
Below activities is repsonsible by SWPM and performed within W130j Software Release Gate Review Activities as Gate 3 Software Freeze and/or in Gate 4 Software Release, however it supported from SW Integrator and LSE:
4.13.Configuration of Delivery
4.14.Acceptance of Delivery for Release
4.15.Documentation of Software Delivery
4.16.Delivery of Software Release
4.17.Review and Update of Software Tune
Input of this WP are:
1. SW Architecture
2. SW Component Source
3. Configured AutoSAR Stack
4. SW Component Integration Status Report
4. SW Requirement and Baseline
5. SW Engineering Traceability Matrix
6. SW Release Plan
7. SW BOM
8. Approved SW Gate 2 Software Design Freeze Reiew Checklist (same as SW Engineering Checklist)
9. Prepared Jenkins Task
Output of this WP are:
1. SW Assemble Build in Jenkins (S1,2,3...)
2. Confidence Test Report per assemble
Responsible: SW Integrator, SWPM (4.12-4.17)
Support: SW Requirement Engineer, SW FM Developer, LSE
Reviewer: SW Integrator Supervisor This is cluster CR. |
|
GAC A39 One LKA parameter change from S to V Variant(LKAS_TORQUE_RATE_LIMIT) Activity Description:
This working package deal with a final interation of all realized W150j and W210j1&j2 tasks as SW Architecure and SWCs to be integrated to a completed executable SW build which shall matches this release defined change scope, fucnitons and requirements defined in SW Engineering Traceability Matrix and Software Release Plan.
It follows ZF Level 3 WI C_040_3_SSE_063_EN GenC Software Integration Work Instruction and breakdown as below activities:
Before any of below activities, Gate 2 - Software Design Freeze must be reviewed and passed! (Refer to W130j Software Reelase Gate Review Activities)
4.1.Project Initiation
4.2.Composite Component Integration
4.3.Configure Repository
4.4.Configure Integration Model
4.5.Update of the Memory Configuration
4.6.AUTOSAR ECU Model Configuration
4.7.Build Configuration Updates
Below Activities (4.8-4.12) directly lead by SWPM during SWPM performing Gate 3 - Software Freeze Review:
4.8.Baseline Check
4.9.Software Build
4.10.Tune Generation for Test
4.11.Software Confidence Test
4.12.Approval of Software Build (This is responsed by SWPM and performed before Jenkins formal build)
Below activities is repsonsible by SWPM and performed within W130j Software Release Gate Review Activities as Gate 3 Software Freeze and/or in Gate 4 Software Release, however it supported from SW Integrator and LSE:
4.13.Configuration of Delivery
4.14.Acceptance of Delivery for Release
4.15.Documentation of Software Delivery
4.16.Delivery of Software Release
4.17.Review and Update of Software Tune
Input of this WP are:
1. SW Architecture
2. SW Component Source
3. Configured AutoSAR Stack
4. SW Component Integration Status Report
4. SW Requirement and Baseline
5. SW Engineering Traceability Matrix
6. SW Release Plan
7. SW BOM
8. Approved SW Gate 2 Software Design Freeze Reiew Checklist (same as SW Engineering Checklist)
9. Prepared Jenkins Task
Output of this WP are:
1. SW Assemble Build in Jenkins (S1,2,3...)
2. Confidence Test Report per assemble
Responsible: SW Integrator, SWPM (4.12-4.17)
Support: SW Requirement Engineer, SW FM Developer, LSE
Reviewer: SW Integrator Supervisor This is cluster CR. | GAC A39 One LKA parameter change from S to V Variant(LKAS_TORQUE_RATE_LIMIT) Activity Description:
This working package deal with a final interation of all realized W150j and W210j1&j2 tasks as SW Architecure and SWCs to be integrated to a completed executable SW build which shall matches this release defined change scope, fucnitons and requirements defined in SW Engineering Traceability Matrix and Software Release Plan.
It follows ZF Level 3 WI C_040_3_SSE_063_EN GenC Software Integration Work Instruction and breakdown as below activities:
Before any of below activities, Gate 2 - Software Design Freeze must be reviewed and passed! (Refer to W130j Software Reelase Gate Review Activities)
4.1.Project Initiation
4.2.Composite Component Integration
4.3.Configure Repository
4.4.Configure Integration Model
4.5.Update of the Memory Configuration
4.6.AUTOSAR ECU Model Configuration
4.7.Build Configuration Updates
Below Activities (4.8-4.12) directly lead by SWPM during SWPM performing Gate 3 - Software Freeze Review:
4.8.Baseline Check
4.9.Software Build
4.10.Tune Generation for Test
4.11.Software Confidence Test
4.12.Approval of Software Build (This is responsed by SWPM and performed before Jenkins formal build)
Below activities is repsonsible by SWPM and performed within W130j Software Release Gate Review Activities as Gate 3 Software Freeze and/or in Gate 4 Software Release, however it supported from SW Integrator and LSE:
4.13.Configuration of Delivery
4.14.Acceptance of Delivery for Release
4.15.Documentation of Software Delivery
4.16.Delivery of Software Release
4.17.Review and Update of Software Tune
Input of this WP are:
1. SW Architecture
2. SW Component Source
3. Configured AutoSAR Stack
4. SW Component Integration Status Report
4. SW Requirement and Baseline
5. SW Engineering Traceability Matrix
6. SW Release Plan
7. SW BOM
8. Approved SW Gate 2 Software Design Freeze Reiew Checklist (same as SW Engineering Checklist)
9. Prepared Jenkins Task
Output of this WP are:
1. SW Assemble Build in Jenkins (S1,2,3...)
2. Confidence Test Report per assemble
Responsible: SW Integrator, SWPM (4.12-4.17)
Support: SW Requirement Engineer, SW FM Developer, LSE
Reviewer: SW Integrator Supervisor This is cluster CR. |
|
GAC A39 One LKA parameter change from S to V Variant(LKAS_TORQUE_RATE_LIMIT) 1. Create SW Architecture per behavior allocated in this SW features, allocation refers to Rhapsody allocation results or workproduct 3000_SW_Eng_Dev_Trace_Matrix.xls (url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/Steering/Projects/GAC/A39%5fCD%5fEPS/PR48718%5fLVS%5fENG%5fAPP%5fGAC%5fA39%5fEPS%5fCD%5fSYS%5fHRoom%5fAP/30%5fSoftware/3000%5fManagement/project.pj&selection=%223000%5fSW%5fEng%5fDev%5fTrace%5fMatrix.xlsx%22
Input:
- Traceability matrix and Release plan for features allocated to this release phase
- Rhapsody Features, behaviors and diagrams defined from SW Requirement phase
- SW Requirement defined for this release
- System Requirement / Architecture
Output:
- SW Physical Architecture
- SW Sequence Diagram
Responsible: SW Architect, Support: SW Requirement Engineer, SW FM Developer, SW PM, Reviewer: Core Architect, LSE This is a cluster CR. | GAC A39 One LKA parameter change from S to V Variant(LKAS_TORQUE_RATE_LIMIT) 1. Create SW Architecture per behavior allocated in this SW features, allocation refers to Rhapsody allocation results or workproduct 3000_SW_Eng_Dev_Trace_Matrix.xls (url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/Steering/Projects/GAC/A39%5fCD%5fEPS/PR48718%5fLVS%5fENG%5fAPP%5fGAC%5fA39%5fEPS%5fCD%5fSYS%5fHRoom%5fAP/30%5fSoftware/3000%5fManagement/project.pj&selection=%223000%5fSW%5fEng%5fDev%5fTrace%5fMatrix.xlsx%22
Input:
- Traceability matrix and Release plan for features allocated to this release phase
- Rhapsody Features, behaviors and diagrams defined from SW Requirement phase
- SW Requirement defined for this release
- System Requirement / Architecture
Output:
- SW Physical Architecture
- SW Sequence Diagram
Responsible: SW Architect, Support: SW Requirement Engineer, SW FM Developer, SW PM, Reviewer: Core Architect, LSE This is a cluster CR. |
|
[b621][CAT3][PTR][VW MEB EBB Wave1.5][CR: 5144832][Retest-ID 5352547] External PTS linearization: Time information of PTS PreProc measurement signals not correctly implemented The linearization of the PTS sensors shall be changed from the internal routine based on the MPS to an external routine based on an external reference sensor on the production line. The external linearization is necessary for Wave 2 devices to achieve the required robustness and accuracy. The linearization algorithm requires PTS PreProc measurement signals with time information.
The external linearization calculates the PTS LUT values on an external station using an external reference sensor and the PTS PreProc values provided by the EBB device via 5ms DAQ-Event. A time information of the PreProc vlues is required for signal validation.
Variant 1:
Usage of XCP timestamp. According to the description below there is an option to receive a timestamp for the sensor values. Is this option available in EBB software?
Variant 2:
Usage of a roling counter which is enclosed in the PTS PreProc measurent signal. The 12bit PreProc Signal could be combined with a 20bit roling counter to a 32bit measurement signal. The counter could be increased each millisecond.
The second variant would be the prefered solution. LakshmiKanth Sriram(Z651461) [5/6/2021]
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As mentioned in CR description , Variant 2 is considered for getting time information of the PreProc vlues for signal validation.
Along with this ,the CR 5144838 changes i.e the default values of the PTS lookup tables shall be replaced with values based on measurements from the production line shall be done.
--------------------------------------------------------------------------------
Risk (low/medium/high):Medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): LakshmiKanth
Proposal of next steps (incl. effort/h and verification): ALM_Task
--------------------------------------------------------------------------------
TASK 1
--------------------------------------------------------------------------------
Title:[CCB_VW_1417] [MEB X621][EBB] external PTS linearization: PTS PreProc measurement signals with time information and PTS LUT default value
--------------------------------------------------------------------------------
Implemenent changes as per the attachment , Perform QAC,Polyspace,VC and Rhapsody
Owner: Lakshmikanth
Reviewer:
Estimated design effort/h: hr
Estimated implementation effort/h: hr
Estimated unit testing effort/h: 9 hrs
---------------------------------------------------------------------------------
Total effort/h: 9 hr
[Optional] Planned completion date: 5/7/2021 | [b621][CAT3][PTR][VW MEB EBB Wave1.5][CR: 5144832][Retest-ID 5352547] External PTS linearization: Time information of PTS PreProc measurement signals not correctly implemented The linearization of the PTS sensors shall be changed from the internal routine based on the MPS to an external routine based on an external reference sensor on the production line. The external linearization is necessary for Wave 2 devices to achieve the required robustness and accuracy. The linearization algorithm requires PTS PreProc measurement signals with time information.
The external linearization calculates the PTS LUT values on an external station using an external reference sensor and the PTS PreProc values provided by the EBB device via 5ms DAQ-Event. A time information of the PreProc vlues is required for signal validation.
Variant 1:
Usage of XCP timestamp. According to the description below there is an option to receive a timestamp for the sensor values. Is this option available in EBB software?
Variant 2:
Usage of a roling counter which is enclosed in the PTS PreProc measurent signal. The 12bit PreProc Signal could be combined with a 20bit roling counter to a 32bit measurement signal. The counter could be increased each millisecond.
The second variant would be the prefered solution. LakshmiKanth Sriram(Z651461) [5/6/2021]
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As mentioned in CR description , Variant 2 is considered for getting time information of the PreProc vlues for signal validation.
Along with this ,the CR 5144838 changes i.e the default values of the PTS lookup tables shall be replaced with values based on measurements from the production line shall be done.
--------------------------------------------------------------------------------
Risk (low/medium/high):Medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): LakshmiKanth
Proposal of next steps (incl. effort/h and verification): ALM_Task
--------------------------------------------------------------------------------
TASK 1
--------------------------------------------------------------------------------
Title:[CCB_VW_1417] [MEB X621][EBB] external PTS linearization: PTS PreProc measurement signals with time information and PTS LUT default value
--------------------------------------------------------------------------------
Implemenent changes as per the attachment , Perform QAC,Polyspace,VC and Rhapsody
Owner: Lakshmikanth
Reviewer:
Estimated design effort/h: hr
Estimated implementation effort/h: hr
Estimated unit testing effort/h: 9 hrs
---------------------------------------------------------------------------------
Total effort/h: 9 hr
[Optional] Planned completion date: 5/7/2021 |
|
[b621][CAT3][PTR][VW MEB EBB Wave1.5][CR: 5144832][Retest-ID 5352547] External PTS linearization: Time information of PTS PreProc measurement signals not correctly implemented The linearization of the PTS sensors shall be changed from the internal routine based on the MPS to an external routine based on an external reference sensor on the production line. The external linearization is necessary for Wave 2 devices to achieve the required robustness and accuracy. The linearization algorithm requires PTS PreProc measurement signals with time information.
The external linearization calculates the PTS LUT values on an external station using an external reference sensor and the PTS PreProc values provided by the EBB device via 5ms DAQ-Event. A time information of the PreProc vlues is required for signal validation.
Variant 1:
Usage of XCP timestamp. According to the description below there is an option to receive a timestamp for the sensor values. Is this option available in EBB software?
Variant 2:
Usage of a roling counter which is enclosed in the PTS PreProc measurent signal. The 12bit PreProc Signal could be combined with a 20bit roling counter to a 32bit measurement signal. The counter could be increased each millisecond.
The second variant would be the prefered solution. Can be tested. | [b621][CAT3][PTR][VW MEB EBB Wave1.5][CR: 5144832][Retest-ID 5352547] External PTS linearization: Time information of PTS PreProc measurement signals not correctly implemented The linearization of the PTS sensors shall be changed from the internal routine based on the MPS to an external routine based on an external reference sensor on the production line. The external linearization is necessary for Wave 2 devices to achieve the required robustness and accuracy. The linearization algorithm requires PTS PreProc measurement signals with time information.
The external linearization calculates the PTS LUT values on an external station using an external reference sensor and the PTS PreProc values provided by the EBB device via 5ms DAQ-Event. A time information of the PreProc vlues is required for signal validation.
Variant 1:
Usage of XCP timestamp. According to the description below there is an option to receive a timestamp for the sensor values. Is this option available in EBB software?
Variant 2:
Usage of a roling counter which is enclosed in the PTS PreProc measurent signal. The 12bit PreProc Signal could be combined with a 20bit roling counter to a 32bit measurement signal. The counter could be increased each millisecond.
The second variant would be the prefered solution. Can be tested. |
|
[b521][CAT3][CASE][VW_MEB_SCS] Setting the signal TS_Status_DrzReg/TS_Status_DrzReg_sek to “Fehler”, the signals “ESC_Achsdrehzahl_*” won’t show the value “Fehler” Preconditions / Ausgangsituation: standstill, all Motor_55 signals valid
SW SCS: b521
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Setting the signal TS_Status_DrzReg/TS_Status_DrzReg_sek from "Init" to “Fehler”
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
1. Signals “ESC_Achsdrehzahl_*” show the value “Fehler”
2. ESP_Lampe is "on"
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
1. Signals “ESC_Achsdrehzahl_*” won't show the value “Fehler”
2. ESP_Lampe is "off"
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
TSM_EBC_nASR-nMSR_162
TSM_EBC_nASR-nMSR_164
--------------------------------------------------------------------------------
Impact / Einfluss:
Cusotmer complaints/confusion Retest with a513 and f521 | [b521][CAT3][CASE][VW_MEB_SCS] Setting the signal TS_Status_DrzReg/TS_Status_DrzReg_sek to “Fehler”, the signals “ESC_Achsdrehzahl_*” won’t show the value “Fehler” Preconditions / Ausgangsituation: standstill, all Motor_55 signals valid
SW SCS: b521
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Setting the signal TS_Status_DrzReg/TS_Status_DrzReg_sek from "Init" to “Fehler”
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
1. Signals “ESC_Achsdrehzahl_*” show the value “Fehler”
2. ESP_Lampe is "on"
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
1. Signals “ESC_Achsdrehzahl_*” won't show the value “Fehler”
2. ESP_Lampe is "off"
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
TSM_EBC_nASR-nMSR_162
TSM_EBC_nASR-nMSR_164
--------------------------------------------------------------------------------
Impact / Einfluss:
Cusotmer complaints/confusion Retest with a513 and f521 |
|
Parameter adaptation for HJB_PHEV Variant New Vehicle HJB_PHEV is added to the project.
CR for:
1, Create a new Parameter variant for HJB_PHEV
Take HHN_PHEV parameter as baseline
2, Adapt the parameter for HJB_PHEV according to CDS and for Gen4 Actuator (HJB_PHEV use Gen4 actuator)
CDS attached. <ACH> (12.07.21 - 21:50):
--------------------------------------------------------------------------------
Brief investigation comment:
CFC parameters to be adjusted as per the calculation sheet attached for variant HJB_PHEV.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <A.Cherukuri>: <Title> / Verifier: <G.Godlewsky> (18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [x] or No [] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 05.07.21 - 09:30:
Please investigate this point and advise the next steps. | Parameter adaptation for HJB_PHEV Variant New Vehicle HJB_PHEV is added to the project.
CR for:
1, Create a new Parameter variant for HJB_PHEV
Take HHN_PHEV parameter as baseline
2, Adapt the parameter for HJB_PHEV according to CDS and for Gen4 Actuator (HJB_PHEV use Gen4 actuator)
CDS attached. <ACH> (12.07.21 - 21:50):
--------------------------------------------------------------------------------
Brief investigation comment:
CFC parameters to be adjusted as per the calculation sheet attached for variant HJB_PHEV.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <A.Cherukuri>: <Title> / Verifier: <G.Godlewsky> (18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [x] or No [] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 05.07.21 - 09:30:
Please investigate this point and advise the next steps. |
|
GAC A39 MPS issue via change AMC component to resolve it Activities Description:
1. Perform Change Analysis Handling per SW Release and one Build and Clustered Input Changes (Aligned Cluster with System):
1.1 Perform Initial Impact analysis
1.1.1 Identify detail change scope per this SW release
Based on Proejct SW engineering traceability matrix which initial prepared in project kick off phase W130j package, the matrix contains full technical required changes (Customer, System, ECU HW etc) input to SW project to realize, then SWPM cross analyze those changes with Project SW Release Plan defined features per this release planned, coordinate and align with system cluastered changes and system release plan, identify the input changes allocated to this release phase applied as detail change scope.
Notes: The granularity of the unit of input changes need to be defined inside team, but normally it can be documentaion sub chapters which contains a non-divided SW fucntions, it also can be directly a DOORs items or grouped DOORs items.
1.1.2 Identify SW release allocated detail changes to SW features, behaviours and SW Components: define each granulated change the general allocation to SW features, behaviours and SW Components, be able to compile the output information used for: SW project detail scheduling and planning, and Furthe SW requirement analyzing and handling.
Project SW engineering traceability Matrix PTC SI Link:
<Project SW engineering traceability Matrix PTC SI Link:>
1.2 Perform Detail Impact Analysis
Based on initial imapct analysis result in SW engineering traceability matrix, the detail analysis can be performed, and create detail Imapct Analysis (IA) doc recoding this release allocated input changes the full impact from W130j-W220j (SWE1-SWE6, MAN3, Safety, Industralization).
The analysis activity was deployed by Initial impact analysis result with PTC IM CR clustered Features and the SWC clustered Tasks, assigned to the proejct team all together to be worked out.
For procedures ZF Level 3 WI defined for IA:
1. W140j and SWE1, shall follow
C_066_3_SSE_036_EN Detailed Impact Analysis for SW Requirements Work Instruction
and
Chapter: 3. Impact Analysis on SWE.1 Change Request level
Input for this WP are:
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. SW engineering traceability matrix
Output of this WP:
1. SW engineering traceability matrix (Update)
2. SW Project Schedule (Update)
3. Imapct Analysis Doc
Initial Impact Analysis:
Responsible: SW Project CCB (SWPM Lead)
Reviewer/Approver: SWPM Supervisor
Detail Impact Analysis:
Responsible: SWPM (Lead), SWRM, FunctionModule Developer, LSE, SWTM, SWTM, Tester
Reviewer/Approver: SWPM This is a cluster CR. | GAC A39 MPS issue via change AMC component to resolve it Activities Description:
1. Perform Change Analysis Handling per SW Release and one Build and Clustered Input Changes (Aligned Cluster with System):
1.1 Perform Initial Impact analysis
1.1.1 Identify detail change scope per this SW release
Based on Proejct SW engineering traceability matrix which initial prepared in project kick off phase W130j package, the matrix contains full technical required changes (Customer, System, ECU HW etc) input to SW project to realize, then SWPM cross analyze those changes with Project SW Release Plan defined features per this release planned, coordinate and align with system cluastered changes and system release plan, identify the input changes allocated to this release phase applied as detail change scope.
Notes: The granularity of the unit of input changes need to be defined inside team, but normally it can be documentaion sub chapters which contains a non-divided SW fucntions, it also can be directly a DOORs items or grouped DOORs items.
1.1.2 Identify SW release allocated detail changes to SW features, behaviours and SW Components: define each granulated change the general allocation to SW features, behaviours and SW Components, be able to compile the output information used for: SW project detail scheduling and planning, and Furthe SW requirement analyzing and handling.
Project SW engineering traceability Matrix PTC SI Link:
<Project SW engineering traceability Matrix PTC SI Link:>
1.2 Perform Detail Impact Analysis
Based on initial imapct analysis result in SW engineering traceability matrix, the detail analysis can be performed, and create detail Imapct Analysis (IA) doc recoding this release allocated input changes the full impact from W130j-W220j (SWE1-SWE6, MAN3, Safety, Industralization).
The analysis activity was deployed by Initial impact analysis result with PTC IM CR clustered Features and the SWC clustered Tasks, assigned to the proejct team all together to be worked out.
For procedures ZF Level 3 WI defined for IA:
1. W140j and SWE1, shall follow
C_066_3_SSE_036_EN Detailed Impact Analysis for SW Requirements Work Instruction
and
Chapter: 3. Impact Analysis on SWE.1 Change Request level
Input for this WP are:
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. SW engineering traceability matrix
Output of this WP:
1. SW engineering traceability matrix (Update)
2. SW Project Schedule (Update)
3. Imapct Analysis Doc
Initial Impact Analysis:
Responsible: SW Project CCB (SWPM Lead)
Reviewer/Approver: SWPM Supervisor
Detail Impact Analysis:
Responsible: SWPM (Lead), SWRM, FunctionModule Developer, LSE, SWTM, SWTM, Tester
Reviewer/Approver: SWPM This is a cluster CR. |
|
GAC A39 MPS issue via change AMC component to resolve it Activity Description:
This working package deal with a final interation of all realized W150j and W210j1&j2 tasks as SW Architecure and SWCs to be integrated to a completed executable SW build which shall matches this release defined change scope, fucnitons and requirements defined in SW Engineering Traceability Matrix and Software Release Plan.
It follows ZF Level 3 WI C_040_3_SSE_063_EN GenC Software Integration Work Instruction and breakdown as below activities:
Before any of below activities, Gate 2 - Software Design Freeze must be reviewed and passed! (Refer to W130j Software Reelase Gate Review Activities)
4.1.Project Initiation
4.2.Composite Component Integration
4.3.Configure Repository
4.4.Configure Integration Model
4.5.Update of the Memory Configuration
4.6.AUTOSAR ECU Model Configuration
4.7.Build Configuration Updates
Below Activities (4.8-4.12) directly lead by SWPM during SWPM performing Gate 3 - Software Freeze Review:
4.8.Baseline Check
4.9.Software Build
4.10.Tune Generation for Test
4.11.Software Confidence Test
4.12.Approval of Software Build (This is responsed by SWPM and performed before Jenkins formal build)
Below activities is repsonsible by SWPM and performed within W130j Software Release Gate Review Activities as Gate 3 Software Freeze and/or in Gate 4 Software Release, however it supported from SW Integrator and LSE:
4.13.Configuration of Delivery
4.14.Acceptance of Delivery for Release
4.15.Documentation of Software Delivery
4.16.Delivery of Software Release
4.17.Review and Update of Software Tune
Input of this WP are:
1. SW Architecture
2. SW Component Source
3. Configured AutoSAR Stack
4. SW Component Integration Status Report
4. SW Requirement and Baseline
5. SW Engineering Traceability Matrix
6. SW Release Plan
7. SW BOM
8. Approved SW Gate 2 Software Design Freeze Reiew Checklist (same as SW Engineering Checklist)
9. Prepared Jenkins Task
Output of this WP are:
1. SW Assemble Build in Jenkins (S1,2,3...)
2. Confidence Test Report per assemble
Responsible: SW Integrator, SWPM (4.12-4.17)
Support: SW Requirement Engineer, SW FM Developer, LSE
Reviewer: SW Integrator Supervisor This is cluster CR. | GAC A39 MPS issue via change AMC component to resolve it Activity Description:
This working package deal with a final interation of all realized W150j and W210j1&j2 tasks as SW Architecure and SWCs to be integrated to a completed executable SW build which shall matches this release defined change scope, fucnitons and requirements defined in SW Engineering Traceability Matrix and Software Release Plan.
It follows ZF Level 3 WI C_040_3_SSE_063_EN GenC Software Integration Work Instruction and breakdown as below activities:
Before any of below activities, Gate 2 - Software Design Freeze must be reviewed and passed! (Refer to W130j Software Reelase Gate Review Activities)
4.1.Project Initiation
4.2.Composite Component Integration
4.3.Configure Repository
4.4.Configure Integration Model
4.5.Update of the Memory Configuration
4.6.AUTOSAR ECU Model Configuration
4.7.Build Configuration Updates
Below Activities (4.8-4.12) directly lead by SWPM during SWPM performing Gate 3 - Software Freeze Review:
4.8.Baseline Check
4.9.Software Build
4.10.Tune Generation for Test
4.11.Software Confidence Test
4.12.Approval of Software Build (This is responsed by SWPM and performed before Jenkins formal build)
Below activities is repsonsible by SWPM and performed within W130j Software Release Gate Review Activities as Gate 3 Software Freeze and/or in Gate 4 Software Release, however it supported from SW Integrator and LSE:
4.13.Configuration of Delivery
4.14.Acceptance of Delivery for Release
4.15.Documentation of Software Delivery
4.16.Delivery of Software Release
4.17.Review and Update of Software Tune
Input of this WP are:
1. SW Architecture
2. SW Component Source
3. Configured AutoSAR Stack
4. SW Component Integration Status Report
4. SW Requirement and Baseline
5. SW Engineering Traceability Matrix
6. SW Release Plan
7. SW BOM
8. Approved SW Gate 2 Software Design Freeze Reiew Checklist (same as SW Engineering Checklist)
9. Prepared Jenkins Task
Output of this WP are:
1. SW Assemble Build in Jenkins (S1,2,3...)
2. Confidence Test Report per assemble
Responsible: SW Integrator, SWPM (4.12-4.17)
Support: SW Requirement Engineer, SW FM Developer, LSE
Reviewer: SW Integrator Supervisor This is cluster CR. |
|
[SWE.6][SiL][MS][WS][FBP3]OVER_VOLTAGE_FAULT is not cleared at all This CR is used to Plan/Monitor the SWE 3 thru 4 work for the bug fixes for FC00 SW *
2021-07-07 PuckettM
*
Ready for FC00 Bug Fixes. | [SWE.6][SiL][MS][WS][FBP3]OVER_VOLTAGE_FAULT is not cleared at all This CR is used to Plan/Monitor the SWE 3 thru 4 work for the bug fixes for FC00 SW *
2021-07-07 PuckettM
*
Ready for FC00 Bug Fixes. |
|
[SWE.6][SiL][MS][WS][FBP3]OVER_VOLTAGE_FAULT is not cleared at all This CR is used to Plan/Monitor the SWE 1 work for the bug fixes for FC00 SW This CR will be used to fix OP's /issues raised against software requirements
Following OPs will be covered under this CR:
OP:5431787
OP:5419648
See attached emails for analysis. | [SWE.6][SiL][MS][WS][FBP3]OVER_VOLTAGE_FAULT is not cleared at all This CR is used to Plan/Monitor the SWE 1 work for the bug fixes for FC00 SW This CR will be used to fix OP's /issues raised against software requirements
Following OPs will be covered under this CR:
OP:5431787
OP:5419648
See attached emails for analysis. |
|
[SWE.6][SiL][MS][WS][FBP3]OVER_VOLTAGE_FAULT is not cleared at all D2 -- Problem Description (R: Originator):
OVER_VOLTAGE_FAULT is not cleared at all even if battery voltage will be set to 13 V.
Associated Requirement IDs (R: Originator):
/Gen-4/04 Software/01 Software Requirements Analysis/GenC Software Requirements Manage Supply (Baseline: 160.0)
Operating Environment (R: Originator):
Provide a list of the operating variables used during the test (i.e. DUT, Execution environment, ControlDesk version, Canalyzer version, etc.) ASY-FI048465-S2-V00FBP3_0317
Associated Test Cases (R: Originator):
/Gen-4/04 Software/01 Software Requirements Analysis/GenC Software Requirements Manage Supply (Baseline: 160.0) WS_SWE.6_MS_640
Preconditions: (R: Originator):
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
Please add Log Files and Par files captured during the testing and add it as an attachment to the open point. Outline briefly the file added and the content that it describes
Copy the following text to the conclusion section of the Open Point after it is created.
D3 -- Established Interim Containment Action (R: ProblemOwner):
Outline the ICA
D4 -- Verified Root Cause (R: ProblemOwner):
Describe the result of the root cause analysis --> AGGREGATE RESULT OF ALL ACTION ITEMS HERE ToDo - Verification to be executed on BA00++ | [SWE.6][SiL][MS][WS][FBP3]OVER_VOLTAGE_FAULT is not cleared at all D2 -- Problem Description (R: Originator):
OVER_VOLTAGE_FAULT is not cleared at all even if battery voltage will be set to 13 V.
Associated Requirement IDs (R: Originator):
/Gen-4/04 Software/01 Software Requirements Analysis/GenC Software Requirements Manage Supply (Baseline: 160.0)
Operating Environment (R: Originator):
Provide a list of the operating variables used during the test (i.e. DUT, Execution environment, ControlDesk version, Canalyzer version, etc.) ASY-FI048465-S2-V00FBP3_0317
Associated Test Cases (R: Originator):
/Gen-4/04 Software/01 Software Requirements Analysis/GenC Software Requirements Manage Supply (Baseline: 160.0) WS_SWE.6_MS_640
Preconditions: (R: Originator):
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
Please add Log Files and Par files captured during the testing and add it as an attachment to the open point. Outline briefly the file added and the content that it describes
Copy the following text to the conclusion section of the Open Point after it is created.
D3 -- Established Interim Containment Action (R: ProblemOwner):
Outline the ICA
D4 -- Verified Root Cause (R: ProblemOwner):
Describe the result of the root cause analysis --> AGGREGATE RESULT OF ALL ACTION ITEMS HERE ToDo - Verification to be executed on BA00++ |
|
[EPB] Review of Lastenheft EPB_Sicherheitskonzept_MQB48W 1.
The VW Lastenheft "EPB_Sicherheitskonzept_MQB48W" was updated.
Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-000f6525?doors.view=00000036
This LH shall be reviewed and the links shall be created.
Consider the attachments.
2.
In Addition check the LH MQB48_W_EPB
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-000e8401?doors.view=000000b6
Therein are ASIL Level given in the Attribut "ASIL"
Please check if the required ASIL Level can be fullfilled and accepted by us. If yes link it to the corresponding safety requirement.
If no link can be established give a comment in the LH. Adrian Fartaes [17.01.2022]
Brief investigation comments
In MQB48_W_EPB document, there were 75 customer requirements who was partialy linked or linked to SyRS, without any link from SyRS to FSC.
As a result:
- new links from Customer RQs to SyRS has been created;
- new links from SyRS to FSC were created, taking into account the corresponding ASIL level;
- some customer requirements (with safety design constrains), which has been linked to SyRS chapter 5 ( System Non-Functional Requirements) or chapter 7 (System Information), are out of scope for FSC. For this, the necessary comments will be added in the specific customer RQs.
Risk: high
Proposal of next steps :
- review meeting to verify the links to Non-Functional Requriements;
- adding the coresponding comments to customer RQs with safety design constrains, with links to SyRS, chapter 5 ( System Non-Functional Requirements);
- complete the task by checking the created links for the requirements that were analyzed (customer RQs to SyRS; SyRS to FSC) | [EPB] Review of Lastenheft EPB_Sicherheitskonzept_MQB48W 1.
The VW Lastenheft "EPB_Sicherheitskonzept_MQB48W" was updated.
Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-000f6525?doors.view=00000036
This LH shall be reviewed and the links shall be created.
Consider the attachments.
2.
In Addition check the LH MQB48_W_EPB
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-000e8401?doors.view=000000b6
Therein are ASIL Level given in the Attribut "ASIL"
Please check if the required ASIL Level can be fullfilled and accepted by us. If yes link it to the corresponding safety requirement.
If no link can be established give a comment in the LH. Adrian Fartaes [17.01.2022]
Brief investigation comments
In MQB48_W_EPB document, there were 75 customer requirements who was partialy linked or linked to SyRS, without any link from SyRS to FSC.
As a result:
- new links from Customer RQs to SyRS has been created;
- new links from SyRS to FSC were created, taking into account the corresponding ASIL level;
- some customer requirements (with safety design constrains), which has been linked to SyRS chapter 5 ( System Non-Functional Requirements) or chapter 7 (System Information), are out of scope for FSC. For this, the necessary comments will be added in the specific customer RQs.
Risk: high
Proposal of next steps :
- review meeting to verify the links to Non-Functional Requriements;
- adding the coresponding comments to customer RQs with safety design constrains, with links to SyRS, chapter 5 ( System Non-Functional Requirements);
- complete the task by checking the created links for the requirements that were analyzed (customer RQs to SyRS; SyRS to FSC) |
|
[Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR | [Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR |
|
[Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM 2023-04-27, C. Diefenthal: covered by CR 7326244 and 7326305 | [Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM 2023-04-27, C. Diefenthal: covered by CR 7326244 and 7326305 |
|
[Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR | [Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR |
|
[Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR | [Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR |
|
[Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No action for EL required | [Defect]: [DCRP 25.03 ML3][EPB] PRF 43 - Diagnostic CloseBrakeRx This Description has to be modified by PSM No action for EL required |
|
[Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR | [Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR |
|
[Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR | [Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR |
|
[Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR | [Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR |
|
[Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR | [Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No requirements to be derived for this release.
=> reject CR |
|
[Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No action for EL required | [Defect]: [DCRP 24.03 ML3][EPB] PRF 42 - Diagnostic OpenBrakeRx This Description has to be modified by PSM No action for EL required |
|
[DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support PSM (K. Hammer) (30.11.22):
--------------------------------------------------------------------------------
Aim:
Minor changes for Periodic Technical Inspection Support.
___
Description:
Update S/W Requirements according to CR 5566174
___
Source Document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
Update S/W Requirements according to CR 5566174
SyDesign Filter: Attribute '015_CM Reference' contains '5566174'
Applicable Doors Module Baselines:
SyDesign: 9.1 or later
___
Output Document(s):
DOORS SwRS Module
___
Acceptance Criteria(s):
1. All the new / changed Requirements are derived in Daimler MMA SwRS Modules.
2. Conflicts or deviations from the existing SW Requirements are identified and addressed.
3. All necessary SWE.1 links to other DOORS Modules are provided. -----------------------------------------------------------------------------------------------------------------------------------------------------
[13.01.2023, Ilakkiya (Z0107096)]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
Inputs:
Daimler EPB - SyDesign @ 9.1
Total 5 objects (SSM – 4 and ESS - 1) are affected with the System CR 5566174
1. ESS part (1 objects) has been worked with CR 6649743
2. Review of 4 SyDesign objects (PBC) should be performed as part of this CR
3. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
4. 4 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
5. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
---------------------------------------------------------------------------------------------------------------------
Complexity: [Medium]
Experience: [Known Topic]
Carry Over: [Basis available]
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
a) Title/Header: Update SW Requirements
Description:
Input : Daimler EPB - SyDesign @ 9.1
Filter: Attribute '015_CM Reference' contains '5566174'
Total 5 objects (SSM – 4 and ESS - 1) are affected with the System CR 5566174
1. ESS part (1 objects) has been worked with CR 6649743
2. Review of 4 SyDesign objects (PBC) should be performed as part of this CR
3. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
4. 4 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
5. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
Acceptance Criteria(s):
1. All SWE.1 relevant attributes are correctly updated
2. New/Modified requirements (SSM) have been derived and Reviewed
Review Type: Stakeholder review [YES], Formal review [YES]
Review Selection Reason: Requirements will be modified and rejected with this CR
Review Department(s): SWE.1, SWE.2, SWE.3 and SWE.6
==> What to review: Please check against the corresponding ALM_Task Notes to identify and confirm the SwRS module baselines to be reviewed!
==> What checklists: Please check against the corresponding ALM_Task Notes to identify, confirm and add the checklists!
Estimated effort: 12 h
----------------------------------------------------------------------------------------------------------------------------------------------------- | [DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support PSM (K. Hammer) (30.11.22):
--------------------------------------------------------------------------------
Aim:
Minor changes for Periodic Technical Inspection Support.
___
Description:
Update S/W Requirements according to CR 5566174
___
Source Document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
Update S/W Requirements according to CR 5566174
SyDesign Filter: Attribute '015_CM Reference' contains '5566174'
Applicable Doors Module Baselines:
SyDesign: 9.1 or later
___
Output Document(s):
DOORS SwRS Module
___
Acceptance Criteria(s):
1. All the new / changed Requirements are derived in Daimler MMA SwRS Modules.
2. Conflicts or deviations from the existing SW Requirements are identified and addressed.
3. All necessary SWE.1 links to other DOORS Modules are provided. -----------------------------------------------------------------------------------------------------------------------------------------------------
[13.01.2023, Ilakkiya (Z0107096)]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
Inputs:
Daimler EPB - SyDesign @ 9.1
Total 5 objects (SSM – 4 and ESS - 1) are affected with the System CR 5566174
1. ESS part (1 objects) has been worked with CR 6649743
2. Review of 4 SyDesign objects (PBC) should be performed as part of this CR
3. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
4. 4 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
5. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
---------------------------------------------------------------------------------------------------------------------
Complexity: [Medium]
Experience: [Known Topic]
Carry Over: [Basis available]
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
a) Title/Header: Update SW Requirements
Description:
Input : Daimler EPB - SyDesign @ 9.1
Filter: Attribute '015_CM Reference' contains '5566174'
Total 5 objects (SSM – 4 and ESS - 1) are affected with the System CR 5566174
1. ESS part (1 objects) has been worked with CR 6649743
2. Review of 4 SyDesign objects (PBC) should be performed as part of this CR
3. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
4. 4 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
5. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
Acceptance Criteria(s):
1. All SWE.1 relevant attributes are correctly updated
2. New/Modified requirements (SSM) have been derived and Reviewed
Review Type: Stakeholder review [YES], Formal review [YES]
Review Selection Reason: Requirements will be modified and rejected with this CR
Review Department(s): SWE.1, SWE.2, SWE.3 and SWE.6
==> What to review: Please check against the corresponding ALM_Task Notes to identify and confirm the SwRS module baselines to be reviewed!
==> What checklists: Please check against the corresponding ALM_Task Notes to identify, confirm and add the checklists!
Estimated effort: 12 h
----------------------------------------------------------------------------------------------------------------------------------------------------- |
|
[DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support This Description has to be modified by PSM 2023-04-27, C. Diefenthal: covered by CR 7326244 and 7326305 | [DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support This Description has to be modified by PSM 2023-04-27, C. Diefenthal: covered by CR 7326244 and 7326305 |
|
[DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support This Description has to be modified by PSM Will be done with CR 7326305 | [DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support This Description has to be modified by PSM Will be done with CR 7326305 |
|
[DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support Kerstin Hammer (25.08.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Requirements need to be adapted according to customer requirements.
Customer LAH: HU-Modus der EPB ausführen
-------------------------------------------------------------------------------- Kerstin Hammer (25.08.22):
--------------------------------------------------------------------------------
Brief investigation comment:
Requirements need to be adapted on SYS.2 & SYS.3 level.
Manual transmission needs to be removed.
All requirments need to be changed from "can be adapted" to done.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for K. Hammer / Verifier: B. Miehling (5 h)
-------------------------------------------------------------------------------- | [DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support Kerstin Hammer (25.08.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Requirements need to be adapted according to customer requirements.
Customer LAH: HU-Modus der EPB ausführen
-------------------------------------------------------------------------------- Kerstin Hammer (25.08.22):
--------------------------------------------------------------------------------
Brief investigation comment:
Requirements need to be adapted on SYS.2 & SYS.3 level.
Manual transmission needs to be removed.
All requirments need to be changed from "can be adapted" to done.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for K. Hammer / Verifier: B. Miehling (5 h)
-------------------------------------------------------------------------------- |
|
[DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support This Description has to be modified by PSM No action for EL required | [DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support This Description has to be modified by PSM No action for EL required |
|
[DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support Benjamin Miehling (28.06.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Review of Asil related REQs in customer specifications
--------------------------------------------------------------------------------
Please review following customer specifications regarding Safety goals
* HU-Modus der EPB ausfuehren Eduard Szucs (23 February 2023):
----------------------------------------------------------------
Brief investigation comments:
Regarding the DOORS module HU-Modus der EPB ausfuehren, no change is required since the requirements that have their ASIL level A, B, C or D are set to not agreed.
However, changes in this open point have been made with CR 5566174 on a system level, thus the safety analysis is conducted. The following updates are required to cover this CR from a safety point of view:
SYS 3
1. TSC: Since the ActuatorState is removed from SyDesign, the requirement TSC 10139 has to be rejected.
2. SyDesign: The safety placeholder SyDesign 7543 has to be rejected since it is linked towards TSC 10139 (rejected as mentioned above).
3. No impact on the FTA.
SYS2
1. SyRS: A new requirement (safety placeholder) is needed in chapter 3.4.2 PRF40 - Periodic Technical Inspection Support, and be linked towards FSC 1051.
2. No impact on the FMEA.
----------------------------------------------------------------
Risk (low / medium / high): low
----------------------------------------------------------------
Next steps proposal (including effort in hours and verifier):
- Task for Eduard Szucs: On SYS3, update the SyDesign and TSC as mentioned above (12 h analysis + implementation, 3 h review with Gabriel Vardarie)
- Task for Eduard Szucs: On SYS2, update the SyRS module as mentioned above (8 h analysis + implementation, 2 h review with Gabriel Vardarie)
---------------------------------------------------------------- | [DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support Benjamin Miehling (28.06.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Review of Asil related REQs in customer specifications
--------------------------------------------------------------------------------
Please review following customer specifications regarding Safety goals
* HU-Modus der EPB ausfuehren Eduard Szucs (23 February 2023):
----------------------------------------------------------------
Brief investigation comments:
Regarding the DOORS module HU-Modus der EPB ausfuehren, no change is required since the requirements that have their ASIL level A, B, C or D are set to not agreed.
However, changes in this open point have been made with CR 5566174 on a system level, thus the safety analysis is conducted. The following updates are required to cover this CR from a safety point of view:
SYS 3
1. TSC: Since the ActuatorState is removed from SyDesign, the requirement TSC 10139 has to be rejected.
2. SyDesign: The safety placeholder SyDesign 7543 has to be rejected since it is linked towards TSC 10139 (rejected as mentioned above).
3. No impact on the FTA.
SYS2
1. SyRS: A new requirement (safety placeholder) is needed in chapter 3.4.2 PRF40 - Periodic Technical Inspection Support, and be linked towards FSC 1051.
2. No impact on the FMEA.
----------------------------------------------------------------
Risk (low / medium / high): low
----------------------------------------------------------------
Next steps proposal (including effort in hours and verifier):
- Task for Eduard Szucs: On SYS3, update the SyDesign and TSC as mentioned above (12 h analysis + implementation, 3 h review with Gabriel Vardarie)
- Task for Eduard Szucs: On SYS2, update the SyRS module as mentioned above (8 h analysis + implementation, 2 h review with Gabriel Vardarie)
---------------------------------------------------------------- |
|
[DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support SWPM (A. Veling) (06.12.22 - 16:16):
--------------------------------------------------------------------------------
Please review the Requirements update and check if the software design needs to be adapted as well.
SyDesign CR 5566174
SyDesign Filter: Attribute '015_CM Reference' contains '5566174'
Applicable Doors Module Baselines:
SyDesign: 9.1 or later
--------------------------------------------------------------------------------
Kerstin Hammer (25.08.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Requirements need to be adapted according to customer requirements.
Customer LAH: HU-Modus der EPB ausführen
--------------------------------------------------------------------------------
[DCRP 22.03] [EPB] PRF 40 - Periodic Technical Inspection Support
This generic Open Point is used to track all systems and software engineering activities for:
PRF 40 - Periodic Technical Inspection Support
Feature Increment 2
Final function w/o trimming <Aruna Dadige> (15.12.22 - 15:56):
--------------------------------------------------------------------------------
Brief investigation comment:
As per the system design update, please update follwing changes in software for Hu Mode
->Please remove manual tranmission check for rollerbench detection.
->Please remove actuator state check to update SSMPbOutApplyReleaseRequest as RollerbenchApply.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Aruna D>: <[DCRP 22.03 ML2][EPB][SWE.3] PRF 40 - Periodic Technical Inspection Support> / Verifier: <Praveen K> (12h)
-------------------------------------------------------------------------------- | [DCRP 22.03 ML2][EPB] PRF 40 - Periodic Technical Inspection Support SWPM (A. Veling) (06.12.22 - 16:16):
--------------------------------------------------------------------------------
Please review the Requirements update and check if the software design needs to be adapted as well.
SyDesign CR 5566174
SyDesign Filter: Attribute '015_CM Reference' contains '5566174'
Applicable Doors Module Baselines:
SyDesign: 9.1 or later
--------------------------------------------------------------------------------
Kerstin Hammer (25.08.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Requirements need to be adapted according to customer requirements.
Customer LAH: HU-Modus der EPB ausführen
--------------------------------------------------------------------------------
[DCRP 22.03] [EPB] PRF 40 - Periodic Technical Inspection Support
This generic Open Point is used to track all systems and software engineering activities for:
PRF 40 - Periodic Technical Inspection Support
Feature Increment 2
Final function w/o trimming <Aruna Dadige> (15.12.22 - 15:56):
--------------------------------------------------------------------------------
Brief investigation comment:
As per the system design update, please update follwing changes in software for Hu Mode
->Please remove manual tranmission check for rollerbench detection.
->Please remove actuator state check to update SSMPbOutApplyReleaseRequest as RollerbenchApply.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Aruna D>: <[DCRP 22.03 ML2][EPB][SWE.3] PRF 40 - Periodic Technical Inspection Support> / Verifier: <Praveen K> (12h)
-------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM PSM (K. Hammer) (29.08.22):
--------------------------------------------------------------------------------
No change required for X0400. CR can be rejected.
-------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode No Action for EL required No action for EL required | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode No Action for EL required No action for EL required |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM SummaryDescription incl. Input and expected outputEffort(h)OwnerReviewer
Task 1[DCRP 30.03][EPB] SYS-RE-AD Manual Maintenance Mode5 interfaces to be added to SIT
5 interfaces to be added to ESS-CT
1 Datatype to be added to CT_Datatyper
54 Requirements to be derived from Bremsbelagwechsel ermoeglichen into SyDesign
SyRS to be updated too, as verification can be done more properly on this level. 60 hrsC. DiefenthalK. Hammer | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode This Description has to be modified by PSM SummaryDescription incl. Input and expected outputEffort(h)OwnerReviewer
Task 1[DCRP 30.03][EPB] SYS-RE-AD Manual Maintenance Mode5 interfaces to be added to SIT
5 interfaces to be added to ESS-CT
1 Datatype to be added to CT_Datatyper
54 Requirements to be derived from Bremsbelagwechsel ermoeglichen into SyDesign
SyRS to be updated too, as verification can be done more properly on this level. 60 hrsC. DiefenthalK. Hammer |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode Function to be derived and implemented according to customer requirements.
PRF 48 - Manual Maintenance Mode
Changes in SyDesign and SyRS made with CR 7291956.
Please analyse from Safety Point of view.
Check also carefully
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-12701-00143fc4?doors.view=00000003
This is currently contradicting MvK to enter maintenance mode. [12.04.2023] AFa: CR 7291956 still in planned.The analysis cannot be started.
[11.07.2023] AMu:
- Customer requirements are present in module Bremsbelagwechsel ermoeglichen (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001a2da8);
- There are 4 safety customer requirements (SZs) which are not agreed because the MB HARA is linked to the ZF HARA from other modules;
- This feature would impact SG 8, SG 6 (uninteded activation) and SG 3 (unintended deactivation).
- The safety concept needs to set with the required ASIL (dependant on the SG) barriers for the false activation and false deactivation situations.
Task (60hr):
- Create FSC Structure;
- Implement FSRs;
- Perform content walkthroughs, peer and formal reviews. | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode Function to be derived and implemented according to customer requirements.
PRF 48 - Manual Maintenance Mode
Changes in SyDesign and SyRS made with CR 7291956.
Please analyse from Safety Point of view.
Check also carefully
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-12701-00143fc4?doors.view=00000003
This is currently contradicting MvK to enter maintenance mode. [12.04.2023] AFa: CR 7291956 still in planned.The analysis cannot be started.
[11.07.2023] AMu:
- Customer requirements are present in module Bremsbelagwechsel ermoeglichen (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001a2da8);
- There are 4 safety customer requirements (SZs) which are not agreed because the MB HARA is linked to the ZF HARA from other modules;
- This feature would impact SG 8, SG 6 (uninteded activation) and SG 3 (unintended deactivation).
- The safety concept needs to set with the required ASIL (dependant on the SG) barriers for the false activation and false deactivation situations.
Task (60hr):
- Create FSC Structure;
- Implement FSRs;
- Perform content walkthroughs, peer and formal reviews. |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode [DCRP 30.03] [EPB] PRF 48 - Manual Maintenance Mode
This generic Open Point is used to track all systems and software engineering activities for:
PRF 48 - Manual Maintenance Mode
Feature Increment 2
Final function w/o trimming
This Change Request shall be used to implement the manual maintenance mode (customer name "MvK" - "Maintenance via Kombi")
This function has already been implemented in previous Daimler projects (MRA V1 BR213 and MRA V3 BR167)
The old Simulink model MvK shall be taken as baseline
and reworked for Autosar
Please also analyze if a new RTE Interface needs to be requested. <Uma Reddy HDR> 25-May-2023, 15:17 CET:
-> This taks will be realized with task of CR: 7749314.
-> Attaching email from Kai, this CR can be cancelled.
Kai Neitzert (13.03.23 - 17:25)
--------------------------------------------------------------------------------
Brief investigation comment:
Customer specification: "/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/DNG/Bremsbelagwechsel ermoeglichen"
The software component "MvK" is not part of SSM nor SSM_PB but integrated as c-file directly in host software.
It is archived in BrkSw pool:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/BrkSw/SwDevelopmentPool/Software/Components/Mvk/project.pj
--> must be added to MMA IBC archive from there.
The c-files are generated out of a Targetlink model which is located in an EPB SA project:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/EPB/CustomerDevelopment/Daimler/BR222/08%5fSoftware/S12x/InfoBase/MvK/project.pj
This model shall be updated and archived in BrkSw pool component "MvK" for future development.
The customer specification has not changed so there is no logic to be changed, but:
- the old model must be updated for TL 4.3 and Simulink 2017b
- in order to save wrapper code files, this model shall be enhanced by TL AUTOSAR interfaces according SwAD arxml specification (will be provided by SwAD Ben Bauer).
--> model changes to be investigated by SSM team.
- SW unit testing must done --> can this be done by SWE4 team of Bhargavi?
- Comms interfaces to be clarified --> SSM team with Comms team
- PBC interfaces to be clarified --> SSM team with Michael Minke
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode [DCRP 30.03] [EPB] PRF 48 - Manual Maintenance Mode
This generic Open Point is used to track all systems and software engineering activities for:
PRF 48 - Manual Maintenance Mode
Feature Increment 2
Final function w/o trimming
This Change Request shall be used to implement the manual maintenance mode (customer name "MvK" - "Maintenance via Kombi")
This function has already been implemented in previous Daimler projects (MRA V1 BR213 and MRA V3 BR167)
The old Simulink model MvK shall be taken as baseline
and reworked for Autosar
Please also analyze if a new RTE Interface needs to be requested. <Uma Reddy HDR> 25-May-2023, 15:17 CET:
-> This taks will be realized with task of CR: 7749314.
-> Attaching email from Kai, this CR can be cancelled.
Kai Neitzert (13.03.23 - 17:25)
--------------------------------------------------------------------------------
Brief investigation comment:
Customer specification: "/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/DNG/Bremsbelagwechsel ermoeglichen"
The software component "MvK" is not part of SSM nor SSM_PB but integrated as c-file directly in host software.
It is archived in BrkSw pool:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/BrkSw/SwDevelopmentPool/Software/Components/Mvk/project.pj
--> must be added to MMA IBC archive from there.
The c-files are generated out of a Targetlink model which is located in an EPB SA project:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/EPB/CustomerDevelopment/Daimler/BR222/08%5fSoftware/S12x/InfoBase/MvK/project.pj
This model shall be updated and archived in BrkSw pool component "MvK" for future development.
The customer specification has not changed so there is no logic to be changed, but:
- the old model must be updated for TL 4.3 and Simulink 2017b
- in order to save wrapper code files, this model shall be enhanced by TL AUTOSAR interfaces according SwAD arxml specification (will be provided by SwAD Ben Bauer).
--> model changes to be investigated by SSM team.
- SW unit testing must done --> can this be done by SWE4 team of Bhargavi?
- Comms interfaces to be clarified --> SSM team with Comms team
- PBC interfaces to be clarified --> SSM team with Michael Minke
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode [DCRP 30.03] [EPB] PRF 48 - Manual Maintenance Mode
This generic Open Point is used to track all systems and software engineering activities for:
PRF 48 - Manual Maintenance Mode
Feature Increment 2
Final function w/o trimming -------------------------------------------------------------------------------------------------------------------------------------------------
[04.01.2024, Z607934]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
As part of System Requirement CR 7291956, 33 objects (1 Information and 32 Requirements) have been covered.
Out of 32 Requirement,
*. 31 are Approved
*. 1 is Rejected
As part of this CR 31 Approved Requirement will be considered and brief analysis is as follows:
*. 26 Requirements are assigned to PerformManualMaintenanceMode Behaviour
*. 5 Requirements are assigned to ProvideDiagnosticServices Behaviour
ALM_Task 8519777 (PerformManualMaintenanceMode Behaviour) and ALM_Task 7918724 (ProvideDiagnosticServices Behaviour) is already existing and it has been assigned to the respective owners.
Since the scope of this CR is covered with ALM_Task 8519777 and 7918724, this CR can be Rejected.
--------------------------------------------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode [DCRP 30.03] [EPB] PRF 48 - Manual Maintenance Mode
This generic Open Point is used to track all systems and software engineering activities for:
PRF 48 - Manual Maintenance Mode
Feature Increment 2
Final function w/o trimming -------------------------------------------------------------------------------------------------------------------------------------------------
[04.01.2024, Z607934]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
As part of System Requirement CR 7291956, 33 objects (1 Information and 32 Requirements) have been covered.
Out of 32 Requirement,
*. 31 are Approved
*. 1 is Rejected
As part of this CR 31 Approved Requirement will be considered and brief analysis is as follows:
*. 26 Requirements are assigned to PerformManualMaintenanceMode Behaviour
*. 5 Requirements are assigned to ProvideDiagnosticServices Behaviour
ALM_Task 8519777 (PerformManualMaintenanceMode Behaviour) and ALM_Task 7918724 (ProvideDiagnosticServices Behaviour) is already existing and it has been assigned to the respective owners.
Since the scope of this CR is covered with ALM_Task 8519777 and 7918724, this CR can be Rejected.
--------------------------------------------------------------------------------------------------------------------- |
|
[DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode copy of CR 7473155 that was rejected by mistake
[DCRP 30.03] [EPB] PRF 48 - Manual Maintenance Mode
This generic Open Point is used to track all systems and software engineering activities for:
PRF 48 - Manual Maintenance Mode
Feature Increment 2
Final function w/o trimming
This Change Request shall be used to implement the manual maintenance mode (customer name "MvK" - "Maintenance via Kombi")
This function has already been implemented in previous Daimler projects (MRA V1 BR213 and MRA V3 BR167)
The old Simulink model MvK shall be taken as baseline
and reworked for Autosar
Please also analyze if a new RTE Interface needs to be requested. CCB - KNE - 05.06.23 - 16:54:
linked task 7749324 for implementation of all changes
<Uma Reddy HDR> 1-June-2023, 8:56IST:
--------------------------------------------------------------------------------------------
-> CR: 7473155, wsa cancelled by mistake, so this new CR created.
-> Task will be realized by not CR: 7749314,but with this CR only.
--------------------------------------------------------------------------------------------
<Uma Reddy HDR> 25-May-2023, 15:17 CET:
-> This taks will be realized with task of CR: 7749314.
-> Attaching email from Kai, this CR can be cancelled.
Kai Neitzert (13.03.23 - 17:25)
--------------------------------------------------------------------------------
Brief investigation comment:
Customer specification: "/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/DNG/Bremsbelagwechsel ermoeglichen"
The software component "MvK" is not part of SSM nor SSM_PB but integrated as c-file directly in host software.
It is archived in BrkSw pool:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/BrkSw/SwDevelopmentPool/Software/Components/Mvk/project.pj
--> must be added to MMA IBC archive from there.
The c-files are generated out of a Targetlink model which is located in an EPB SA project:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/EPB/CustomerDevelopment/Daimler/BR222/08%5fSoftware/S12x/InfoBase/MvK/project.pj
This model shall be updated and archived in BrkSw pool component "MvK" for future development.
The customer specification has not changed so there is no logic to be changed, but:
- the old model must be updated for TL 4.3 and Simulink 2017b
- in order to save wrapper code files, this model shall be enhanced by TL AUTOSAR interfaces according SwAD arxml specification (will be provided by SwAD Ben Bauer).
--> model changes to be investigated by SSM team.
- SW unit testing must done --> can this be done by SWE4 team of Bhargavi?
- Comms interfaces to be clarified --> SSM team with Comms team
- PBC interfaces to be clarified --> SSM team with Michael Minke
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------------------------------- | [DCRP 30.03 ML2][EPB] PRF 48 - Manual Maintenance Mode copy of CR 7473155 that was rejected by mistake
[DCRP 30.03] [EPB] PRF 48 - Manual Maintenance Mode
This generic Open Point is used to track all systems and software engineering activities for:
PRF 48 - Manual Maintenance Mode
Feature Increment 2
Final function w/o trimming
This Change Request shall be used to implement the manual maintenance mode (customer name "MvK" - "Maintenance via Kombi")
This function has already been implemented in previous Daimler projects (MRA V1 BR213 and MRA V3 BR167)
The old Simulink model MvK shall be taken as baseline
and reworked for Autosar
Please also analyze if a new RTE Interface needs to be requested. CCB - KNE - 05.06.23 - 16:54:
linked task 7749324 for implementation of all changes
<Uma Reddy HDR> 1-June-2023, 8:56IST:
--------------------------------------------------------------------------------------------
-> CR: 7473155, wsa cancelled by mistake, so this new CR created.
-> Task will be realized by not CR: 7749314,but with this CR only.
--------------------------------------------------------------------------------------------
<Uma Reddy HDR> 25-May-2023, 15:17 CET:
-> This taks will be realized with task of CR: 7749314.
-> Attaching email from Kai, this CR can be cancelled.
Kai Neitzert (13.03.23 - 17:25)
--------------------------------------------------------------------------------
Brief investigation comment:
Customer specification: "/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/DNG/Bremsbelagwechsel ermoeglichen"
The software component "MvK" is not part of SSM nor SSM_PB but integrated as c-file directly in host software.
It is archived in BrkSw pool:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/BrkSw/SwDevelopmentPool/Software/Components/Mvk/project.pj
--> must be added to MMA IBC archive from there.
The c-files are generated out of a Targetlink model which is located in an EPB SA project:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/EPB/CustomerDevelopment/Daimler/BR222/08%5fSoftware/S12x/InfoBase/MvK/project.pj
This model shall be updated and archived in BrkSw pool component "MvK" for future development.
The customer specification has not changed so there is no logic to be changed, but:
- the old model must be updated for TL 4.3 and Simulink 2017b
- in order to save wrapper code files, this model shall be enhanced by TL AUTOSAR interfaces according SwAD arxml specification (will be provided by SwAD Ben Bauer).
--> model changes to be investigated by SSM team.
- SW unit testing must done --> can this be done by SWE4 team of Bhargavi?
- Comms interfaces to be clarified --> SSM team with Comms team
- PBC interfaces to be clarified --> SSM team with Michael Minke
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------------------------------- |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release PSM (K. Hammer) (05.12.22):
--------------------------------------------------------------------------------
Aim:
Determine DAA TextmessageRequired needs to be added to project.
___
Description:
Update S/W Requirements according to CR 5565912
___
Source Document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
Update S/W Requirements according to CR 5565912
SyDesign Filter: Attribute '015_CM Reference' contains '5565912'
Applicable Doors Module Baselines:
SyDesign: 9.1 or later
___
Output Document(s):
DOORS SwRS Module
___
Acceptance Criteria(s):
1. All the new / changed Requirements are derived in Daimler MMA SwRS Modules.
2. Conflicts or deviations from the existing SW Requirements are identified and addressed.
3. All necessary SWE.1 links to other DOORS Modules are provided. -----------------------------------------------------------------------------------------------------------------------------------------------------
[13.01.2023, Ilakkiya (Z0107096)]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
Inputs:
Daimler EPB - SyDesign @ 9.1
Total 1 objects (SSM – 1) are affected with the System CR 5565912
1. Review of 1 SyDesign objects (SSM) should be performed as part of this CR
2. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
3. 1 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
4. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
---------------------------------------------------------------------------------------------------------------------
Complexity: [Medium]
Experience: [Known Topic]
Carry Over: [Basis available]
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
a) Title/Header: Derive SW Requirements (DaaTextMessageRequired)
Description:
Input : Daimler EPB - SyDesign @ 9.1
Filter: Attribute '015_CM Reference' contains '5565912'
Total 1 objects (SSM – 1) are affected with the System CR 5565912
1. Review of 1 SyDesign objects (SSM) should be performed as part of this CR
2. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
3. 1 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
4. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
Acceptance Criteria(s):
1. All SWE.1 relevant attributes are correctly updated
2. New/Modified requirements (SSM) have been derived and Reviewed
Review Type: Stakeholder review [YES], Formal review [YES]
Review Selection Reason: Requirements will be modified and rejected with this CR
Review Department(s): SWE.1, SWE.2, SWE.3 and SWE.6
==> What to review: Please check against the corresponding ALM_Task Notes to identify and confirm the SwRS module baselines to be reviewed!
==> What checklists: Please check against the corresponding ALM_Task Notes to identify, confirm and add the checklists!
Estimated effort: 10 h
----------------------------------------------------------------------------------------------------------------------------------------------------- | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release PSM (K. Hammer) (05.12.22):
--------------------------------------------------------------------------------
Aim:
Determine DAA TextmessageRequired needs to be added to project.
___
Description:
Update S/W Requirements according to CR 5565912
___
Source Document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
Update S/W Requirements according to CR 5565912
SyDesign Filter: Attribute '015_CM Reference' contains '5565912'
Applicable Doors Module Baselines:
SyDesign: 9.1 or later
___
Output Document(s):
DOORS SwRS Module
___
Acceptance Criteria(s):
1. All the new / changed Requirements are derived in Daimler MMA SwRS Modules.
2. Conflicts or deviations from the existing SW Requirements are identified and addressed.
3. All necessary SWE.1 links to other DOORS Modules are provided. -----------------------------------------------------------------------------------------------------------------------------------------------------
[13.01.2023, Ilakkiya (Z0107096)]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
Inputs:
Daimler EPB - SyDesign @ 9.1
Total 1 objects (SSM – 1) are affected with the System CR 5565912
1. Review of 1 SyDesign objects (SSM) should be performed as part of this CR
2. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
3. 1 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
4. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
---------------------------------------------------------------------------------------------------------------------
Complexity: [Medium]
Experience: [Known Topic]
Carry Over: [Basis available]
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
a) Title/Header: Derive SW Requirements (DaaTextMessageRequired)
Description:
Input : Daimler EPB - SyDesign @ 9.1
Filter: Attribute '015_CM Reference' contains '5565912'
Total 1 objects (SSM – 1) are affected with the System CR 5565912
1. Review of 1 SyDesign objects (SSM) should be performed as part of this CR
2. Document the review comments in ‘SyDesign’ review attributes (021*, 022* and 023*).
3. 1 SyDesign objects have been updated, corresponding SW requirements need to be modified as per SyDesign update.
4. PIA should be conducted for updated SyDesign requirements and capture the MOM in this CR.
Acceptance Criteria(s):
1. All SWE.1 relevant attributes are correctly updated
2. New/Modified requirements (SSM) have been derived and Reviewed
Review Type: Stakeholder review [YES], Formal review [YES]
Review Selection Reason: Requirements will be modified and rejected with this CR
Review Department(s): SWE.1, SWE.2, SWE.3 and SWE.6
==> What to review: Please check against the corresponding ALM_Task Notes to identify and confirm the SwRS module baselines to be reviewed!
==> What checklists: Please check against the corresponding ALM_Task Notes to identify, confirm and add the checklists!
Estimated effort: 10 h
----------------------------------------------------------------------------------------------------------------------------------------------------- |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release This Description has to be modified by PSM 2023-04-27, C. Diefenthal: covered by CR 7326244 and 7326305 | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release This Description has to be modified by PSM 2023-04-27, C. Diefenthal: covered by CR 7326244 and 7326305 |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release This Description has to be modified by PSM Will be done with CR 7326305 | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release This Description has to be modified by PSM Will be done with CR 7326305 |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release Kerstin Hammer (13.12.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Determine "DAA TextMessageRequired" needs to be added to requirements.
Requirements can be carried over from MQB48W:
-------------------------------------------------------------------------------- Kerstin Hammer (13.12.22):
--------------------------------------------------------------------------------
Brief investigation comment:
Carry over requirements to Daimler MMA in SyDesign.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for K. Hammer / Verifier: C. Diefenthal (1 h)
-------------------------------------------------------------------------------- | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release Kerstin Hammer (13.12.22):
--------------------------------------------------------------------------------
S&RE Description / Reason for OP:
Determine "DAA TextMessageRequired" needs to be added to requirements.
Requirements can be carried over from MQB48W:
-------------------------------------------------------------------------------- Kerstin Hammer (13.12.22):
--------------------------------------------------------------------------------
Brief investigation comment:
Carry over requirements to Daimler MMA in SyDesign.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for K. Hammer / Verifier: C. Diefenthal (1 h)
-------------------------------------------------------------------------------- |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release This Description has to be modified by PSM No action for EL required | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release This Description has to be modified by PSM No action for EL required |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release [DCRP 15.03] [EPB] PRF 22- Drive Away Release
This generic Open Point is used to track all systems and software engineering activities for:
PRF 22- Drive Away Release
Feature Increment 2
Final function w/o trimming
SWPM (A. Veling) (13.12.22 - 17:57):
--------------------------------------------------------------------------------
Determine DAA TextmessageRequired needs to be added to project.
___
S/W Requirements will be updated with CR 5565915, according to System Req CR 5565912
___
Please adapt the Sw Design accordingly if necessary (carry over from VW MQB48W) <Pravallika Gutta> (12.01.23 - 18:37):
--------------------------------------------------------------------------------
Brief investigation comment:
1. Please add TailGate check to the text message calculation as shown below:
--------------------------------------------------------------------------------
Risk (low/medium/high): Low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Pravallika Gutta>: <[DCRP 15.03 ML2][EPB][SWE.3] PRF 22- Drive Away Release> / Verifier: <Anyone> (9 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release [DCRP 15.03] [EPB] PRF 22- Drive Away Release
This generic Open Point is used to track all systems and software engineering activities for:
PRF 22- Drive Away Release
Feature Increment 2
Final function w/o trimming
SWPM (A. Veling) (13.12.22 - 17:57):
--------------------------------------------------------------------------------
Determine DAA TextmessageRequired needs to be added to project.
___
S/W Requirements will be updated with CR 5565915, according to System Req CR 5565912
___
Please adapt the Sw Design accordingly if necessary (carry over from VW MQB48W) <Pravallika Gutta> (12.01.23 - 18:37):
--------------------------------------------------------------------------------
Brief investigation comment:
1. Please add TailGate check to the text message calculation as shown below:
--------------------------------------------------------------------------------
Risk (low/medium/high): Low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Pravallika Gutta>: <[DCRP 15.03 ML2][EPB][SWE.3] PRF 22- Drive Away Release> / Verifier: <Anyone> (9 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release 6 Reqs in EPB automatisch oeffnen
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001b2953?doors.view=00000003 No requirements to be derived for this release.
=> reject CR | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release 6 Reqs in EPB automatisch oeffnen
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001b2953?doors.view=00000003 No requirements to be derived for this release.
=> reject CR |
|
[DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release [DCRP 15.03] [EPB] PRF 22- Drive Away Release
Feature Increment 2
Final function w/o trimming
with CRs 5565913 and 5565914 the system related work products have been closed
with CR 7122088 the function Drive Away Release has been activated in SSM PB
and now with this CR the text message shall be implemented <Pravallika Gutta> (05.05.23 - 12:11):
--------------------------------------------------------------------------------
Brief investigation comment:
1. Update 'DaaTextMessageRequired' calculation as per latest requirements
--------------------------------------------------------------------------------
Risk (low/medium/high): Medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Pravallika Gutta>: <[DCRP 15.03 ML2][EPB][SWE.3] PRF 22- Drive Away Release - text message> / Verifier: <Anyone> (18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- | [DCRP 15.03 ML2][EPB] PRF 22- Drive Away Release [DCRP 15.03] [EPB] PRF 22- Drive Away Release
Feature Increment 2
Final function w/o trimming
with CRs 5565913 and 5565914 the system related work products have been closed
with CR 7122088 the function Drive Away Release has been activated in SSM PB
and now with this CR the text message shall be implemented <Pravallika Gutta> (05.05.23 - 12:11):
--------------------------------------------------------------------------------
Brief investigation comment:
1. Update 'DaaTextMessageRequired' calculation as per latest requirements
--------------------------------------------------------------------------------
Risk (low/medium/high): Medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Pravallika Gutta>: <[DCRP 15.03 ML2][EPB][SWE.3] PRF 22- Drive Away Release - text message> / Verifier: <Anyone> (18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- |
|
DiagRequestStatus = Error when it should be Done then Idle Date 7/28/21
Description of issue or needed change Scenario:
Actuator State L = Applied
Actuators State R = Applied
DiagnosticRequest = Release
During Diagnostic set host availability Release Only Left
PbcFaultStatus (10) = Failed
Actuator State L = Released (Successful)
Actuator State R = Released (Successful)
DiagRequestStatus = Error
Test Environment (SIL,HIL,VEH) SIL
Software level X042
Software Module if known
Requirement
DataFile SIL test case: -700-005-PBC_MSC_DIAG_APPLIED_DIAG_OPEN_BOTH_HOST_RELEASE_ONLY_DURING
Note/Screenshot Is this expected or desired? The diagnostic request was successful in the sense that it completed the release, even if the host availability went to release only. Should we be setting DiagRequestStatus = Error or Done. EPB System CCB - JAS - 08.03.21:Please investigate this point and advise the next steps. | DiagRequestStatus = Error when it should be Done then Idle Date 7/28/21
Description of issue or needed change Scenario:
Actuator State L = Applied
Actuators State R = Applied
DiagnosticRequest = Release
During Diagnostic set host availability Release Only Left
PbcFaultStatus (10) = Failed
Actuator State L = Released (Successful)
Actuator State R = Released (Successful)
DiagRequestStatus = Error
Test Environment (SIL,HIL,VEH) SIL
Software level X042
Software Module if known
Requirement
DataFile SIL test case: -700-005-PBC_MSC_DIAG_APPLIED_DIAG_OPEN_BOTH_HOST_RELEASE_ONLY_DURING
Note/Screenshot Is this expected or desired? The diagnostic request was successful in the sense that it completed the release, even if the host availability went to release only. Should we be setting DiagRequestStatus = Error or Done. EPB System CCB - JAS - 08.03.21:Please investigate this point and advise the next steps. |
|
DiagRequestStatus = Error when it should be Done then Idle Date 7/28/21
Description of issue or needed change Scenario:
Actuator State L = Applied
Actuators State R = Applied
DiagnosticRequest = Release
During Diagnostic set host availability Release Only Left
PbcFaultStatus (10) = Failed
Actuator State L = Released (Successful)
Actuator State R = Released (Successful)
DiagRequestStatus = Error
Test Environment (SIL,HIL,VEH) SIL
Software level X042
Software Module if known
Requirement
DataFile SIL test case: -700-005-PBC_MSC_DIAG_APPLIED_DIAG_OPEN_BOTH_HOST_RELEASE_ONLY_DURING
Note/Screenshot Is this expected or desired? The diagnostic request was successful in the sense that it completed the release, even if the host availability went to release only. Should we be setting DiagRequestStatus = Error or Done. EPB System CCB - JAS - 05.11.21:Please investigate this point and advise the next steps.
11/9/21: mrb See M Lubbers for relevant Design Document (specific version) | DiagRequestStatus = Error when it should be Done then Idle Date 7/28/21
Description of issue or needed change Scenario:
Actuator State L = Applied
Actuators State R = Applied
DiagnosticRequest = Release
During Diagnostic set host availability Release Only Left
PbcFaultStatus (10) = Failed
Actuator State L = Released (Successful)
Actuator State R = Released (Successful)
DiagRequestStatus = Error
Test Environment (SIL,HIL,VEH) SIL
Software level X042
Software Module if known
Requirement
DataFile SIL test case: -700-005-PBC_MSC_DIAG_APPLIED_DIAG_OPEN_BOTH_HOST_RELEASE_ONLY_DURING
Note/Screenshot Is this expected or desired? The diagnostic request was successful in the sense that it completed the release, even if the host availability went to release only. Should we be setting DiagRequestStatus = Error or Done. EPB System CCB - JAS - 05.11.21:Please investigate this point and advise the next steps.
11/9/21: mrb See M Lubbers for relevant Design Document (specific version) |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 ADBY4.3 - MarxT [30.06.2021 - 12:31]:
Due to CR 4741455, expectation would be that DriveAwayRelease is working in AT vehicles.
Currently DAA is not working. <M.Kumar> (19.07.21):
--------------------------------------------------------------------------------
Brief investigation comment:
After investigation we see that DAA is not possible due to SsmPbIn.EngineSpeed Invalid value. 65535. This issue has been fixed with Task - ALM_Task 5489066
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- Issue is resolved with other task, This CR could be rejected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 ADBY4.3 - MarxT [30.06.2021 - 12:31]:
Due to CR 4741455, expectation would be that DriveAwayRelease is working in AT vehicles.
Currently DAA is not working. <M.Kumar> (19.07.21):
--------------------------------------------------------------------------------
Brief investigation comment:
After investigation we see that DAA is not possible due to SsmPbIn.EngineSpeed Invalid value. 65535. This issue has been fixed with Task - ALM_Task 5489066
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- Issue is resolved with other task, This CR could be rejected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 Variable SsmPbIn.EngineSpeed always shows 65535 rpm, which is invalid -> I guess DAA function is affected by this and therefore it is not working.
Variable _SsmPbIn._Mileage always shows 4294967295, which is invalid -> PWA function won't work.
40 Test cases impacted. [Tayfun Ikinci (ikincit), 08.07.2021, 11:50:59]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Tayfun Ikinci
Verifier: Arnd Bagusat
Estimated effort: 8h
-------------------------------
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
CCB - KNE - 08.07.21 - 09:09:
see comment from Comms team (below in comments field):
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--> Please investigate effort for changing the IV in ssm_pbi.c.
Kai Neitzert (07.07.21 - 15:47)
--------------------------------------------------------------------------------
Brief investigation comment:
Ssm_Pbi.c: SsmPbIn.Mileage is filled with code as follows:
mileage_u32t = GetKmMileage();
/*--------------------------------------------------------------------------*/
/* Fill M I L E A G E for P W A acc VDA10 */
/*--------------------------------------------------------------------------*/
/* check Mileage input valid */
if ((FALSE == IsInputValid(INPUT_VALID_ODOMETER))
|| (SSM_PB_MILEAGE_TYPE_FAULT == mileage_u32t)
|| (SSM_PB_MILEAGE_TYPE_MAX < mileage_u32t))
{
/* set INVALID */
SsmPbIn.Mileage = SSM_PB_MILEAGE_TYPE_FAULT;
}
else
{
/* set valid Value */
SsmPbIn.Mileage = mileage_u32t;
}
--> either GetKmMileage() returns wrong value or IsInputValid(INPUT_VALID_ODOMETER)
SsmPbIn.EngineSpeed will be investigated with CR 5470791
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- The investigation shall be continued by Comms team in order to check these two interfaces.
-------------------------------------------------------------------------------- | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 Variable SsmPbIn.EngineSpeed always shows 65535 rpm, which is invalid -> I guess DAA function is affected by this and therefore it is not working.
Variable _SsmPbIn._Mileage always shows 4294967295, which is invalid -> PWA function won't work.
40 Test cases impacted. [Tayfun Ikinci (ikincit), 08.07.2021, 11:50:59]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Tayfun Ikinci
Verifier: Arnd Bagusat
Estimated effort: 8h
-------------------------------
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
CCB - KNE - 08.07.21 - 09:09:
see comment from Comms team (below in comments field):
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--> Please investigate effort for changing the IV in ssm_pbi.c.
Kai Neitzert (07.07.21 - 15:47)
--------------------------------------------------------------------------------
Brief investigation comment:
Ssm_Pbi.c: SsmPbIn.Mileage is filled with code as follows:
mileage_u32t = GetKmMileage();
/*--------------------------------------------------------------------------*/
/* Fill M I L E A G E for P W A acc VDA10 */
/*--------------------------------------------------------------------------*/
/* check Mileage input valid */
if ((FALSE == IsInputValid(INPUT_VALID_ODOMETER))
|| (SSM_PB_MILEAGE_TYPE_FAULT == mileage_u32t)
|| (SSM_PB_MILEAGE_TYPE_MAX < mileage_u32t))
{
/* set INVALID */
SsmPbIn.Mileage = SSM_PB_MILEAGE_TYPE_FAULT;
}
else
{
/* set valid Value */
SsmPbIn.Mileage = mileage_u32t;
}
--> either GetKmMileage() returns wrong value or IsInputValid(INPUT_VALID_ODOMETER)
SsmPbIn.EngineSpeed will be investigated with CR 5470791
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- The investigation shall be continued by Comms team in order to check these two interfaces.
-------------------------------------------------------------------------------- |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 [Tayfun Ikinci (ikincit), 18.11.2021, 12:46:00]
This CR shall be used to fill / add the remaining missing interfaces
/*
*@ FUNC_NAME : GetSsmPbLearnedCep
*@ INPUT : SsmPbOut.ClutchEngagementPoint
*@ ---------------------------------------------------------------------------
*/
/*
*@ VAR_NAME : GetSsmPbLearnedCep()
*@ PROPERTIES : U16 | [0...32768] | | PERCENT | bit
*@ ---------------------------------------------------------------------------
*/
U16 GetSsmPbLearnedCep(void)
{
U16 cep_u16;
cep_u16 = (U16)( ( (U32)SsmPbOut.ClutchEngagementPoint
* HUNDRED_PERCENT
)
/ (SSM_PB_CLUTCHENGAGEMENTPOINT_TYPE_SCALING * SSM_PB_CLUTCH_TRAVEL_RANGE)
);
return (cep_u16);
}
/*
*@ FUNC_NAME : IsSsmPbLearnedCepValid
*@ INPUT : SsmPbOut.ClutchEngagementPoint
*@ ---------------------------------------------------------------------------
*/
/*
*@ VAR_NAME : IsSsmPbLearnedCepValid()
*@ PROPERTIES : BN | [0...1] | | 1 | bit
*@ ---------------------------------------------------------------------------
*/
BOOLEAN IsSsmPbLearnedCepValid(void)
{
BOOLEAN result_bn;
if (SsmPbOut.ClutchEngagementPoint == SSM_PB_CLUTCHENGAGEMENTPOINT_TYPE_INVALID)
{
result_bn = FALSE;
}
else
{
result_bn = TRUE;
}
return (result_bn);
}
/*
*@ FUNC_NAME : GetSsmPbInitialCep
*@ INPUT : SsmPbOut.InitialClutchEngagementPoint
*@ ---------------------------------------------------------------------------
*/
/*
*@ VAR_NAME : GetSsmPbInitialCep()
*@ PROPERTIES : U16 | [0...32768] | | PERCENT | bit
*@ ---------------------------------------------------------------------------
*/
U16 GetSsmPbInitialCep(void)
{
U16 cep_u16;
cep_u16 = (U16)( ( (U32)SsmPbOut.InitialClutchEngagementPoint
* HUNDRED_PERCENT
)
/ (SSM_PB_CLUTCHENGAGEMENTPOINT_TYPE_SCALING * SSM_PB_CLUTCH_TRAVEL_RANGE)
);
return (cep_u16);
} [Tayfun Ikinci (ikincit), 16.12.2021, 15:37:18]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
the missing interfaces has been meanwhile added with ALM_Task 5962549
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
link Task to this CR
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
-------------------------------------------------------------------------------- | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 [Tayfun Ikinci (ikincit), 18.11.2021, 12:46:00]
This CR shall be used to fill / add the remaining missing interfaces
/*
*@ FUNC_NAME : GetSsmPbLearnedCep
*@ INPUT : SsmPbOut.ClutchEngagementPoint
*@ ---------------------------------------------------------------------------
*/
/*
*@ VAR_NAME : GetSsmPbLearnedCep()
*@ PROPERTIES : U16 | [0...32768] | | PERCENT | bit
*@ ---------------------------------------------------------------------------
*/
U16 GetSsmPbLearnedCep(void)
{
U16 cep_u16;
cep_u16 = (U16)( ( (U32)SsmPbOut.ClutchEngagementPoint
* HUNDRED_PERCENT
)
/ (SSM_PB_CLUTCHENGAGEMENTPOINT_TYPE_SCALING * SSM_PB_CLUTCH_TRAVEL_RANGE)
);
return (cep_u16);
}
/*
*@ FUNC_NAME : IsSsmPbLearnedCepValid
*@ INPUT : SsmPbOut.ClutchEngagementPoint
*@ ---------------------------------------------------------------------------
*/
/*
*@ VAR_NAME : IsSsmPbLearnedCepValid()
*@ PROPERTIES : BN | [0...1] | | 1 | bit
*@ ---------------------------------------------------------------------------
*/
BOOLEAN IsSsmPbLearnedCepValid(void)
{
BOOLEAN result_bn;
if (SsmPbOut.ClutchEngagementPoint == SSM_PB_CLUTCHENGAGEMENTPOINT_TYPE_INVALID)
{
result_bn = FALSE;
}
else
{
result_bn = TRUE;
}
return (result_bn);
}
/*
*@ FUNC_NAME : GetSsmPbInitialCep
*@ INPUT : SsmPbOut.InitialClutchEngagementPoint
*@ ---------------------------------------------------------------------------
*/
/*
*@ VAR_NAME : GetSsmPbInitialCep()
*@ PROPERTIES : U16 | [0...32768] | | PERCENT | bit
*@ ---------------------------------------------------------------------------
*/
U16 GetSsmPbInitialCep(void)
{
U16 cep_u16;
cep_u16 = (U16)( ( (U32)SsmPbOut.InitialClutchEngagementPoint
* HUNDRED_PERCENT
)
/ (SSM_PB_CLUTCHENGAGEMENTPOINT_TYPE_SCALING * SSM_PB_CLUTCH_TRAVEL_RANGE)
);
return (cep_u16);
} [Tayfun Ikinci (ikincit), 16.12.2021, 15:37:18]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
the missing interfaces has been meanwhile added with ALM_Task 5962549
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
link Task to this CR
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
-------------------------------------------------------------------------------- |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 Park Brake subfunction DAA is inhibited for several COMMS monitors. The list of monitors that needed to be reviewed is below , If they do not contain relevant information then PB_FUNCTION_DAA should be "No Effect"
MSG_CMM_278_TIMEOUT
MSG_CMM_278_CRC_FAULT
MSG_CMM_278_RC_FAULT
MSG_CMM_278_EFCMNT_PDLE_ACCEL_INVALID
MSG_CMM_298_TIMEOUT
MSG_CMM_2B2_TIMEOUT
MSG_CMM_2B8_TIMEOUT
MSG_CMM_228_EFCMNT_PDLE_ACCEL_INVALID
MSG_CMM_228_POS_PDLE_EMBR_CMM_INVALID
MSG_CMM_228_TIMEOUT
MSG_CMM_228_CRC_FAULT
MSG_CMM_228_RC_FAULT
Check if these messages contain signal information relevant for DAA
MSG_CMM_278
MSG_CMM_298
MSG_CMM_2B2
MSG_CMM_2B8
MSG_CMM_228 Change PB_FUNCTION DAA to "No Effect" for the following monitors
MSG_CMM_2B2_TIMEOUT
MSG_CMM_2B8_TIMEOUT
The rest of the analysis will be done with CR 6222011
url:integrity://skobde-mks-im.kobde.trw.com:7001/im/viewissue?selection=6222011 | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 Park Brake subfunction DAA is inhibited for several COMMS monitors. The list of monitors that needed to be reviewed is below , If they do not contain relevant information then PB_FUNCTION_DAA should be "No Effect"
MSG_CMM_278_TIMEOUT
MSG_CMM_278_CRC_FAULT
MSG_CMM_278_RC_FAULT
MSG_CMM_278_EFCMNT_PDLE_ACCEL_INVALID
MSG_CMM_298_TIMEOUT
MSG_CMM_2B2_TIMEOUT
MSG_CMM_2B8_TIMEOUT
MSG_CMM_228_EFCMNT_PDLE_ACCEL_INVALID
MSG_CMM_228_POS_PDLE_EMBR_CMM_INVALID
MSG_CMM_228_TIMEOUT
MSG_CMM_228_CRC_FAULT
MSG_CMM_228_RC_FAULT
Check if these messages contain signal information relevant for DAA
MSG_CMM_278
MSG_CMM_298
MSG_CMM_2B2
MSG_CMM_2B8
MSG_CMM_228 Change PB_FUNCTION DAA to "No Effect" for the following monitors
MSG_CMM_2B2_TIMEOUT
MSG_CMM_2B8_TIMEOUT
The rest of the analysis will be done with CR 6222011
url:integrity://skobde-mks-im.kobde.trw.com:7001/im/viewissue?selection=6222011 |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 [Summary]
Failsafe specification: create and include Baseline and generate source code for X01_400_170
[Description]
This item covers all activities to transfer the system level specification and documentation regarding monitors/degradation/OBD/DTC into the software build.
The system level data is maintained in a DOORS database. Baselines of the relevant modules need to be created, exported, and archived. Source code needs to be generated from the DMT baseline.
The relationships 'Required and Requires' can link related changes of other domains.
Workpackages which might be considered:
- System: Create baselines
- DMT: Generate source files from exported baseline
- MeMo: Update DEM block sizes
- BswAutocore: Generate xdms and run importer Aimen Rouissi (23.02.22 - 14:12):
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Baselines of the relevant DOORS modules need to be created, exported, and archived.
Afterwards, source code needs to be generated from the DMT baseline.
It may also be necessary to adjust details of Thirdparty/ Autosar configuration.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Rouissia
Proposal of next steps (incl. effort/h and verification): Please see the tasks related to this CR.
-------------------------------------------------------------------------------- | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 22 - Drive Away Release not working as expected due to CR4741455 [Summary]
Failsafe specification: create and include Baseline and generate source code for X01_400_170
[Description]
This item covers all activities to transfer the system level specification and documentation regarding monitors/degradation/OBD/DTC into the software build.
The system level data is maintained in a DOORS database. Baselines of the relevant modules need to be created, exported, and archived. Source code needs to be generated from the DMT baseline.
The relationships 'Required and Requires' can link related changes of other domains.
Workpackages which might be considered:
- System: Create baselines
- DMT: Generate source files from exported baseline
- MeMo: Update DEM block sizes
- BswAutocore: Generate xdms and run importer Aimen Rouissi (23.02.22 - 14:12):
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Baselines of the relevant DOORS modules need to be created, exported, and archived.
Afterwards, source code needs to be generated from the DMT baseline.
It may also be necessary to adjust details of Thirdparty/ Autosar configuration.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Rouissia
Proposal of next steps (incl. effort/h and verification): Please see the tasks related to this CR.
-------------------------------------------------------------------------------- |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 15 - Switch Failure Apply not working as expected due to CR4741455 this change request shall be used create new branch in integrity as below.
this is a scs project with scs only and scs with epb support.
this project is based on project vw mqb48-w for bsw/psw
please share the following software (epb) into the opel k0 project archive (current sw is stored in opel_x250 project):
checkpoint as below for hsb/ ssm_pb from latest core:
hsb_appl: 1.30.1.2
08_software 1.4.2.12 (https://skobde-mks.kobde.trw.com:7001/si/viewproject?projectname=/brk/productdevelopment/subsystems/ssmpb/08%5fsoftware/project.pj&projectrevision=1.4.2.12)
ssm_pb_appl: 1.3.3.11
ssm_pb_para: 1.3.3.4
tools: 1.2.2.3
name for development path should be: psa_opel_k0
compiler/ setting checkpoints (see task 3736261):
vw variant: tasking_tricore-vx_v6.3r1
checkpoint 1.1.1.3.1.2 cr 4725627
prj 3539831
integ_psa_opel_k0_ssm_pb_a
integ_psa_opel_k0_hsb_a
--------------------------------------------------------------------------------
brief analysis summary: psa_opel_k0 - baseline creation share core 11.4 ssm-pb into psa_opel_k0 project
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
risk (low/medium/high):
--------------------------------------------------------------------------------
analysis completed by (applicable only for distributed analyses):
proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
task
------------------------------------------------------
title: psa_opel_k0 - baseline creation share core 11.4 ssm-pb into psa_opel_k0 project
brief analysis summary: psa_opel_k0 - baseline creation share core 11.4 ssm-pb into psa_opel_k0 project
description:
execute the follwing steps: create new variante
from epbi core 11.4.1 (1.90) take
hsb 1.30 support by m.minke
from core_ssm_pb_114_00 08_software (1.4.2.12)
ssm_pb_appl 1.3.3.11
ssm_pb_para 1.3.3.4
tools 1.2.2.3
compiler tasking
buildtoolchainoption
make2000 make
(compiler/ setting checkpoints (see task 3736261):
vw variant: tasking_tricore-vx_v6.3r1
checkpoint 1.1.1.3.1.2 )
-update winmake ini
checkpoint subprojects block ssm (appl and para ) 08_software for iqm_base
create developer/ preinteg
delete binary in developer/ preinteg
owner: m.lecnek
reviewer: willi rempel
estimated design 1 effort/h:
estimated implementation 8 effort/h:
estimated unit testing 3 effort/h:
------------------------------------------------------
total 12 effort/h:
[optional] planned completion date:
------------------------------------------------------
29.06.2021 | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 15 - Switch Failure Apply not working as expected due to CR4741455 this change request shall be used create new branch in integrity as below.
this is a scs project with scs only and scs with epb support.
this project is based on project vw mqb48-w for bsw/psw
please share the following software (epb) into the opel k0 project archive (current sw is stored in opel_x250 project):
checkpoint as below for hsb/ ssm_pb from latest core:
hsb_appl: 1.30.1.2
08_software 1.4.2.12 (https://skobde-mks.kobde.trw.com:7001/si/viewproject?projectname=/brk/productdevelopment/subsystems/ssmpb/08%5fsoftware/project.pj&projectrevision=1.4.2.12)
ssm_pb_appl: 1.3.3.11
ssm_pb_para: 1.3.3.4
tools: 1.2.2.3
name for development path should be: psa_opel_k0
compiler/ setting checkpoints (see task 3736261):
vw variant: tasking_tricore-vx_v6.3r1
checkpoint 1.1.1.3.1.2 cr 4725627
prj 3539831
integ_psa_opel_k0_ssm_pb_a
integ_psa_opel_k0_hsb_a
--------------------------------------------------------------------------------
brief analysis summary: psa_opel_k0 - baseline creation share core 11.4 ssm-pb into psa_opel_k0 project
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
risk (low/medium/high):
--------------------------------------------------------------------------------
analysis completed by (applicable only for distributed analyses):
proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
task
------------------------------------------------------
title: psa_opel_k0 - baseline creation share core 11.4 ssm-pb into psa_opel_k0 project
brief analysis summary: psa_opel_k0 - baseline creation share core 11.4 ssm-pb into psa_opel_k0 project
description:
execute the follwing steps: create new variante
from epbi core 11.4.1 (1.90) take
hsb 1.30 support by m.minke
from core_ssm_pb_114_00 08_software (1.4.2.12)
ssm_pb_appl 1.3.3.11
ssm_pb_para 1.3.3.4
tools 1.2.2.3
compiler tasking
buildtoolchainoption
make2000 make
(compiler/ setting checkpoints (see task 3736261):
vw variant: tasking_tricore-vx_v6.3r1
checkpoint 1.1.1.3.1.2 )
-update winmake ini
checkpoint subprojects block ssm (appl and para ) 08_software for iqm_base
create developer/ preinteg
delete binary in developer/ preinteg
owner: m.lecnek
reviewer: willi rempel
estimated design 1 effort/h:
estimated implementation 8 effort/h:
estimated unit testing 3 effort/h:
------------------------------------------------------
total 12 effort/h:
[optional] planned completion date:
------------------------------------------------------
29.06.2021 |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 15 - Switch Failure Apply not working as expected due to CR4741455 --------------------------------------------------------------------------------
Aim (Objective and Rationale): Analyse on how EPBi subsystem related calls can be handled in Non EPB environment
--------------------------------------------------------------------------------
Details (Exact description): EPB/NonEPB Hw variants will be supported with single software. Mechanism to switch between these variants need to be implemented and dependencies in EPB/Non EPB should be known and handled
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
1. Refer Attachment "EPB_Dependency_K0.xlsx" for high level analysis for EPB dependencies (see dependencies tab). And please refer CR linked for proposal on how to handle EPB variants
--------------------------------------------------------------------------------
Output Work Products: All EPB related implementations with respect to EPB/Non EPB variant handling for EPBi subsystem should be adapted
--------------------------------------------------------------------------------
Acceptance Criteria: Implementation CRs for changes expected
-------------------------------------------------------------------------------- [Tayfun Ikinci (ikincit), 28.10.2021, 13:16:38]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
1. compiler switch shall be replaced
2. Make use of PSSD for DAA
3. Provide SsmPb internal refspeed
4. Make use of new available clutch interfaces
5. DOOR Status is available - Seat Belt shall be stubbed as it is not available at all
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Tayfun Ikinci
Verifier: Reddy Bommana
Estimated effort: 4h
-------------------------------
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
CCB - KNE - 26.10.21 - 09:57:
CR in "Requires" relationship implemented this interface in Chassinf:
U8 GetEpbHwType(void);
Tayfun, can you please check usage of it in SsmPbi?
[Tayfun Ikinci (ikincit), 13.08.2021, 17:08:42]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
Still waiting for the Diag Interface.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
please assign CR back to Susanne Konradi to clarify who will provide with which task the Diag Interface, or can we reject this CR?
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
Tayfun Ikinci, Prasanna Madeti 26.02.2021
This is the upcoming CR for ALM_Change Request 4998566
So the introduce compiler switch has to be replaced with a new Diag Interface. This new Interface will be provided with ALM_Change Request 4964747. | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 15 - Switch Failure Apply not working as expected due to CR4741455 --------------------------------------------------------------------------------
Aim (Objective and Rationale): Analyse on how EPBi subsystem related calls can be handled in Non EPB environment
--------------------------------------------------------------------------------
Details (Exact description): EPB/NonEPB Hw variants will be supported with single software. Mechanism to switch between these variants need to be implemented and dependencies in EPB/Non EPB should be known and handled
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
1. Refer Attachment "EPB_Dependency_K0.xlsx" for high level analysis for EPB dependencies (see dependencies tab). And please refer CR linked for proposal on how to handle EPB variants
--------------------------------------------------------------------------------
Output Work Products: All EPB related implementations with respect to EPB/Non EPB variant handling for EPBi subsystem should be adapted
--------------------------------------------------------------------------------
Acceptance Criteria: Implementation CRs for changes expected
-------------------------------------------------------------------------------- [Tayfun Ikinci (ikincit), 28.10.2021, 13:16:38]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
1. compiler switch shall be replaced
2. Make use of PSSD for DAA
3. Provide SsmPb internal refspeed
4. Make use of new available clutch interfaces
5. DOOR Status is available - Seat Belt shall be stubbed as it is not available at all
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Tayfun Ikinci
Verifier: Reddy Bommana
Estimated effort: 4h
-------------------------------
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
CCB - KNE - 26.10.21 - 09:57:
CR in "Requires" relationship implemented this interface in Chassinf:
U8 GetEpbHwType(void);
Tayfun, can you please check usage of it in SsmPbi?
[Tayfun Ikinci (ikincit), 13.08.2021, 17:08:42]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
Still waiting for the Diag Interface.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
please assign CR back to Susanne Konradi to clarify who will provide with which task the Diag Interface, or can we reject this CR?
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
Tayfun Ikinci, Prasanna Madeti 26.02.2021
This is the upcoming CR for ALM_Change Request 4998566
So the introduce compiler switch has to be replaced with a new Diag Interface. This new Interface will be provided with ALM_Change Request 4964747. |
|
[Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 15 - Switch Failure Apply not working as expected due to CR4741455 ADBY4.3 - MarxT [30.06.2021 - 12:31]:
Due to CR 4741455, expectation would be that SwitchFailureApply is working in AT vehicles.
Currently Switch Failure Apply is not working. Reason for that could be OP 5466472, not working DAA function. <M.Kumar> (23-08-2021):
--------------------------------------------------------------------------------
Brief investigation comment:
After investigation we see that DAA is not possible due to SsmPbIn.EngineSpeed Invalid value. 65535. This maked Daa validity False which is used in Auto Apply as precondition,
This issue has been fixed with Task - ALM_Task 5489066
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- Issue is resolved with other task, This CR could be rejected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- | [Opel K0][300_174][CAT2][ADBY4.3][Vehicle Test] - PRF 15 - Switch Failure Apply not working as expected due to CR4741455 ADBY4.3 - MarxT [30.06.2021 - 12:31]:
Due to CR 4741455, expectation would be that SwitchFailureApply is working in AT vehicles.
Currently Switch Failure Apply is not working. Reason for that could be OP 5466472, not working DAA function. <M.Kumar> (23-08-2021):
--------------------------------------------------------------------------------
Brief investigation comment:
After investigation we see that DAA is not possible due to SsmPbIn.EngineSpeed Invalid value. 65535. This maked Daa validity False which is used in Auto Apply as precondition,
This issue has been fixed with Task - ALM_Task 5489066
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- Issue is resolved with other task, This CR could be rejected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- |
|
[0521][CAT3][CASE][VW_MEB31x_SCS][VW_MEB41x_SCS] - DTC $60081 / 393345 TASK_OVERRUN Preconditions / Ausgangsituation:
SW SCS: b512
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Flash d512 (FL_1EA614517AJ_d521__V001_E.odx)
2. Some Kl15 change (on/of)
3. DTC $60081 / 393345 TASK_OVERRUN --------------------------------------------------------------------------------
Brief analysis summary:
Rte_Task_QM_Priv_C0 has the same priority as Rte_Task_QM_C0 and Rte_Task_D_C0. If Rte_Task_QM_C0 and Rte_Task_D_C0 are called before Rte_Task_QM_Priv_C0, it will get preempted a long time. Since Rte_Task_QM_C0 and Rte_Task_D_C0 consume much time and runtime on Core 0 is already very high this could lead to an TaskOverrun of Rte_Task_QM_Priv_C0. Prio of Rte_Task_QM_Priv_C0 shall be increased.
Also it was noticed that Task_Init_BB_RkapRle_B_C2, Rte_Task_QM_D_C0 and Rte_Task_QM_Priv_C0 are not configured correctly. This shall be fixed too.
For Task_Init_BB_RkapRle_B_C2, Rte_Task_QM_D_C0 and Rte_Task_QM_Priv_C0 the parameter /MICROSAR/Os/OsTask/OsTaskSchedule shall be set to "FULL".
For Rte_Task_QM_Priv_C0 the Prio shall be set to 61.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeberA4
Proposal of next steps (incl. effort/h and verification):
Create Task and approve CR.
-------------------------------------------------------------------------------- | [0521][CAT3][CASE][VW_MEB31x_SCS][VW_MEB41x_SCS] - DTC $60081 / 393345 TASK_OVERRUN Preconditions / Ausgangsituation:
SW SCS: b512
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Flash d512 (FL_1EA614517AJ_d521__V001_E.odx)
2. Some Kl15 change (on/of)
3. DTC $60081 / 393345 TASK_OVERRUN --------------------------------------------------------------------------------
Brief analysis summary:
Rte_Task_QM_Priv_C0 has the same priority as Rte_Task_QM_C0 and Rte_Task_D_C0. If Rte_Task_QM_C0 and Rte_Task_D_C0 are called before Rte_Task_QM_Priv_C0, it will get preempted a long time. Since Rte_Task_QM_C0 and Rte_Task_D_C0 consume much time and runtime on Core 0 is already very high this could lead to an TaskOverrun of Rte_Task_QM_Priv_C0. Prio of Rte_Task_QM_Priv_C0 shall be increased.
Also it was noticed that Task_Init_BB_RkapRle_B_C2, Rte_Task_QM_D_C0 and Rte_Task_QM_Priv_C0 are not configured correctly. This shall be fixed too.
For Task_Init_BB_RkapRle_B_C2, Rte_Task_QM_D_C0 and Rte_Task_QM_Priv_C0 the parameter /MICROSAR/Os/OsTask/OsTaskSchedule shall be set to "FULL".
For Rte_Task_QM_Priv_C0 the Prio shall be set to 61.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeberA4
Proposal of next steps (incl. effort/h and verification):
Create Task and approve CR.
-------------------------------------------------------------------------------- |
|
[0521][CAT3][CASE][VW_MEB31x_SCS][VW_MEB41x_SCS] - DTC $60081 / 393345 TASK_OVERRUN Preconditions / Ausgangsituation:
SW SCS: b512
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Flash d512 (FL_1EA614517AJ_d521__V001_E.odx)
2. Some Kl15 change (on/of)
3. DTC $60081 / 393345 TASK_OVERRUN Not reproducible therefore not directly testable with a clear result.
Can only be observe during the release maneuver and documented accordingly if it was seen again or not to release end. | [0521][CAT3][CASE][VW_MEB31x_SCS][VW_MEB41x_SCS] - DTC $60081 / 393345 TASK_OVERRUN Preconditions / Ausgangsituation:
SW SCS: b512
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Flash d512 (FL_1EA614517AJ_d521__V001_E.odx)
2. Some Kl15 change (on/of)
3. DTC $60081 / 393345 TASK_OVERRUN Not reproducible therefore not directly testable with a clear result.
Can only be observe during the release maneuver and documented accordingly if it was seen again or not to release end. |
|
[Opel K0][X0300_173][CAT3][HIL] Mileage and Engine speed are Invalid on the interface Variable SsmPbIn.EngineSpeed always shows 65535 rpm, which is invalid -> I guess DAA function is affected by this and therefore it is not working.
Variable _SsmPbIn._Mileage always shows 4294967295, which is invalid -> PWA function won't work.
40 Test cases impacted. [Tayfun Ikinci (ikincit), 08.07.2021, 11:50:59]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Tayfun Ikinci
Verifier: Arnd Bagusat
Estimated effort: 8h
-------------------------------
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
CCB - KNE - 08.07.21 - 09:09:
see comment from Comms team (below in comments field):
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--> Please investigate effort for changing the IV in ssm_pbi.c.
Kai Neitzert (07.07.21 - 15:47)
--------------------------------------------------------------------------------
Brief investigation comment:
Ssm_Pbi.c: SsmPbIn.Mileage is filled with code as follows:
mileage_u32t = GetKmMileage();
/*--------------------------------------------------------------------------*/
/* Fill M I L E A G E for P W A acc VDA10 */
/*--------------------------------------------------------------------------*/
/* check Mileage input valid */
if ((FALSE == IsInputValid(INPUT_VALID_ODOMETER))
|| (SSM_PB_MILEAGE_TYPE_FAULT == mileage_u32t)
|| (SSM_PB_MILEAGE_TYPE_MAX < mileage_u32t))
{
/* set INVALID */
SsmPbIn.Mileage = SSM_PB_MILEAGE_TYPE_FAULT;
}
else
{
/* set valid Value */
SsmPbIn.Mileage = mileage_u32t;
}
--> either GetKmMileage() returns wrong value or IsInputValid(INPUT_VALID_ODOMETER)
SsmPbIn.EngineSpeed will be investigated with CR 5470791
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- The investigation shall be continued by Comms team in order to check these two interfaces.
-------------------------------------------------------------------------------- | [Opel K0][X0300_173][CAT3][HIL] Mileage and Engine speed are Invalid on the interface Variable SsmPbIn.EngineSpeed always shows 65535 rpm, which is invalid -> I guess DAA function is affected by this and therefore it is not working.
Variable _SsmPbIn._Mileage always shows 4294967295, which is invalid -> PWA function won't work.
40 Test cases impacted. [Tayfun Ikinci (ikincit), 08.07.2021, 11:50:59]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Tayfun Ikinci
Verifier: Arnd Bagusat
Estimated effort: 8h
-------------------------------
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
CCB - KNE - 08.07.21 - 09:09:
see comment from Comms team (below in comments field):
The IV mapped to GetKmMileage() is not INPUT_VALID_ODOMETER instead is INPUT_VALID_KBI_KILOMETERSTAND_INVALID.
--> Please investigate effort for changing the IV in ssm_pbi.c.
Kai Neitzert (07.07.21 - 15:47)
--------------------------------------------------------------------------------
Brief investigation comment:
Ssm_Pbi.c: SsmPbIn.Mileage is filled with code as follows:
mileage_u32t = GetKmMileage();
/*--------------------------------------------------------------------------*/
/* Fill M I L E A G E for P W A acc VDA10 */
/*--------------------------------------------------------------------------*/
/* check Mileage input valid */
if ((FALSE == IsInputValid(INPUT_VALID_ODOMETER))
|| (SSM_PB_MILEAGE_TYPE_FAULT == mileage_u32t)
|| (SSM_PB_MILEAGE_TYPE_MAX < mileage_u32t))
{
/* set INVALID */
SsmPbIn.Mileage = SSM_PB_MILEAGE_TYPE_FAULT;
}
else
{
/* set valid Value */
SsmPbIn.Mileage = mileage_u32t;
}
--> either GetKmMileage() returns wrong value or IsInputValid(INPUT_VALID_ODOMETER)
SsmPbIn.EngineSpeed will be investigated with CR 5470791
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- The investigation shall be continued by Comms team in order to check these two interfaces.
-------------------------------------------------------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swe.5 - softwareintegrationtest - request swad spec
--------------------------------------------------------------------------------
details (exact description):
this cr is required to add / update specification in the architectureconcept, which were discussed with christianseifen, see attached mail from (20.05.2021 15:47).
today verbal agreed specification are already used for softwareintegrationtest, this cr should also provided written evidence in swad concept.
the budgets used for testing today (mentioned below) should be changed to the projects need, please compare also with specification christianseifen which may apply in general for each product / project.
the following specifications should be available:
1. rom overall consumption
(today used for testing 80% budget)
(mention relation to rombudget per swad_component)
2. ram overall consumption
(today used for testing 80% budget)
(mention relation to rambudget per swad_component)
3. runtime budget per core
is should be noted that the budget is used for testing from specification per core in document resourceestimationsheet.
furthermore, the runtime budget should be per core and not be specified per runnable. (runtime values per runnable in swad are used to calculate overall runtime per core)
4. stack consumption budget for task/isr stacks and csa stacks
(today used for testing 70% budget / csa stacks 80% budget)
5. nvram budget
6. memorybudget (ram/rom) for each swad_component is defined and it is valid for a component to consume 100-200% of its budget.
furthremore, it should clarified from swad if it is possible to have these kind of specifications available in the rpy swad model to include them in an automatic generated export.
--------------------------------------------------------------------------------
input work products (link or other reference): architectureconcept
--------------------------------------------------------------------------------
output work products: updated architectureconcept
--------------------------------------------------------------------------------
acceptance criteria: a written specification is available for each requested topic above.
-------------------------------------------------------------------------------- 2021-09-06 cse:
add µc resource consumption objectives to architecture concept.
create related task, effort ~2h | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swe.5 - softwareintegrationtest - request swad spec
--------------------------------------------------------------------------------
details (exact description):
this cr is required to add / update specification in the architectureconcept, which were discussed with christianseifen, see attached mail from (20.05.2021 15:47).
today verbal agreed specification are already used for softwareintegrationtest, this cr should also provided written evidence in swad concept.
the budgets used for testing today (mentioned below) should be changed to the projects need, please compare also with specification christianseifen which may apply in general for each product / project.
the following specifications should be available:
1. rom overall consumption
(today used for testing 80% budget)
(mention relation to rombudget per swad_component)
2. ram overall consumption
(today used for testing 80% budget)
(mention relation to rambudget per swad_component)
3. runtime budget per core
is should be noted that the budget is used for testing from specification per core in document resourceestimationsheet.
furthermore, the runtime budget should be per core and not be specified per runnable. (runtime values per runnable in swad are used to calculate overall runtime per core)
4. stack consumption budget for task/isr stacks and csa stacks
(today used for testing 70% budget / csa stacks 80% budget)
5. nvram budget
6. memorybudget (ram/rom) for each swad_component is defined and it is valid for a component to consume 100-200% of its budget.
furthremore, it should clarified from swad if it is possible to have these kind of specifications available in the rpy swad model to include them in an automatic generated export.
--------------------------------------------------------------------------------
input work products (link or other reference): architectureconcept
--------------------------------------------------------------------------------
output work products: updated architectureconcept
--------------------------------------------------------------------------------
acceptance criteria: a written specification is available for each requested topic above.
-------------------------------------------------------------------------------- 2021-09-06 cse:
add µc resource consumption objectives to architecture concept.
create related task, effort ~2h |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - Scheduling&Timing - Provide SwAD Spec
--------------------------------------------------------------------------------
Details (Exact description):
Request: Provide SwAD specification for static Scheduling&Timing test with tool SwAD OsConfigChecker.
Therefore Caesar provided an updated document version of VW_MQB_SCS_Partitioning.xlsm.
The same format should be used as for previous test execution of SwAD_OsConfigChecker, which was only executed once, see attached email.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): VW_MQB_SCS_Partitioning.xlsm
--------------------------------------------------------------------------------
Output Work Products: Updated document VW_MQB_SCS_Partitioning.xlsm, for next VW MQB ESC 0403 ALM_Deliver 3018912
--------------------------------------------------------------------------------
Acceptance Criteria: The document VW_MQB_SCS_Partitioning.xlsm is available for next VW MQB ESC 0403 ALM_Deliver 3018912, to execute SwAD_OsConfigChecker.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The document is attache to this CR, which shall be checked in.
It is based on the Partitioning document 1.61.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:Check in manual paritioning export for OsConfigChecker
Description:
Check in manual paritioning export for OsConfigChecker
Owner:Caesar
Reviewer:Jeremy
------------------------------------------------------
Total effort/h:1
[Optional] Planned completion date:today
------------------------------------------------------ | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - Scheduling&Timing - Provide SwAD Spec
--------------------------------------------------------------------------------
Details (Exact description):
Request: Provide SwAD specification for static Scheduling&Timing test with tool SwAD OsConfigChecker.
Therefore Caesar provided an updated document version of VW_MQB_SCS_Partitioning.xlsm.
The same format should be used as for previous test execution of SwAD_OsConfigChecker, which was only executed once, see attached email.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): VW_MQB_SCS_Partitioning.xlsm
--------------------------------------------------------------------------------
Output Work Products: Updated document VW_MQB_SCS_Partitioning.xlsm, for next VW MQB ESC 0403 ALM_Deliver 3018912
--------------------------------------------------------------------------------
Acceptance Criteria: The document VW_MQB_SCS_Partitioning.xlsm is available for next VW MQB ESC 0403 ALM_Deliver 3018912, to execute SwAD_OsConfigChecker.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The document is attache to this CR, which shall be checked in.
It is based on the Partitioning document 1.61.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:Check in manual paritioning export for OsConfigChecker
Description:
Check in manual paritioning export for OsConfigChecker
Owner:Caesar
Reviewer:Jeremy
------------------------------------------------------
Total effort/h:1
[Optional] Planned completion date:today
------------------------------------------------------ |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - Scheduling&Timing - Provide SwAD Spec Partitioning created by RPY Model
--------------------------------------------------------------------------------
Details (Exact description):
Required: ALM_Change Request 5490484 should provided information about required format
Required: ALM_Review 5208770 should check if all required data for input of tool SwAD_OsConfigChecker is available in the SwAD RPY Model.
Request: Provide SwAD specification for static Scheduling&Timing test with tool SwAD OsConfigChecker.
The document document VW_MQB_SCS_Partitioning.xlsm (same format as from CR5490484) should be created automatically based on the data from SwAD RPY Model.
Furthermore, document VW_MQB_SCS_Partitioning.xlsm should be added as required default item for the task called "Finalize Build", which is created for SwAD_Baseline, see example Task 5044046.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5490484
--------------------------------------------------------------------------------
Output Work Products: Updated document VW_MQB_SCS_Partitioning.xlsm
--------------------------------------------------------------------------------
Acceptance Criteria: The Partitioning document is automatically created as an export from SwAD RPY Model, an added as default item for Finalize Build Task.
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2022-05-30, 11:19:15]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
As agreed between SWE.2 and SWE.5, this document will not be updated for VW MQB.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - Scheduling&Timing - Provide SwAD Spec Partitioning created by RPY Model
--------------------------------------------------------------------------------
Details (Exact description):
Required: ALM_Change Request 5490484 should provided information about required format
Required: ALM_Review 5208770 should check if all required data for input of tool SwAD_OsConfigChecker is available in the SwAD RPY Model.
Request: Provide SwAD specification for static Scheduling&Timing test with tool SwAD OsConfigChecker.
The document document VW_MQB_SCS_Partitioning.xlsm (same format as from CR5490484) should be created automatically based on the data from SwAD RPY Model.
Furthermore, document VW_MQB_SCS_Partitioning.xlsm should be added as required default item for the task called "Finalize Build", which is created for SwAD_Baseline, see example Task 5044046.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5490484
--------------------------------------------------------------------------------
Output Work Products: Updated document VW_MQB_SCS_Partitioning.xlsm
--------------------------------------------------------------------------------
Acceptance Criteria: The Partitioning document is automatically created as an export from SwAD RPY Model, an added as default item for Finalize Build Task.
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2022-05-30, 11:19:15]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
As agreed between SWE.2 and SWE.5, this document will not be updated for VW MQB.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swad - update rpy model export - schedulingtable
--------------------------------------------------------------------------------
details (exact description): the following information should be added to the document swad_model-schedulingtable.csv exported from swad rpy model.
1. add core information for each runnable to the new attribute “960_core relation".
a. add core information for each runnable e.g. runnable updatefm for core0 and updatefm for core1.
i. this means a cyclic runnable like updatefm 10ms can be available on core0 and core1
ii. this means a init runnable like runnableinit can be called on core0 and on core1 during inilisation.
b. add core information to object text for runnable
c. “960_core relation" should contain only numbers
2. add new format for runnable with function argument call, like activatetask or trw_synchere
a. today the specification says only as runnable name only "activatetask_task_10ms_send_d_c1"
instead a specification is required, which allows to distinguish between runnable name and runnable function argument, e.g. "activatetask(task_10ms_send_d_c1) or activatetask.task_10ms_send_d_c1
3. rename in the export the attribute "951period time" to "951_period time".
4. remove the following attributes from the export "020_review assignment", "021_review agreed", "022_review not agreed", "023_review comment".
5. change text of attribute "057_testcomment", current text: "attributes 050_test department, 051_verificationmethod, 066_test department accepted, 067_test department not accepted are automatically filled during export from architecture model."
the attribute should be seperated by another character than "," or ";" because this may cause issues during excel csv conversion and import to doors.
6. the attribute "921_project architecture" contains only the value "swad_model", but this should be project specific like in export version before, e.g. "swad_vw_mqb48w_esc".
7. the attribute "951_period time" should not contain the character "_" before a number, like "_5ms". instead it should be "5ms".
8. runnable name of vx1000_* name should be correct or function name and function argument name should be split up.
9. runnable name of activatetask_* should be removed from specification if not available as runnable in the software.
10. runnable name of trw_synchere_* should be corrected, as function name and function argument name should be split up. furthermore, for good test results to information for attribute 960_core relation is needed.
11. runnable name should not contain the componentname as prefix, e.g. "faultmanager_updatefm" should be specified as "updatefm".
12. the attribute "951_period time" should be capable to specify numbers with comma/point, e.g. runnable "pbasic_pbasicmaindispatcherfasttask" was specified as 2.5ms but the export only contains 2ms.
13. runnable called during init should be specified with "951_period time=inilization", e.g. the following runnable may be an issue: runnable "hsb_init" was specified with a period time of 20ms, but may be specified as inilization period time.
14. runnable name should be unique in the complete sw and should be called only from one task, e.g. the runnable fmsyncrxprocess shouldn't be called from init and cyclic task.
information: specified runnable name from swad needs to be as function name in the software, otherwise no match is possible.
2021-08-23: meeting took place with (cseifen, bbauer, pruckhaber, lhoppe, janczykowski), review done of attached document for runnablecyclechecker and runnablesequencechecker report for 0401-008 sw, see also cr 5360207.
--------------------------------------------------------------------------------
input work products (link or other reference): https://skobde-mks.kobde.trw.com:7001/si/viewrevision?projectname=/brk/customer/vw/mqb48%2dw/esc/05%5fsoftware/01%5farchitecture%5fdesign/04%5fswad%5fmodel/project.pj&developmentpath=vw%5fcommon%5fesc&selection=swad%5fmodel%2dschedulingtable.csv rev 1.9
--------------------------------------------------------------------------------
output work products: updated document swad_model-schedulingtable.csv
--------------------------------------------------------------------------------
acceptance criteria: core information is available for each runnable, function argument name can be distinguished from runnable name
-------------------------------------------------------------------------------- [benjamin bauer (bauerb), 2022-02-15, 10:29:12]
--------------------------------------------------------------------------------
brief investigation comment:
the topics can be split into two parts
- changes to the exporter tool and changes in the model.
this cr will take care to implement the exporter topics, the model changes are split into a spawned cr.
exporter changes
1. add core information for each runnable to the new attribute “960_core relation".
a. add core information for each runnable e.g. runnable updatefm for core0 and updatefm for core1.
->can be done (medium effort, because runnables need to be traced to tasks, etc.)
i. this means a cyclic runnable like updatefm 10ms can be available on core0 and core1
ii. this means a init runnable like runnableinit can be called on core0 and on core1 during initialisation.
b. add core information to object text for runnable
c. “960_core relation" should contain only numbers
-> cores have a name in sw architecture. therefore numbers only is not possible.
3. rename in the export the attribute "951period time" to "951_period time".
4. remove the following attributes from the export "020_review assignment", "021_review agreed", "022_review not agreed", "023_review comment".
5. change text of attribute "057_testcomment", current text: "attributes 050_test department, 051_verificationmethod, 066_test department accepted, 067_test department not accepted are automatically filled during export from architecture model."
the attribute should be seperated by another character than "," or ";" because this may cause issues during excel csv conversion and import to doors.
6. the attribute "921_project architecture" contains only the value "swad_model", but this should be project specific like in export version before, e.g. "swad_vw_mqb48w_esc".’
->the architecture model is named as “swad model”. the only way to get the project name would be from integrity development path. (to be analysed if feasible, but can be tried)
7. the attribute "951_period time" should not contain the character "_" before a number, like "_5ms". instead it should be "5ms".
additional (meeting 2022-02-15): add information on extended task to period time.
changes in model
2. add new format for runnable with function argument call, like activatetask or trw_synchere
a. today the specification says only as runnable name only "activatetask_task_10ms_send_d_c1" instead a specification is required, which allows to distinguish between runnable name and runnable function argument, e.g. "activatetask(task_10ms_send_d_c1) or activatetask.task_10ms_send_d_c1
8. runnable name of vx1000_* name should be corrected or function name and function argument name should be split up.
9. runnable name of activatetask_* should be removed from specification if not available as runnable in the software.
10. runnable name of trw_synchere_* should be corrected, as function name and function argument name should be split up. furthermore, for good test results to information for attribute 960_core relation is needed.
11. runnable name should not contain the componentname as prefix, e.g. "faultmanager_updatefm" should be specified as "updatefm".
èchange property of project (swad_model): c_cg:object:publicname to $opname
12. the attribute "951_period time" should be capable to specify numbers with comma/point, e.g. runnable "pbasic_pbasicmaindispatcherfasttask" was specified as 2.5ms but the export only contains 2ms.
è the tag allocation is based on steering enumeration which does not have a value for 2.5 ms.
è requires a generic solution (specification of period time in different way ?)
13. runnable called during init should be specified with "951_period time=inilization", e.g. the following runnable may be an issue: runnable "hsb_init" was specified with a period time of 20ms, but may be specified as inilization period time.
14. runnable name should be unique in the complete sw and should be called only from one task, e.g. the runnable fmsyncrxprocess shouldn't be called from init and cyclic task.
information: specified runnable name from swad needs to be as function name in the software, otherwise no match is possible.
--------------------------------------------------------------------------------
risk (low/medium/high): medium
--------------------------------------------------------------------------------
proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
task 1
-------------------------------
title/header: see cr
description: see investigation
assigned to: ben bauer
verifier: jens auer
estimated effort: 8h
------------------------------- | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swad - update rpy model export - schedulingtable
--------------------------------------------------------------------------------
details (exact description): the following information should be added to the document swad_model-schedulingtable.csv exported from swad rpy model.
1. add core information for each runnable to the new attribute “960_core relation".
a. add core information for each runnable e.g. runnable updatefm for core0 and updatefm for core1.
i. this means a cyclic runnable like updatefm 10ms can be available on core0 and core1
ii. this means a init runnable like runnableinit can be called on core0 and on core1 during inilisation.
b. add core information to object text for runnable
c. “960_core relation" should contain only numbers
2. add new format for runnable with function argument call, like activatetask or trw_synchere
a. today the specification says only as runnable name only "activatetask_task_10ms_send_d_c1"
instead a specification is required, which allows to distinguish between runnable name and runnable function argument, e.g. "activatetask(task_10ms_send_d_c1) or activatetask.task_10ms_send_d_c1
3. rename in the export the attribute "951period time" to "951_period time".
4. remove the following attributes from the export "020_review assignment", "021_review agreed", "022_review not agreed", "023_review comment".
5. change text of attribute "057_testcomment", current text: "attributes 050_test department, 051_verificationmethod, 066_test department accepted, 067_test department not accepted are automatically filled during export from architecture model."
the attribute should be seperated by another character than "," or ";" because this may cause issues during excel csv conversion and import to doors.
6. the attribute "921_project architecture" contains only the value "swad_model", but this should be project specific like in export version before, e.g. "swad_vw_mqb48w_esc".
7. the attribute "951_period time" should not contain the character "_" before a number, like "_5ms". instead it should be "5ms".
8. runnable name of vx1000_* name should be correct or function name and function argument name should be split up.
9. runnable name of activatetask_* should be removed from specification if not available as runnable in the software.
10. runnable name of trw_synchere_* should be corrected, as function name and function argument name should be split up. furthermore, for good test results to information for attribute 960_core relation is needed.
11. runnable name should not contain the componentname as prefix, e.g. "faultmanager_updatefm" should be specified as "updatefm".
12. the attribute "951_period time" should be capable to specify numbers with comma/point, e.g. runnable "pbasic_pbasicmaindispatcherfasttask" was specified as 2.5ms but the export only contains 2ms.
13. runnable called during init should be specified with "951_period time=inilization", e.g. the following runnable may be an issue: runnable "hsb_init" was specified with a period time of 20ms, but may be specified as inilization period time.
14. runnable name should be unique in the complete sw and should be called only from one task, e.g. the runnable fmsyncrxprocess shouldn't be called from init and cyclic task.
information: specified runnable name from swad needs to be as function name in the software, otherwise no match is possible.
2021-08-23: meeting took place with (cseifen, bbauer, pruckhaber, lhoppe, janczykowski), review done of attached document for runnablecyclechecker and runnablesequencechecker report for 0401-008 sw, see also cr 5360207.
--------------------------------------------------------------------------------
input work products (link or other reference): https://skobde-mks.kobde.trw.com:7001/si/viewrevision?projectname=/brk/customer/vw/mqb48%2dw/esc/05%5fsoftware/01%5farchitecture%5fdesign/04%5fswad%5fmodel/project.pj&developmentpath=vw%5fcommon%5fesc&selection=swad%5fmodel%2dschedulingtable.csv rev 1.9
--------------------------------------------------------------------------------
output work products: updated document swad_model-schedulingtable.csv
--------------------------------------------------------------------------------
acceptance criteria: core information is available for each runnable, function argument name can be distinguished from runnable name
-------------------------------------------------------------------------------- [benjamin bauer (bauerb), 2022-02-15, 10:29:12]
--------------------------------------------------------------------------------
brief investigation comment:
the topics can be split into two parts
- changes to the exporter tool and changes in the model.
this cr will take care to implement the exporter topics, the model changes are split into a spawned cr.
exporter changes
1. add core information for each runnable to the new attribute “960_core relation".
a. add core information for each runnable e.g. runnable updatefm for core0 and updatefm for core1.
->can be done (medium effort, because runnables need to be traced to tasks, etc.)
i. this means a cyclic runnable like updatefm 10ms can be available on core0 and core1
ii. this means a init runnable like runnableinit can be called on core0 and on core1 during initialisation.
b. add core information to object text for runnable
c. “960_core relation" should contain only numbers
-> cores have a name in sw architecture. therefore numbers only is not possible.
3. rename in the export the attribute "951period time" to "951_period time".
4. remove the following attributes from the export "020_review assignment", "021_review agreed", "022_review not agreed", "023_review comment".
5. change text of attribute "057_testcomment", current text: "attributes 050_test department, 051_verificationmethod, 066_test department accepted, 067_test department not accepted are automatically filled during export from architecture model."
the attribute should be seperated by another character than "," or ";" because this may cause issues during excel csv conversion and import to doors.
6. the attribute "921_project architecture" contains only the value "swad_model", but this should be project specific like in export version before, e.g. "swad_vw_mqb48w_esc".’
->the architecture model is named as “swad model”. the only way to get the project name would be from integrity development path. (to be analysed if feasible, but can be tried)
7. the attribute "951_period time" should not contain the character "_" before a number, like "_5ms". instead it should be "5ms".
additional (meeting 2022-02-15): add information on extended task to period time.
changes in model
2. add new format for runnable with function argument call, like activatetask or trw_synchere
a. today the specification says only as runnable name only "activatetask_task_10ms_send_d_c1" instead a specification is required, which allows to distinguish between runnable name and runnable function argument, e.g. "activatetask(task_10ms_send_d_c1) or activatetask.task_10ms_send_d_c1
8. runnable name of vx1000_* name should be corrected or function name and function argument name should be split up.
9. runnable name of activatetask_* should be removed from specification if not available as runnable in the software.
10. runnable name of trw_synchere_* should be corrected, as function name and function argument name should be split up. furthermore, for good test results to information for attribute 960_core relation is needed.
11. runnable name should not contain the componentname as prefix, e.g. "faultmanager_updatefm" should be specified as "updatefm".
èchange property of project (swad_model): c_cg:object:publicname to $opname
12. the attribute "951_period time" should be capable to specify numbers with comma/point, e.g. runnable "pbasic_pbasicmaindispatcherfasttask" was specified as 2.5ms but the export only contains 2ms.
è the tag allocation is based on steering enumeration which does not have a value for 2.5 ms.
è requires a generic solution (specification of period time in different way ?)
13. runnable called during init should be specified with "951_period time=inilization", e.g. the following runnable may be an issue: runnable "hsb_init" was specified with a period time of 20ms, but may be specified as inilization period time.
14. runnable name should be unique in the complete sw and should be called only from one task, e.g. the runnable fmsyncrxprocess shouldn't be called from init and cyclic task.
information: specified runnable name from swad needs to be as function name in the software, otherwise no match is possible.
--------------------------------------------------------------------------------
risk (low/medium/high): medium
--------------------------------------------------------------------------------
proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
task 1
-------------------------------
title/header: see cr
description: see investigation
assigned to: ben bauer
verifier: jens auer
estimated effort: 8h
------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.2 - Scheduling & Timing - OIE Runnable Spec
--------------------------------------------------------------------------------
Details (Exact description):
Request: Clarify SwAD internal wether specification for Operation Invoked Event (OIE) Runnable is required for Scheduling & Timing Model in SwAD Rhapsody Model.
If yes, develop SwAD strategy to specify OIE Runnable for Scheduling & Timing Model in SwAD Rhapsody Model.
This strategy should consider specifications, which are testable e.g. today it is already possible to invoke a Rte_Call_* function and to check afterwards if the related runnable is called.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current SwAD Rhapsody Model
--------------------------------------------------------------------------------
Output Work Products: Update SwAD Rhapsody Model
--------------------------------------------------------------------------------
Acceptance Criteria: Decision available weather OIE Runnable will be specified from SwAD (yes/no). If yes, strategy "how to".
-------------------------------------------------------------------------------- SWAD plan round CBa,CSK,SSp: Quick analyze, not needed for this project. Especially OIE have no order, only relevant in the timing event.
@CCB: Please reject this CR
SwAD CCB - Ssp, JAu, RLo: Owner(s) assigned, CR switched to 'Checked' state. Please analyse and propose next steps. | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.2 - Scheduling & Timing - OIE Runnable Spec
--------------------------------------------------------------------------------
Details (Exact description):
Request: Clarify SwAD internal wether specification for Operation Invoked Event (OIE) Runnable is required for Scheduling & Timing Model in SwAD Rhapsody Model.
If yes, develop SwAD strategy to specify OIE Runnable for Scheduling & Timing Model in SwAD Rhapsody Model.
This strategy should consider specifications, which are testable e.g. today it is already possible to invoke a Rte_Call_* function and to check afterwards if the related runnable is called.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current SwAD Rhapsody Model
--------------------------------------------------------------------------------
Output Work Products: Update SwAD Rhapsody Model
--------------------------------------------------------------------------------
Acceptance Criteria: Decision available weather OIE Runnable will be specified from SwAD (yes/no). If yes, strategy "how to".
-------------------------------------------------------------------------------- SWAD plan round CBa,CSK,SSp: Quick analyze, not needed for this project. Especially OIE have no order, only relevant in the timing event.
@CCB: Please reject this CR
SwAD CCB - Ssp, JAu, RLo: Owner(s) assigned, CR switched to 'Checked' state. Please analyse and propose next steps. |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs Design scheduling for init phase [Michael Fischbach, 2021-04-27, 09:33:54]:
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
The scheduling for the init phase needs to be adapted to allow freedom from interference also in the init phase. Currently the
existing tasks contain runnables of differenty ASIL levels.
The scheduling of the init phase shall be aligned to the init scheduling used in VW MQB project.
Impact on Software Architecture:
Define Structure:
Define Static and Dynamic Behavior:
Perform Requirements Linkage:
Define Interfaces:
Define Resource Budget:
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header: Design the scheduling for the init phase
Description: Model the scheduling for the init phase in the SW architecture model for cores 0 and 1. Use partitioning concept from VW MQB project as baseline.
Assigned to: Michael Fischbach
Verifier: Jens Auer
Estimated effort: 32
------------------------------- | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs Design scheduling for init phase [Michael Fischbach, 2021-04-27, 09:33:54]:
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
The scheduling for the init phase needs to be adapted to allow freedom from interference also in the init phase. Currently the
existing tasks contain runnables of differenty ASIL levels.
The scheduling of the init phase shall be aligned to the init scheduling used in VW MQB project.
Impact on Software Architecture:
Define Structure:
Define Static and Dynamic Behavior:
Perform Requirements Linkage:
Define Interfaces:
Define Resource Budget:
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
--------------------------------------------------------------------------------
TASK 1
-------------------------------
Title/Header: Design the scheduling for the init phase
Description: Model the scheduling for the init phase in the SW architecture model for cores 0 and 1. Use partitioning concept from VW MQB project as baseline.
Assigned to: Michael Fischbach
Verifier: Jens Auer
Estimated effort: 32
------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - Scheduling&Timing - Request SwAD Spec LSM/TSM
--------------------------------------------------------------------------------
Details (Exact description):
Request: Provide SwAD specification for LSM/TSM configuration to improve dynamic Scheduling&Timing test in RPY SwAD Model.
The information about LSM/TSM configuration should be added to the export SwAD_Model-SchedulingTable.csv document.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current RPY SwAD Model
--------------------------------------------------------------------------------
Output Work Products: Updated RPY SwAD Model, Updated SwAD_Model-SchedulingTable.csv
--------------------------------------------------------------------------------
Acceptance Criteria: LSM/TSM specification are available in SwAD_Model-SchedulingTable.csv document.
-------------------------------------------------------------------------------- 2021-09-09 CSe: Current approach does not require dedicated LSM/TSM specification in SW Architecture. LSM/TSM are detailed design safety mechanisms to detect errors in sequential execution of runnables.
[2024-03-01 bauerb - SwArch]
Based on statement of CSe (above) and attached in mail, it is proposed to reject the CR | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - Scheduling&Timing - Request SwAD Spec LSM/TSM
--------------------------------------------------------------------------------
Details (Exact description):
Request: Provide SwAD specification for LSM/TSM configuration to improve dynamic Scheduling&Timing test in RPY SwAD Model.
The information about LSM/TSM configuration should be added to the export SwAD_Model-SchedulingTable.csv document.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current RPY SwAD Model
--------------------------------------------------------------------------------
Output Work Products: Updated RPY SwAD Model, Updated SwAD_Model-SchedulingTable.csv
--------------------------------------------------------------------------------
Acceptance Criteria: LSM/TSM specification are available in SwAD_Model-SchedulingTable.csv document.
-------------------------------------------------------------------------------- 2021-09-09 CSe: Current approach does not require dedicated LSM/TSM specification in SW Architecture. LSM/TSM are detailed design safety mechanisms to detect errors in sequential execution of runnables.
[2024-03-01 bauerb - SwArch]
Based on statement of CSe (above) and attached in mail, it is proposed to reject the CR |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
The outputs delivered by the BrkSw Architecture SW Team to the BrkSw Build Test Team need to be checked before being delivered.
--------------------------------------------------------------------------------
Details (Exact description):
Currently there is no check performed by the BrkSw Architecture SW Team on the Rhapsody exports for SWE.5. In order to avoid unnecessary work on SWE.5 side, all the outputs need to be checked by a Quality Gate.
Quality Gate should consider at least:
- all the defined and agreed attributes are filled
- consistency check (correct runnables, provider/receiver paths, return types, data types etc)
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Targeted workflow SwAD
--------------------------------------------------------------------------------
Output Work Products: Quality Gateway on the Rhapsody Exports for SWE.5
--------------------------------------------------------------------------------
Acceptance Criteria:
Guideline:
- Quality Gateway provides a reports of the performed checks
- Quality Gateway informs SW ARCH that some rework is required
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-04-12, 09:29:40]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
The following quality gateway checks have been proposed and agreed by Integration test:
Data type checks (generic, for data elements or operation return values):
- Data type is not defined or not defined a Type model element.
- Enumeration type does not have literals
Autosar S/R interfaces:
- No Sender port or multiple sender ports found
- No receiver port found
- Interface does not have data elements
- Port access dependency (Runnable->Port) to be present for sender and receiver
- Data access dependency at least for one data element
Direct C-Function call interfaces:
- No provide port or multiple provider ports found
- No receiver port found
- Naming convention checks:
- Get-/Is-functions must have a non-void return type
- void(void) functions named Init-/Reinit-/Update- are considered as runnable and not C-function call interface
Linked Autosar S/R interfaces:
- Connection must start with sender and end with receiver port
- connection start and end must have same type (interface)
- all parts of connection must have same type (only as warning)
- connection must follow hierarchy rules
- direct connection between two components of different domains or domains of different platforms is not allowed
- direct connection between component and platform (omitting domain) not allowed.
Task export:
Task must have a ScheduleRunnables operation which contains one sequence diagram which is not empty.
Functionality:
The items which fail the quality gateway criteria are not exported. Errors are given while exporting.
In order to systematically capture and close these findings, the model checker shall implement checks which find the erroneous modeling
(not all quality gateway findings may be erroneous modeling, e.g. it could be that an interface is defined but dedicatedly not connected in a project. The quality gateway would find that as error for the export, but it's not a modeling error to be captured by the model checker)
Next steps:
- The quality gateway checks are to be implemented in the SWE.5 exporters => Task 4296870
- The model checker shall be adapted accordingly => New task
It should be checked if an elegant method could be found to re-use the same checks for both.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
1. Link available task 4298670
TASK 2
-------------------------------
Title/Header: Extend model checker with interface quality gateway checks
Description: see investigation
Assigned to: Ben Bauer
Verifier: Rene Lotz
Estimated effort: 16h
------------------------------- | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
The outputs delivered by the BrkSw Architecture SW Team to the BrkSw Build Test Team need to be checked before being delivered.
--------------------------------------------------------------------------------
Details (Exact description):
Currently there is no check performed by the BrkSw Architecture SW Team on the Rhapsody exports for SWE.5. In order to avoid unnecessary work on SWE.5 side, all the outputs need to be checked by a Quality Gate.
Quality Gate should consider at least:
- all the defined and agreed attributes are filled
- consistency check (correct runnables, provider/receiver paths, return types, data types etc)
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Targeted workflow SwAD
--------------------------------------------------------------------------------
Output Work Products: Quality Gateway on the Rhapsody Exports for SWE.5
--------------------------------------------------------------------------------
Acceptance Criteria:
Guideline:
- Quality Gateway provides a reports of the performed checks
- Quality Gateway informs SW ARCH that some rework is required
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-04-12, 09:29:40]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
The following quality gateway checks have been proposed and agreed by Integration test:
Data type checks (generic, for data elements or operation return values):
- Data type is not defined or not defined a Type model element.
- Enumeration type does not have literals
Autosar S/R interfaces:
- No Sender port or multiple sender ports found
- No receiver port found
- Interface does not have data elements
- Port access dependency (Runnable->Port) to be present for sender and receiver
- Data access dependency at least for one data element
Direct C-Function call interfaces:
- No provide port or multiple provider ports found
- No receiver port found
- Naming convention checks:
- Get-/Is-functions must have a non-void return type
- void(void) functions named Init-/Reinit-/Update- are considered as runnable and not C-function call interface
Linked Autosar S/R interfaces:
- Connection must start with sender and end with receiver port
- connection start and end must have same type (interface)
- all parts of connection must have same type (only as warning)
- connection must follow hierarchy rules
- direct connection between two components of different domains or domains of different platforms is not allowed
- direct connection between component and platform (omitting domain) not allowed.
Task export:
Task must have a ScheduleRunnables operation which contains one sequence diagram which is not empty.
Functionality:
The items which fail the quality gateway criteria are not exported. Errors are given while exporting.
In order to systematically capture and close these findings, the model checker shall implement checks which find the erroneous modeling
(not all quality gateway findings may be erroneous modeling, e.g. it could be that an interface is defined but dedicatedly not connected in a project. The quality gateway would find that as error for the export, but it's not a modeling error to be captured by the model checker)
Next steps:
- The quality gateway checks are to be implemented in the SWE.5 exporters => Task 4296870
- The model checker shall be adapted accordingly => New task
It should be checked if an elegant method could be found to re-use the same checks for both.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
1. Link available task 4298670
TASK 2
-------------------------------
Title/Header: Extend model checker with interface quality gateway checks
Description: see investigation
Assigned to: Ben Bauer
Verifier: Rene Lotz
Estimated effort: 16h
------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Provide Platform Interface List Export
--------------------------------------------------------------------------------
Details (Exact description):
In order to assure the traceability for the Platform Interfaces to the Architectural model, an export shall be provided.
The architectural checkpoint which contains all the inter platform interfaces is CP: 1.103
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Attachment: AW Status Rte Migraiton VW MQB48-W Introduction of new project generic.msg
--------------------------------------------------------------------------------
Output Work Products: Platform Interface List Export
--------------------------------------------------------------------------------
Acceptance Criteria: Complete Platform Interface List Export.
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-04-12, 09:07:45]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
Except for deriving interfaces via the links as shown above, the generator shall generate a similar export to the Autosar SR Interfaces export.
One addition: The sender/receiver path information shall include the hierarchy Platform->Domain->Component as far as applicable.
In order to allow this, all technical architecture domains shall be instantiated in the platforms (and declared as external to prevent that their information is exported by autosar exporter)
This could be covered as well in Task 4296870
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Link available task 4296870 | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Provide Platform Interface List Export
--------------------------------------------------------------------------------
Details (Exact description):
In order to assure the traceability for the Platform Interfaces to the Architectural model, an export shall be provided.
The architectural checkpoint which contains all the inter platform interfaces is CP: 1.103
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Attachment: AW Status Rte Migraiton VW MQB48-W Introduction of new project generic.msg
--------------------------------------------------------------------------------
Output Work Products: Platform Interface List Export
--------------------------------------------------------------------------------
Acceptance Criteria: Complete Platform Interface List Export.
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-04-12, 09:07:45]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
Except for deriving interfaces via the links as shown above, the generator shall generate a similar export to the Autosar SR Interfaces export.
One addition: The sender/receiver path information shall include the hierarchy Platform->Domain->Component as far as applicable.
In order to allow this, all technical architecture domains shall be instantiated in the platforms (and declared as external to prevent that their information is exported by autosar exporter)
This could be covered as well in Task 4296870
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Link available task 4296870 |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Rhapsody Detailed Design Model - ComponentList OldFormat
--------------------------------------------------------------------------------
Details (Exact description): Provide ComponentList Export based on new information from Rhapsody Detailed Design Model in the old ComponentList format + memory section information, as specified in CR 5037625.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5037625
--------------------------------------------------------------------------------
Output Work Products: ComponentList Export from Rhapsody Detailed Design Model in the OldFormat + memory section information for VW MQB ESC project.
--------------------------------------------------------------------------------
Acceptance Criteria: The ComponentList format is based on the old format and contains also the "Component / RamBudget / allocation / section" information, like in the new ComponentList Export.
-------------------------------------------------------------------------------- 2021-06-09 16:46:40 RBr:the required Model and Scipt updates are done with an previous CR and both exports ( old and new Format) are available.
==> reject this CR | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Rhapsody Detailed Design Model - ComponentList OldFormat
--------------------------------------------------------------------------------
Details (Exact description): Provide ComponentList Export based on new information from Rhapsody Detailed Design Model in the old ComponentList format + memory section information, as specified in CR 5037625.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5037625
--------------------------------------------------------------------------------
Output Work Products: ComponentList Export from Rhapsody Detailed Design Model in the OldFormat + memory section information for VW MQB ESC project.
--------------------------------------------------------------------------------
Acceptance Criteria: The ComponentList format is based on the old format and contains also the "Component / RamBudget / allocation / section" information, like in the new ComponentList Export.
-------------------------------------------------------------------------------- 2021-06-09 16:46:40 RBr:the required Model and Scipt updates are done with an previous CR and both exports ( old and new Format) are available.
==> reject this CR |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - PartitioningAnalysis - Update OS input file
--------------------------------------------------------------------------------
Details (Exact description):
The tool MapFileAnalyzer uses for the PartitioningAnalysis the file "Os_Hal_MemoryProtection_Lcfg.c" to get available partitions including it's start- and end-address.
Request: Update Os_Hal_MemoryProtection_Lcfg.c with all available ram and rom partitions from PartitioningWizard, see example below:
This is needed for a proper working of the tool MapFileAnalyzer - PartitioningAnalysis feature.
Ram Partitions:
The start address should be "BeginOf_"+ partition name for ram partitions.
The end address should be "EndOf_"+ partition name for ram partitions.
Rom Partitions:
The start address should be "_lc_gb_ROMSections_"+ partition name for rom partitions.
The end address should be "_lc_ge_ROMSections_" + partition name for rom partitions.
Topic was discussed with Martin Krolikowski.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Os_Hal_MemoryProtection_Lcfg.c
--------------------------------------------------------------------------------
Output Work Products: Updated Os_Hal_MemoryProtection_Lcfg.c
--------------------------------------------------------------------------------
Acceptance Criteria: All available ram and rom partitions from PartitioningWizard, are available in Os_Hal_MemoryProtection_Lcfg.c file with start- and end-address, which start with BeginOf_* and end with EndOf_*.
-------------------------------------------------------------------------------- With latest MPU Integration with MQB ESC the naming conventions are updated according to request above. Therefore CR can be rejected because all changes are implemented with CR 4744470. | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.5 - SoftwareIntegrationTest - PartitioningAnalysis - Update OS input file
--------------------------------------------------------------------------------
Details (Exact description):
The tool MapFileAnalyzer uses for the PartitioningAnalysis the file "Os_Hal_MemoryProtection_Lcfg.c" to get available partitions including it's start- and end-address.
Request: Update Os_Hal_MemoryProtection_Lcfg.c with all available ram and rom partitions from PartitioningWizard, see example below:
This is needed for a proper working of the tool MapFileAnalyzer - PartitioningAnalysis feature.
Ram Partitions:
The start address should be "BeginOf_"+ partition name for ram partitions.
The end address should be "EndOf_"+ partition name for ram partitions.
Rom Partitions:
The start address should be "_lc_gb_ROMSections_"+ partition name for rom partitions.
The end address should be "_lc_ge_ROMSections_" + partition name for rom partitions.
Topic was discussed with Martin Krolikowski.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Os_Hal_MemoryProtection_Lcfg.c
--------------------------------------------------------------------------------
Output Work Products: Updated Os_Hal_MemoryProtection_Lcfg.c
--------------------------------------------------------------------------------
Acceptance Criteria: All available ram and rom partitions from PartitioningWizard, are available in Os_Hal_MemoryProtection_Lcfg.c file with start- and end-address, which start with BeginOf_* and end with EndOf_*.
-------------------------------------------------------------------------------- With latest MPU Integration with MQB ESC the naming conventions are updated according to request above. Therefore CR can be rejected because all changes are implemented with CR 4744470. |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swe.5 - softwareintegrationtest - partitioninganalysis - request swad spec update
--------------------------------------------------------------------------------
details (exact description):
after review of componentlist export from rpy dd model, it was identified that not all information for a ram memory partition (and rom memory partition) is available in the rpy swad model for each swad_component.
request: please add ram memory partition relation (and rom memory partition relation) to the swad_component of list "rammemorypartition_info_missing.txt" from the attachment and check if all ram memory partiton (and rom memory partiton) are up to date.
--------------------------------------------------------------------------------
input work products (link or other reference): vw mqb esc - cp:1.633.1.312 , link to rpy detaileddesign model - componentlist
--------------------------------------------------------------------------------
output work products: updated rpy swad model
--------------------------------------------------------------------------------
acceptance criteria: memorypartition reference for ram (and rom) is available for all swad_component and are up to date.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
[09/07/2021, venu ponnaboaina]
--------------------------------------------------------------------------------
brief analysis summary:
--------------------------------------------------------------------------------
---> component list generation plug in needs to updated for proper component list xml generation.
---> as conformation received from ben, he is already working on fix.
--> with the cr#4325201, issue will be resolved.please refer attached mail for more info.
hence no further improvements required with this cr.
--------------------------------------------------------------------------------
risk (low/medium/high): low
--------------------------------------------------------------------------------
proposal of next steps (incl. effort / h and verification):
-------------------------
@ccb: please reject this cr. | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swe.5 - softwareintegrationtest - partitioninganalysis - request swad spec update
--------------------------------------------------------------------------------
details (exact description):
after review of componentlist export from rpy dd model, it was identified that not all information for a ram memory partition (and rom memory partition) is available in the rpy swad model for each swad_component.
request: please add ram memory partition relation (and rom memory partition relation) to the swad_component of list "rammemorypartition_info_missing.txt" from the attachment and check if all ram memory partiton (and rom memory partiton) are up to date.
--------------------------------------------------------------------------------
input work products (link or other reference): vw mqb esc - cp:1.633.1.312 , link to rpy detaileddesign model - componentlist
--------------------------------------------------------------------------------
output work products: updated rpy swad model
--------------------------------------------------------------------------------
acceptance criteria: memorypartition reference for ram (and rom) is available for all swad_component and are up to date.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
[09/07/2021, venu ponnaboaina]
--------------------------------------------------------------------------------
brief analysis summary:
--------------------------------------------------------------------------------
---> component list generation plug in needs to updated for proper component list xml generation.
---> as conformation received from ben, he is already working on fix.
--> with the cr#4325201, issue will be resolved.please refer attached mail for more info.
hence no further improvements required with this cr.
--------------------------------------------------------------------------------
risk (low/medium/high): low
--------------------------------------------------------------------------------
proposal of next steps (incl. effort / h and verification):
-------------------------
@ccb: please reject this cr. |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [ESC] MapFileAnalyzer - BudgetComparison Config Update
--------------------------------------------------------------------------------
Details (Exact description): After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/SCS/ToolDevelopment/MapFileAnalyzer/Ti4x/Ti4x%5fGEN%5f3/1%5fBinaries/BUILD%5fVIEW/project.pj&projectrevision=1.13.1.2
--------------------------------------------------------------------------------
Output Work Products: Updated MapFileAnalyzer configuration
--------------------------------------------------------------------------------
Acceptance Criteria: BudgetComparison Threshold is set to 200% and only components who consume more than 200% of Ram or Rom are highlighted red.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
[ESC] MapFileAnalyzer - BudgetComparison Config Update / PartitioningAnalysis Update
Description:
After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%
Furthermore, update configuration of PartitioningAnalysis with new ComponentList file.
Owner: Jeremy Anczykowski
Reviewer: Lukas Hoppe
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 23.07.2021
------------------------------------------------------ | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [ESC] MapFileAnalyzer - BudgetComparison Config Update
--------------------------------------------------------------------------------
Details (Exact description): After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/SCS/ToolDevelopment/MapFileAnalyzer/Ti4x/Ti4x%5fGEN%5f3/1%5fBinaries/BUILD%5fVIEW/project.pj&projectrevision=1.13.1.2
--------------------------------------------------------------------------------
Output Work Products: Updated MapFileAnalyzer configuration
--------------------------------------------------------------------------------
Acceptance Criteria: BudgetComparison Threshold is set to 200% and only components who consume more than 200% of Ram or Rom are highlighted red.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
[ESC] MapFileAnalyzer - BudgetComparison Config Update / PartitioningAnalysis Update
Description:
After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%
Furthermore, update configuration of PartitioningAnalysis with new ComponentList file.
Owner: Jeremy Anczykowski
Reviewer: Lukas Hoppe
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 23.07.2021
------------------------------------------------------ |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
Provide the AUTOSAR/Legacy Interface List Export with each Architecture Build
--------------------------------------------------------------------------------
Details (Exact description):
The AUTOSAR and Legacy Interface List export needs to be provided by the architecture team with each scheduled architecture build.
This export is mandatory for creating Specification Baselines and developing the correspondent test specifications for testing the modeled interfaces
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): -
--------------------------------------------------------------------------------
Output Work Products:
AUTOSAR Interface List Export
Legacy Interface List Export
--------------------------------------------------------------------------------
Acceptance Criteria: Mentioned documents are available with each architecture build and stored in Integrity
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------This CR directs in the SwAD process definition,
(clarified with T.Kremer, refer to attached email )
which means that the current Build outcome must be defined in process.
Therefore, the process CR 4817174 is created
Hint:For project specific acceptance criteria,
the Build 3919359 contains the checkpoint of the whole architecture,
including the export files.
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verification):
-------------------------
@CCB: Please reject this CR | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
Provide the AUTOSAR/Legacy Interface List Export with each Architecture Build
--------------------------------------------------------------------------------
Details (Exact description):
The AUTOSAR and Legacy Interface List export needs to be provided by the architecture team with each scheduled architecture build.
This export is mandatory for creating Specification Baselines and developing the correspondent test specifications for testing the modeled interfaces
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): -
--------------------------------------------------------------------------------
Output Work Products:
AUTOSAR Interface List Export
Legacy Interface List Export
--------------------------------------------------------------------------------
Acceptance Criteria: Mentioned documents are available with each architecture build and stored in Integrity
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------This CR directs in the SwAD process definition,
(clarified with T.Kremer, refer to attached email )
which means that the current Build outcome must be defined in process.
Therefore, the process CR 4817174 is created
Hint:For project specific acceptance criteria,
the Build 3919359 contains the checkpoint of the whole architecture,
including the export files.
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verification):
-------------------------
@CCB: Please reject this CR |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
The Test Case Specification need to be checked automatically before being imported in DOORs TSM
--------------------------------------------------------------------------------
Details (Exact description):
Currently there is no check performed by the BrkSw Build Test Team on the Test Case Specifications. In order to avoid importing incomplete Test Case Specifications in DOORs, a Quality Gate shall be implemented.
Quality Gate should consider at least:
- all the defined and agreed attributes are filled
- consistency check (test case description, data type ranges, preconditions etc)
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Targeted Workflow SWI Build Test
--------------------------------------------------------------------------------
Output Work Products: Quality Gateway on the Rhapsody Exports for SWE.5
--------------------------------------------------------------------------------
Acceptance Criteria:
Guideline:
- Quality Gateway provides a reports of the performed checks
- Quality Gateway informs TE that some rework is required
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Implementation of the quality gateway should consider a script which checks the test specifications created by the SWI Build Test team.
This can be achieved in two steps:
1. The requirements for the script shall be defined
High level requirements:
- all the required attributes are filled
- the data filled is consistent with the Rhapsody exports
2. Implementation of the script.
The required programming language is Python.
--------------------------------------------------------------------------------
Risk (low/medium/high): -
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): -
Proposal of next steps (incl. effort/h and verification): -
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: Define Quality Gateway for Test Case Specification - Requirements definition
Description: Define requirements for Quality Gateway
Owner: Andrei Mereu/Jeremy Anczykowski
Reviewer: Paul Voica
Estimated design effort/h: 4
Estimated implementation effort/h: 4
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 26/02/2021
--------------------------------------------------------------------------------
TASK 2
------------------------------------------------------
Title: Define Quality Gateway for Test Case Specification Script Implementation
Description: Implement the Quality Gateway script based on the requirements
Owner: Paul Voica
Reviewer: Andrei Mereu/Jeremy Anczykowski
Estimated design effort/h: 8
Estimated implementation effort/h: 8
Estimated unit testing effort/h: 8
------------------------------------------------------
Total effort/h: 24
[Optional] Planned completion date: 05/03/2021 | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
The Test Case Specification need to be checked automatically before being imported in DOORs TSM
--------------------------------------------------------------------------------
Details (Exact description):
Currently there is no check performed by the BrkSw Build Test Team on the Test Case Specifications. In order to avoid importing incomplete Test Case Specifications in DOORs, a Quality Gate shall be implemented.
Quality Gate should consider at least:
- all the defined and agreed attributes are filled
- consistency check (test case description, data type ranges, preconditions etc)
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Targeted Workflow SWI Build Test
--------------------------------------------------------------------------------
Output Work Products: Quality Gateway on the Rhapsody Exports for SWE.5
--------------------------------------------------------------------------------
Acceptance Criteria:
Guideline:
- Quality Gateway provides a reports of the performed checks
- Quality Gateway informs TE that some rework is required
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Implementation of the quality gateway should consider a script which checks the test specifications created by the SWI Build Test team.
This can be achieved in two steps:
1. The requirements for the script shall be defined
High level requirements:
- all the required attributes are filled
- the data filled is consistent with the Rhapsody exports
2. Implementation of the script.
The required programming language is Python.
--------------------------------------------------------------------------------
Risk (low/medium/high): -
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): -
Proposal of next steps (incl. effort/h and verification): -
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: Define Quality Gateway for Test Case Specification - Requirements definition
Description: Define requirements for Quality Gateway
Owner: Andrei Mereu/Jeremy Anczykowski
Reviewer: Paul Voica
Estimated design effort/h: 4
Estimated implementation effort/h: 4
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 26/02/2021
--------------------------------------------------------------------------------
TASK 2
------------------------------------------------------
Title: Define Quality Gateway for Test Case Specification Script Implementation
Description: Implement the Quality Gateway script based on the requirements
Owner: Paul Voica
Reviewer: Andrei Mereu/Jeremy Anczykowski
Estimated design effort/h: 8
Estimated implementation effort/h: 8
Estimated unit testing effort/h: 8
------------------------------------------------------
Total effort/h: 24
[Optional] Planned completion date: 05/03/2021 |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
Define requirements for importing Test Case Specification into DOORs by DXL script
--------------------------------------------------------------------------------
Details (Exact description):
Currently the creation/updates of the DOORs Test Specification Modules are done manually via a script which needs to be tailored/adapted.
The exact requirements of the DXL script needs to be defined (input structure, script behavior and expectations)
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): -
--------------------------------------------------------------------------------
Output Work Products: Requirements for DXL scripts which updates DOORs Test Specification Modules
--------------------------------------------------------------------------------
Acceptance Criteria: Requirements for DXL scripts which updates DOORs Test Specification Modules are defined and accepted by the tooling team
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The requirements for the DXL script shall be developed and shall be provided in excel format. The requirements shall be created in close collaboration between Interface Test activities and Scheduling/Timing activities.
The key requirements shall consider:
- the input document extension (to be agreed with the development team - json/text format proposed)
- the input document layout
- key attributes
- link creation between modules
- automatization perspective (possibility to execute the script via an API)
- logs provided after script execution in a readable format
--------------------------------------------------------------------------------
Risk (low/medium/high): -
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Andrei Mereu
Proposal of next steps (incl. effort/h and verification): Create Tasks
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: [SWE.5][Automatization] Define Requirements for DXL script - Test Case Specification import to DOORs - Interface
Description: Create the requirements for DXL script for Interface Test activities
Owner: Andrei Mereu
Reviewer: Jeremy Anczykowski
Estimated design effort/h: 3
Estimated implementation effort/h: 3
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 6
[Optional] Planned completion date: 19/02/2021
--------------------------------------------------------------------------------
TASK 2
------------------------------------------------------
Title: [SWE.5][Automatization] Define Requirements for DXL script - Test Case Specification import to DOORs - Scheduling/Timing
Description: Create the requirements for DXL script for scheduling and timing test activities
Owner: Jeremy Anczykowski
Reviewer: Andrei Mereu
Estimated design effort/h: 3
Estimated implementation effort/h: 3
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 6
[Optional] Planned completion date: 19/02/2021 | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
Define requirements for importing Test Case Specification into DOORs by DXL script
--------------------------------------------------------------------------------
Details (Exact description):
Currently the creation/updates of the DOORs Test Specification Modules are done manually via a script which needs to be tailored/adapted.
The exact requirements of the DXL script needs to be defined (input structure, script behavior and expectations)
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): -
--------------------------------------------------------------------------------
Output Work Products: Requirements for DXL scripts which updates DOORs Test Specification Modules
--------------------------------------------------------------------------------
Acceptance Criteria: Requirements for DXL scripts which updates DOORs Test Specification Modules are defined and accepted by the tooling team
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The requirements for the DXL script shall be developed and shall be provided in excel format. The requirements shall be created in close collaboration between Interface Test activities and Scheduling/Timing activities.
The key requirements shall consider:
- the input document extension (to be agreed with the development team - json/text format proposed)
- the input document layout
- key attributes
- link creation between modules
- automatization perspective (possibility to execute the script via an API)
- logs provided after script execution in a readable format
--------------------------------------------------------------------------------
Risk (low/medium/high): -
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Andrei Mereu
Proposal of next steps (incl. effort/h and verification): Create Tasks
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: [SWE.5][Automatization] Define Requirements for DXL script - Test Case Specification import to DOORs - Interface
Description: Create the requirements for DXL script for Interface Test activities
Owner: Andrei Mereu
Reviewer: Jeremy Anczykowski
Estimated design effort/h: 3
Estimated implementation effort/h: 3
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 6
[Optional] Planned completion date: 19/02/2021
--------------------------------------------------------------------------------
TASK 2
------------------------------------------------------
Title: [SWE.5][Automatization] Define Requirements for DXL script - Test Case Specification import to DOORs - Scheduling/Timing
Description: Create the requirements for DXL script for scheduling and timing test activities
Owner: Jeremy Anczykowski
Reviewer: Andrei Mereu
Estimated design effort/h: 3
Estimated implementation effort/h: 3
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 6
[Optional] Planned completion date: 19/02/2021 |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
The exporter script shall
1. Filter the specifications which are not complete
2. Distinguish between implict/explicit read/write APIs (Rte_IRead/IWrite and Rte_Read/Write)
--------------------------------------------------------------------------------
Details (Exact description):
Currently the script cannot distinguish
1. if an architecture specification is expected to be complete or not, therefore all the specifications are exported. The script shall be capable to identify if a a platform is fully modeled (i.e. ZfControlSw) and if a specification is not complete, to filter it out.
2. between implicit and explicit read/write
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): See attachment.
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR_1-3-2-69_1-10.xlsx
RE Build VW_MQB48-W_ESC_SW_AD_403.msg
--------------------------------------------------------------------------------
Output Work Products: Updated LinkedAutosarSR Rhapsody export
--------------------------------------------------------------------------------
Acceptance Criteria: The incomplete architecture specifications are not part of LinkedAutosarSR and the implicit/explicit read/write is distinguished.
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-11-08, 08:22:52]
--------------------------------------------------------------------------------
Brief investigation comment:
1. Filter specifications which are not complete => Already implemented with CR 4892226
2. IRead/IWrite: this topic is covered by CR 5719739
=> This CR can be rejected
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
The exporter script shall
1. Filter the specifications which are not complete
2. Distinguish between implict/explicit read/write APIs (Rte_IRead/IWrite and Rte_Read/Write)
--------------------------------------------------------------------------------
Details (Exact description):
Currently the script cannot distinguish
1. if an architecture specification is expected to be complete or not, therefore all the specifications are exported. The script shall be capable to identify if a a platform is fully modeled (i.e. ZfControlSw) and if a specification is not complete, to filter it out.
2. between implicit and explicit read/write
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): See attachment.
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR_1-3-2-69_1-10.xlsx
RE Build VW_MQB48-W_ESC_SW_AD_403.msg
--------------------------------------------------------------------------------
Output Work Products: Updated LinkedAutosarSR Rhapsody export
--------------------------------------------------------------------------------
Acceptance Criteria: The incomplete architecture specifications are not part of LinkedAutosarSR and the implicit/explicit read/write is distinguished.
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-11-08, 08:22:52]
--------------------------------------------------------------------------------
Brief investigation comment:
1. Filter specifications which are not complete => Already implemented with CR 4892226
2. IRead/IWrite: this topic is covered by CR 5719739
=> This CR can be rejected
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
Connect the missing links from Rhapsody model in order to reflect the expected current status of ZfControlSw platform
--------------------------------------------------------------------------------
Details (Exact description):
ZfControlSw platform is expected to contain the links from Platform level to Domain and to SWC level. Currently some of the links are missing
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): See attachments.
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR_1-3-2-69_1-10.xlsx
RE Build VW_MQB48-W_ESC_SW_AD_403.msg
--------------------------------------------------------------------------------
Output Work Products: Updated Rhapsody Model
--------------------------------------------------------------------------------
Acceptance Criteria: The Rhapsody model contains complete links for ZfControlSw
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2022-06-01, 11:33:32]
--------------------------------------------------------------------------------
Brief investigation comment:
The issue found is on ZfControlSw ports which have no connection link to a control software domain:
By looking at which component ports are connected to the interfaces, it can be seen that the interface connection should only be within ZfBsw, but not go to ZfControlSw
Rte_Read_R_MoDrehzahlEm_MoDrehzahlEm ==> From Comms to RkapRle
Rte_Read_R_MoDrehzahlEm_MoDrehzahlEmsek ==> From Comms to RkapRle
Rte_Read_R_OBDAussenTempGef_OBDAussenTempGef ==> From Comms to RkapRle
Rte_Read_R_RadMomente_RadMomente ==> From Comms to RkapRle
Rte_Read_R_EmlReifenumfang_EmlQbitReifenumfang ==> From Comms to ChassInf
Rte_Read_R_EmlReifenumfang_EmlReifenumfang ==> From Comms to ChassInf
Therefore, it is proposed to remove the ZfBsw and ZfControlSw ports for above interfaces, including their linkage
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: Cleanup ZfBsw to ZfControlSw interface links for interfaces which are only connected in ZfBsw
Description:
Remove ports for SR_MoDrehzahlEm, SR_OBDAussenTempGef, SR_RadMomente, SR_EmlReifenumfang from ZfBsw and ZControlSw platforms, including links in between.
Assigned to: VW Project architect
Verifier: Rene Lotz
Estimated effort: 4h
------------------------------- | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale):
Connect the missing links from Rhapsody model in order to reflect the expected current status of ZfControlSw platform
--------------------------------------------------------------------------------
Details (Exact description):
ZfControlSw platform is expected to contain the links from Platform level to Domain and to SWC level. Currently some of the links are missing
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): See attachments.
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR_1-3-2-69_1-10.xlsx
RE Build VW_MQB48-W_ESC_SW_AD_403.msg
--------------------------------------------------------------------------------
Output Work Products: Updated Rhapsody Model
--------------------------------------------------------------------------------
Acceptance Criteria: The Rhapsody model contains complete links for ZfControlSw
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2022-06-01, 11:33:32]
--------------------------------------------------------------------------------
Brief investigation comment:
The issue found is on ZfControlSw ports which have no connection link to a control software domain:
By looking at which component ports are connected to the interfaces, it can be seen that the interface connection should only be within ZfBsw, but not go to ZfControlSw
Rte_Read_R_MoDrehzahlEm_MoDrehzahlEm ==> From Comms to RkapRle
Rte_Read_R_MoDrehzahlEm_MoDrehzahlEmsek ==> From Comms to RkapRle
Rte_Read_R_OBDAussenTempGef_OBDAussenTempGef ==> From Comms to RkapRle
Rte_Read_R_RadMomente_RadMomente ==> From Comms to RkapRle
Rte_Read_R_EmlReifenumfang_EmlQbitReifenumfang ==> From Comms to ChassInf
Rte_Read_R_EmlReifenumfang_EmlReifenumfang ==> From Comms to ChassInf
Therefore, it is proposed to remove the ZfBsw and ZfControlSw ports for above interfaces, including their linkage
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: Cleanup ZfBsw to ZfControlSw interface links for interfaces which are only connected in ZfBsw
Description:
Remove ports for SR_MoDrehzahlEm, SR_OBDAussenTempGef, SR_RadMomente, SR_EmlReifenumfang from ZfBsw and ZControlSw platforms, including links in between.
Assigned to: VW Project architect
Verifier: Rene Lotz
Estimated effort: 4h
------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs Main Micro Application:
VW10_P03_M10_S02_VTx_401-007-000_X329_O CP: 1.633.1.215.1.7
BswAutocore CP: 1.490
ECU: Static Analysis
Vehicle / Fahrzueg: -
----------------------------------------------
Preconditions / Ausgangsituation:
- Architecture Interface Specifications available (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d7c0 - Baseline 9.3)
- Understand C license available
-----------------------------------------------
Activity / durchgefuhre Aktion:
During Interface Tests execution for CAT 3 - x401 on Standard C Interfaces Static Analysis.
Generate Understand C Database using Intra ECU Comm Analysis Tool
Extract Standard C Interfaces from the Databases using Standard C Extractor
Generate Static Analysis using Standard C Compare based on Understand Export (.xls) and Architecture Specifications
Export from Doors Module (.xls).
----------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
All the Specifications should reffer to Functions which are Standard C.
All the Standard C Interfaces implemented in the Software should not deviate from Architecture Specifications.
----------------------------------------------
Actual Behavior / Istverhalten:
- Not all the Architecture Specifications reffer to Functions which are Standard C.
- Not all the Interfaces are implemented in the SW as it is Specified in the Architecture.
----------------------------------------------
Requirement ID not fullfilled / Lastenhelf ID nicht erfullt:
Trace / Messung:
Please see in the attachments the report StandardC_StaticAnalysis_VW_MQB_ESC_401.xls.
For more details see the PortTest CR: 5357479
Impact / Einfluss:
---------------------------------------------- [Benjamin Bauer (bauerb), 2022-05-30, 10:18:45]
--------------------------------------------------------------------------------
Brief investigation comment:
This CR can be rejected as already newer test results from X500 are available with OP 6339326.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs Main Micro Application:
VW10_P03_M10_S02_VTx_401-007-000_X329_O CP: 1.633.1.215.1.7
BswAutocore CP: 1.490
ECU: Static Analysis
Vehicle / Fahrzueg: -
----------------------------------------------
Preconditions / Ausgangsituation:
- Architecture Interface Specifications available (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d7c0 - Baseline 9.3)
- Understand C license available
-----------------------------------------------
Activity / durchgefuhre Aktion:
During Interface Tests execution for CAT 3 - x401 on Standard C Interfaces Static Analysis.
Generate Understand C Database using Intra ECU Comm Analysis Tool
Extract Standard C Interfaces from the Databases using Standard C Extractor
Generate Static Analysis using Standard C Compare based on Understand Export (.xls) and Architecture Specifications
Export from Doors Module (.xls).
----------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
All the Specifications should reffer to Functions which are Standard C.
All the Standard C Interfaces implemented in the Software should not deviate from Architecture Specifications.
----------------------------------------------
Actual Behavior / Istverhalten:
- Not all the Architecture Specifications reffer to Functions which are Standard C.
- Not all the Interfaces are implemented in the SW as it is Specified in the Architecture.
----------------------------------------------
Requirement ID not fullfilled / Lastenhelf ID nicht erfullt:
Trace / Messung:
Please see in the attachments the report StandardC_StaticAnalysis_VW_MQB_ESC_401.xls.
For more details see the PortTest CR: 5357479
Impact / Einfluss:
---------------------------------------------- [Benjamin Bauer (bauerb), 2022-05-30, 10:18:45]
--------------------------------------------------------------------------------
Brief investigation comment:
This CR can be rejected as already newer test results from X500 are available with OP 6339326.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs Main Micro Application: VW10_P03_M10_S02_VTx_401-007-000_X329_O - CP: 1.633.1.215.1.7
ECU: N.A.
Vehicle / Fahrzueg: N.A.
----------------------------------------------
Preconditions / Ausgangsituation:
- AUTOSAR Model available (BswAutocore - CP: 1.490)
- Architecture Interface Specifications available (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d7c0 - Baseline 9.3)
- Interface Test Specifications available (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d7c0 - Baseline 7.3)
----------------------------------------------
Activity / durchgefuhre Aktion: Static Analysis
Steps to reproduce the issue (before, during, after):
- Extract interfaces from AUTOSAR Model (connections between components)
- Compare the AUTOSAR Model with the Architecture Interface Specifications/Interface Test Specification Module
----------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
- Runable name shall be UpdateChassInf
- No duplicate specification shall be present in the Architecture Specifications
Actual Behavior / Istverhalten:
- Runnable name is UpdateChassinf (details can be identified in the attached document: SwAD_Model-SoftwareInterfaceTable_1-3-2-7_Analyzed_2021_04_30.xlsx, column A: Status, filter "Naming" or "Duplicate, Naming")
- There are multiple Architecture Specification duplicated (details can be identified in the attached document: SwAD_Model-SoftwareInterfaceTable_1-3-2-7_Analyzed_2021_04_30.xlsx, column A: Status, filter "Duplicate" or "Duplicate, Naming")
----------------------------------------------
Requirement ID not fullfilled / Lastenhelf ID nicht erfullt:
Trace / Messung:
Impact / Einfluss:
---------------------------------------------- [Benjamin Bauer (bauerb), 2022-05-30, 10:30:27]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
There are two findings from SWE.5
1. Naming of runnable UpdateChassInf (software) deviates from UpdateChassinf (Sw Architecture) ==> This issue still exists, so it should be fixed
Software:
Sw Architecture:
2. Duplicate unique IDs in export => This issue has been resolved by exporter and does no longer occur
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: VW MQB ESC Sw Architecture - Align runnable name UpdateChassInf
Description: Naming of runnable UpdateChassInf (software) deviates from UpdateChassinf (Sw Architecture)
Assigned to: ChassInf domain architect
Verifier: VW project architect
Estimated effort: 4h
------------------------------- | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs Main Micro Application: VW10_P03_M10_S02_VTx_401-007-000_X329_O - CP: 1.633.1.215.1.7
ECU: N.A.
Vehicle / Fahrzueg: N.A.
----------------------------------------------
Preconditions / Ausgangsituation:
- AUTOSAR Model available (BswAutocore - CP: 1.490)
- Architecture Interface Specifications available (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d7c0 - Baseline 9.3)
- Interface Test Specifications available (http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d7c0 - Baseline 7.3)
----------------------------------------------
Activity / durchgefuhre Aktion: Static Analysis
Steps to reproduce the issue (before, during, after):
- Extract interfaces from AUTOSAR Model (connections between components)
- Compare the AUTOSAR Model with the Architecture Interface Specifications/Interface Test Specification Module
----------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
- Runable name shall be UpdateChassInf
- No duplicate specification shall be present in the Architecture Specifications
Actual Behavior / Istverhalten:
- Runnable name is UpdateChassinf (details can be identified in the attached document: SwAD_Model-SoftwareInterfaceTable_1-3-2-7_Analyzed_2021_04_30.xlsx, column A: Status, filter "Naming" or "Duplicate, Naming")
- There are multiple Architecture Specification duplicated (details can be identified in the attached document: SwAD_Model-SoftwareInterfaceTable_1-3-2-7_Analyzed_2021_04_30.xlsx, column A: Status, filter "Duplicate" or "Duplicate, Naming")
----------------------------------------------
Requirement ID not fullfilled / Lastenhelf ID nicht erfullt:
Trace / Messung:
Impact / Einfluss:
---------------------------------------------- [Benjamin Bauer (bauerb), 2022-05-30, 10:30:27]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
There are two findings from SWE.5
1. Naming of runnable UpdateChassInf (software) deviates from UpdateChassinf (Sw Architecture) ==> This issue still exists, so it should be fixed
Software:
Sw Architecture:
2. Duplicate unique IDs in export => This issue has been resolved by exporter and does no longer occur
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: VW MQB ESC Sw Architecture - Align runnable name UpdateChassInf
Description: Naming of runnable UpdateChassInf (software) deviates from UpdateChassinf (Sw Architecture)
Assigned to: ChassInf domain architect
Verifier: VW project architect
Estimated effort: 4h
------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs As part of the software integration tests please analyze the possibility to increase the test coverage of AUTOSAR Port Test activity for Swc-ModeManager and Swc-FaultManager.
Provide a review report and/or derive action.
Please use the CP: 1.633.1.215.1.7
PTC Checkpoint Label: VW10_P03_M10_S02_VTx_401-007-000_X329_O
More information can be found in the ALM_Action: 5290479. [08/10/2021, Madalin Pauna]:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Due to the transition of the Bootloader on TestBenches from x325 to x326 with new HSM, the Extending of the Coverage will be made using SW X404: 1.633.1.384
The Specifications from SwAD and the not tested SWCs were analized and was conclusioned that following components should be tested(if possible):
1. Services:
- Swc - CommsMeasurementInterface_QM_Cdd, Swc - Dcmwrapper, Swc - EngStatus, Swc - FmQm_Cdd, Swc - ModeManager_cdd, Swc - NvramArWrp_Cdd.
2. EcuAL:
- Swc - AnalogSignals, Swc - PmBridge, Swc - SystemAsicMain.
3. Application:
- Swc - SensSup, Swc - PbcWrp, Swc - SysTest.
According to SwAD Swc - FmQm_Cdd, Swc - ModeManager_cdd, Swc - SystemAsicMain are manadatory !
--------------------------------------------------------------------------------
Risk (low/medium/high): -
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): -
Proposal of next steps (incl. effort/h and verification): -
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE.5][MQB48-W][ESC][PT] - Extend coverage of AUTOSAR Port Testing
Description: Prepare tests, Execute tests, Archive test reports
Owner: Madalin Pauna
Reviewer: Daniel Nicoras
Estimated design effort/h: 20
Estimated implementation effort/h: 20
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: TBD
Planned completion date: 15.10.2021 | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs As part of the software integration tests please analyze the possibility to increase the test coverage of AUTOSAR Port Test activity for Swc-ModeManager and Swc-FaultManager.
Provide a review report and/or derive action.
Please use the CP: 1.633.1.215.1.7
PTC Checkpoint Label: VW10_P03_M10_S02_VTx_401-007-000_X329_O
More information can be found in the ALM_Action: 5290479. [08/10/2021, Madalin Pauna]:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Due to the transition of the Bootloader on TestBenches from x325 to x326 with new HSM, the Extending of the Coverage will be made using SW X404: 1.633.1.384
The Specifications from SwAD and the not tested SWCs were analized and was conclusioned that following components should be tested(if possible):
1. Services:
- Swc - CommsMeasurementInterface_QM_Cdd, Swc - Dcmwrapper, Swc - EngStatus, Swc - FmQm_Cdd, Swc - ModeManager_cdd, Swc - NvramArWrp_Cdd.
2. EcuAL:
- Swc - AnalogSignals, Swc - PmBridge, Swc - SystemAsicMain.
3. Application:
- Swc - SensSup, Swc - PbcWrp, Swc - SysTest.
According to SwAD Swc - FmQm_Cdd, Swc - ModeManager_cdd, Swc - SystemAsicMain are manadatory !
--------------------------------------------------------------------------------
Risk (low/medium/high): -
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): -
Proposal of next steps (incl. effort/h and verification): -
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE.5][MQB48-W][ESC][PT] - Extend coverage of AUTOSAR Port Testing
Description: Prepare tests, Execute tests, Archive test reports
Owner: Madalin Pauna
Reviewer: Daniel Nicoras
Estimated design effort/h: 20
Estimated implementation effort/h: 20
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: TBD
Planned completion date: 15.10.2021 |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Update the Interface List Export Script in order to support the requirements mentioned below
--------------------------------------------------------------------------------
Details (Exact description):
General updates for both files:
- the files shall be provided in the following format: *.xlsx
- 01 Requirement shall be replaced with Requirement
- introduce column: 953_SwAD Version which shall contain architecture baseline used for export
AUTOSAR Interface List export:
Content Updates:
- Remove component name from the concatenation of the RTE API (i.e Rte_Abs_S_AbsAtEndOfStop_AbsAtEndOfStop shall be Rte_S_AbsAtEndOfStop_AbsAtEndOfStop)
- Data Element shall contain only the last part (i.e Rte_Comms_S_CruiseControl_CrueControlActive shall be CrueControlActive)
Attributes renaming:
- detailed renaming can be found in the sheet SWC - AR-Attribute list from attachment InterfaceListExport_Attributes.xlsx
Legacy Interface List export:
Content Updates:
- include architecture basline
- introduce column: 912_Unique ID which shall contain concatenation between 931_Unique ID Operation and 932_Unique ID ReceiverPort
Attributes renaming:
- detailed renaming can be found in the sheet SWC - LE-Attribute list from attachment InterfaceListExport_Attributes.xlsx
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
Rhapsody_Exports_for_SWE-5_Attributes.xlsx
SwAD_VW_MQB48W_ESC-SoftwareInterfaceTable.csv
(url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/BRK/Customer/VW/MQB48%2dW/ESC/05%5fSoftware/01%5fArchitecture%5fDesign/project.pj&selection=%22SwAD%5fVW%5fMQB48W%5fESC%2dSoftwareInterfaceTable.csv%22)
SwAD_VW_MQB48W_ESC-SoftwareInterfaceTable_CFunctions.csv (url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/BRK/Customer/VW/MQB48%2dW/ESC/05%5fSoftware/01%5fArchitecture%5fDesign/project.pj&selection=%22SwAD%5fVW%5fMQB48W%5fESC%2dSoftwareInterfaceTable%5fCFunctions.csv%22)
--------------------------------------------------------------------------------
Output Work Products: Updated AUTOSAR/Legacy Interface List Export
--------------------------------------------------------------------------------
Acceptance Criteria: The mentioned requirements shall be implemented in the Interface List Export and the Exports shall be accordingly created
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-03-17, 09:13:36]
Analysis:
General updates for both files:
- the files shall be provided in the following format: *.xlsx ==> Rejected, the file format will be changed to a text format used for automated import with CR
- 01 Requirement shall be replaced with Requirement ==> OK
- introduce column: 953_SwAD Version which shall contain architecture baseline used for export ==> Create column.
AUTOSAR Interface List export:
Content Updates:
- Remove component name from the concatenation of the RTE API (i.e Rte_Abs_S_AbsAtEndOfStop_AbsAtEndOfStop shall be Rte_S_AbsAtEndOfStop_AbsAtEndOfStop) => OK
- Data Element shall contain only the last part (i.e Rte_Comms_S_CruiseControl_CrueControlActive shall be CrueControlActive) => OK
Attributes renaming:
- detailed renaming can be found in the sheet SWC - AR-Attribute list from attachment InterfaceListExport_Attributes.xlsx
- Bug fixes/changes:
- task mapping does not work correctly.
- add behavior pin to behavior information
- map behaviors from component level and not only domain level
- Found ports with multiple runnable connected where different data elements are update by differnet runnable, but each only by one: Check runnable data access in export (example Abs)
- Found ports with multiple runnable connected, where runnable are not cyclic runnable: Split of export per runnable. Example DiagHsbRequest. Attention. Change of GUID required (including sender side)
Legacy Interface List export:
Content Updates:
- include architecture basline ==> Not easy to implement(because the model does not know about it and - most importantly, it does not exist when the interface export is created, at least as long as it needs to be checked in). Proposed to split to other task
- introduce column: 912_Unique ID which shall contain concatenation between 931_Unique ID Operation and 932_Unique ID ReceiverPort => OK
Attributes renaming:
- detailed renaming can be found in the sheet SWC - LE-Attribute list from attachment InterfaceListExport_Attributes.xlsx
--------------------------------------------------------------------------------
Next steps:
This work package can be covered with existing task 4296870.
It is proposed to set up all plugins based on a common class hierarchy, so generic changes can be done once and all plugins are covered in the same way.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Link available task 4296870 | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Update the Interface List Export Script in order to support the requirements mentioned below
--------------------------------------------------------------------------------
Details (Exact description):
General updates for both files:
- the files shall be provided in the following format: *.xlsx
- 01 Requirement shall be replaced with Requirement
- introduce column: 953_SwAD Version which shall contain architecture baseline used for export
AUTOSAR Interface List export:
Content Updates:
- Remove component name from the concatenation of the RTE API (i.e Rte_Abs_S_AbsAtEndOfStop_AbsAtEndOfStop shall be Rte_S_AbsAtEndOfStop_AbsAtEndOfStop)
- Data Element shall contain only the last part (i.e Rte_Comms_S_CruiseControl_CrueControlActive shall be CrueControlActive)
Attributes renaming:
- detailed renaming can be found in the sheet SWC - AR-Attribute list from attachment InterfaceListExport_Attributes.xlsx
Legacy Interface List export:
Content Updates:
- include architecture basline
- introduce column: 912_Unique ID which shall contain concatenation between 931_Unique ID Operation and 932_Unique ID ReceiverPort
Attributes renaming:
- detailed renaming can be found in the sheet SWC - LE-Attribute list from attachment InterfaceListExport_Attributes.xlsx
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
Rhapsody_Exports_for_SWE-5_Attributes.xlsx
SwAD_VW_MQB48W_ESC-SoftwareInterfaceTable.csv
(url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/BRK/Customer/VW/MQB48%2dW/ESC/05%5fSoftware/01%5fArchitecture%5fDesign/project.pj&selection=%22SwAD%5fVW%5fMQB48W%5fESC%2dSoftwareInterfaceTable.csv%22)
SwAD_VW_MQB48W_ESC-SoftwareInterfaceTable_CFunctions.csv (url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/BRK/Customer/VW/MQB48%2dW/ESC/05%5fSoftware/01%5fArchitecture%5fDesign/project.pj&selection=%22SwAD%5fVW%5fMQB48W%5fESC%2dSoftwareInterfaceTable%5fCFunctions.csv%22)
--------------------------------------------------------------------------------
Output Work Products: Updated AUTOSAR/Legacy Interface List Export
--------------------------------------------------------------------------------
Acceptance Criteria: The mentioned requirements shall be implemented in the Interface List Export and the Exports shall be accordingly created
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-03-17, 09:13:36]
Analysis:
General updates for both files:
- the files shall be provided in the following format: *.xlsx ==> Rejected, the file format will be changed to a text format used for automated import with CR
- 01 Requirement shall be replaced with Requirement ==> OK
- introduce column: 953_SwAD Version which shall contain architecture baseline used for export ==> Create column.
AUTOSAR Interface List export:
Content Updates:
- Remove component name from the concatenation of the RTE API (i.e Rte_Abs_S_AbsAtEndOfStop_AbsAtEndOfStop shall be Rte_S_AbsAtEndOfStop_AbsAtEndOfStop) => OK
- Data Element shall contain only the last part (i.e Rte_Comms_S_CruiseControl_CrueControlActive shall be CrueControlActive) => OK
Attributes renaming:
- detailed renaming can be found in the sheet SWC - AR-Attribute list from attachment InterfaceListExport_Attributes.xlsx
- Bug fixes/changes:
- task mapping does not work correctly.
- add behavior pin to behavior information
- map behaviors from component level and not only domain level
- Found ports with multiple runnable connected where different data elements are update by differnet runnable, but each only by one: Check runnable data access in export (example Abs)
- Found ports with multiple runnable connected, where runnable are not cyclic runnable: Split of export per runnable. Example DiagHsbRequest. Attention. Change of GUID required (including sender side)
Legacy Interface List export:
Content Updates:
- include architecture basline ==> Not easy to implement(because the model does not know about it and - most importantly, it does not exist when the interface export is created, at least as long as it needs to be checked in). Proposed to split to other task
- introduce column: 912_Unique ID which shall contain concatenation between 931_Unique ID Operation and 932_Unique ID ReceiverPort => OK
Attributes renaming:
- detailed renaming can be found in the sheet SWC - LE-Attribute list from attachment InterfaceListExport_Attributes.xlsx
--------------------------------------------------------------------------------
Next steps:
This work package can be covered with existing task 4296870.
It is proposed to set up all plugins based on a common class hierarchy, so generic changes can be done once and all plugins are covered in the same way.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Link available task 4296870 |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.2 - SoftwareIntegrationTest - Scheduling&Timing / Interface Tests - Request SwAD Spec ASIL
--------------------------------------------------------------------------------
Details (Exact description):
Info: The BEPS9.0 release request in the MAN3 document "Project Managemant Plan" several metrics and specifies the needs for a calculation related to the ASIL.
Request: Add column "961_ASIL Relation" to each SwAD export specified below in the "Input Work Products" and specify the related ASIL. This should apply e.g. for each specified task, runnable and interface.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
SwAD_Model-SchedulingTable.csv
SwAD_Model-SoftwareInterfaceTable.csv
SwAD_Model-SoftwareInterfaceTable_CFunctions.csv
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
--------------------------------------------------------------------------------
Output Work Products:
Updated exports below:
SwAD_Model-SchedulingTable.csv
SwAD_Model-SoftwareInterfaceTable.csv
SwAD_Model-SoftwareInterfaceTable_CFunctions.csv
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
--------------------------------------------------------------------------------
Acceptance Criteria: Each export contains the column "961_ASIL Relation" to specify for each element e.g. like task, runnable or interface a relation to an ASIL.
-------------------------------------------------------------------------------- 2021-11-29 CSe:
Relevant ASIL is already defined in Scheduling export. Attribute 954_Task_Name contains the ASIL of the task as postfix (as well as the CPU allocation).
All runnables within this task need to implement at least this ASIL. Therefore a separte attribut 961_ASIL_Relation would be redundant.
Interfaces have no ASIL property in the Architecture, therefore this attribute cannot be added to the interface exports.
Since no change in exports required, this CR shall be rejected. | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): SWE.2 - SoftwareIntegrationTest - Scheduling&Timing / Interface Tests - Request SwAD Spec ASIL
--------------------------------------------------------------------------------
Details (Exact description):
Info: The BEPS9.0 release request in the MAN3 document "Project Managemant Plan" several metrics and specifies the needs for a calculation related to the ASIL.
Request: Add column "961_ASIL Relation" to each SwAD export specified below in the "Input Work Products" and specify the related ASIL. This should apply e.g. for each specified task, runnable and interface.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
SwAD_Model-SchedulingTable.csv
SwAD_Model-SoftwareInterfaceTable.csv
SwAD_Model-SoftwareInterfaceTable_CFunctions.csv
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
--------------------------------------------------------------------------------
Output Work Products:
Updated exports below:
SwAD_Model-SchedulingTable.csv
SwAD_Model-SoftwareInterfaceTable.csv
SwAD_Model-SoftwareInterfaceTable_CFunctions.csv
SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
--------------------------------------------------------------------------------
Acceptance Criteria: Each export contains the column "961_ASIL Relation" to specify for each element e.g. like task, runnable or interface a relation to an ASIL.
-------------------------------------------------------------------------------- 2021-11-29 CSe:
Relevant ASIL is already defined in Scheduling export. Attribute 954_Task_Name contains the ASIL of the task as postfix (as well as the CPU allocation).
All runnables within this task need to implement at least this ASIL. Therefore a separte attribut 961_ASIL_Relation would be redundant.
Interfaces have no ASIL property in the Architecture, therefore this attribute cannot be added to the interface exports.
Since no change in exports required, this CR shall be rejected. |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.2][VW MQB48-W][ESC][0401-008][RunnableSequenceChecker] Task Sequence Specification Problem/Bug
--------------------------------------------------------------------------------
Details (Exact description):
Issue: SwAD specification task sequence contains within one task sequence runnables from different task, see email attachment for more information.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
SwAD_Model_SchedulingTable.csv Rev 1.13.1.1
Scheduling&Timing - RunnableSequenceChecker - 0401-008 - Test results
--------------------------------------------------------------------------------
Output Work Products: Updated SwAD Spec SchedulingTable, Update of Exporter tool?
--------------------------------------------------------------------------------
Acceptance Criteria: Task Sequence contains only related runnable
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-09-09, 20:53:36]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
Following issue was observed:
The Rte_Task_10ms_1_D_C1 contains the actvation of Rte_Tas_EpbEnable_B_D_C1 (5.), afterwards this task is modeled with activation of Hsb_Init.
One task sequence diagram shall not contain activation from a dependent task because that cause side effect in the export for integration test AND does not represent what that task is actually doing
Furthermore, the modeling of Rte_Task_EpbEnable_B_D_C1 is incorrect as it calls Hsb_Cyclic and not Hsb_Init!
Change proposal:
Out of above diagram, remove Rte_Tas_10ms_EpbEnable_B_D_C1 lifeline, VehicleContol.Hsb lifeline and the messages 6 (ScheduleRunnables) and 7 (Hsb_Init)
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: Remove Rte_Task_EpbEnable_B_D_C1 content out of Rte_Task_10ms_1_D_C1 sequence diagram
Description: see investigation
Assigned to: <Sw Architect>
Verifier: Ben Bauer
Estimated effort: 2h
------------------------------- | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.2][VW MQB48-W][ESC][0401-008][RunnableSequenceChecker] Task Sequence Specification Problem/Bug
--------------------------------------------------------------------------------
Details (Exact description):
Issue: SwAD specification task sequence contains within one task sequence runnables from different task, see email attachment for more information.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
SwAD_Model_SchedulingTable.csv Rev 1.13.1.1
Scheduling&Timing - RunnableSequenceChecker - 0401-008 - Test results
--------------------------------------------------------------------------------
Output Work Products: Updated SwAD Spec SchedulingTable, Update of Exporter tool?
--------------------------------------------------------------------------------
Acceptance Criteria: Task Sequence contains only related runnable
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2021-09-09, 20:53:36]
--------------------------------------------------------------------------------
Brief investigation comment:
Overview:
Following issue was observed:
The Rte_Task_10ms_1_D_C1 contains the actvation of Rte_Tas_EpbEnable_B_D_C1 (5.), afterwards this task is modeled with activation of Hsb_Init.
One task sequence diagram shall not contain activation from a dependent task because that cause side effect in the export for integration test AND does not represent what that task is actually doing
Furthermore, the modeling of Rte_Task_EpbEnable_B_D_C1 is incorrect as it calls Hsb_Cyclic and not Hsb_Init!
Change proposal:
Out of above diagram, remove Rte_Tas_10ms_EpbEnable_B_D_C1 lifeline, VehicleContol.Hsb lifeline and the messages 6 (ScheduleRunnables) and 7 (Hsb_Init)
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: Remove Rte_Task_EpbEnable_B_D_C1 content out of Rte_Task_10ms_1_D_C1 sequence diagram
Description: see investigation
Assigned to: <Sw Architect>
Verifier: Ben Bauer
Estimated effort: 2h
------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.5][VW MQB48-W][ESC] Update Budgets as specified by SwAD
--------------------------------------------------------------------------------
Details (Exact description): Update budgets for SoftwareIntegrationTest as specified in update from CR 5478641.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5478641
--------------------------------------------------------------------------------
Output Work Products: Updated Budgets for SoftwareIntegrationTest
--------------------------------------------------------------------------------
Acceptance Criteria: Budgets specified in chapter 6.2.4 "uc resource consumption objectives and constrains" are used for software integration testing.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description: Update budgets for SoftwareIntegrationTest as specified in update from CR 5478641.
Owner: Jeremy Anczykowski
Reviewer: Paul Voica
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 22.10.2021
------------------------------------------------------ | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.5][VW MQB48-W][ESC] Update Budgets as specified by SwAD
--------------------------------------------------------------------------------
Details (Exact description): Update budgets for SoftwareIntegrationTest as specified in update from CR 5478641.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5478641
--------------------------------------------------------------------------------
Output Work Products: Updated Budgets for SoftwareIntegrationTest
--------------------------------------------------------------------------------
Acceptance Criteria: Budgets specified in chapter 6.2.4 "uc resource consumption objectives and constrains" are used for software integration testing.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description: Update budgets for SoftwareIntegrationTest as specified in update from CR 5478641.
Owner: Jeremy Anczykowski
Reviewer: Paul Voica
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 22.10.2021
------------------------------------------------------ |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.5][VW MQB48-W][ESC][MapFileAnalyzer] Maintenance
--------------------------------------------------------------------------------
Details (Exact description): Update MapFileAnalyzer to new version and check configuration
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current MapFileAnalyzer version.
--------------------------------------------------------------------------------
Output Work Products: Updated MapFileAnalyzer version.
--------------------------------------------------------------------------------
Acceptance Criteria: Requested topic from details section implemented.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------Brief analysis summary: Update MapFileAnalyzer version and related config.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description:
Owner: Jeremy Anczykowski
Reviewer: Lukas Hoppe
Update MapFileAnalyzer to newest version and related configuration.
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 17.12.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description:
Requests:
1. Update APP.ini file as specified in the attachment "file_APP_INI_updates.txt".
Owner: Hendrik Stertz
Reviewer: Sascha Kwiotek
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 2
[Optional] Planned completion date: 17.12.2021
------------------------------------------------------ | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.5][VW MQB48-W][ESC][MapFileAnalyzer] Maintenance
--------------------------------------------------------------------------------
Details (Exact description): Update MapFileAnalyzer to new version and check configuration
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current MapFileAnalyzer version.
--------------------------------------------------------------------------------
Output Work Products: Updated MapFileAnalyzer version.
--------------------------------------------------------------------------------
Acceptance Criteria: Requested topic from details section implemented.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------Brief analysis summary: Update MapFileAnalyzer version and related config.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description:
Owner: Jeremy Anczykowski
Reviewer: Lukas Hoppe
Update MapFileAnalyzer to newest version and related configuration.
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 17.12.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description:
Requests:
1. Update APP.ini file as specified in the attachment "file_APP_INI_updates.txt".
Owner: Hendrik Stertz
Reviewer: Sascha Kwiotek
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 2
[Optional] Planned completion date: 17.12.2021
------------------------------------------------------ |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Update the exporter scripts to include in the exports also the interfaces which are modeled between components linked to the same behavior.
--------------------------------------------------------------------------------
Details (Exact description): It was observed that if a behavior contains more than one components, the interfaces which are modeled between these components are not part of the Rhapsody Exports for SWE.5. Below it can be seen an example for DetermineHydraulicPressureRaw behavior.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): - Rhapsody Model - Exporter Scripts
--------------------------------------------------------------------------------
Output Work Products: Updated Rhapsody Exports: - SwAD_Model-SoftwareInterfaceTable.csv - SwAD_Model-SoftwareInterfaceTable_CFunctions.csv - SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
--------------------------------------------------------------------------------
Acceptance Criteria: The Rhapsody Exports mentioned below will contain the interfaces between components linked in the same behavior.
- SwAD_Model-SoftwareInterfaceTable.csv
- SwAD_Model-SoftwareInterfaceTable_CFunctions.csv
- SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2022-02-21, 13:24:32]
--------------------------------------------------------------------------------
Brief investigation comment:
A behavior is a functional blackbox which is corresponds to a set of requirements.
For a behavior, the external interface (behavior inputs and outputs) is described, and it is expected that the input/output parameters are completely linked to technical architecture
The relationship between functional behavior and technical component is m:n. There are components (typically in control software) which implement m behaviors, but there are behaviors which are implemented by several components.
In the situation where more than one behavior is implemented by one component, it can occur that interfaces between the behaviors are component-internal interfaces. Those are typically provided as test port in technical architecture.
In the situation where more than one component realizes one behavior, the communication between the components in technical architecture does not correspond to anything in functional architecture (and shall not, because the behavior is intended as black box).
It could make sense to denote in Sw Architecture, that some technical interface is an internal interface of a behavior to distinguish it from an interface which was forgotten to link to functional architecture.
Possibility 1:
- do not tag/identify technical interfaces as "feature internal" (Advantage: no change required, as this is what we currently do; Disadvantage: the information that some interface is behavior internal is lost)
Possibility 2:
- identify technical interfaces as "feature internal"
This could be done using
- Dependency from port to the corresponding behavior
- Tag with behavior name
- just a tag (or stereotype) BehaviorInternal
Considering the impact of Possibility 2 which requires analysis and adaptation of interfaces + changes in exporters to implement new behavior, it is not considered as feasible for VW MQB. Therefore, it is proposed to reject this CR and create a follow-up for IBC core to introduce a proper handling, also including model checker behavior, etc.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Update the exporter scripts to include in the exports also the interfaces which are modeled between components linked to the same behavior.
--------------------------------------------------------------------------------
Details (Exact description): It was observed that if a behavior contains more than one components, the interfaces which are modeled between these components are not part of the Rhapsody Exports for SWE.5. Below it can be seen an example for DetermineHydraulicPressureRaw behavior.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): - Rhapsody Model - Exporter Scripts
--------------------------------------------------------------------------------
Output Work Products: Updated Rhapsody Exports: - SwAD_Model-SoftwareInterfaceTable.csv - SwAD_Model-SoftwareInterfaceTable_CFunctions.csv - SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
--------------------------------------------------------------------------------
Acceptance Criteria: The Rhapsody Exports mentioned below will contain the interfaces between components linked in the same behavior.
- SwAD_Model-SoftwareInterfaceTable.csv
- SwAD_Model-SoftwareInterfaceTable_CFunctions.csv
- SwAD_Model-SoftwareInterfaceTable_LinkedAutosarSR.csv
-------------------------------------------------------------------------------- [Benjamin Bauer (bauerb), 2022-02-21, 13:24:32]
--------------------------------------------------------------------------------
Brief investigation comment:
A behavior is a functional blackbox which is corresponds to a set of requirements.
For a behavior, the external interface (behavior inputs and outputs) is described, and it is expected that the input/output parameters are completely linked to technical architecture
The relationship between functional behavior and technical component is m:n. There are components (typically in control software) which implement m behaviors, but there are behaviors which are implemented by several components.
In the situation where more than one behavior is implemented by one component, it can occur that interfaces between the behaviors are component-internal interfaces. Those are typically provided as test port in technical architecture.
In the situation where more than one component realizes one behavior, the communication between the components in technical architecture does not correspond to anything in functional architecture (and shall not, because the behavior is intended as black box).
It could make sense to denote in Sw Architecture, that some technical interface is an internal interface of a behavior to distinguish it from an interface which was forgotten to link to functional architecture.
Possibility 1:
- do not tag/identify technical interfaces as "feature internal" (Advantage: no change required, as this is what we currently do; Disadvantage: the information that some interface is behavior internal is lost)
Possibility 2:
- identify technical interfaces as "feature internal"
This could be done using
- Dependency from port to the corresponding behavior
- Tag with behavior name
- just a tag (or stereotype) BehaviorInternal
Considering the impact of Possibility 2 which requires analysis and adaptation of interfaces + changes in exporters to implement new behavior, it is not considered as feasible for VW MQB. Therefore, it is proposed to reject this CR and create a follow-up for IBC core to introduce a proper handling, also including model checker behavior, etc.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
Reject CR |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.2][VW MQB ESC][ESC][SwAD Export] ComponentList Improvement
--------------------------------------------------------------------------------
Details (Exact description):
The ComponentList Export from SwAD should be improved to be able to review availability SwAD spec in terms of partitioning specification, required for review 5621447.
Request1: Add RamMemorySection to the ComponentList Export, as specified in the example below.
Request2: Add RomMemorySection to the ComponentList Export, as specified in the example below.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current SwAD ComponentList Export
--------------------------------------------------------------------------------
Output Work Products: Updated SwAD ComponentList Export
--------------------------------------------------------------------------------
Acceptance Criteria: RamMemorySection and RomMemorySection information available in the SwAD ComponentList Export.
-------------------------------------------------------------------------------- Benjamin Bauer (bauerb), 2022-02-14, 09:07:05
--------------------------------------------------------------------------------
Brief investigation comment:
The current extended component list looks like this:
As mentioned above, this information is not sufficient to execute the review by integration tester according to checklist template 5621447 which asks for review of partitioning.
Therefore, the information on partitioning needs to be included. That could either be done as sub-tag of <RamBudget> and <RomBudget> or on same level.
Since typically, there is no budget on the memory region but on the RAM/ROM only, it is proposed to add a tag <MemoryRegion> inside of <RamBudget>/<RomBudget>
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: [SwAT][ComponentListXml] Add memory region information to export
Description: see investigation
Assigned to: Ben Bauer
Verifier: Jens Auer
Estimated effort: 8h
------------------------------- | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.2][VW MQB ESC][ESC][SwAD Export] ComponentList Improvement
--------------------------------------------------------------------------------
Details (Exact description):
The ComponentList Export from SwAD should be improved to be able to review availability SwAD spec in terms of partitioning specification, required for review 5621447.
Request1: Add RamMemorySection to the ComponentList Export, as specified in the example below.
Request2: Add RomMemorySection to the ComponentList Export, as specified in the example below.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current SwAD ComponentList Export
--------------------------------------------------------------------------------
Output Work Products: Updated SwAD ComponentList Export
--------------------------------------------------------------------------------
Acceptance Criteria: RamMemorySection and RomMemorySection information available in the SwAD ComponentList Export.
-------------------------------------------------------------------------------- Benjamin Bauer (bauerb), 2022-02-14, 09:07:05
--------------------------------------------------------------------------------
Brief investigation comment:
The current extended component list looks like this:
As mentioned above, this information is not sufficient to execute the review by integration tester according to checklist template 5621447 which asks for review of partitioning.
Therefore, the information on partitioning needs to be included. That could either be done as sub-tag of <RamBudget> and <RomBudget> or on same level.
Since typically, there is no budget on the memory region but on the RAM/ROM only, it is proposed to add a tag <MemoryRegion> inside of <RamBudget>/<RomBudget>
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
TASK 1
-------------------------------
Title/Header: [SwAT][ComponentListXml] Add memory region information to export
Description: see investigation
Assigned to: Ben Bauer
Verifier: Jens Auer
Estimated effort: 8h
------------------------------- |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.3][VW MQB][ESC] DesignModel - ComponentList
--------------------------------------------------------------------------------
Details (Exact description):
Issue: RamMemorySections and RomMemorySections are mixed and not correctly specified in the ComponentList, see picture below and attached ComponentList.xml file.
Request: The DesignModel and related plugins shall be updated to create the ComponentList in the correct format.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current DesignModel from SW 0502-006 - #JB 298882 - CP:1.633.1.623.3.11
--------------------------------------------------------------------------------
Output Work Products: Updated Design Model
--------------------------------------------------------------------------------
Acceptance Criteria: ComponentList can be generated in the correct format like from VW MQB or Daimler MMA
-------------------------------------------------------------------------------- 2022-07-28 14:13:17 RBr: this issue is solved in the actual Release ==> cancel | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.3][VW MQB][ESC] DesignModel - ComponentList
--------------------------------------------------------------------------------
Details (Exact description):
Issue: RamMemorySections and RomMemorySections are mixed and not correctly specified in the ComponentList, see picture below and attached ComponentList.xml file.
Request: The DesignModel and related plugins shall be updated to create the ComponentList in the correct format.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): Current DesignModel from SW 0502-006 - #JB 298882 - CP:1.633.1.623.3.11
--------------------------------------------------------------------------------
Output Work Products: Updated Design Model
--------------------------------------------------------------------------------
Acceptance Criteria: ComponentList can be generated in the correct format like from VW MQB or Daimler MMA
-------------------------------------------------------------------------------- 2022-07-28 14:13:17 RBr: this issue is solved in the actual Release ==> cancel |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.5][VW MQB48-W][ESC][SoftwareIntegrationTestPlan] Share updated core document to project
--------------------------------------------------------------------------------
Details (Exact description): Share updated SoftwareIntegrationTestPlan core document to the project and adapt Tailoring document accordingly.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): SoftwareIntegrationTestPlan after update from CR 7079976
--------------------------------------------------------------------------------
Output Work Products: AD_BRK_VW_MQB48-W_ESC_SW_Integration_Test_Plan_Tailoring.xlsm, AD_BRK_SW_Integration_Test_Plan.docx
--------------------------------------------------------------------------------
Acceptance Criteria: Updated revision of documents from "Output Work Products".
------------------------------------------------------------------------------ --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): AnczykoJ
Proposal of next steps (incl. effort/h and verification): See task description.
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description:
This Change Request shall be used to tailor the latest Core SW Integration Test Plan for this project. Therefore, following Tasks shall be created:
- Tailor SW Integration Test Plan as per Tailoring instruction - SW Integration Test Team part
[Tailoring Guideline]: This work product shall not be tailored away.
Owner: Jeremy Anczykowski
Reviewer: Yessika Legat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 2
[Optional] Planned completion date: 05.05.2023
------------------------------------------------------ | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.5][VW MQB48-W][ESC][SoftwareIntegrationTestPlan] Share updated core document to project
--------------------------------------------------------------------------------
Details (Exact description): Share updated SoftwareIntegrationTestPlan core document to the project and adapt Tailoring document accordingly.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): SoftwareIntegrationTestPlan after update from CR 7079976
--------------------------------------------------------------------------------
Output Work Products: AD_BRK_VW_MQB48-W_ESC_SW_Integration_Test_Plan_Tailoring.xlsm, AD_BRK_SW_Integration_Test_Plan.docx
--------------------------------------------------------------------------------
Acceptance Criteria: Updated revision of documents from "Output Work Products".
------------------------------------------------------------------------------ --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): AnczykoJ
Proposal of next steps (incl. effort/h and verification): See task description.
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
Description:
This Change Request shall be used to tailor the latest Core SW Integration Test Plan for this project. Therefore, following Tasks shall be created:
- Tailor SW Integration Test Plan as per Tailoring instruction - SW Integration Test Team part
[Tailoring Guideline]: This work product shall not be tailored away.
Owner: Jeremy Anczykowski
Reviewer: Yessika Legat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 2
[Optional] Planned completion date: 05.05.2023
------------------------------------------------------ |
|
[SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.2][VW MQB48-W][ESC][SwAD Model][ModelChecker][Review] Resolve warning
--------------------------------------------------------------------------------
Details (Exact description):
Issue: Model Checker Warning present, which shall be resolved to ensure proper SwAD specification for testing.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): SwAD Build Rev 1.3.2.644 ,file ModelCheckerLog.csv
--------------------------------------------------------------------------------
Output Work Products: Updated SwAD Model
--------------------------------------------------------------------------------
Acceptance Criteria: Model Checker Warning for ID 4106 shall be resolved.
-------------------------------------------------------------------------------- NvramWrapper is a QM module so the tags has been corrected to QM to resolve the 4106 Model Checker Warning.
These changes will be taken up with the ALM_Task 7072824. | [SWE.5][VW MQB48-W][ESC] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [SWE.2][VW MQB48-W][ESC][SwAD Model][ModelChecker][Review] Resolve warning
--------------------------------------------------------------------------------
Details (Exact description):
Issue: Model Checker Warning present, which shall be resolved to ensure proper SwAD specification for testing.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): SwAD Build Rev 1.3.2.644 ,file ModelCheckerLog.csv
--------------------------------------------------------------------------------
Output Work Products: Updated SwAD Model
--------------------------------------------------------------------------------
Acceptance Criteria: Model Checker Warning for ID 4106 shall be resolved.
-------------------------------------------------------------------------------- NvramWrapper is a QM module so the tags has been corrected to QM to resolve the 4106 Model Checker Warning.
These changes will be taken up with the ALM_Task 7072824. |
|
[BSW_Test][SW: 1.7.1.55]: Issue with DID 207E and 207F To implement diag control AVH via interface IsAvhSwitchedOnByDiag Attachments has been done and tested, ready for check-in. | [BSW_Test][SW: 1.7.1.55]: Issue with DID 207E and 207F To implement diag control AVH via interface IsAvhSwitchedOnByDiag Attachments has been done and tested, ready for check-in. |
|
[SWE.5][VW MQB48-W][EBB] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Rhapsody Detailed Design Model - ComponentList OldFormat
--------------------------------------------------------------------------------
Details (Exact description): Provide ComponentList Export based on new information from Rhapsody Detailed Design Model in the old ComponentList format + memory section information, as specified in CR 5037625.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5037625
--------------------------------------------------------------------------------
Output Work Products: ComponentList Export from Rhapsody Detailed Design Model in the OldFormat + memory section information for VW MQB ESC project.
--------------------------------------------------------------------------------
Acceptance Criteria: The ComponentList format is based on the old format and contains also the "Component / RamBudget / allocation / section" information, like in the new ComponentList Export.
-------------------------------------------------------------------------------- 2021-06-09 16:46:40 RBr:the required Model and Scipt updates are done with an previous CR and both exports ( old and new Format) are available.
==> reject this CR | [SWE.5][VW MQB48-W][EBB] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): Rhapsody Detailed Design Model - ComponentList OldFormat
--------------------------------------------------------------------------------
Details (Exact description): Provide ComponentList Export based on new information from Rhapsody Detailed Design Model in the old ComponentList format + memory section information, as specified in CR 5037625.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): CR 5037625
--------------------------------------------------------------------------------
Output Work Products: ComponentList Export from Rhapsody Detailed Design Model in the OldFormat + memory section information for VW MQB ESC project.
--------------------------------------------------------------------------------
Acceptance Criteria: The ComponentList format is based on the old format and contains also the "Component / RamBudget / allocation / section" information, like in the new ComponentList Export.
-------------------------------------------------------------------------------- 2021-06-09 16:46:40 RBr:the required Model and Scipt updates are done with an previous CR and both exports ( old and new Format) are available.
==> reject this CR |
|
[SWE.5][VW MQB48-W][EBB] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [ESC] MapFileAnalyzer - BudgetComparison Config Update
--------------------------------------------------------------------------------
Details (Exact description): After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/SCS/ToolDevelopment/MapFileAnalyzer/Ti4x/Ti4x%5fGEN%5f3/1%5fBinaries/BUILD%5fVIEW/project.pj&projectrevision=1.13.1.2
--------------------------------------------------------------------------------
Output Work Products: Updated MapFileAnalyzer configuration
--------------------------------------------------------------------------------
Acceptance Criteria: BudgetComparison Threshold is set to 200% and only components who consume more than 200% of Ram or Rom are highlighted red.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
[ESC] MapFileAnalyzer - BudgetComparison Config Update / PartitioningAnalysis Update
Description:
After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%
Furthermore, update configuration of PartitioningAnalysis with new ComponentList file.
Owner: Jeremy Anczykowski
Reviewer: Lukas Hoppe
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 23.07.2021
------------------------------------------------------ | [SWE.5][VW MQB48-W][EBB] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
Aim (Objective and Rationale): [ESC] MapFileAnalyzer - BudgetComparison Config Update
--------------------------------------------------------------------------------
Details (Exact description): After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/SCS/ToolDevelopment/MapFileAnalyzer/Ti4x/Ti4x%5fGEN%5f3/1%5fBinaries/BUILD%5fVIEW/project.pj&projectrevision=1.13.1.2
--------------------------------------------------------------------------------
Output Work Products: Updated MapFileAnalyzer configuration
--------------------------------------------------------------------------------
Acceptance Criteria: BudgetComparison Threshold is set to 200% and only components who consume more than 200% of Ram or Rom are highlighted red.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:
[ESC] MapFileAnalyzer - BudgetComparison Config Update / PartitioningAnalysis Update
Description:
After discussion with the architect C.Seifen it was decided that the BudgetComparison Threshold should be set to 200%
Furthermore, update configuration of PartitioningAnalysis with new ComponentList file.
Owner: Jeremy Anczykowski
Reviewer: Lukas Hoppe
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 23.07.2021
------------------------------------------------------ |
|
[SWE.5][VW MQB48-W][EBB] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swe.5 - softwareintegrationtest - request swad spec
--------------------------------------------------------------------------------
details (exact description):
this cr is required to add / update specification in the architectureconcept, which were discussed with christianseifen, see attached mail from (20.05.2021 15:47).
today verbal agreed specification are already used for softwareintegrationtest, this cr should also provided written evidence in swad concept.
the budgets used for testing today (mentioned below) should be changed to the projects need, please compare also with specification christianseifen which may apply in general for each product / project.
the following specifications should be available:
1. rom overall consumption
(today used for testing 80% budget)
(mention relation to rombudget per swad_component)
2. ram overall consumption
(today used for testing 80% budget)
(mention relation to rambudget per swad_component)
3. runtime budget per core
is should be noted that the budget is used for testing from specification per core in document resourceestimationsheet.
furthermore, the runtime budget should be per core and not be specified per runnable. (runtime values per runnable in swad are used to calculate overall runtime per core)
4. stack consumption budget for task/isr stacks and csa stacks
(today used for testing 70% budget / csa stacks 80% budget)
5. nvram budget
6. memorybudget (ram/rom) for each swad_component is defined and it is valid for a component to consume 100-200% of its budget.
furthremore, it should clarified from swad if it is possible to have these kind of specifications available in the rpy swad model to include them in an automatic generated export.
--------------------------------------------------------------------------------
input work products (link or other reference): architectureconcept
--------------------------------------------------------------------------------
output work products: updated architectureconcept
--------------------------------------------------------------------------------
acceptance criteria: a written specification is available for each requested topic above.
-------------------------------------------------------------------------------- [benjamin bauer (bauerb), 2022-03-10, 16:04:37]
--------------------------------------------------------------------------------
brief investigation comment:
based on the scope of this cr, it is proposed to carry over chapter 6.2.4 (µc resource consumption objectives and constrains) of the vw mqb esc sw architecture documentation to the ebb documentation.
--------------------------------------------------------------------------------
risk (low/medium/high): medium
--------------------------------------------------------------------------------
proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
task 1
-------------------------------
title/header: vw common ebb - copy chapter on µc resource consumption objectives and constrains from esc concept document
description: see investigation
assigned to: benjamin bauer
verifier: christoph bayer
estimated effort: 2h
------------------------------- | [SWE.5][VW MQB48-W][EBB] - Software Integration Test - Test Objective Overview - Incidents/Problems/Bugs --------------------------------------------------------------------------------
aim (objective and rationale): swe.5 - softwareintegrationtest - request swad spec
--------------------------------------------------------------------------------
details (exact description):
this cr is required to add / update specification in the architectureconcept, which were discussed with christianseifen, see attached mail from (20.05.2021 15:47).
today verbal agreed specification are already used for softwareintegrationtest, this cr should also provided written evidence in swad concept.
the budgets used for testing today (mentioned below) should be changed to the projects need, please compare also with specification christianseifen which may apply in general for each product / project.
the following specifications should be available:
1. rom overall consumption
(today used for testing 80% budget)
(mention relation to rombudget per swad_component)
2. ram overall consumption
(today used for testing 80% budget)
(mention relation to rambudget per swad_component)
3. runtime budget per core
is should be noted that the budget is used for testing from specification per core in document resourceestimationsheet.
furthermore, the runtime budget should be per core and not be specified per runnable. (runtime values per runnable in swad are used to calculate overall runtime per core)
4. stack consumption budget for task/isr stacks and csa stacks
(today used for testing 70% budget / csa stacks 80% budget)
5. nvram budget
6. memorybudget (ram/rom) for each swad_component is defined and it is valid for a component to consume 100-200% of its budget.
furthremore, it should clarified from swad if it is possible to have these kind of specifications available in the rpy swad model to include them in an automatic generated export.
--------------------------------------------------------------------------------
input work products (link or other reference): architectureconcept
--------------------------------------------------------------------------------
output work products: updated architectureconcept
--------------------------------------------------------------------------------
acceptance criteria: a written specification is available for each requested topic above.
-------------------------------------------------------------------------------- [benjamin bauer (bauerb), 2022-03-10, 16:04:37]
--------------------------------------------------------------------------------
brief investigation comment:
based on the scope of this cr, it is proposed to carry over chapter 6.2.4 (µc resource consumption objectives and constrains) of the vw mqb esc sw architecture documentation to the ebb documentation.
--------------------------------------------------------------------------------
risk (low/medium/high): medium
--------------------------------------------------------------------------------
proposal of next steps (incl. effort / h and verifier):
-------------------------------------------------------
task 1
-------------------------------
title/header: vw common ebb - copy chapter on µc resource consumption objectives and constrains from esc concept document
description: see investigation
assigned to: benjamin bauer
verifier: christoph bayer
estimated effort: 2h
------------------------------- |