T-Mobile

Updated December 2006

T-Mobile (United Kingdom)
24th of July 2006 – current

Test Stream Leader

Capability test

· First projectmilestone was to prove that the Disaster Recovery (DR) infrastructure (hardware, network and software) is able to switch to the remote site (Vienna) and perform a key business process (billing run). I successfully leaded the DR capability test according to the plan. I received signoff from T-Mobile business two weeks before the deadline. This was an important Amdocs project milestone. The test was performed by T-systems and Amdocs delivering the results to T-Mobile IS Quality.

People involved
	Management	24 h shifts	normal WH
T-systems	1 Project manager	1 TSL storage 1 TSL DBA 1 TSL Unix
Amdocs	1 Project manager	1 Amdocs Infra 1 Amdocs Storage 3 Amdocs Support	1 Amdocs DBA 1 Amdocs Unix 2 Amdocs Test
T-Mobile	1 Operations manager	2 Operators

Regression test

· Second milestone was to prove that the DR infrastructure (hardware, network and software) can perform exactly the same functionality as in production. The release compared was the fourth of 2006. The signoff criteria was 99% of all tests passed and 100% executed with no critical defects open. T-Mobile business signed off the test results after 2 months of test execution by 4 full time testers.

New Functionality test

· Third milestone is to prove that the DR newly developped software (in the first release of 2007) can recover the application within the agreed scope. After the new release went into production it was automtically synchronised to the disaster site and the functionlity was tested in three weeks by 4 dedicated full time testers.

Interface test

· Fourth milestone is to prove that the interfaces in production are able to switch to the DR site in case of a disaster. All external interfaces are tested in coorporation with the T-Mobile system owners. T-systems were responsible for the firewall changes and the tests are executed by two dedicated full time testers during 3 months.

Performance test

· Fith milestone was to prove that the DR infrastructure (hardware, network and software) has the same performance as production and is capable of handling daily operations when a disaster occurs. Criteria are recovery of the system, amount of CSA's connecting, meeting billing and rating KPI's and handling the CDR backlog in the contractual pre-defined period.

End to End Cycle test

· Sixth milestone was to prove that the DR infrastructure (hardware, network and software) is capable of recovering all daily operations when a disaster occurs. Criteria are recovery of the system within 24 hours, recovering the billing and rating functionality in 48 hours and handling the backlog of EOD's and billing cycles in the contractual pre-defined period.