0% found this document useful (0 votes)
923 views1 page

ABAP Code Review Process Flow

The document outlines the ABAP code review process which involves a reviewer completing a code review with a developer, discussing any needed changes, the developer completing unit testing, and getting sign-off from the reviewer before moving to further testing. It details the steps, roles, and decisions involved such as arbitrating changes with leads, requesting resources, and getting transport approval to move code to quality systems.

Uploaded by

K Vinay Kumar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
923 views1 page

ABAP Code Review Process Flow

The document outlines the ABAP code review process which involves a reviewer completing a code review with a developer, discussing any needed changes, the developer completing unit testing, and getting sign-off from the reviewer before moving to further testing. It details the steps, roles, and decisions involved such as arbitrating changes with leads, requesting resources, and getting transport approval to move code to quality systems.

Uploaded by

K Vinay Kumar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

ABAP Code Review Process

A Reviewer ABAP Developer BEGIN Complete Coding Perform Code Review with Developer Make Changes & Communicate Back to Reviewer YES ABAP Developer Follow Up with Functional Team for Unit Test Data NO Is Unit Test Data Available ? Changes Needed? YES Is the Developer in agreement with the changes needed? Is the group in agreement with Changes Needed? NO YES ABAP Developer Complete Unit Test including all test cases in Unit Test Plan NO YES ABAP Developer

Reviewer Is Basis Team's involvement required ?

NO ARBITRATE TO SUB-LEAD

ARBITRATE TO TEAM LEAD Team Lead to decide if changes are needed or not

YES ABAP Developer Fill Out Column 1 & 2 of QA Checklist Template Reviewer Request Basis Team Lead for Basis Resource NO

Reviewer SIGN-OFF ON CODE REVIEW

Developer/Sub Lead Request Functional Team for conducting FAT

ABAP Developer (cc: Sub Lead) Basis Team Lead Request Team Lead for Code Review Resource Assign Basis Resource for validating ABAP code

Developer Is FAT successful ? YES Request Sub Lead for transport approval to QAS.

ABAP Team Lead Assign ABAP Resource (Reviewer) for Code Review

Reviewer Coordinate validation of code with Basis Resource

Reviewer NO Communicate Sign-off confirmation to Sub Lead and Team Lead A

Owner: Sundar Movva ; Last Updated: 07/07/03 5:55pm

You might also like