CAP-SST
PROCESS V9 HANDBOOK
Page | 1
CONTENTS
1.
Purpose of the Document .................................................................................................................... 3
2.
REQUIREMENTS .................................................................................................................................... 4
3.
4.
2.A
Baseline creation in DOORS .......................................................................................................... 5
2.B
Requirement Analysis in Doors ..................................................................................................... 5
DESIGN .................................................................................................................................................. 6
3.A
Add Related artifacts under the task/Linkages to the Task .......................................................... 8
3.B
Linkages to the Defect Fix WI........................................................................................................ 8
3.C
Baseline creation in EA.................................................................................................................. 9
3.D
GUID’s Doors Mapping ................................................................................................................. 9
3.E
Apply user lock in EA/Release user Lock ..................................................................................... 10
3.F
Get GUID to be mapped to DOORS Requirement....................................................................... 10
CODE ................................................................................................................................................... 11
4.A
5.
Baseline creation in Code............................................................................................................ 12
TEST ..................................................................................................................................................... 14
5.A
CT [Component Test](Drivers) .................................................................................................... 14
5.B
CT [Component Test](Upper Layers) .......................................................................................... 15
5.C
UT [Unit Test] .............................................................................................................................. 16
5.D
CIT [Component Integration Test] .............................................................................................. 16
5.E
Test w.r.t ALM,DOORS and EA .................................................................................................... 17
5.F
Example for Test Case mapping IN DOORS ................................................................................. 18
6.
TABLE with Required Links ................................................................................................................. 19
7.
Process Self Review Checklist ............................................................................................................ 21
8.
Version Information ........................................................................................................................... 22
Page | 2
1. PURPOSE OF THE DOCUMENT
This document is the handbook for the Users/developers of CUBAS/CAP2 complaint to CAP-SST
ASPICE/V9.x process. Though all the processes are mentioned in the Prolib, this handbook ensures
the understanding of the process followed in RDCT phase quickly and get necessary links easily from
Prolib and CAP-SST V9.x tools. This document is developer friendly that would also help the new
comers in the team to understand the processes easily.
Page | 3
2. REQUIREMENTS
ALM
ALM
CR is created and assigned.
CR : New
Create an estimation task i.e. a task with
tag {EST] in the headline and Task Type
as Analysis and enter the effort
estimation and analysis into it.
Close the estimation task
CR : New Evaluated
Once planned for the release
CR : Evaluated  Approved
If <80 hrs.
One task of Task Type
Other to be created with
tags [rdct] or whatever is
applicable
If >80 hrs.
Create separate task for
each of phase with less or
equal to 80 hrs. Task Type
select accordingly.
Task Owner creates a DOU +BSW Effort estimation
sheet
If the effort of the CR > 80 hours, then the BSW
estimation sheet needs to be attached to the CR.
CR : Approved  In Progress
REQ task is started.
Move REQ task to In Progress
1] Add Related artifacts under the task.
2] Create a Req Review
Refer Example 2.a)
DOORS
DOORS
Requirement is in New State
Fill all the columns as shown in Fig
1.a) below
<RB_RS_MS_Status>
NEW ACCEPTED
Tag Implemented by with the CR
number
Tag in/out if there is any related
requirement.
If the requirements have been analyzed,
and they are not feasible or cannot be
realized because of cost or risk, the status
should be changed. <RB_RS_MS_Status>
NEW REJECTED
Fill the attribute Internal Remark
< RB_RS_Remark> with the rejection
reason.
Run ALM-DOORS sync up tool to update
<WI_ID>, <WI_Type>, <WI_Status>,
<WI_Iteration>
Run DOORS consistency check(Refer
Table 5)
1] Create baseline.
2] Comment should be mentioned in
DOORS as a part of which task a
baseline is created. Refer 1.a)
Send for requirement review. For a
requirement review, artifacts that needs
to be given: DOU, DOORS baseline
Page | 4
2.A
BASELINE CREATION IN DOORS
2.B
REQUIREMENT ANALYSIS IN DOORS
Page | 5
3. DESIGN
ALM
ALM
AR
DOORS
EA
DOORS
Once AR task is started,
AR task move to In Progress
Apply lock before doing the
changes. Refer 2.e)
Architectural Design (Find
the process in link provided
in the Table 5)
1] Sequence diagram
2] Class Diagram
3] Top level diagram
Get the GUID that has to be
mapped in the DOORS.
Refer Example 2.f)
GUID’s to be mapped in
DOORS. Refer 2.d)
Run DOORS consistency
check
Execution of EA DOORS
Sync up Tool
Create a baseline.
1] Add Related artifacts under
the task.
2] Create a AR Review
Refer 2.a)
Baselining of EA.
Refer 2.c)
DOORS baseline should
be given for review
along with EA baseline.
Send it for Review.
For a Design review, artifacts
that needs to be given: DOORS
Baseline and EA baseline
Page | 6
ALM
DD
DOORS
ALM
EA
DD task is started. DD task
move to In Progress
Apply lock before doing the
changes. Refer 2.e)
DOORS
Detailed Design(Find the
process in link provided in
the Table 5)
1] Activity diagram and
Header files update
2] Attributes and
operations Update
DLL Check
Get the GUID that has to be
mapped in the DOORS. Refer
2.e)
Execution of EA DOORS
Sync up Tool
1] Add Related artifacts
under the task.
2] Create a DD Review
Refer Example 2.a)
GUID’s to be Mapped in
DOORS. Refer 2.d)
Run DOORS consistency
check
Create a baseline.
DOORS baseline should
be given for review
along with EA baseline.
Baselining of EA.
Refer 2.c)
Send it for Review.
For a Design review, artifacts
that needs to be given:
DOORS Baseline and EA
baseline
Page | 7
3.A
ADD RELATED ARTIFACTS UNDER THE TASK/LINKAGES TO THE TASK
Add Related artifacts under task
3.B
LINKAGES TO THE DEFECT FIX WI
Link the Fixing Change Set to the Defect Fix WI and additionally to the underlying Task WI.
Link the Review WI with Parent/Child to the Defect Fix WI and with Related to the underlying Task WI.
Page | 8
3.C
BASELINE CREATION IN EA
Naming of the Baseline: 001 AR42.8.4.0
001  Number of times the Baseline created for that release
AR42.8.4.0  Release Version
3.D
GUID’S DOORS MAPPING
GUID
Page | 9
3.E
APPLY USER LOCK IN EA/RELEASE USER LOCK
3.F
GET GUID TO BE MAPPED TO DOORS REQUIREMENT
Page | 10
4. CODE
ALM/ CODE
EA/DOORS
Code task is started. Code task is In Progress
Do the code code/Script changes
Perform code generation and build successfully
SIM build and ECU build both to be verified for
upper layer modules
Update Delivey Document and validate the
document.
Update workflow properties, Update the Software
version Macro
Nothing to do in DOORS and EA
Run Cchecker tool and solve the MISRA and
Compiler warnings. And verify HIS Metrics
Resource Consumption has to be done
Create baseline
Refer Example 3.a)
Send it for review. For a Code review, artifacts
that needs to be given: Code Changes, HIS,
Cchecker, Compiler warning reports
Once reviewed, deliver the Change sets linked with
Task WI\Defect Fix WI
Page | 11
4.A
BASELINE CREATION IN CODE
Enter the comment that describes the Changeset - meaningful
ModuleName_ARVersion_Task WI number_SmallDesc
Page | 12
Naming of the Baseline: AR42.8.4.0_259528_RR
AR42.8.4.0  Release Version
259528 Task Number/ Task Review WI number for Review Report delivery/ Defect Fix number for
CUBAS changes/ Defect Fix Review WI number for Review Report delivery/ Defect Fix Task WI number
for Quality and Test changes/ Defect Fix Task WI’s Review WI number for Review Report delivery
RR/R Review Required/ Review Report
Page | 13
5. TEST
5.A
CT [COMPONENT TEST](DRIVERS)
Automated Testing
a] Automated tests have been executed for new
added Test Cases/Re execution and passed
b] Save the Execution reports and place it in
rba_Can_AT_TestReports.zip and
rba_Can_AT_TestReport_Stack.zip
c] Update Test Spec and Test Report Summary for
new added Test Cases/for Re-execution as well.
Manual Testing
a] Manual Test have been executed for new
added Test Cases/Re execution and passed
--
d] Map the respective Requirements Id to the Test
case.
b] Update
Manual_Tests_TestReportSummary.xls and
Manual_Testspec.xls for new added Test Cases
and for Re-execution as well.
d] Map the respective Requirements Id to the
Test case.
e] Run RTMG tool
e] Run RTMG tool
f] Necessary review activity has been performed
f] Necessary review activity has been performed
Page | 14
5.B
CT [COMPONENT TEST](UPPER LAYERS)
Automated Testing
a) Automated tests have been executed for
new added Test Cases/Re execution and
passed
b] Automated tests is executed and passed
c] Save the Execution reports and place it in
MSN_TestReport.zip(MSN :- Module Short
name)
d] Update Test Spec and Test Report Summary
for new added Test Cases/for Re-execution as
well.
Manual Testing
a] Manual Test have been executed for new
added Test Cases/Re execution and passed
-b] For CanIf and CanTSyn :Update
Manual_Tests_TestReportSummary.xls and
Manual_Testspec.xls for new added Test
Cases and for Re-execution as well.
(ii) For CanSM and CanNm : - Update Manual
Test Case Sheet in MSN_ TestSpec.xlsm and
MSN_ TestReportSummary.xlsm for new
added Test Cases and for Re-execution as
well.
e] Map the respective Requirements Id to the
Test case.
d] Map the respective Requirements Id to the
Test case.
f] Run RTMG tool
e] Run RTMG tool
g] Necessary review activity has been
performed
f] Necessary review activity has been
performed
Page | 15
5.C
UT [UNIT TEST]
a] Unit tests have been executed in Cantata/AEEE-Eco and passed.
b] UT Test cases executed should be delivered in Zip format.
c] UT test Spec needs to be updated.
d] UT Test Report Summary should be updated with all the executed Test
Cases marked as passed or failed accordingly.
e] Map the respective GUID to the test cases
f] Update Coverage Report Summary in xlsm sheet and also the html reports
generated from Cantata in the zip folder.
g] Run ITMG tool
h] Necessary review activity has been performed
5.D
CIT [COMPONENT INTEGRATION TEST]
CIT tests have been executed in Cantata/AEEE-Eco and passed.
b] CIT test Spec needs to be updated.
c] CIT Test Report Summary should be updated with all the executed
d] Test Cases marked as passed or failed accordingly.
e] Map the respective GUID to the test cases
f] Necessary review activity has been performed
Page | 16
5.E TEST W.R.T ALM,DOORS AND EA
ALM
DOORS
EA
CR  In Progress
Run RTMG.
Run ITMG
Import RTMG output to
Baseline the ITMG Report
change sets
DOORS.
Test Cases will be mapped to
respective Requirement
once Imported
Baseline the RTMG Report
change sets.
CR: In Progress  Closed
<RB_RS_MS_Status>
ACCEPTED/ANALYZED
VALIDATED
Run ALM-DOORS sync up
tool.
Run DOORS consistency
check
Baseline DOORS
Send for review: DOORS
baseline, Test and quality
change set baseline
Page | 17
5.F EXAMPLE FOR TEST CASE MAPPING IN DOORS
Testcase mapping that are covered by review
Testcase mapping that are covered by Component Test
Test case
mapped
Test case
mapped
Page | 18
6. TABLE WITH REQUIRED LINKS
Requirement
Step
Links
Prolib link for
requirement
http://abtprolib.de.bosch.com:8080/pkit/go/process/element.do?elementType=Method
&elementName=Product+Engineering%7CRequirements%7CWork+Instruction
+for+Requirement+Engineering&projectName=proCCess+library%7CCAPSST+BSW+Process+Handbook
https://connect.bosch.com/wikis/home?lang=dede#!/wiki/W6a62b2b7ae56_457c_b6cd_63a7c8b6b3fb/page/Doors%20Consis
tency%20Check%20Script
Doors consistency
check
Design Step
Links
Prolib link for AR
http://abtprolib.de.bosch.com:8080/pkit/go/process/element.do?elementType=Method
&elementName=Product+Engineering%7CArchitecture%7CWork+Instruction+f
or+Architecture&projectName=proCCess+library%7CCAPSST+BSW+Process+Handbook
http://abtprolib.de.bosch.com:8080/pkit/go/process/element.do?elementType=Artifact
&elementName=Product+Engineering%7CRequirements%2C+Architecture+an
d+Design%7CSW+Design&projectName=proCCess+library%7CCAPSST+BSW+Process+Handbook
Prolib Link for DD
Code Step
Links
Prolib Link for
Code
http://abtprolib.de.bosch.com:8080/pkit/go/process/element.do?elementType=Method&el
ementName=Support%7CDocumentation%7CWork+Instruction+for+Documentati
on&projectName=proCCess+library%7CCAP-SST+BSW+Process+Handbook
Prolib Link for
Coding
guideline
http://abtprolib.de.bosch.com:8080/pkit/go/process/element.do?elementType=Method&el
ementName=Product+Engineering%7CCoding%7CCoding+Guidelines&projectNam
e=proCCess+library%7CCAP-SST+BSW+Process+Handbook
Page | 19
Test Step
Links
Prolib Link for
Test
http://abtprolib.de.bosch.com:8080/pkit/go/process/element.do?elementType=Activity&ele
mentName=Product+Engineering%7CTest&projectName=proCCess+library%7CCAP
-SST+BSW+Process+Handbook
Component
Baseline and
Snapshot
https://connect.bosch.com/forums/html/threadTopic?id=0680b0e3-735042b3-a1a7-2bb3016709d7&ps=25
Jenkins (CB/CT/CI) links in CanStack
VirtualCan/Mcan
Jenkins
http://rb-cdgjenkins.de.bosch.com/job/L1/job/ComDrv/job/AR42_9_0_X/job/Unicon/
Multican Jenkins
http://rb-cdgjenkins.de.bosch.com/job/L1/job/ComDrv/job/AR42_9_0_X/job/uC1/
Zyncan Jenkins
http://rb-cdgjenkins.de.bosch.com/job/L1/job/ComDrv/job/AR42_9_0_X/job/Xilinx/
Rscan Jenkins
http://rb-cdgjenkins.de.bosch.com/job/L1/job/ComDrv/job/AR42_9_0_X/job/RCAR/job/CAN
/
Canstack Jenkins
https://rb-cdg-jenkins.de.bosch.com/job/L1/job/CanStack/job/AR42_9_0_X/
Comstack Jenkins https://rb-cdg-jenkins.de.bosch.com/job/L1/job/ComStack/job/AR42_9_0_X/
Page | 20
7. PROCESS SELF REVIEW CHECKLIST
Process_Self_Review_
Checklist.xlsx
This is an internal checklist for the team to keep a track if all the above mentioned
processes are completed as a part of RDCT task and during the required releases.
This checklist has to be used after completion of the respective RDCT task to
ensure that all the activities are completed before sending it for review.
Also, the checklist can be sent to the reviewer to make sure all the activities as a
part of RDCT tasks are completed.
Page | 21
8. VERSION INFORMATION
1 Version overview and history of change
Version Date
Version
1.0.0
date
2020-04-30
Change
Initial Version
Publisher
Reenal Lobo
State
FINAL
Page | 22