Você está na página 1de 4

ERF Process

1. Vantive/CR Creation

Vantive or CR number is required for applying any change in production. Vantive ticket is
required for production defect and change request number is required for addition of any
new feature. OMS Production support team can raise Vantive ticket for OMS and its
sister applications. Project Manager of OMS can raise the CR.

2. Check in code in CVS

After completion of code development and unit testing, check in and submit the latest
code changes in CVS.

3. ERF Creation

Definition of ERF is Emergency Request for Fix. It is an automated workflow tracking


system built in Mercury Quality center to monitor Emergency Requests through all steps
from development to final push to a production and/or testing environment. ERF employs
approvals and mail notification of teams and team members at each step.

Create ERF in quality center.

• QC Login Website:http://quality-center.sbc.com/qcbin/start_a.htm
• Userid/Password: ITSERVICES Domain userid/password
• Domain: ATT
• Project: Emergency_Fix
• Module: Defects

The ERF comprises of the following tabs:


• Main – Provide key information on the fix
• Test Install – Populated by Testing/ADBA/Infra
• Prod Deployment – Populated by EMAS
• Details – Provide details on the defect and the fix
• Prod Install – Provide detailed instructions how to install in production
• SCM Controlled Fields – Provide details on sources and build instructions
• Testing – Provide Detailed Test plan

ERF Main Tab Fields Description:


Field Name Description Type
Emergency Fix ID Unique Identification Number created by the system for each System
ERF. Generated.

Status Indicates current status of the ERF. This is system populated as System
the ERF moves through various stages in its life cycle. Generated

Developer ID ATTUID for the Developer providing the fix. This person Drop down list
would be the primary contact for any technical concerns
regarding the ERF
Team Lead The name of the Team Lead of the group creating the ERF. Text

Functional Area of The name of the group creating the ERF. This value may be Keywords
Fix different from the area that caused the error.

Fix for Markets The market, or markets that the fix is for. (Ex: Enabler Rating, Keywords
AMSS, OMS, BUS, PCT)

Root Cause Identify the type of root cause for the defect that the ERF is Keywords
correcting. (Ex: Release Item Defect, ERF Defect). Depending
on the value selected, other fields may become mandatory.
File Type Identify the type of the file provided by the ERF. Keywords
Emergency Fix # This field is mandatory if the root cause is ERF Defect. Enter Text
the previous ERF that caused the defect that this ERF is fixing.
1st missed in test The 1st test phase that this defect should have been found in. Keywords
phase
Release Type This field is mandatory when a Root cause of Release Item Keywords
defect is selected. Select the appropriate release from the drop
down list.
ERF for version The version that the ERF should be put in. Text
System Tested Populated only after the ERF has completed testing. Will show Keywords
results of testing.
Production ERF being delivered to production version = “immediate”, to Keywords
Emergency Fix? production plus one = “incremental” and to testing only = “no”.
Other Root Cause This field becomes mandatory if the root cause for the ERF is Text
selected as “Other”
CC Put in Version The version of code ERF is ccput and ERF removed. Text
Unit Tested Check Yes or No if the fix has been unit tested. Should always Keywords
be marked yes before sending to Testing.
Emergency Fix Indicate the type of ERF (Ex: Code, Data scrub) Keywords
Type
Ready for SCM Must be “Y” for production code ERFs that require to go Text
build through an SCM build. If so, add all relevant details in the
“SCM Controlled fields” tab.
Related Build A build ticket must be created for ERFs that involve any Text
Ticket # elements that are part of the code base.
Related Defect Enter the defect ID that documents the error the ERF is Text
ID correcting.
Root Cause Appl The application that was the root cause for the defect Keywords

Submit the ERF to STD for approval.

4. ERF Presentation

After STD’s approval for ERF, present it in ERF meeting.


Bridge number 312 442 3710 Passcode - 8984057# ( Timing 8:30 AM CST and 4:30 PM
CST). [Note: Announce the ERF numbers to be presented at the start of the meeting]

After getting the approval from ERF committee, ERF will go to System Testing team for
testing the fix.

5. System Testing

System Testing team communicate OMS infra team to install the hot fix on either of
system testing environment.

After applying the hot fix, system testing team does the testing based on the test cases
provided in the ERF form.

6. Test result presentation in ERF Meeting

System Testing team present the test results in ERF committee. If the fix is test certified,
ERF committee provides the approval for production deployment.

7. CCB Approval

Send CCB request form to CCB mail box. (LS CCB Prod)
Sample CCB form –

LS CCB Prod
Request Form ERF 1...

CCB meeting request mail will be send for presentation of ERF in CCB committee.
[Send the page to LSPRODCCB for emergency CCB meeting]

[OTE: As per new process, we don’t need to present ERF in CCB meeting, instead
create CR and submit for approval]
8. KARMIN Creation

After getting approval from CCB, send mail to Ross Adams ( ra1562) to create the
KARMIN request for the fix.

Make sure that all important information is available while creation of KARMIN request.
Please refer attached document

KARMIN Request
Required Inform...

KARMIN request will be submitted to EMASS group for applying the fix in production.

9. Production Deployment

EMASS team will apply the hotfix in production based on the installation instructions in
the KARMIN request.

10. Validation

Send Deployment validation status to woc-communication@techmahindra.com and


CC the LS CCB Prod mailbox.

Você também pode gostar