【正文】 ution Architecture Huawei APS Project Page 11 of 29 ARCHITECTURE The following diagram indicates the environments that will be used during the APS BR1 Test. The specific environment requirements for the defined levels of test will be covered in the Detailed Test Plan and once the technical specification development process has been pleted. F u l l U A TI n te g r a ti o nU n i t T e s tPr o to ty p eEx te n d e d SI TL i m i te d U A TER P SI TER P U A TC o r e SI TStr e s sM a n u a l TEST ENVIRONMENT REQUIREMENTS The SIT and UAT Detailed Test Plans will document the necessary test environments for each of these test levels. The current plan for testing activities is provided below. Activity End Date Develop Test Strategy 4 Sep 2020 Sign off Test Strategy Complete SIT Detailed Test Plan Complete Development of SIT Test Cases Complete SIT Environment Setup Commence Core SIT Commence Extended SIT Complete SIT Complete UAT Detailed Test Plan Complete UAT Environment Setup Overall Solution Architecture Huawei APS Project Page 12 of 29 Activity End Date Complete Development of UAT Test Cases Commence Limited UAT Commence Full UAT UAT Go/No Go Checkpoint (after Limited UAT) UAT Go/No Go Checkpoint (after Full UAT) Sign Off Acceptance Production Cut over Final Go/No Go Checkpoint TEST DELIVERABLES The following deliverables will be created: ? Test Strategy ? Test plans for unit, and internal integration by module teams ? Detailed Test Plan for SIT 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 bined exercises in order to address the test focus areas. They will be performed during the designated Levels of Test (for example: Integration Test, Systems Integration Test, User Acceptance Test). Types of test are broadly classified as Functional Testing and Structural Testing. The purpose of functional testing is to ensure that the user functional requirements and specifications are met. Test conditions are generated to evaluate the correctness of the application. The following are some of the categories anized alphabetically: Functional Types of Test Description Priority Audit amp。 conditions coverage ? To test exception conditions 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 am