50 likes | 207 Views
Integration Testing System States. 13 th December,2006. Dart 3.2. Dart 4. Dart 3.1. {. {. ?GSS 2.1 / Dart 4?. {. GSS 2.1 / Dart 3.1. RAP / Dart 3.2. ‘Regression’ Testing. GSS 3.1 / Dart 4. RAP / Dart 3.1. GSS 2.1 / Dart 3.2. RAP / Dart 4. AUS Dart 3.1 – GSS 2.1
E N D
Integration Testing System States 13th December,2006
Dart 3.2 Dart 4 Dart 3.1 { { ?GSS 2.1 / Dart 4? { GSS 2.1 / Dart 3.1 RAP / Dart 3.2 ‘Regression’ Testing GSS 3.1 / Dart 4 RAP / Dart 3.1 GSS 2.1 / Dart 3.2 RAP / Dart 4 AUS Dart 3.1 – GSS 2.1 AUS FI sync – GSS 3.1 GSS 3.1 / Dart 3.2 GSS 3.2 / Dart 4 UK Dart 3.2 – GSS 3.1 UK Dart 3.2 – RAP AUS Dart 3.2 – GSS 2.1 AUS FI sync – Dart 3.2 NZ FI sync – Dart 3.2 ?US Legacy / Dart 4? + + + GSS 4 / Dart 4 GSS 3.2 / Dart 3.2 Dart 2.1 GSS 3.1 / Dart 3.1 Dart 4 Product Test GSS 2.1 / Dart 2.1 Dart 3.2 Product Test < < Dart 3.1 Product Test Dart 2.1 Product Test GSS 4 Product Test GSS 3.2 Product Test GSS 3.1 Product Test GSS 2.1 Product Test USA Dart 4 - GSS 4 ?USA Dart 4 – Legacy? NZ/AUS Dart 4 – GSS 3.2 AUS Dart 4 – GSS 2.1 AUS FI sync – Dart 4 UK Dart 4 – RAP UK Dart 4 – GSS 3.1 IK Dart 4 – GSS 3.2 AUS Dart 2.1 – GSS 2.1 AUS FI synch UK Dart 3.1 – GSS 3.1 UK Dart 3.1 – RAP NZ Dart 3.2 – GSS 3.2 AUS Dart 3.2 – GSS 3.2
Release 3.1current • Dart 3.1 to GSS 3.1 (GSS Track) • Dart 3.1 to GSS 2.1 (AUS Track) • Unless upgrade of sites from GSS 2.1 to GSS 3.1 is trivial and can be done big-bang…will be period of live operation with this combination • FI synch from Dart 2.1 to Dart 3.1 (AUS legacy) • Have to switch legacy to synch with new instance of Dart • RAP inbound into Dart 3.1 (UK Track) • Release 3.2 • Dart 3.2 to GSS 3.2 (GSS Track) • Dart 3.2 to GSS 2.1 (AUS Track) • AUS will have some sites on GSS 2.1, and some on GSS 3.1 so again unless sites on GSS 2.1 can be upgraded big-bang…. will be period of live operation with this combination while 2.1 sites are upgraded • FI synch from Dart 3.1 to Dart 3.2 (AUS legacy) • AUS will have some sites on GSS 2.1 and some still on legacy so there is a need to upgrade the FI synch to hook into Dart 3.2 rather than the current Dart 3.1 • Dart 3.2 to GSS 3.1 (UK GSS Track) • UK will have some sites on GSS 3.1, so again unless sites on GSS 3.1 can be upgraded big-bang…. will be period of live operation with this combination • Dart 3.2 to RAP (UK Legacy Track) • UK will have some sites on RAP still at this point in time according to rollout schedule so will be period of live operation with this combination
Release 4 • Dart 4.1 to GSS 4.1 (GSS Track) • Dart 4.1 to GSS 3.2 (ANZ Track 1 /UK Track 1) • Unless upgrade of sites from GSS 3.2 to GSS 4.1 is trivial and can be done big-bang…will be period of live operation with this combination for both UK and ANZ sites • Will also be sites live with GSS 3.2 in UK if guiding principle of stopping roll-out of non-current version of GSS is followed in UK deployment. First sites to receive GSS 3.2 in UK will be those sites already on GSS 3.1 who will be upgraded (see UK Track 2 below). • ?Dart 4.1 to GSS 3.1 (AUS Track 2 / UK Track 2)? • If AUS sites and UK sites on 3.1 have not been upgraded to 3.2 by the time that Dart 4.1 goes live, there will be a period of live operation with this combination (in both UK and AUS) • FI synch from Dart 3.2 to Dart 4.1 (AUS Track 3,legacy) • According to AUS rollout schedule, rollout continues throughout 2007 so not all sites will be off legacy systems until then and therefore this combination will exist in production • ? whether we have potential for Dart 4.1 – GSS 2.1 depends on a) how quickly 2.1 is rolled out, and b) how quickly any rolled out 2.1 sites are upgraded to either 3.1 or 3.2 • RAP inbound into Dart 4.1 (UK Track 3) • According to UK rollout schedule, rollout continues until October so not all sites will be off legacy systems until then and therefore this combination will exist in production