1 / 10

DART Product Test ANZ 4.2 Planning

DART Product Test ANZ 4.2 Planning. Hoang Nguyen / Ajay Joshi June 2007 V.1.0. Version History. Background and Purpose.

gizela
Télécharger la présentation

DART Product Test ANZ 4.2 Planning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DART Product Test ANZ 4.2 Planning Hoang Nguyen / Ajay Joshi June 2007 V.1.0

  2. Version History

  3. Background and Purpose • Experience from previous deployments suggests that there is a need to have a focussed effort on Product Test of DART applications (R/3, BW, POSDM and IFA) to ensure appropriate level of readiness of the applications prior to commencement of Link Test and Integration test. • The purpose of this presentation is to describe… • A suitable scope that meet the objective of Product Test • The resources required • The timeline that support the existing DART-GSS programme timeline

  4. Objective of Product Test • Prior to commencement of Link Test as part of Product Test following objective is set to ensure that; • all DART outbound files are generated as per design • all inbound processing from IFA to SAP works as per design (release mgmt) • new developments and configuration work end-to-end within DART applications • required staging tasks are completed • necessary data are completed and corrected

  5. Key Planning Assumptions • Product Test start 23/07 in IT environment! • To ensure smooth transition to Link Test (LT) and subsequent Integration Test (IT), Product Test needs to take place in ITC environment (PTZ 200). • IT environment with 4.2 codes is not available before 30/07 (due 3.2 codes will only be migrated to production on 27/07) • This means test team – including Ajay - needs to share time between Product test execution and 4.2 ITC planning and preparation from 23/07 to 10/08 • Selected functional and development resources need to be freed by from 23/07 to 10/08 • This is achievable based on the logic that an adequate Product Test upfront will result in reduction of effort in the subsequent LT and IT • Why not do Product Test before 23/07? • To many things going. • Resource contention; • test team busy supporting 2.1/3.2 ITC3 • data/functional team busy with… • AU 2.1 to 3.2 data enhancement • V&P for AU SC execution start 09/07

  6. Applications SAP R/3 SAP BW and POSDM Informatica New developments; ME inbound SCR0425 : Upper case GRN SCR0425 : WPUWBW01 Enhancement Ver07 Informatica change to rec type 21 -UK Production issue ME outbound FRD359 : NZ Loyalty and Epay FRD359 : Assortment List Ver24 FNS10341 : Central Keyboard management in SAP New configuration NZ tender configuration New changes on auto. Account determination table New variants required for NZ company code Other key processes FFR and regular outbound Note: Not in Scope FI – no new developments FRD395 : Fuel delivery reconciliation Alternates required for LIS reports missing in Release 3 Product Test Scope

  7. High-level Approach • Entry criteria • ITC environment on 30th of July • All new developments and configuration successfully unit tested • All relevant 4.2 transports imported into ITC environment • Assumptions • No test scripts and result recording required; Execution will be done based on a list of functions/processes • Will actively involve functional consultants as part of execution • DART applications readiness • Confirm staging in the respective applications • Establish base connectivity within applications (e.g. handshake between SAP and IFA) • Define and set up new variants • Data readiness • Identify and setup any additional master data in ITC environment • Identify and correct a subset of the master data to be used Product Test • Identify and create the transaction data to be used Product Test

  8. Resources

  9. Points to clarify • SCR0425 : Upper case GRN: Confirm with Bill Upper case – inbound does it involve outbound as well? • New changes on auto. Account determination table; Should this be included as part of 4.2 track – Utpal to confirm? • Confirm what data exist in ITC – Ajay to study Anant’s email

  10. High-level Plan, Activities and Roles

More Related