huaweiintegratedtestingstrategy-華為供應鏈(doc29)-供應鏈管理(存儲版)

　　

【正文】 verall Solution Architecture Huawei APS Project Page 3 of 29 PURPOSE This is a munication vehicle for the entire ISC project team including the APS team as well as the ERP team. It should be used by all of those who will be responsible for planning preparation and execution of test ponents. This document will be further substantiated by the Test Plans, which will define in detail the specific areas of testing for each level and type of test. INTRODUCTION This document constitutes the Testing Strategy for the APS BR1 implementation. It describes the overall test strategy to be adopted and defines the following: ? What is the scope of the modules to be tested? ? What are the key risks within that scope? ? What test needs to be performed to address those risks? ? When should the test be done? ? Who is responsible for performing the key testing activities? SCOPE This section describes the scope of the APS BR1 solution, cover at a high level, the functions included, the application architecture, technical architecture and operational changes. The diagram below defines the scope of the APS BR1 implementation. It also shows the information flows between the ERP system and i2 APS. Overall Solution Architecture Huawei APS Project Page 4 of 29 De mandPl anningDPForecas t Ne tt ingFcN t_ DFSamp。OP, MASTER PLANNING amp。 FORECAST NETTING TO Samp。 SUPPLIER COLLABORATION SCC TO MASTER PLANNING SCP... 錯誤 !未定義書簽。 Channel Forecast DP19 Archiving Archiving DP20 KPI Measurement KPI Tracking Forecast Netting Business Scenarios Serial Number Categories of Scenarios Target User Scenarios within Category/Comments FcNt1 Forecast Netting Orders less than forecast in each planning bucket of a forecast bucket FcNt2 Orders more than forecast in some planning buckets but less than total forecast for the forecast bucket FcNt3 Orders more than total forecast in a forecast bucket FcNt4 Different AIs for one Sales Order (one ATO) consume forecast from different planning buckets FcNt5 Forecast Profiling over Partial Weeks FcNt6 Avoiding noninteger daily quantities during Forecast Profiling FcNt7 Netting of backlog orders FcNt8 Backward amp。 verify the readiness of application for system integration Verify that data has been migrated as per the defined mappings System Integration ? To test the coexistence of products and applications that are required to perform together in the productionlike operational environment (hardware, software, work) ? To ensure that the system functions together with all the ponents of its environment as a total system ? To ensure that the system releases can be deployed in the current environment Verify the ability of the application to be integrated with other systems and modules User Acceptance ? To ensure the system meets the business user requirements and business processes Verify the integrated system meets business requirements including service levels Overall Solution Architecture Huawei APS Project Page 16 of 29 Level Focus Benefit Operations Acceptance ? To ensure the product can operate in the production environment ? To ensure the product meets the acceptable level of service as per Service Level Agreement ? To ensure the product operates as stated in the Operations Standards ? To ensure the system can be recovered / restarted as per standards ? To ensure that UNIX Scripts are as per standard Verify that the application can operate in the production environment. Operability tests will be concurrent with, User Acceptance Tests. For the APS BR1 implementation project the following levels of test will be required: Levels of Test Where needed Unit test All data migration ponents All ponents where code has been changed Integration test All separate and unique functions and transactions within the Data Migration suite All customized transactions and functions within the Oracle modules All Type and 2 systems that required change to functions and transactions Systems Integration Test (SIT) The integrated suite of implemented Oracle 11i modules Oracle 11i and all of the interfacing Type 1, 2 and 3 applications User Acceptance Test (UAT) The total solution plus desktop procedures, business processes SCOPE OF TEST LEVELS AND TEST TYPES One of the key principle behind all tests is to ensure that tests are performed as early as possible so that errors can be corrected early which in turn reduces the cost and time required for fixes. Given that principle, the following Types of Test should be included in the scope of each Level of Test. Levels Types Unit Integration SIT UAT Audit amp。 recover after failure H Correctness Ability to process data according to prescribed rules. Controls over transactions and data field edits provide an assurance on accuracy and pleteness of data H Maintainability Ability to locate and fix an error in the system. Can also be the ability to make dynamic changes to system environment without making system changes H Operability Effort required to learn and operate the system (can be manual or automated) M Performance Ability of the system to perform certain functions within a prescribed time H Portability Ability for a system to operate in multiple operating environments L Reliability Extent to which system will provide the intended function without failing H Security Assurance that the system/data resources will be protected against accidental and or intentional modifications or misuse M Technology Extent to which new technology poses a risk to performance, reliability M Usability Effort required to learn and use the system M TEST TYPES Testing types are logical tests that are to be conducted in isolation or as