ࡱ> BD?@A[ hbjbj 5ΐΐ1`8^#$($$$&Zo)*+^-^-^-^-^-^-^ac-^+&&++-^$$hB^4E4E4E+$$+^4E++^4E4E[]$R+.{]^X^0^]d/Z d4]d]h+"1+4EI+]+Y+++-^-^=&+++^++++d+++++++++ :  Automation Test Estimation Framework Prepared by/Modified by RoleDate of preparation/ ModificationTest Managerdd/mmm/yyyy Reviewed byRoleDate of ReviewReviewer 1 Reviewer 2Project Manager Test Leaddd/mmm/yyyy Approved byRoleDate of ApprovalHeaddd/mmm/yyyy Circulation List Group1, Group2Version number of the work product1.0 TABLE OF CONTENTS  TOC \o "2-2" \t "Heading 1,1" 1. Introduction  PAGEREF _Toc90873819 \h 3 2. Objective  PAGEREF _Toc90873820 \h 3 3. ProjectName Test Activities  PAGEREF _Toc90873821 \h 4 4. Size Estimation  PAGEREF _Toc90873822 \h 6 5. Productivity  PAGEREF _Toc90873823 \h 8 6. Effort Estimation  PAGEREF _Toc90873824 \h 10 7. Conclusion  PAGEREF _Toc90873825 \h 14 8. Assumptions  PAGEREF _Toc90873826 \h 14 9. Appendix  PAGEREF _Toc90873827 \h 14 10. Revision History  PAGEREF _Toc90873828 \h 15  Introduction Testing is the mechanism by which defects can be found during execution of the application, which are undetected during reviews in different stages of software development. This document is an attempt to come out with test estimation framework that has a sound basis and which is more aligned to ProjectName testing requirements. The proposed estimation framework is based on the current set of testing activities carried out as part of ProjectName testing. If the activities change [scope, no. Of activities, type of activities etc] in future, the estimation framework has to be modified as appropriate. Objective This document introduces an estimation framework for ProjectName testing activities. The goal of this estimation framework is to: Identify the major testing activities that are carried out as a part of ProjectName testing. Arrive at Size estimation for each work product pertaining to all the testing activities. Based on empirical data, compute productivity for each work product pertaining to all the testing activities. Arrive at Effort estimation for each work product pertaining to all the testing activities. ProjectName Test Activities The following table provides the list of testing activities that are carried out in ProjectName during the various ProjectName-PLM stages. The White Box activities are newly identified for future needs. ProjectName PLM Stage Test ActivitiesCommentsM0None ProjectName Test team is not involved in this phase.M1Understanding SRD/PRD and FS Identify test requirement by going through SRD/PRD, FS documents and participating in relevant Fagan reviews / JAD sessions.M1Prepare Master Test planContains test requirements [Functional / Performance / Security / Compatibility] for the product, test strategy, test environment, overall test schedule and plan. M1Review Master Test PlanReview for completeness based on test requirementsM2Black Box Testing: Prepare functional test planFunctional test plan is prepared for critical features of the product.M2Review functional test planReview for completeness based on functional test requirementsM2Black Box Testing: Prepare Functional Test Case documentsIt contains test cases pertaining to all test requirements (PRD/SRD) It also traces the test cases to product requirements (PRD/SRD)M2White Box Testing: Design of test casesCreate unit test design document (The JUNIT test framework can be used for testing Java code)M2Prepare QTP Scripts: Black Box Test cases.Identify features, which can be automated using QTP. Define Actions and data sets for the identified features Identify Workflows Create/Update Global Object File Create QTP Scripts (VBScript)VB (according to data driven test technique) Add checkpoints and update shared object repository Integrate in the QTP frameworkM2Review and Update Functional Test Case documents.Read the updated requirements document or PCR Update the traceability matrix Identify and remove Obsolete test cases Identify Updates to existing test cases Identify new test cases M2/M3Prepare Test Data Read the test case doc(Functional, Performance, Security, Compatibility) Identify the data requirement for each kind of testingM3White Box Testing: implementation of test codeCoding of white box test cases using JUnit framework. Creation of test data sets for white box testingM3Setting up Test EnvironmentSetup Performance test environment Setup Functional test environment Setup Unit test environment Setup Integration test environmentM3Execute manual Functional Test Cases for Desktop. Set the test environment Configure user Execute the testsM3Execute QTP scripts (Functional Test Cases) for Desktop. Set the test Framework Execute the testsM3Execute manual Functional Test Cases for Devices.Configure Devices Execute the testsM3Execute QTP scripts (Functional Test Cases) for Devices. Using device simulators / browsers on desktop.M3Performance testing using Spider tool.Identify no. of users to be simulated Create Spider Sessions (50 user/ session is limit) Execute the testsM3Perform V&V (Verification & Validation)Go through V&V bugs that are fixed Identify V&V tests Setup Test Environment Execute V&V testsM3Perform incremental & regression testing Go through regression bugs that are fixed Identify regression tests Setup Test Environment Execute regression testsM3Log and Report Test execution results. Bugs are filed in the defect tracking system - Bugzilla. Provide test summary reports in the form of an excel sheet.M3Defect Triage involvementParticipation in defect prioritization.M4/M5NoneProjectName Test team is not involved in this phase. Size Estimation In this section we have come out with the definition of Size for each of the test activities identified in the previous section. ProjectName PLM StageTest ActivitiesActivities for arriving at Sizing / Work Product Items Work product sizeM0None (ProjectName Test team is not involved in this phase.)None (ProjectName Test team is not involved in this phase.)N/AM1Understanding SRD/PRD and FSN/AN/AM1Prepare Master Test planMaster Test Plan document will contain high level 1) Test requirements [Functional / Performance / Security / Compatibility], 2) Test Strategy, 3) Test Environment, 4) QA Review Plan, 5) Resourcing & 6) Scheduling.Sizing not applicable ( To obtain data based on past history )M1Review Master Test PlanReview RecordSizing not applicable ( To obtain data based on past history )M2Black Box Testing: Prepare functional test planSizing not applicable ( To obtain data based on past history )M2Review functional test planSizing not applicable ( To obtain data based on past history )M2Black Box Testing: Prepare Functional Test Cases. (for a given feature.) (1) Identify test items (Usually one test item per use case) for a given use case. (2) Identify test scenarios for each of the test item. (Typically there are at least three scenarios for a given test item viz. Functional test scenario, Alternate test scenario, Exceptional test scenario. For example in some cases, there will be multiple sets of the above three test scenario categories.) (3) Identify and compute number of test cases under each scenario depending on the corresponding test requirements. Total # of test cases / testsM2White Box Testing: Design of test cases1) Identify the packages, classes or functions which need white box testing 2) Identify Asserts in the same. 3)Design a fixture or test suite for the same 4)Create unit test design documentTotal # of Asserts per class Total # of i/o for total no. of test cases(Asserts) Per classM2Prepare QTP Scripts: Black Box Test cases.Identify Workflow Identify number of unique actions (one action equivalent to test case) Associate actions with workflow. Arrive at SLOC based on actions. QTP Source Lines Of Code.M2Review and Update Functional Test Case documents.Review regression suite Update regression suite Review functional test case Update functional test caseTotal # of regression test cases Total # of functional test casesM2/M3Prepare Test Data [user data creation, content data creation etc.]Pst files, nsf files, attachments of various application types, QTP scripts for user data generation Sizing not applicable M3White Box Testing: implementation of test codeCoding of white box test cases using JUnit framework. Creation of test data sets for white box testing (The JUNIT test framework can be used for testing Java code)Java Source lines of code OR # of JUnit ClassesM3Setting up Test EnvironmentSetup Performance test environment Setup Functional test environment Setup Unit test environment Setup Integration test environment Sizing not applicableM3Execute Functional Test Cases Desktop Test Execution Total # of executed test cases M3Execute Functional Test CasesExecute QTP scripts (Functional Test Cases) for Desktop.Total # of executed test casesM3Execute Functional Test Cases Device Test Execution Total # of executed test cases M3Execute Functional Test CasesExecute QTP scripts (Functional Test Cases) for Devices.Total # of executed test casesM3Performance testing 1) Identify product areas whose throughput will be tested 2) Identify product areas which will stress tested 3) Identify product areas which will Load testedDelphi technique will be usedM3Perform V&V (Verification & Validation)V&V test reportTotal # of executed V&V test cases M3Perform incremental & regression testing Regression test reportTotal # of executed regression test casesM3Log and Report Test execution results. Updated bugzilla defect entries & consolidate test reports Total # of defects updated / added in bugzillaM3Defect Triage involvementParticipation in defect prioritization.Sizing not applicableM4/M5None (ProjectName Test team is not involved in this phase.)N/A (ProjectName Test team is not involved in this phase.)N/A Productivity This section outlines the productivity for the test activities, which are carried out at ProjectName. The data was computed based on empirical data based on Razor & Unifi releases in the past. The productivity (figures are based on average productivity viz. Averaged out across complexities of requirements. ProjectName PLM StageTest ActivitiesWork Product ItemsAverage Productivity M0None (ProjectName Test team is not involved in this phase.)N/AN/AM1Understanding SRD/PRD and FS N/AN/AM1Prepare Master Test planMaster Test Plan documentN/AM1Review Master Test PlanReview RecordN/AM2Black Box Testing: Prepare functional test planFunctional Test Plan documentN/AM2Review functional test planReview RecordN/AM2Black Box Testing: Prepare Functional Test Cases. (For a given feature.) 1) Identify test items (Usually one test item per use case) for a given use case. (2) Identify test scenarios for each of the test item. (Typically there are at least three scenarios for a given test item viz. Functional test scenario, Alternate test scenario, Exceptional test scenario. For example in some cases, there will be multiple sets of the above three test scenario categories.) (3) Identify number of test cases under each scenario depending on the corresponding test requirements.3 to 4 test cases per hr (For writing test cases )M2White Box Testing: Design of test cases1) Document which will no. of packages, classes and function to be tested with Assert candidate And I/O details3 to 4 Classes per hourM2Prepare QTP Scripts. (Black Box Test cases.)(1) Identify Workflow (2) Identify number of unique actions (one action equivalent to test case) (3) Associate actions with workflow. (4) Arrive at SLOC based on actions. 10 QTP Source Lines of Code per hour. M2Review and Update Functional Test Case documents.Update functional test case3 to 4 test case per hour M2/M3Prepare Test Data [user data creation, content data creation etc.]Pst files, nsf files, attachments of various application types, QTP scripts for user data generation 20 email or PIM data / hour 20 Admin setting / hourM3White Box Testing: implementation of test code1) JUnit source code60 Lines of JUnit Code/Day with (all asserts and comments)M3Setting up Test EnvironmentSetup Performance test environment Setup Functional test environment Setup Unit test environment Setup Integration test environmentN/AM3Execute Functional Test Cases - Manual Testing on DesktopDesktop Test Execution (Manual Testing) 5 to 6 test cases execution per hour. M3Execute Functional Test Cases - Automated Testing on DesktopDesktop Test Execution (Automated Testing) 40 to 50 test cases execution per hour. M3Execute Functional Test Cases Manual Testing on DevicesDevice Test Execution (Manual Testing) 3 to 4 test cases execution per hour M3Execute Functional Test Cases Automated Testing on DevicesDevice Test Execution (Automated Testing) Note: QTP scripting on device emulators is work in progress. Right now productivity data not available.M3Performance testing Test Reports for transaction latencies Test reports for maximum load Test report for optimal Configuration5 to 6 test cases execution per hourM3Perform V&V (Verification & Validation (Manual Desktop Testing)V&V test report 5 to 6 test cases execution per hour. M3Perform V&V (Verification & Validation (Manual Device Testing)V&V test report3 to 4 test cases execution per hour M3Perform incremental & regression testing Desktop, Manual testing.Test Summary report 5 to 6 test cases execution per hour. M3Perform incremental & regression testing Desktop, Automated testing.Test Summary report40 to 50 test cases execution per hour. M3Perform incremental & regression testing Device, Manual testing.Test Summary report3 to 4 test cases execution per hour M3Perform incremental & regression testing Device, Automated testing.Test Summary reportNote: QTP scripting on device emulators is work in progress. Right now productivity data not available.M3Log and Report Test execution results. Updated bugzilla defect entries & consolidate test reports 4-5 defects / hr [bugzilla entries / updates]M3Defect Triage involvementParticipation in defect prioritization.Productivity not applicableM4/M5None (ProjectName Test team is not involved in this phase.)N/A (ProjectName Test team is not involved in this phase.)N/A (ProjectName Test team is not involved in this phase.) Effort Estimation Once the size of each work product is estimated (as outlined in previous section), the next step is to arrive at the effort in person hours. There are two scenarios here: One scenario where we have the empirical data for the Productivity for the activities and the other where we do not have any empirical data. In the second scenario, we have to rely on Wide Band Delphi Technique for estimation. This technique for arriving at effort estimation is based on effort estimates arrived independently by three engineers and consolidating them in a effort estimate meeting chaired by a moderator. ProjectName PLM StageTest ActivitiesWork Product ItemsSize Units [A]Productivity [B]Effort in Person Hours. M0None (ProjectName Test team is not involved in this phase.)N/AN/AN/AN/AM1Understanding SRD/PRD and FS Total # of test requirements [Functional + Performance + Security + Compatibility]N/AN/AThis will be computed at the start of M1. The estimates depend on size of the SRD/PRD/FS items. The effort estimates are based on Wide Band Delphi Technique ( Effort estimates computed separately by three engineers )M1Prepare Master Test PlanTest requirements, Test Strategy, Test Environment, QA Review Plan, Resourcing & Scheduling. N/AN/AThis will be computed at the start of M1. The estimates depend on size of the SRD/PRD/FS items. The effort estimates are based on Wide Band Delphi Technique ( Effort estimates computed separately by three engineers )M1Review Master Test PlanReview RecordN/AN/AThe effort estimates are based on Wide Band Delphi Technique ( Effort estimates computed separately by three engineers )M2Black Box Testing: Prepare functional test planFunctional Test Plan documentN/AN/AThe effort estimates are based on Wide Band Delphi Technique ( Effort estimates computed separately by three engineers )M2Review functional test planReview RecordN/AN/AThe effort estimates are based on Wide Band Delphi Technique (Effort estimates computed separately by three engineers)M2Black Box Testing: Prepare Functional Test Case documents. (1) Identify test items (Usually one test item per use case) for a given use case. (2) Identify test scenarios for each of the test item. (Typically there are at least three scenarios for a given test item viz. Functional test scenario, Alternate test scenario, Exceptional test scenario. For example in some cases, there will be multiple sets of the above three test scenario categories.) (3) Identify and compute number of test cases under each scenario depending on the corresponding test requirements. Total number of test cases / tests 3 to 4 test cases / tests per hour.[A] Divided by [B] will provide the effort in person hours.M2White Box Testing: Design of test cases1) Identify the packages, classes or functions which need white box testing 2) Identify Asserts in the same. 3) Design a fixture or test suite for the same 4) Identify whether specific input/output needs for testing if yes then verify if any other framework can be utilized (e.g. Cactus Framework)Total # of Asserts per class (A1) Total # of i/o for total no. of test cases(Asserts) Per class (A2) Here A=A1+A23 to 4 Classes per hour[A] Divided by [B] will provide the effort in person hours ( Here A=A1+A2 )M2Prepare QTP Scripts. (Black Box Test cases.)(1) Identify Workflow (2) Identify number of unique actions (one action equivalent to test case) (3) Associate actions with workflow. (4) Arrive at SLOC based on actions. Total QTP Source Lines of Code10 QTP Source Lines of Code per hour. (Based on past three months empirical data)[A] Divided by [B] will provide the effort in person hours. M2Review and Update Functional Test Case documents.Update functional test caseTotal number of test cases3 to 4 tests per hour[A] Divided by [B] will provide the effort in person hoursM2/M3Prepare Test Data [user data creation, content data creation etc.]Pst files, nsf files, attachments of various application types, QTP scripts for user data generation N/AN/AThis will be computed at the start of M3. The estimates depend on size of the SRD/PRD/FS items. The effort estimates are based on Delphi Technique (Effort estimates computed separately by three engineers)M3White Box Testing: implementation of test code1) JUnit source code# of JUnit Classes60 Lines of JUnit Code/Day with (all asserts and comments)[A] Divided by [B] will provide the effort in person hoursM3Setting up Test EnvironmentSetup Performance test environment Setup Functional test environment Setup Unit test environment Setup Integration test environmentN/AN/AThe estimates depend on size of the SRD/PRD/FS items. The effort estimates are based on Delphi Technique (Effort estimates computed separately by three engineers)M3Execute Functional Test Cases - Manual Testing on DesktopDesktop Test Execution (Manual Testing) No of test cases executed per hour.5 to 6 test cases execution per hour. [A] Divided by [B] will provide the effort in person hours.M3Execute Functional Test Cases Manual Testing on DevicesDevice Test Execution (Manual Testing) No of test cases executed per hour.3 to 4 test cases execution per hour [A] Divided by [B] will provide the effort in person hours.M3Execute Functional Test Cases - Automated Testing on DesktopDesktop Test Execution (Automated Testing) No of test cases executed per hour.40 - 50 test cases execution per hour. ( Based on past three months empirical data ) [A] Divided by [B] will provide the effort in person hours.M3Execute Functional Test Cases Automated Testing on DevicesDevice Test Execution (Automated Testing) No of test cases executed per hour.Note: QTP scripting on device emulators is work in progress. Right now productivity data not available.Note: QTP scripting on device emulators is work in progress. Right now productivity data not availableM3Performance testing Test Reports for transaction latencies Delphi technique will be used5 to 6 test cases execution per hour[A] Divided by [B] will provide the effort in person hoursM3Perform V&V (Verification & Validation (Manual Desktop Testing)V&V test report No of test cases executed per hour.5 to 6 test cases execution per hour. [A] Divided by [B] will provide the effort in person hours.M3Perform V&V (Verification & Validation (Manual Device Testing)V&V test reportNo of test cases executed per hour.3 to 4 test cases execution per hour [A] Divided by [B] will provide the effort in person hours.M3Perform incremental & regression testing Desktop, Manual testing..Test Summary reportNo of test cases executed per hour. 5 to 6 test cases execution per hour. [A] Divided by [B] will provide the effort in person hours.M3Perform incremental & regression testing Desktop, Automated testing.Test Summary reportNo of test cases executed per hour.40 to 50 test cases execution per hour. [A] Divided by [B] will provide the effort in person hours.M3Perform incremental & regression testing Device, Manual testing. (Only for Maintenance cycles) Device, Manual testing.Test Summary reportNo of test cases executed per hour.3 to 4 test cases execution per hour [A] Divided by [B] will provide the effort in person hours.M3Perform incremental & regression testing (Only for Maintenance cycles) Device, Automated testing.Test Summary reportNo of test cases executed per hour. Note: QTP scripting on device emulators is work in progress. Right now productivity data not availableNote: QTP scripting on device emulators is work in progress. Right now productivity data not availableM3Log and Report Test execution results. Updated bugzilla defect entries & consolidate test reports Total # of defects updated / added in bugzilla4-5 defects / hr [bugzilla entries / updates][A] Divided by [B] will provide the effort in person hours.M3Defect Triage involvementParticipation in defect prioritization.N/AN/ATotal Effort varies depending on the number of Bugs/CRs/Enhancements. ( It also depends on the number of participants in this activity )M4/M5None (ProjectName Test team is not involved in this phase.)None (ProjectName Test team is not involved in this phase.)N/A N/AN/A Conclusion With the proposed Test Estimation framework for ProjectName-QA in place, the following improvements can be expected: The testing team will be able to arrive at a close-to accurate estimate, which will allow it to predict and manage schedules effectively. The proposed estimation framework is based on the current set of testing activities carried out as part of ProjectName testing. If the activities change [scope, number of activities, type of activities etc] in future, the estimation framework has to be suitably modified. Assumptions The estimation framework is for pure Engineering activities. Project management efforts are NOT taken into account. Appendix The ExcelSheet workbook titled ProjectName-TestEstimationWorkBook would be used to capture size, productivity, effort estimation for each ProjectName-QA activity. This workbook also captures the effort summary for all the QA activities for a given project in the second worksheet. Glossary: The following are a list of glossary of terms used. (As used in the Unifi Test Case Documents) Test Cases / Tests: This is lowest possible testing unit, denotes one unique action (with input data variations) according to ProjectName usage. Test Data: Data that is used for carrying out testing (Manual or Automated). For example, test data pertains to Email content, PIM content or Admin Settings for ProjectName One Business Server. Workflow: It is defined as a set of test items, which have corresponding QTP scripts. Each QTP script represents an automated test scenario. Revision History Section ChangedChange DescriptionRevision DateVersion NumberReviewed byApproved byInitial Initial Versiondd mmm yyyyDraft 1.0Testmanager/ProjectManagerDeliveryManager     Company Title/Name Project Name Date Version 1.0 Page  PAGE 5 of  NUMPAGES 15( Company Logo Company Title/Name Company Internal  )*+,nos|     2 8 : @ B e h i j o žwojhzUhz@nHtH hz5 hz5@ h)@hxo@nHo(tH hz@ hxo@hz@nHo(tHhznHo(tH hz9@hz59@CJ hxo59@CJ nHtHhz59@CJ nHo(tHhz9@nHo(tHhz+)*+,-FKm$If` mno|UOOOO$Ifkd$$Ifl4F $  0    4 la f4pzttt$Ifkd$$Ifl4F $ 0    4 la f4UOOOOFO $Ifgdxo$Ifkd$$Ifl4F $  0    4 la f4p zttt$Ifkd$$Ifl4F $ 0    4 la f4    UOOFO $Ifgdxo$Ifkd$$Ifl4F $  0    4 la f4p 2 A ztd$H$If^Ha$gd)$Ifkd$$Ifl4kF $ 0    4 la f4A B e i {uh $H$If^Ha$$Ifkd?$$Ifl40$  04 la f4p i j k l m n < n {yyyyttmmmmm XM$ $a$kd $$Ifl40$  04 la f4p     7 8 9 : ; < > ? O P i ȺȩȺȏсȺpȺ jhzUmHnHuh:h:6mHnHu j^hzUmHnHuh+mHnHu jhzUmHnHujhIgUmHnHuhIgmHnHu(hIg5CJOJQJaJmHnHtHuh<hIg^JmHnHujhzUhz&i j k l m n p q ~      ) óê᪙óê᪈óêwiêh<hIg^JmHnHu j hzUmHnHu jJ hzUmHnHu jhzUmHnHuhIgmHnHuh<hIg^JmHnHtHu(hIg5CJOJQJaJmHnHtHuh+mHnHujhIgUmHnHu jThzUmHnHu( / [ N O   H*$ & Fa$*$a$$a$*$a$  ^ XM$ ) * + - . / 1 2 ; < U V W Y Z [ ^ _ p q M õìᬛõìᬊÂ~tlclclchz0J0CJo(hz0J0CJhzB*CJphhzjhzU j6 hzUmHnHu j hzUmHnHuhIgmHnHuh<hIg^JmHnHu(hIg5CJOJQJaJmHnHtHuh+mHnHujhIgUmHnHu j@ hzUmHnHu" X c   CN"234ߥߘߥ߳~vvhvhl6hl60J056CJhz0J0CJhzOJQJh:h:6CJh;10J0CJhz0J0CJnHo(tHh:h:0J056CJhzhzB*CJphhzCJOJQJ hz0J0h:h:0J056CJhz0J0CJhz0J0CJo(h:h:0J056CJo("34*3 $$Ifa$$$a$  ^ *3467<=HrsuI"#% $6GHIKwɽxhzCJPJo(hzCJPJnHo(tHhzCJPJnHtHhzCJPJo(h:h:56PJ hzCJhzCJPJhzVhzV56PJhz5CJPJo(hz5CJPJnHo(tHhz5CJPJnHtHhl6hl656PJnHtH/347=rXRRR$Ifkd $$Ifl4F*Ht", 0    4 laprsv~xxxx$Ifkd $$Ifl4F*Ht",0    4 la.~xxxx$IfkdR $$Ifl4F*Ht",0    4 la"~xxx$Ifkd $$Ifl4F*Ht",0    4 la"#&V~xxx$Ifkd$$Ifl4F*Ht",0    4 la~xxx$IfkdS$$Ifl4F*Ht",0    4 la9~~xxxx$Ifkd$$Ifl4F*Ht",0    4 la H~xxxx$Ifkd$$Ifl4F*Ht",0    4 laHILwd~xxxxxxxxx$IfkdT$$Ifl4F*Ht",0    4 la  9"CNv~=>@p|}+8ATUW羯hzCJnHo(tHhzVhzV56nHo(tHhzCJPJnHtHhzCJPJhzVhzV56PJhzCJPJo(hzCJPJnHo(tHhzCJPJnHtH@:b~xxxxxxxx$Ifkd$$Ifl4F*Ht",0    4 la =~xxxx$Ifkd$$Ifl4F*Ht",0    4 la=>Ap~xxxx$IfkdU$$Ifl4F*Ht",0    4 la=Y|~xxxxxx$Ifkd$$Ifl4F*Ht",0    4 la|}~xxxxx$Ifkd$$Ifl4F*Ht",0    4 la+BT~xxxx$IfkdV$$Ifl4F*Ht",0    4 laTUX~xxxx$Ifkd$$Ifl4F*Ht",0    4 la~xxx$Ifkd$$Ifl4F*Ht",0    4 laFl~xxxxx$IfkdW$$Ifl4F*Ht",0    4 laF=>@k  ־쪦yjyhz5CJPJnHo(tHhz5CJPJnHtHhl6hl656PJnHtHhz0J0CJhzOJQJhzhzCJPJh:h:56PJhSKhSK56PJhzCJPJnHtHhzCJPJo(hzCJPJnHo(tHhzCJPJhzVhzV56PJ&+=~xxxxxx$Ifkd$$Ifl4F*Ht",0    4 la=>Ak~xxxxxx$Ifkd$$Ifl4F*Ht",0    4 la ~xxx$IfkdX$$Ifl4F*Ht",0    4 la~xxx$Ifkd$$Ifl4F*Ht",0    4 la~xxx$Ifkd$$Ifl4F*Ht",0    4 la  ~|tkidd[[[ $$Ifa$$a$  ^$ & Fa$$kdY$$Ifl4F*Ht",0    4 la P1++$Ifkd$$Ifl4      \,"@   (0      4 lap( $$Ifa$%OPVa W [ j n !!\!]!^!`!!!!!!!!!0"1"2"4"e"i"|"~""}$$$$$$Ž౽ŧŧŧŧŧŧ౽౽౽౽hzCJnHtHhzCJPJnHtHhzCJPJhzCJnHo(tHh:h:56 hzCJhzCJPJhzVhzV56PJhzCJPJnHtHBPekd4$$Ifl4      \,"@  0      4 la$If < X k keeeeeeeeee$Ifkd$$Ifl4      \,"@  0      4 la !!]!ekd$$Ifl4      \,"@  0      4 la$If]!^!a!!!!keeee$Ifkd$$Ifl4      \,"@  0      4 la!!!!!1"keeee$Ifkdp $$Ifl4      \,"@  0      4 la1"2"5"~""""$}$$keeeeeeee$Ifkd?!$$Ifl4      \,"@  0      4 la $$$$%5%c%%%%%keeeeeeeee$Ifkd"$$Ifl4      \,"@  0      4 la $$$% %K%U%e%%%%%%%%%&&&&&']'h's'~'''''''''''''Z(q(r(t(( ))$)6)G)H)x)y){)|))*4*5*7***** + + +c+d+f+g+++̱̱hzVhzV56nHo(tHhzVhzV56PJhzCJPJhzCJPJnHtHhzCJPJnHo(tHhzCJnHo(tHhzCJPJF%%%&$&l&&&&keeeeeee$Ifkd"$$Ifl4      \,"@  0      4 la&&&''0'L'h'''keeeeeeee$Ifkd#$$Ifl4      \,"@  0      4 la ''''Z(q(keeee$Ifkd{$$$Ifl4      \,"@  0      4 laq(r(u(((H)b)e)x)keeeeeee$IfkdJ%$$Ifl4      \,"@  0      4 lax)y)|)))))*4*keeeeeee$Ifkd&$$Ifl4      \,"@  0      4 la4*5*8*W*o**keeee$Ifkd&$$Ifl4      \,"@  0      4 la***** +keeee$Ifkd'$$Ifl4      \,"@  0      4 la + + +,+C+c+keeee$Ifkd($$Ifl4      \,"@  0      4 lac+d+g++++keeee$IfkdU)$$Ifl4      \,"@  0      4 la++++++b,c,,,,--- -/-X-Y------....8._.v.w.y.z.|.}.............̖y hzCJhzCJnHo(tHh:h:56PJhSKhSK56nHo(tHhSKhSK56PJhzVhzV56nHo(tHhzCJPJnHtHhzCJnHo(tHhzVhzV56PJhzCJPJhzCJPJnHo(tHhzCJPJ.++++0,d,,,keeeeee$Ifkd$*$$Ifl4      \,"@  0      4 la,,,,,-keeee$Ifkd*$$Ifl4      \,"@  0      4 la---B-Y--keeee$Ifkd+$$Ifl4      \,"@  0      4 la-----.keeee$Ifkd,$$Ifl4      \,"@  0      4 la...8.`.v.keeee$Ifkd`-$$Ifl4      \,"@  0      4 lav.w.}....keeee$Ifkd/.$$Ifl4      \,"@  0      4 la...... / /B0C0kiiid[idd  ^$a$kd.$$Ifl4      \,"@  0      4 la . / /e/p///B0C0N000000000000000011111!1;1>1?1@1ʺ}s}mc}s}XmX}mhzCJnHo(tHhzVhzV56 hzCJhzCJnHtHhzCJPJnHtHh:h:56 hzCJhzCJPJhzVhzV56PJhz5CJPJnHtHhl6hl656PJnHtH hz0J0 j hz0J0CJh:h:0J056CJhz0J0CJhznHo(tH hzo("C0Y0i0|0001kd/$$Ifl4\\ ,"<  > (04 lap( $$Ifa$00000000011ekd0$$Ifl4\\ ,"<  >04 la$If 111!1;1?1keeee$Ifkd1$$Ifl4\\ ,"<  >04 la?1@1C1[1i1m1keeee$Ifkdq2$$Ifl4\\ ,"<  >04 la@1B1[1h1i1l1m1n1p111111111111111)2,2/2@2B2C2224e4f4h4i444445555566 6S6o66666666ſſſŦſŦ׿ſſhzVhzV56nHo(tHhzVhzV56hzCJPJnHtHhzCJPJnHo(tH hzCJ hzCJhzCJPJnHtHhzCJnHtHhzCJnHo(tHhzCJPJhzVhzV56PJ7m1n1q1111kee]e1$If$Ifkd23$$Ifl4\\ ,"<  >04 la111111kee]e1$If$Ifkd3$$Ifl4\\ ,"<  >04 la111B2C22324e4keee]eee1$If$Ifkd4$$Ifl4\\ ,"<  >04 lae4f4i44455kee]]e1$If$Ifkdu5$$Ifl4\\ ,"<  >04 la555J556keeee$Ifkd66$$Ifl4\\ ,"<  >04 la66!6S6o66keeee$Ifkd6$$Ifl4\\ ,"<  >04 la6666:7V7n7keeeee$Ifkd7$$Ifl4\\ ,"<  >04 la6n7o7q7r777777777777888888*9+9-9999P:Q:S:$;%;';c;;;;;;;;< <K<L<N<O<v<<<<<<<<<< ==G=H=J=Ө͞hzB*CJphhzCJPJnHo(tHhzVhzV56PJhzCJPJnHtH hzCJhzCJPJhzCJnHo(tHhzVhzV56 hzCJhzCJnHtH>n7o7r7777kee]e1$If$Ifkdy8$$Ifl4\\ ,"<  >04 la777858W8s888keeeeeee$Ifkd:9$$Ifl4\\ ,"<  >04 la88889(9*9keeeee$Ifkd9$$Ifl4\\ ,"<  >04 la*9+9.9l99999keeeeee$Ifkd:$$Ifl4\\ ,"<  >04 la999:*:O:P:keeeee$Ifkd};$$Ifl4\\ ,"<  >04 laP:Q:T:::$;keeee$Ifkd><$$Ifl4\\ ,"<  >04 la$;%;(;=;d;;;;keeeeee$Ifkd<$$Ifl4\\ ,"<  >04 la;;;<#<I<K<keeeee$Ifkd=$$Ifl4\\ ,"<  >04 laK<L<O<<<<<keeeee$Ifkd>$$Ifl4\\ ,"<  >04 la<<< ==F=G=keeeee$IfkdB?$$Ifl4\\ ,"<  >04 laG=H=K=====keeeee$Ifkd@$$Ifl4\\ ,"<  >04 laJ=K=S=b=t==========%>&>L>M>O>P>X>g>y>>>???&>K>L>keeeee$Ifkd@$$Ifl4\\ ,"<  >04 laL>M>P>>>?keeee$IfkdA$$Ifl4\\ ,"<  >04 la???04 la?????@keeee$IfkdC$$Ifl4\\ ,"<  >04 la@ @@K@@@keeee$IfkdC$$Ifl4\\ ,"<  >04 la@@@@@@@@@@@@AA/B*C,C7CdCeCCCCCCCCCCCdDeDDDHE׾עzj`XjjhzCJPJh:h:56hzVhzV56PJnHtHhzCJPJnHtHhz5CJPJnHo(tHhz5CJPJnHtHhl6hl656PJnHtHhzCJPJnHtHhzCJPJnHo(tHhzhznHtHhznHo(tH hzCJ hzCJhzCJPJh:h:56PJ"@@@@@+C,CBCRCeCkig^YiPPP $$Ifa$$a$  ^$kdD$$Ifl4\\ ,"<  >04 la eCqCuCCCCCCCCCCCC$IfFfF $$Ifa$ CCCDDKDeDiDE??????$IfkdH$$Ifl4ֈp& #<$ 04 laiDmDHEIELEeEEE?kdI$$Ifl4ֈp& #<$ 04 la$IfHEIEKETEZEdEeEEEEEFFFFFFFSGTGVGGGG(H)H+HHHUHVH^HHHHKKKKKKKLILSLLLLLLLMM2M[?[{[$If{[|[[[[[$\%\E??????$IfkdH[$$Ifl4ֈp& #<$ 04 la%\a\b\e\\\]9]?kd5\$$Ifl4ֈp& #<$ 04 la$If[a\b\d\m\|\\\v]w]y]]]]]^^^____)`2`````````aaHaIaTaUaVaaaaϝ쉀vllhzPJnHtHhzCJOJQJhznHo(tHhzh:h:56PJnHtH!hSKhSK56PJnHo(tHhSKhSK56PJnHtH!hzVhzV56PJnHo(tHhzCJPJnHo(tHhzVhzV56PJnHtHhzCJPJhzCJPJnHtH)9]:]v]w]z]]]^?kd"]$$Ifl4ֈp& #<$ 04 la$If^^|^^^^_K_?kd^$$Ifl4ֈp& #<$ 04 la$IfK_z_____`*`?kd^$$Ifl4ֈp& #<$ 04 la$If*`.`2`````;a?kd_$$Ifl4ֈp& #<$ 04 la$If;a@aDaHaIaUa?6  ^kd`$$Ifl4ֈp& #<$ 04 la$IfUaVaaaWbXbhcicwcxcccccee e!eeeffffeggghg$-$a$-  ^$a$aaaab+bXbYbbbccgchcicxccccccd%dddeee!eeeeƺƤwl^lThz56>*CJhzCJOJQJnHtHhz5>*nHtHhz5>*nHo(tH hz5>*h:h:56CJOJQJhzCJOJQJhzOJQJhz0J0B*CJo(phhz0J0B*CJphhzhzCJOJQJ hz0J0h:h:56PJnHtHhzPJnHtHhzPJnHo(tHeeeeee ffffff#f0f9f*CJ!hl6hl656CJnHo(tHhz56>*CJo(hz0J0B*ph!h:h:56CJnHo(tHhzCJnHtHhzCJnHo(tHhznHo(tHhz56>*nHo(tH(hgjg{g|ggggggggggghh/h <<$Ifgdy <<$IfFf=c$If  ^gghhh.h0h1h2h4h5h7h8h:h;h=hOhQhUhahbhchghyhzhhhhhhhhhhhhhhhhhhh䵯xq h!z5CJ h 5CJhxohz0J@CJ j hz0Jjhz0JU*h+0JmHnHu* hz0Jjhz0JUh+h!znHtHhznHo(tHh!zhT!*jhT!*UhzhzB*CJhphhyB*CJhph*/h0h1h3h4h6h7h<:8888$kdJe$$Iflֈ8:zf!% T80%4 layty7h9h:h#v<#v #v #v>:V l4 (05<5 5 5>4p($$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4$$If!vh5<5 5 5>#v<#v #v #v>:V l405<5 5 5>4x$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l4 <05<55$ 5554p<kdJE$$Ifl4ֈp& #<$  <04 lap<$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554$$If!vh5<55$ 555#v<#v#v$ #v#v#v:V l405<55$ 5554x$$If!vh55 5T5558#v#v #vT#v#v8:V l <0%,55 5T5584ap<yty kda$$Iflֈ8:zf!% T8 <0%4 lap<yty$$If!vh55 5T5558#v#v #vT#v#v8:V l0%55 5T5584aytyb5 2 0@P`p2( 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p8XV~PJ_HmH nH sH tH @`@ NormalOJQJ_HmH sH tH R@R  Heading 1$$ & Fx@&a$5CJJJ  Heading 2$ & Fx@&a$5BB  Heading 3 @&^B*CJDD  Heading 4$ & F@&5CJFF  Heading 5$$ & F@&a$5FF  Heading 6$$ & F@&a$CJFF  Heading 7$$ & F@&a$CJDD  Heading 8$ & F@&5CJ@ @  Heading 9 $ & F@&CJDA`D Default Paragraph FontVi@V  Table Normal :V 44 la (k (No List D>@D Title$xx@&a$ 9CJKH>@> Header&d (#CJ@ @@ Footer$d "(#@CJ*@* TOC 158O28 Table_Header-DF1BF Table_Header_Bold5@.. TOC 2 ^.. TOC 3 ^.. TOC 4 X^X.. TOC 5  ^ .. TOC 6 ^.. TOC 7 ^.. TOC 8 x^x.. TOC 9 @^@0U0 Hyperlink>*B*.)@. Page NumberDC@D 4Body Text Indent ^h7h List Bullet 3) $ & F h<<^a$ htH u@Y@  Document Map!-D OJQJFV!F FollowedHyperlink >*B* phH2H  Balloon Text#CJOJQJ^JaJ4@B4  Comment Text$@jAB@ Comment Subject%5\NRbN Body Text Indent 2&$^a$6r6  Footnote Text'@&@ Footnote ReferenceH*B'B Comment ReferenceCJaJHB@H 3 Body Text*$a$CJOJPJQJaJbPb Body Text 2+$a$*5B*OJPJQJ\aJnHphftHuR^R Normal (Web),dd[$\$CJPJ^JaJVoV Default -7$8$H$!B*CJ_HaJmH phsH tH :Q: Body Text 3.CJ^JPSP Body Text Indent 3 /^CJ^J|O| "Normal + 11 pt Char,Justified CharCJOJQJ_HmH sH tH u>O> 00 BodyText1CJPJ<1< *:Body Text CharCJaJJAJ :Body Text Indent CharOJQJPK![Content_Types].xmlj0Eжr(΢Iw},-j4 wP-t#bΙ{UTU^hd}㨫)*1P' ^W0)T9<l#$yi};~@(Hu* Dנz/0ǰ $ X3aZ,D0j~3߶b~i>3\`?/[G\!-Rk.sԻ..a濭?PK!֧6 _rels/.relsj0 }Q%v/C/}(h"O = C?hv=Ʌ%[xp{۵_Pѣ<1H0ORBdJE4b$q_6LR7`0̞O,En7Lib/SeеPK!kytheme/theme/themeManager.xml M @}w7c(EbˮCAǠҟ7՛K Y, e.|,H,lxɴIsQ}#Ր ֵ+!,^$j=GW)E+& 8PK!Ptheme/theme/theme1.xmlYOo6w toc'vuر-MniP@I}úama[إ4:lЯGRX^6؊>$ !)O^rC$y@/yH*񄴽)޵߻UDb`}"qۋJחX^)I`nEp)liV[]1M<OP6r=zgbIguSebORD۫qu gZo~ٺlAplxpT0+[}`jzAV2Fi@qv֬5\|ʜ̭NleXdsjcs7f W+Ն7`g ȘJj|h(KD- dXiJ؇(x$( :;˹! I_TS 1?E??ZBΪmU/?~xY'y5g&΋/ɋ>GMGeD3Vq%'#q$8K)fw9:ĵ x}rxwr:\TZaG*y8IjbRc|XŻǿI u3KGnD1NIBs RuK>V.EL+M2#'fi ~V vl{u8zH *:(W☕ ~JTe\O*tHGHY}KNP*ݾ˦TѼ9/#A7qZ$*c?qUnwN%Oi4 =3ڗP 1Pm \\9Mؓ2aD];Yt\[x]}Wr|]g- eW )6-rCSj id DЇAΜIqbJ#x꺃 6k#ASh&ʌt(Q%p%m&]caSl=X\P1Mh9MVdDAaVB[݈fJíP|8 քAV^f Hn- "d>znNJ ة>b&2vKyϼD:,AGm\nziÙ.uχYC6OMf3or$5NHT[XF64T,ќM0E)`#5XY`פ;%1U٥m;R>QD DcpU'&LE/pm%]8firS4d 7y\`JnίI R3U~7+׸#m qBiDi*L69mY&iHE=(K&N!V.KeLDĕ{D vEꦚdeNƟe(MN9ߜR6&3(a/DUz<{ˊYȳV)9Z[4^n5!J?Q3eBoCM m<.vpIYfZY_p[=al-Y}Nc͙ŋ4vfavl'SA8|*u{-ߟ0%M07%<ҍPK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-![Content_Types].xmlPK-!֧6 +_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!Ptheme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK] `  22iw i ) $+.@16J=@HEO[aeghh5?@BCEOYais{m  A i 3r"H=|T=P ]!!1"$%&'q(x)4** +c++,--.v..C001?1m111e4566n778*99P:$;;K<<G==L>??@@eCCiDEFG,HHKLMNOPQpRSqT:U V-WaX5YYZ{[%\9]^K_*`;aUahg/h7hh6789:;<=>ADFGHIJKLMNPQRSTUVWXZ[\]^_`bcdefghjklmnopqrtuvwxyz|}~8:Ojl~*-;VYp` t%%%%%%%%%%HOQVad!ttt  ,R$HL "֩@ 0(  B S  ?H0(  " _Hlt87455581 _Hlt21849635 projectinfo _Toc90873819 _Toc90873820 _Toc86561106 _Toc88640233 _Toc90873821 _Toc86561107 _Toc88640234 _Toc90873822 _Toc85965968 _Toc87325729 _Toc87447010 _Toc86561108 _Toc88640235 _Toc90873823 _Toc88640236 _Toc90873824 _Toc90873825 _Toc85965969 _Toc87325730 _Toc87447011 _Toc90873826 _Toc85965970 _Toc87325731 _Toc87447012 _Toc90873827Hardware _Hlt6397294Baselinemetrics _Hlt7427730 _Toc90873828   &&&&&&88JYi[i[i[i[[[[[j_j_j_j_j_j_`@   ! 222 ' ' '88TYTYTYTYt[t[t[t[[[[[j_j_j_j_j_z_`>mi?m$aP`$gP`9*urn:schemas-microsoft-com:office:smarttagsplace HO|~;Om~.;ZpXcCN"  = H %Va&&&&e'p'C(N(((8 8P8[888,;7;;;XXYYYYZZ\<\\\] ^^^______`````.`0`1`1`3`3`4`4`6`7`9`:`<`=`y``````;Om~.;Zp0`1`1`3`3`4`4`6`7`9`:`<`=`y````` nnos|   28:@Beo ;Om~.;ZpXcCNc"4  4 6 = H s u   . # % & I K L >@A}UWX+>@k %Va^`a245gTZ r t u e!y!{!!"5"7"o"""" # #C#d#f#####$$$$$%%Y%%%%&&w&y&z&|&}&&&&&& 'e'p'C(N((((((((())@)B)n)p)q)))))))+*C*+d+f,h,i,,-----. .!.S.o......o/q/r/////00000+1-1.1111Q2S2T2%3'3=33334#4L4N4O444444 55H5J5K5555556&6M6O6P66677777 8 8 8888 8P8[88888,;7;;;;;;;;;<K<m<<<I=K=e=====>>>T?V?W???)@+@^@@@@A9BCCCdE|EEEEEFFWGYGZGGGGGHHHHHHHHHIIIIImJoJJKKKKKLLLMMMNNN!P#P9PPPP$Q5QQQQRRRRRRR|S~SSSSbTdTeTTTwUyUzUUUVVVWW2XXXXXXXXYY;YVYYYZZi[x[[[\%\\\] ^^^-_______```.`0`1`1`3`3`4`4`6`7`9`:`<`O`U`a`c`g`y``````````` nnos|   28:@ XcCN"  4 6 = H s u   # % I K >@}UW>@%Va^`24r t y!{!5"7""" # #d#f###$$%%%%&&w&y&z&|&&&&&e'p'C(N((((((())@)B)n)p)))))f,h,--. .....o/q///00+1-111Q2S2%3'333L4N444H5J555M6O67777 8 8 888 8P8[888,;7;;;;;;;<<I=K===>>T?V?)@+@@@CCEEWGYGHHHHHHIImJoJKKLLMMNN!P#PPPQQRR|S~SbTdTwUyUVVWWXXXXXXYYYYZZ\%\\\] ^^^______```.`0`1`1`3`3`4`4`6`7`9`:`<`O`U`a`c`g``````` ^ :'`L#z@h7S?2;TvA6;H +lGRH} 6`K𦤃8z>`( vdWy0Bh^`.h^`.hpLp^p`L.h@ @ ^@ `.h^`.hL^`L.h^`.h^`.hPLP^P`L.h 88^8`OJQJo(h ^`OJQJo(oh   ^ `OJQJo(h   ^ `OJQJo(h xx^x`OJQJo(oh HH^H`OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo(h 88^8`OJQJo(h^`.h   ^ `OJQJo(h   ^ `OJQJo(h xx^x`OJQJo(oh HH^H`OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo(h hh^h`OJQJo(h 88^8`OJQJo(oh ^`OJQJo(h   ^ `OJQJo(h   ^ `OJQJo(oh xx^x`OJQJo(h HH^H`OJQJo(h ^`OJQJo(oh ^`OJQJo( hh^h`OJQJo(^`OJQJ^Jo(.^`.h^`^`... ^` .... ^` ..... ^` ...... ^`....... ^`........h^`OJQJo(hHh^`OJQJ^Jo(hHohpp^p`OJQJo(hHh@ @ ^@ `OJQJo(hHh^`OJQJ^Jo(hHoh^`OJQJo(hHh^`OJQJo(hHh^`OJQJ^Jo(hHohPP^P`OJQJo(hH  P^`POJQJo( ^`.  pp^p`OJQJo(  @ @ ^@ `OJQJo(  ^`OJQJo(o  ^`OJQJo(  ^`OJQJo(  ^`OJQJo(o  PP^P`OJQJo(h 88^8`OJQJo(h ^`OJQJo(oh   ^ `OJQJo(h   ^ `OJQJo(h xx^x`OJQJo(oh HH^H`OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo(h ^`OJQJo(h ^`OJQJo(oh pp^p`OJQJo(h @ @ ^@ `OJQJo(h ^`OJQJo(oh ^`OJQJo(h ^`OJQJo(h ^`OJQJo(oh PP^P`OJQJo(A6;+lG@h7^8z>`'`L# v6`K?2;dWy+lG+lG+lG+lG+lG+lG+lG+lG+lG yRG)T!*+;1SKRKPzVxo!zz @:Ig+c+l61`3`@`H@Unknown G* Times New Roman5Symbol3. * ArialW&  Nokia SansArial NarrowG5  hMS Mincho-3 fg5. *aTahomaI. ??Arial Unicode MS?= * Courier New;WingdingsA BCambria Math"1h   [Q1[Q1!4d``2HX?Ig2! xx"Software Test Estimation Framework"Software Test Estimation FrameworkQATutorial.comQATutorial.com4         Oh+'0(< T`    $Software Test Estimation FrameworkQATutorial.com$Software Test Estimation Framework Normal.dotmQATutorial.com4Microsoft Office Word@F#@f+@ ߪ+@f+[Q՜.+,D՜.+,|8 px  QATutorial.comQATutorial.com1` #Software Test Estimation Framework Title@@4_AdHocReviewCycleID_EmailSubject _AuthorEmail_AuthorEmailDisplayName_ReviewingToolsShownOnce0VReviewed SPPmanjunatha.hebbar@igate.comManjunatha Hebbar  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-.012345689:;<=>CRoot Entry F}+EData 5f1TabledWordDocument5SummaryInformation(/DocumentSummaryInformation87CompObjy  F'Microsoft Office Word 97-2003 Document MSWordDocWord.Document.89q