ࡱ> _ bjbj ^bb0(0(55555D666896sJ=T EGGGqH& U[Y+s-s-s-s-s-s-s$ wyQs5?[qHqH?[?[Qs55GGfs4```?[5G5G+s`?[+s``/p8rG@^V)]Bgr,ss<srPzk^JzXrz5r4?[?[`?[?[?[?[?[QsQs`?[?[?[s?[?[?[?[z?[?[?[?[?[?[?[?[?[0( P4:  Generic Project Prepared for Project Name Prepared by Company Name Date July 17, 2001 2001, COMPANY NAME. All rights reserved. This documentation is the confidential and proprietary intellectual property of COMPANY NAME. Any unauthorized use, reproduction, preparation of derivative works, performance, or display of this document, or software represented by this document, without the express written permission of COMPANY. is strictly prohibited. COMPANY NAME and the COMPANY NAME logo design are trademarks and/or service marks of an affiliate of COMPANY NAME. All other trademarks, service marks, and trade names are owned by their respective companies. PROJECT NAME  TITLE \* MERGEFORMAT Automated Testing Detail Test Plan DOCUMENT REVISION INFORMATION The following information is to be included with all versions of the document. Project NameProject NumberPrepared byDate PreparedRevised byDate RevisedRevision ReasonRevision Control No.Revised byDate RevisedRevision Reason Revision Control No.Revised byDate RevisedRevision ReasonRevision Control No. PROJECT NAME  TITLE \* MERGEFORMAT Automated Testing Detail Test Plan DOCUMENT APPROVAL This signature page is to indicate approval from COMPANY NAME sponsor and Client sponsor for the attached  TITLE \* MERGEFORMAT PROJECT NAME Detail Test Plan for the PROJECT NAME. All parties have reviewed the attached document and agree with its contents. COMPANY NAME Project Manager: Name, Title: Project Manager, PROJECT NAMEDateCUSTOMER Project Manager: Name, Title:DateCOMPANY NAME/DEPARTMENT Sponsor: Name, Title: DateCOMPANY NAME Sponsor: Name, Title: DateCUSTOMER NAME Sponsor: Name, Title: DateCOMPANY NAME Manager: Name, Title: Date Table of Contents  TOC \o "2-9" \h \z \t "Heading 1,1"  HYPERLINK \l "_Toc328850541" 1 Introduction  PAGEREF _Toc328850541 \h 1  HYPERLINK \l "_Toc328850542" 1.1 Automated Testing DTP Overview  PAGEREF _Toc328850542 \h 1  HYPERLINK \l "_Toc328850543" 2 Test Description  PAGEREF _Toc328850543 \h 2  HYPERLINK \l "_Toc328850544" 2.1 Test Identification  PAGEREF _Toc328850544 \h 2  HYPERLINK \l "_Toc328850545" 2.2 Test Purpose and Objectives  PAGEREF _Toc328850545 \h 2  HYPERLINK \l "_Toc328850546" 2.3 Assumptions, Constraints, and Exclusions  PAGEREF _Toc328850546 \h 2  HYPERLINK \l "_Toc328850547" 2.4 Entry Criteria  PAGEREF _Toc328850547 \h 2  HYPERLINK \l "_Toc328850548" 2.5 Exit Criteria  PAGEREF _Toc328850548 \h 3  HYPERLINK \l "_Toc328850549" 2.6 Pass/Fail Criteria  PAGEREF _Toc328850549 \h 3  HYPERLINK \l "_Toc328850550" 3 Test Scope  PAGEREF _Toc328850550 \h 5  HYPERLINK \l "_Toc328850551" 3.1 Items to be tested by Automation  PAGEREF _Toc328850551 \h 5  HYPERLINK \l "_Toc328850552" 3.2 Items not to be tested by Automation  PAGEREF _Toc328850552 \h 5  HYPERLINK \l "_Toc328850553" 4 Test Approach  PAGEREF _Toc328850553 \h 6  HYPERLINK \l "_Toc328850554" 4.1 Description of Approach  PAGEREF _Toc328850554 \h 6  HYPERLINK \l "_Toc328850555" 5 Test Definition  PAGEREF _Toc328850555 \h 7  HYPERLINK \l "_Toc328850556" 5.1 Test Functionality Definition (Requirements Testing)  PAGEREF _Toc328850556 \h 7  HYPERLINK \l "_Toc328850557" 5.2 Test Case Definition (Test Design)  PAGEREF _Toc328850557 \h 7  HYPERLINK \l "_Toc328850558" 5.3 Test Data Requirements  PAGEREF _Toc328850558 \h 7  HYPERLINK \l "_Toc328850559" 5.4 Automation Recording Standards  PAGEREF _Toc328850559 \h 7  HYPERLINK \l "_Toc328850560" 5.5 Loadrunner Menu Settings  PAGEREF _Toc328850560 \h 8  HYPERLINK \l "_Toc328850561" 5.6 Loadrunner Script Naming Conventions  PAGEREF _Toc328850561 \h 8  HYPERLINK \l "_Toc328850562" 5.7 Loadrunner GUIMAP Naming Conventions  PAGEREF _Toc328850562 \h 8  HYPERLINK \l "_Toc328850563" 5.8 Loadrunner Result Naming Conventions  PAGEREF _Toc328850563 \h 9  HYPERLINK \l "_Toc328850564" 5.9 Loadrunner Report Naming Conventions  PAGEREF _Toc328850564 \h 9  HYPERLINK \l "_Toc328850565" 5.10 Loadrunner Script, Result and Report Repository  PAGEREF _Toc328850565 \h 9  HYPERLINK \l "_Toc328850566" 6 Test Preparation Specifications  PAGEREF _Toc328850566 \h 11  HYPERLINK \l "_Toc328850567" 6.1 Test Environment  PAGEREF _Toc328850567 \h 11  HYPERLINK \l "_Toc328850568" 6.2 Test Team Roles and Responsibilities  PAGEREF _Toc328850568 \h 12  HYPERLINK \l "_Toc328850569" 6.3 Test Team Training Requirements  PAGEREF _Toc328850569 \h 13  HYPERLINK \l "_Toc328850570" 6.4 Automation Test Preparation  PAGEREF _Toc328850570 \h 13  HYPERLINK \l "_Toc328850571" 7 Test Issues and Risks  PAGEREF _Toc328850571 \h 14  HYPERLINK \l "_Toc328850572" 7.1 Issues  PAGEREF _Toc328850572 \h 14  HYPERLINK \l "_Toc328850573" 7.2 Risks  PAGEREF _Toc328850573 \h 14  HYPERLINK \l "_Toc328850574" 8 Appendices  PAGEREF _Toc328850574 \h 16  HYPERLINK \l "_Toc328850575" 8.1 Traceability Matrix  PAGEREF _Toc328850575 \h 16  HYPERLINK \l "_Toc328850576" 8.2 Definitions for Use in Testing  PAGEREF _Toc328850576 \h 18  HYPERLINK \l "_Toc328850577" 8.2.1 Test Requirement  PAGEREF _Toc328850577 \h 18  HYPERLINK \l "_Toc328850578" 8.2.2 Test Case  PAGEREF _Toc328850578 \h 18  HYPERLINK \l "_Toc328850579" 8.2.3 Test Procedure  PAGEREF _Toc328850579 \h 18  HYPERLINK \l "_Toc328850580" 8.3 Automated Test Cases  PAGEREF _Toc328850580 \h 19  HYPERLINK \l "_Toc328850581" 8.3.1 NAME OF FUNCTION Test Case  PAGEREF _Toc328850581 \h 19  HYPERLINK \l "_Toc328850582" 9 Project Glossary  PAGEREF _Toc328850582 \h 21  HYPERLINK \l "_Toc328850583" 9.1 Glossary Reference  PAGEREF _Toc328850583 \h 21  HYPERLINK \l "_Toc328850584" 9.2 Sample Addresses for Testing  PAGEREF _Toc328850584 \h 22  HYPERLINK \l "_Toc328850585" 9.3 Test Equipment Example Credit card numbers  PAGEREF _Toc328850585 \h 23  1 Introduction  STYLEREF \l"Chapter Head" \* MERGEFORMAT Introduction Automated Testing DTP Overview This Automated Testing Detail Test Plan (ADTP) will identify the specific tests that are to be performed to ensure the quality of the delivered product. System/Integration Test ensures the product functions as designed and all parts work together. This ADTP will cover information for Automated testing during the System/Integration Phase of the project and will map to the specification or requirements documentation for the project. This mapping is done in conjunction with the Traceability Matrix document, that should be completed along with the ADTP and is referenced in this document. This ADTP refers to the specific portion of the product known as PRODUCT NAME. It provides clear entry and exit criteria, and roles and responsibilities of the Automated Test Team are identified such that they can execute the test. The objectives of this ADTP are: Describe the test to be executed. Identify and assign a unique number for each specific test. Describe the scope of the testing. List what is and is not to be tested. Describe the test approach detailing methods, techniques, and tools. Outline the Test Design including: Functionality to be tested. Test Case Definition. Test Data Requirements. Identify all specifications for preparation. Identify issues and risks. Identify actual test cases. Document the design point or requirement tested for each test case as it is developed. 2 Test Description  STYLEREF \l"Chapter Head" \* MERGEFORMAT Test Description Test Identification This ADTP is intended to provide information for System/Integration Testing for the PRODUCT NAME module of the PROJECT NAME. The test effort may be referred to by its PROJECT REQUEST (PR) number and its project title for tracking and monitoring of the testing progress. Test Purpose and Objectives Automated testing during the System/Integration Phase as referenced in this document is intended to ensure that the product functions as designed directly from customer requirements. The testing goal is to identify the quality of the structure, content, accuracy and consistency, some response times and latency, and performance of the application as defined in the project documentation. Assumptions, Constraints, and Exclusions Factors which may affect the automated testing effort, and may increase the risk associated with the success of the test include: Completion of development of front-end processes Completion of design and construction of new processes Completion of modifications to the local database Movement or implementation of the solution to the appropriate testing or production environment Stability of the testing or production environment Load Discipline Maintaining recording standards and automated processes for the project Completion of manual testing through all applicable paths to ensure that reusable automated scripts are valid Entry Criteria The ADTP is complete, excluding actual test results. The ADTP has been signed-off by appropriate sponsor representatives indicating consent of the plan for testing. The Problem Tracking and Reporting tool is ready for use. The Change Management and Configuration Management rules are in place. The environment for testing, including databases, application programs, and connectivity has been defined, constructed, and verified. Exit Criteria In establishing the exit/acceptance criteria for the Automated Testing during the System/Integration Phase of the test, the Project Completion Criteria defined in the Project Definition Document (PDD) should provide a starting point. All automated test cases have been executed as documented. The percent of successfully executed test cases met the defined criteria. Recommended criteria: No Critical or High severity problem logs remain open and all Medium problem logs have agreed upon action plans; successful execution of the application to validate accuracy of data, interfaces, and connectivity. Pass/Fail Criteria The results for each test must be compared to the pre-defined expected test results, as documented in the ADTP (and DTP where applicable). The actual results are logged in the Test Case detail within the Detail Test Plan if those results differ from the expected results. If the actual results match the expected results, the Test Case can be marked as a passed item, without logging the duplicated results. A test case passes if it produces the expected results as documented in the ADTP or Detail Test Plan (manual test plan). A test case fails if the actual results produced by its execution do not match the expected results. The source of failure may be the application under test, the test case, the expected results, or the data in the test environment. Test case failures must be logged regardless of the source of the failure. Any bugs or problems will be logged in the DEFECT TRACKING TOOL. The responsible application resource corrects the problem and tests the repair. Once this is complete, the tester who generated the problem log is notified, and the item is re-tested. If the retest is successful, the status is updated and the problem log is closed. If the retest is unsuccessful, or if another problem has been identified, the problem log status is updated and the problem description is updated with the new findings. It is then returned to the responsible application personnel for correction and test. Severity Codes are used to prioritize work in the test phase. They are assigned by the test group and are not modifiable by any other group. The following standard Severity Codes to be used for identifying defects are: Table  SEQ Table \* ARABIC 1 Severity Codes Severity Code NumberSeverity Code Name Description1CriticalAutomated tests cannot proceed further within applicable test case (no work around)2HighThe test case or procedure can be completed, but produces incorrect output when valid information is input.3MediumThe test case or procedure can be completed and produces correct output when valid information is input, but produces incorrect output when invalid information is input. (e.g. no special characters are allowed as part of specifications but when a special character is a part of the test and the system allows a user to continue, this is a medium severity)4LowAll test cases and procedures passed as written, but there could be minor revisions, cosmetic changes, etc. These defects do not impact functional execution of system The use of the standard Severity Codes produces four major benefits: Standard Severity Codes are objective and can be easily and accurately assigned by those executing the test. Time spent in discussion about the appropriate priority of a problem is minimized. Standard Severity Code definitions allow an independent assessment of the risk to the on-schedule delivery of a product that functions as documented in the requirements and design documents. Use of the standard Severity Codes works to ensure consistency in the requirements, design, and test documentation with an appropriate level of detail throughout. Use of the standard Severity Codes promote effective escalation procedures. 3 Test Scope  STYLEREF \l"Chapter Head" \* MERGEFORMAT Test Scope The scope of testing identifies the items which will be tested and the items which will not be tested within the System/Integration Phase of testing. Items to be tested by Automation PRODUCT NAME PRODUCT NAME PRODUCT NAME PRODUCT NAME PRODUCT NAME Items not to be tested by Automation PRODUCT NAME PRODUCT NAME 4 Test Approach  STYLEREF \l"Chapter Head" \* MERGEFORMAT Test Approach Description of Approach The mission of Automated Testing is the process of identifying recordable test cases through all appropriate paths of a website, creating repeatable scripts, interpreting test results, and reporting to project management. For the Generic Project, the automation test team will focus on positive testing and will complement the manual testing undergone on the system. Automated test results will be generated, formatted into reports and provided on a consistent basis to Generic project management. System testing is the process of testing an integrated hardware and software system to verify that the system meets its specified requirements. It verifies proper execution of the entire set of application components including interfaces to other applications. Project teams of developers and test analysts are responsible for ensuring that this level of testing is performed. Integration testing is conducted to determine whether or not all components of the system are working together properly. This testing focuses on how well all parts of the web site hold together, whether inside and outside the website are working, and whether all parts of the website are connected. Project teams of developers and test analyst are responsible for ensuring that this level of testing is performed. For this project, the System and Integration ADTP and Detail Test Plan complement each other. Since the goal of the System and Integration phase testing is to identify the quality of the structure, content, accuracy and consistency, response time and latency, and performance of the application, test cases are included which focus on determining how well this quality goal is accomplished. Content testing focuses on whether the content of the pages match what is supposed to be there, whether key phrases exist continually in changeable pages, and whether the pages maintain quality content from version to version. Accuracy and consistency testing focuses on whether todays copies of the pages download the same as yesterdays, and whether the data presented to the user is accurate enough. Response time and latency testing focuses on whether the web site server responds to a browser request within certain performance parameters, whether response time after a SUBMIT is acceptable, or whether parts of a site are so slow that the user discontinues working. Although Loadrunner provides the full measure of this test, there will be various AD HOC time measurements within certain Loadrunner Scripts as needed. Performance testing (Loadrunner) focuses on whether performance varies by time of day or by load and usage, and whether performance is adequate for the application. Completion of automated test cases is denoted in the test cases with indication of pass/fail and follow-up action. 5 Test Definition  STYLEREF \l"Chapter Head" \* MERGEFORMAT Test Definition This section addresses the development of the components required for the specific test. Included are identification of the functionality to be tested by automation, the associated automated test cases and scenarios. The development of the test components parallels, with a slight lag, the development of the associated product components. Test Functionality Definition (Requirements Testing) The functionality to be automated tested is listed in the Traceability Matrix, attached as an appendix. For each function to undergo testing by automation, the Test Case is identified. Automated Test Cases are given unique identifiers to enable cross-referencing between related test documentation, and to facilitate tracking and monitoring the test progress. As much information as is available is entered into the Traceability Matrix in order to complete the scope of automation during the System/Integration Phase of the test. Test Case Definition (Test Design) Each Automated Test Case is designed to validate the associated functionality of a stated requirement. Automated Test Cases include unambiguous input and output specifications. This information is documented within the Automated Test Cases in Appendix 8.5 of this doc. Test Data Requirements The automated test data required for the test is described below. The test data will be used to populate the data bases and/or files used by the application/system during the System/Integration Phase of the test. Automation Recording Standards Initial Automation Testing Rules for the Generic Project: Ability to move through all paths within the applicable system Ability to identify and record the GUI Maps for all associated test items in each path Specific times for loading into automation test environment Code frozen between loads into automation test environment Minimum acceptable system stability Loadrunner Menu Settings Default recording mode is CONTEXT SENSITIVE Record owner-drawn buttons as OBJECT Maximum length of list item to record is 253 characters Delay for Window Synchronization is 1000 milliseconds (unless Loadrunner is operating in same environment and then must increase appropriately) Timeout for checkpoints and CS statements is 1000 milliseconds Timeout for Text Recognition is 500 milliseconds All scripts will stop and start on the main menu page All recorded scripts will remain short; Debugging is easier. However, the entire script, or portions of scripts, can be added together for long runs once the environment has greater stability. Loadrunner Script Naming Conventions All automated scripts will begin with GE abbreviation representing the Generic Project and be filed under the Loadrunner on LAB W Drive/Generic/Scripts Folder. GE will be followed by the Product Path name in lower case: air, htl, car After the automated scripts have been debugged, a date for the script will be attached: 0710 for July 10. When significant improvements have been made to the same script, the date will be changed. As incremental improvements have been made to an automated script, version numbers will be attached signifying the script with the latest improvements: eg. GEsea0710.1 GEsea0710.2 The .2 version is the most up-to-date Loadrunner GUIMAP Naming Conventions All Generic GUI Maps will begin with GE followed by the area of test. Eg. GEsea. GEpond GUI Map represents all pond paths. GEmemmainmenu GUI Map represents all membership and main menu concerns. GElogin GUI Map represents all GE login concerns. As there can only be one GUI Map for each Object, etc on the site, they are under constant revision when the site is undergoing frequent program loads. Loadrunner Result Naming Conventions When beginning a script, allow default res## name to be filed After a successful run of a script where the results will be used toward a report, move file to results and rename: GE for project name, res for Test Results, 0718 for the date the script was run, your initials and the original default number for the script. Eg. GEres0718jr.1 Loadrunner Report Naming Conventions 1. When the accumulation of test result(s) files for the day are formulated, and the statistics are confirmed, a report will be filed that is accessible by upper management. The daily Report file will be as follows: GEdaily0718 GE for project name, daily for daily report, and 0718 for the date the report was issued. 2. When the accumulation of test result(s) files for the week are formulated, and the statistics are confirmed, a report will be filed that is accessible by upper management. The weekly Report file will be as follows: GEweek0718 GE for project name, week for weekly report, and 0718 for the date the report was issued. Loadrunner Script, Result and Report Repository LAB 11, located within the GE Test Lab, will house the original Loadrunner Script, Results and Report Repository for automated testing within the Generic Project. WRITE access is granted Loadrunner Technicians and READ ONLY access is granted those who are authorized to run scripts but not make any improvements. This is meant to maintain the purity of each script version. Loadrunner on LAB W Drive houses all Loadrunner related documents, etc for GE automated testing. Project file folders for the Generic Project represent the initial structure of project folders utilizing automated testing. As our automation becomes more advanced, the structure will spread to other appropriate areas. Under each Project file folder, a folder for SCRIPT, RESULT and REPORT can be found. All automated scripts generated for each project will be filed under Loadrunner on LAB W Drive/Generic/Scripts Folder and moved to folder ARCHIVE SCRIPTS as necessary All GUI MAPS generated will be filed under Loadrunner on LAB W Drive/Generic/Scripts/gui_files Folder. All automated test results are filed under the individual Script Folder after each script run. Results will be referred to and reports generated utilizing applicable statistics. Automated Test Results referenced by reports sent to management will be kept under the Loadrunner on LAB W Drive/Generic/Results Folder. Before work on evaluating a new set of test results is begun, all prior results are placed into Loadrunner on LAB W Drive/Generic/Results/Archived Results Folder. This will ensure all reported statistics are available for closer scrutiny when required. All reports generated from automated scripts and sent to upper management will be filed under Loadrunner on LAB W Drive/Generic/Reports Folder 6 Test Preparation Specifications  STYLEREF \l"Chapter Head" \* MERGEFORMAT Test Preparation Specifications Test Environment Table 2 Environment for Automated Test Automated Test environment is indicated below. Existing dependencies are entered in comments. EnvironmentTest SystemCommentsTest System/Integration Test (SIT)CertAccess via http://xxxxx/xxxxx ProductionProductionAccess via http:// www.xxxxxx.xxxOther (specify)DevelopmentIndividual Test Environments Table 3 Hardware for Automated Test The following is a list of the hardware needed to create production like environment: ManufacturerDevice TypeVariousPersonal Computer (486 or Higher) with monitor & required peripherals; with connectivity to internet test/production environments. Must be enabled to ADDITIONAL REQUIREMENTS. Table 4 Software The following is a list of the software needed to create a production like environment: SoftwareVersion (if applicable)Programmer SupportFirefoxZZZ or higherInternet ExplorerZZZ or higher Test Team Roles and Responsibilities Table 5 Test Team Roles and Responsibilities RoleResponsibilitiesNameCOMPANY NAME SponsorApprove project development, handle major issues related to project development, and approve development resourcesName, PhoneAbacus Sponsor Signature approval of the project, handle major issuesName, Phone Abacus Project ManagerEnsures all aspects of the project are being addressed from CUSTOMERS point of viewName, Phone COMPANY NAME Development ManagerManage the overall development of project, including obtaining resources, handling major issues, approving technical design and overall timeline, delivering the overall product according to the Partner RequirementsName, PhoneCOMPANY NAME Project Manager Provide PDD (Project Definition Document), project plan, status reports, track project development status, manage changes and issuesName, PhoneCOMPANY NAME Technical Lead Provide Technical guidance to the Development Team and ensure that overall Development is proceeding in the best technical directionName, PhoneCOMPANY NAME Back End Services Manager Develop and deliver the necessary Business Services to support the PROJECT NAME Name, PhoneCOMPANY NAME Infrastructure Manager Provide PROJECT NAME development certification, production infrastructure, service level agreement, and testing resources Name, PhoneCOMPANY NAME Test Coordinator Develops ADTP and Detail Test Plans, tests changes, logs incidents identified during testing, coordinates testing effort of test team for projectName, PhoneCOMPANY NAME Tracker Coordinator/ TesterTracks SCRs in DEFECT TRACKING TOOL. Reviews new SCRs for duplicates, completeness and assigns to Module Tech Leads for fix. Produces status documents as needed. Tests changes, logs incidents identified during testing. Name, PhoneCOMPANY NAME Automation EnginneerTests changes, logs incidents identified during testing.Name, Phone Test Team Training Requirements Table 6 Automation Training Requirements Training Requirement Training ApproachTarget Date for CompletionRoles/Resources to be Trained Automation Test Preparation Write and receive approval of the ADTP from Generic Project management Manually test the cases in the plan to make sure they actually work before recording repeatable scripts Record appropriate scripts and file them according to the naming conventions described within this document Initial order of automated script runs will be to load GUI Maps through a STARTUP script. After the successful run of this script, scripts testing all paths will be kicked off. Once an appropriate number of PNRs are generated, Generic Cancel scripts will be used to automatically take the inventory out of the test profile and system environment. During the automation test period, requests for testing of certain functions can be accommodated as necessary as long as these functions have the ability to be tested by automation. The ability to use Generic Automation will be READ ONLY for anyone outside of the test group. Of course, this is required to maintain the pristine condition of master scripts on our data repository. Generic Test Group will conduct automated tests under the rules specified in our agreement for use of the Loadrunner tool marketed by HP. Results filed for each run will be analyzed as necessary, reports generated, and provided to upper management. 7 Test Issues and Risks  STYLEREF \l"Chapter Head" \* MERGEFORMAT Test Issues and Risks Issues The table below lists known project testing issues to date. Upon sign-off of the Detail Test Plan, this table will not be maintained, and these issues and all new issues will be tracked through the Issue Management System, as indicated in the projects approved Issue Management Process. Table 7 Issues Issue ImpactTarget Date for Resolution OwnerCOMPANY NAME test team is not in possession of market data regarding what browsers are most in use in CUSTOMER target market.Testing may not cover some browsers used by CLIENT customersBeginning of Automated Testing during System and Integration Test Phase CUSTOMER TO PROVIDEOTHER Risks The table below identifies any high impact or highly probable risks that may impact the success of the Automated testing process. Table 8 Risk Assessment Matrix Risk AreaPotential ImpactLikelihood of OccurrenceDifficulty of Timely DetectionOverall Threat (H, M, L)1. Unstable EnvironmentDelayed Start HISTORY OF PROJECT ImmediatelyDEPENDENT ON LIKELIHOOD2. Quality of Unit TestingGreater delays taken by automated scriptsDependent upon quality standards of development groupImmediately3. Browser IssuesIntermittent DelaysDependent upon browser versionImmediately Table 9 Risk Management Plan Risk AreaPreventative ActionContingency Plan ActionTriggerOwner1. Meet with Environment Group2. Meet with Development Group3.  8 Appendices  STYLEREF \l"Chapter Head" \* MERGEFORMAT Appendices Traceability Matrix The purpose of the Traceability Matrix is to identify all business requirements and to trace each requirement through the project's completion. Each business requirement must have an established priority as outlined in the Business Requirements Document. They are: Essential - Must satisfy the requirement to be accepted by the customer. Useful - Value -added requirement influencing the customer's decision. Nice-to-have - Cosmetic non-essential condition, makes product more appealing. The Traceability Matrix will change and evolve throughout the entire project life cycle. The requirement definitions, priority, functional requirements, and automated test cases are subject to change and new requirements can be added. However, if new requirements are added or existing requirements are modified after the Business Requirements document and this document have been approved, the changes will be subject to the change management process. The Traceability Matrix for this project will be developed and maintained by the test coordinator. At the completion of the matrix definition and the project, a copy will be added to the project notebook. Functional Areas of Traceability Matrix #Functional AreaPriorityB1PondEB2RiverEB3LakeUB4SeaEB5OceanEB6Misc UB7ModifyELegend:L1LanguageEEE1End-to-End TestingEEB = Order EngineL = LanguageN = Nice to haveEE = End-to-EndE = EssentialU = Useful Definitions for Use in Testing Test Requirement A scenario is a prose statement of requirements for the test. Just as there are high level and detailed requirements in application development, there is a need to provide detailed requirements in the test development area. Test Case A test case is a transaction or list of transactions that will satisfy the requirements statement in a test scenario. The test case must contain the actual entries to be executed as well as the expected results, i.e., what a user entering the commands would see as a system response. Test Procedure Test procedures define the activities necessary to execute a test case or set of cases. Test procedures may contain information regarding the loading of data and executables into the test system, directions regarding sign in procedures, instructions regarding the handling of test results, and anything else required to successfully conduct the test. Automated Test Cases NAME OF FUNCTION Test Case Project Name/NumberGeneric Project / Project Request #DateTest Case Description Check all drop down boxes, fill in boxes and pop-up windows operate according to requirements on the main Pond web page.Build #Run #Function / Module Under TestB1.1 Execution Retry #Test Requirement #Case #AB1.1.1 (A for Automated)Written byGoalsVerify that Pond module functions as requiredSetup for TestAccess browser, Go to ..Pre-conditionsLogin with name and password. When arrive at Generic Main Menu..StepActionExpected ResultsPass / FailActual Results if Step Fails1.Go to Pond and ..From the Generic Main Menu, click on the Pond gif and go to Pond web page. Once on the Pond web page, check all drop down boxes for appropriate information (eg Time.7a, 8a in 1 hour increments), fill in boxes (remarks allows alpha and numeric but no other special characters), and pop up windows (eg. Privacy. Ensure it is retrieved, has correct verbage and closes).  9 Project Glossary  STYLEREF \l"Chapter Head" \* MERGEFORMAT Project Glossary Glossary Reference TermDefinitionPertains to:CATCustomer Acceptance TestingCRChange RequestDOCDocument Only ChangeProblem LogADTPAutomated Detail Test PlanDTPDetail Test PlanDUPDuplicateProblem LogFIXFix incident resolved/repairedProblem LogMTPMaster Test PlanPDDProject Definition DocumentPMOProject Management OfficePRProject RequestSITSystem/Integration TestSMESubject Matter ExpertUTRDeveloper unable to recreateProblem LogWADWorking As DesignedProblem Log Sample Addresses for Testing United States International Test Equipment Example Credit card numbers American Express (AX) Visa (BA) Diners Club (DC) Discover Card (DS) MasterCard (IK)      STYLEREF \l"Chapter Head" \* MERGEFORMAT Introduction  PAGE 15  PAGE iv SUBJECT \* MERGEFORMAT Abacus Web Reservations  TITLE \* MERGEFORMAT Abacus Detail Test Plan SAVEDATE \@ "MMMM d, yyyy" \* MERGEFORMAT June 30, 2012 Sabre Inc. Confidential/All Rights Reserved  PAGE iv  PAGE vi SUBJECT \* MERGEFORMAT Abacus Web Reservations  TITLE \* MERGEFORMAT Abacus Detail Test Plan SAVEDATE \@ "MMMM d, yyyy" \* MERGEFORMAT June 30, 2012 Sabre Inc. Confidential/All Rights Reserved  STYLEREF \l"Contents Title" Table of Contents  PAGE vi A- PAGE 15 STYLEREF \l"Heading 1" Introduction Technical Reference Guide Template Writer Guide10/20/99Revision:  FILENAME \* MERGEFORMAT automated_test_dtp.doc Sabre Inc. Confidential/All Rights Reserved  STYLEREF \l"Heading 1" Introduction  PAGE 1  PAGE 4 SUBJECT \* MERGEFORMAT Abacus Web Reservations  TITLE \* MERGEFORMAT Abacus Detail Test Plan SAVEDATE \@ "MMMM d, yyyy" \* MERGEFORMAT June 30, 2012 Sabre Inc. Confidential/All Rights Reserved  STYLEREF \l"Heading 2" Pass/Fail Criteria  PAGE 4  PAGE 6 SUBJECT \* MERGEFORMAT Abacus Web Reservations  TITLE \* MERGEFORMAT Abacus Detail Test Plan SAVEDATE \@ "MMMM d, yyyy" \* MERGEFORMAT June 30, 2012 Sabre Inc. Confidential/All Rights Reserved  STYLEREF \l"Heading 1" Test Scope  PAGE 5  PAGE 16 SUBJECT \* MERGEFORMAT Abacus Web Reservations  TITLE \* MERGEFORMAT Abacus Detail Test Plan SAVEDATE \@ "MMMM d, yyyy" \* MERGEFORMAT June 30, 2012 COMPANY NAME Confidential/All Rights Reserved  STYLEREF \l"Heading 1" Test Preparation Specifications  PAGE 13   m z { |      ( * + @ A H S T U b c d t u v ʼh-CJ0EHh-B*CJphh-B*CJOJQJph h-EHh-@$EH h-EHjh-EHUhYL h-CJh-h-CJOJQJC      B$Ifgd-^gd--:GS`est gd-:kd$$Ifl4\1%%4 laf4yt- @$Ifgd-\dL$&dIfP]\gd- A$Ifgd- B$Ifgd-  m z { | -d`@$Ifgd-d`@$Ifgd- Hdgd- Jd@&gd-gd-G|d@&]|gd-F$@&gd- p`pp`-d`@$Ifgd-d`@$Ifgd-kdW$$IfTrL(#Layt-T pppppd`6($Ifgd-kd$$IfTrL(#Layt-T p`pp`-d`@$Ifgd-d`@$Ifgd-kd$$IfTrL(#Layt-T p`pp`-d`@$Ifgd-d`@$Ifgd-kd$$IfTrL(#Layt-T pppppd`6($Ifgd-kd$$IfTrL(#Layt-T     p`pp`-d`@$Ifgd-d`@$Ifgd-kd.$$IfTrL(#Layt-T  ( ) * + @ A p``pp`-d`@$Ifgd-d`@$Ifgd-kd$$IfTrL(#Layt-TA B C D E F G pppppd`6($Ifgd-kd@$$IfTrL(#Layt-TG H S T U b c p`pp`-d`@$Ifgd-d`@$Ifgd-kd$$IfTrL(#Layt-Tc d t u v p`pp`-d`@$Ifgd-d`@$Ifgd-kdR$$IfTrL(#Layt-T {bPF= Jd@&gd- $$gd-G$$|d@&]|gd-$$$$|d@&]|a$gd-gd-kd$$IfTrL(#Layt-T  ( U V m n z QZ _h     뻵v)h9`^hp @B*CJOJQJaJphjh5lhp 0J^Uhp h5lhp 0J^jh5lhp 0J^U h-0J;jh-0J;Uh-B*CJOJQJphjh-EHU h-EHh-@$EHh- h-EHjh-EHU. QRWfDd$&dIfPgd-\kdH$$Ifl#$04 layt-Dd8$&dIfPgd- Hdgd-WXYZ5\kd<$$Ifl#$04 layt-Dd$Ifgd-\kd$$Ifl#$04 layt-ZpDd$&dIfPgd-\kd$$Ifl#$04 layt-Dd8$&dIfPgd-5\kd$$Ifl#$04 layt-Dd$Ifgd-\kd0$$Ifl#$04 layt-pDd$&dIfPgd-\kd$ $$Ifl#$04 layt-Dd8$&dIfPgd-5\kd $$Ifl#$04 layt-Dd$Ifgd-\kd $$Ifl#$04 layt-pDd$&dIfPgd-\kd $$Ifl#$04 layt-Dd8$&dIfPgd- 5\kd $$Ifl#$04 layt-Dd$Ifgd-\kd $$Ifl#$04 layt- _`epDd$&dIfPgd-\kd $$Ifl#$04 layt-Dd8$&dIfPgd-efgh5\kd $$Ifl#$04 layt-Dd$Ifgd-\kdz $$Ifl#$04 layt-hpDd$&dIfPgd-\kdn $$Ifl#$04 layt-Dd8$&dIfPgd-5) Ddgd-\kd~$$Ifl#$04 layt-Dd$Ifgd-\kd $$Ifl#$04 layt-<P!v#rDH,M#5,9$@&gd-Fdgd- Ddgd-6789:;<=>Z[\]ָָֆָvָijwhp Ujh5lhp 0J^U h9`^hp CJEHOJQJaJj}hp Ujh5lhp 0J^Uhp h5lhp 0J^)h9`^hp @B*CJOJQJaJphjh5lhp 0J^Ujhp Ujhp U hp )./0JKLMNOPQRnopqԻԃԻvfjh5lhp 0J^Ujkhp Ujh5lhp 0J^U h9`^hp CJEHOJQJaJjqhp Ujhp U hp jh5lhp 0J^Uhp h5lhp 0J^)h9`^hp @B*CJOJQJaJphjh5lhp 0J^U( !"#?@ABTUVpqrstuvwxνννjYhp Ujh5lhp 0J^Uj_hp Ujh5lhp 0J^Uhp h9`^hp CJEHOJQJaJjh5lhp 0J^Ujehp Ujhp U hp h5lhp 0J^. !"#$%ABCDEFPQRlmnopqrstԽ٨٘كv٨fjh5lhp 0J^UjMhp U)h9`^hp @B*CJOJQJaJphjh5lhp 0J^Uhp h9`^hp CJEHOJQJaJjShp Ujhp U hp h5lhp 0J^jh5lhp 0J^Ujh5lhp 0J^U("#$>?@ABCDEFbcdefgtuv׽׽׽׽wjwj;hp U)h9`^hp @B*CJOJQJaJphjh5lhp 0J^UjAhp Ujh5lhp 0J^Uhp h5lhp 0J^ h9`^hp CJEHOJQJaJjh5lhp 0J^U hp jhp UjGhp U)&'(BCDEFGHIJfghiѺ֩wքgjh5lhp 0J^Uj/hp U)h9`^hp @B*CJOJQJaJphjh5lhp 0J^U h9`^hp CJEHOJQJaJj5hp Ujhp U hp jh5lhp 0J^Ujh5lhp 0J^Uhp h5lhp 0J^(   &'()*+,-.JKLMghiּּּּ~ּj hp Ujh5lhp 0J^Uj#hp Ujh5lhp 0J^Uhp h5lhp 0J^ h9`^hp CJEHOJQJaJjh5lhp 0J^Uj)hp Ujhp U hp -  +,-GHIJKLMNOklmnԽ٨٘ԋ٨{nj #hp Uj"h5lhp 0J^Uj"hp Uj!h5lhp 0J^Uhp h9`^hp CJEHOJQJaJj!hp Ujhp U hp h5lhp 0J^jh5lhp 0J^Uj h5lhp 0J^U+ !"#$%ABCDlmnٙ|j|%h5lhp 0J^Uj$hp Uj$h5lhp 0J^Uj$hp Ujhp U hp j#h5lhp 0J^Uhp h5lhp 0J^jh5lhp 0J^U h9`^hp CJEHOJQJaJ+NOPjklmnopqr׽׽׽׽wjwj'hp U)h9`^hp @B*CJOJQJaJphjp'h5lhp 0J^Uj&hp Ujv&h5lhp 0J^Uhp h5lhp 0J^ h9`^hp CJEHOJQJaJjh5lhp 0J^U hp jhp Uj%hp U)p-c Yjo/C $$$gd-gd-6,5   &'(*+,-./KLMNvwxѺ֩ь֩|oj*hp Uj^*h5lhp 0J^Uj)hp Ujd)h5lhp 0J^U h9`^hp CJEHOJQJaJj(hp Ujhp U hp jh5lhp 0J^Ujj(h5lhp 0J^Uhp h5lhp 0J^+ !@AB\]^`abcdeɵɘɃvj,hp U)h9`^hp @B*CJOJQJaJphjR,h5lhp 0J^Uj+hp UjX+h5lhp 0J^Uhp h5lhp 0J^ h9`^hp CJEHOJQJaJjh5lhp 0J^Ujhp U hp *     *+,-678RSTVWXYZ[wxyz{|Խ٨٘ԋ٨{f)h9`^hp @B*CJOJQJaJphj@/h5lhp 0J^Uj.hp UjF.h5lhp 0J^Uhp h9`^hp CJEHOJQJaJj-hp Ujhp U hp h5lhp 0J^jh5lhp 0J^UjL-h5lhp 0J^U("#$%GHIcdeghijkl׹׹ׇ׹w׹jׇ׹j1hp Uj41h5lhp 0J^U h9`^hp CJEHOJQJaJj0hp Uj:0h5lhp 0J^Uhp h5lhp 0J^)h9`^hp @B*CJOJQJaJphjh5lhp 0J^U hp jhp Uj/hp U)5678LMNhijlmվڭՌڭ|oj4hp Uj"4h5lhp 0J^Uj3hp Uj(3h5lhp 0J^Uhp h9`^hp CJEHOJQJaJj2hp Ujhp U hp jh5lhp 0J^Uj.2h5lhp 0J^Uh5lhp 0J^+mnopq  ()*,-./01MNOPQؿؘؿ{j7h5lhp 0J^Uj6hp Uj6h5lhp 0J^Uj5hp Ujhp U hp j5h5lhp 0J^Uhp h5lhp 0J^ h9`^hp CJEHOJQJaJjh5lhp 0J^U)QRbcd~ ! " < = > @ A ҸᤸܗҸvij9hp Uj9h5lhp 0J^U h9`^hp CJEHOJQJaJj8hp Uj 8h5lhp 0J^Uhp jh5lhp 0J^Uj7hp Ujhp U hp h5lhp 0J^)h9`^hp @B*CJOJQJaJph)A B C D E a b c d !!&&&&&&&&&& 667ؿᗓ|tthh-B*OJQJphh-B*ph h-EHh-mHnHujh-Uh- jh-0J;B*EHUphj{:hp Ujhp U hp j9h5lhp 0J^Uhp h5lhp 0J^ h9`^hp CJEHOJQJaJjh5lhp 0J^U& !!!r#[$|$$$$$%i%%%%%&&;&&&& $$$gd- $dgd-gd-gd-gd-gd-Mgd-$Ml&#$+D.X/gd-&&&&(#())T****O++++H,W,,-...s0t0gd-gd-gd-Mgd-$Ml&#$+D.X/gd-t0u00"23456 66*7?7R7_7 !$Ifgd-<@&gd-Kgd-gd-gd- 777777_7`777384899P:Q: = ===B=C=M=N=>>>>>>IIJJ,J-JTT^^?aBabbddedfdddddddddjeh-CJOJQJh-CJOJQJhp h-mHnHujh-U h-EHh-h-CJEHh-B*ph"h-B*OJQJmHnHphuh-B*OJQJph jh-B*OJQJUph8_7`7b7k77xooo $Ifgd-kd:$$IfTlFA I"0    4 layt-T777738xooo $Ifgd-kd;$$IfTlFA I"0    4 layt-T384868=889xoooo $Ifgd-kd<$$IfTlFA I"0    4 layt-T9999P:xooo $Ifgd-kd=$$IfTlFA I"0    4 layt-TP:Q:R:S::X;<<=== =xssniiiinnngd-gd-2gd-kd>$$IfTlFA I"0    4 layt-T = = ==O===>>!>.>;>H>I>n>{>>>>>. & F gd-. & Fgd-.gd-gd-gd-Mgd-$Ml&#$+D.X/gd- $$$gd- $dgd->>@_BC\DElFGHjIIIIII.JKK$MMMMOMgd-$Ml&#$+D.X/gd- $$$gd-gd-gd-OOOOOOPMPPPQZQ~QQQQQQ"RRR"SXSTTATBT & Fgd- & Fgd-gd-gd-2gd-BTT1UUVVVWXXXXYZZCZDZ[\\\]]^^ & Fgd- & Fgd- & Fgd-gd-gd- & Fgd-^_``oac>d?d@dAdBdCdEdeddddIeUeaeje !$Ifgd-gd-Mgd-$Ml&#$+D.X/gd- $$$gd-gd- & Fgd-jekeeeee|ssss [$Ifgd-kd?$$IflF$ x"$ T0    4 lalyt-jekeee'f(f)f0f1f9fffffvgxgygzggggh h1h2hShThUh}hhhhZi[iii)j*j.k/kkkllmmmm~nnoooo!p(ppprruuvv*v+vSwh-mHnHujh-UhWLh-CJEHh-OJQJhp h-5CJ h-CJ h-5h-CJOJQJh-CJOJQJh- h-CJBeeeee|sss [$Ifgd-kd@$$IflF$ x"$ T0    4 lalyt-eee f'f|sss $Ifgd-kd(A$$IflF$ x"$ T0    4 lalyt-'f(f)fMffff|tooff !$Ifgd-gd- & Fgd-kdA$$IflF$ x"$ T0    4 lalyt-fffug $Ifgd-okd^B$$Ifl0$ "$ 04 lalyt-ugvgwgxg $Ifgd-okdB$$Ifl0$ "$ 04 lalyt-xgygzgggghhvvv !$Ifgd-gd- $ & Fa$gd-okdC$$Ifl0$ "$ 04 lalyt-hh!h0h1h|sss $Ifgd-kdD$$IflF~ "~  0    4 lalyt-1h2hDhShTh|sss $Ifgd-kdD$$IflF~ "~  0    4 lalyt-ThUhVhXh}hhhhh|wwrlccc !$Ifgd-<@&gd-gd-gd-kdWE$$IflF~ "~  0    4 lalyt-hhhNiZi{rrr $Ifgd-kdE$$Ifl4Fq# 0    4 layt-Zi[ijikiiii|sssss $Ifgd-kdF$$IflFq# 0    4 layt-iiij(j)j|ssss $Ifgd-kdG$$IflFq# 0    4 layt-)j*jKj"k.k|sss $Ifgd-kdH$$IflFq# 0    4 layt-.k/kLkMkkk|ssss $Ifgd-kdI$$IflFq# 0    4 layt-kkkkll|ssss $Ifgd-kdJ$$IflFq# 0    4 layt-llllmmm|sssss $Ifgd-kdK$$IflFq# 0    4 layt-mm8m9mmmm|sssss $Ifgd-kdL$$IflFq# 0    4 layt-mmmmrn~n|ssss $Ifgd-kdM$$IflFq# 0    4 layt-~nnnoo|sss $Ifgd-kdN$$IflFq# 0    4 layt-ooooo|sss $Ifgd-kdO$$IflFq# 0    4 layt-ooopp!pJp_prppp|wwrmg^^^^ !$Ifgd-<@&gd-gd-gd-2gd-kdP$$IflFq# 0    4 layt- ppppppe\\\\ $Ifgd-kdQ$$Ifl44\(# p04 lalf4yt-ppppppf]]]] $Ifgd-kdGR$$Ifl4\(# p04 lalf4yt-ppppppqqqtfa\W\OOOO & Fgd-gd-gd-2gd-kdR$$Ifl4\(# p04 lalf4yt- tt\uuuuuuuu,v3vSwbwiwqwww !$Ifgd-<@&gd-gd-Mgd-$Ml&#$+D.X/gd- $$$gd-gd- & Fgd-SwZwwwDyKyLybyyy{{{,{q{r{{{{| | |*}3}s}}}}ɀʀ,-;BST()56؉ى)¹¹h-CJEH h-5>*h-5>*OJQJh-mHnHujh-Uh-5CJOJQJ h-CJh-CJOJQJh-CJOJQJ h-5h-h-OJQJ;wwxOxxxe\\\\ $Ifgd-kdS$$Ifl44\ #  a04 lalf4yt-xxxxxxf]]]] $Ifgd-kdWT$$Ifl4\ #  a04 lalf4yt-xxxxxCyDycymyfaa\WWWN ]$Ifgd-gd-gd-2gd-kdU$$Ifl4\ #  a04 lalf4yt-my~yyyyyyy zz0zqhhhhh [$Ifgd-kdU$$Ifk4r\ "T4 kakf4yt- ]$Ifgd- 0z1zMzwzzzzzqqqqq [$Ifgd-kdV$$Ifk4r\ "T4 kakf4yt-zzzz{ {{zqqqqq [$Ifgd-kdW$$Ifk4r\ "T4 kakf4yt-{{{-{7{K{c{k{q{zupggggg ]$Ifgd-\gd-gd-kdX$$Ifk4r\ "T4 kakf4yt-q{r{{{{{{zqqqqq [$Ifgd-kd{Y$$Ifk4ro ."o4 kakf4yt-{{{{{{{zmdddd [$Ifgd- . & F$Ifgd-kdZ$$Ifk4ro ."o4 kakf4yt-{{{{{{{zqqqqq [$Ifgd-kdZ$$Ifk4ro ."o4 kakf4yt-{{{{{ | ||zuiTKCu & F gd-Mgd-$Ml&#$+D.X/gd- $$$gd-gd-kd[$$Ifk4ro ."o4 kakf4yt-|*}s}} ~ɀʀ̀܀ `$Ifgd-_$$da$gd-_$$d`a$gd-gd-gd- zqqq `$Ifgd-kd\$$IflF t< 0\     4 layt-zqqq `$Ifgd-kd^]$$IflF t< 0\     4 layt-zqqq `$Ifgd-kd]$$IflF t< 0\     4 layt- zqqq `$Ifgd-kd^$$IflF t< 0\     4 layt-zqqqqq `$Ifgd-kd/_$$IflF t< 0\     4 layt- #)+,-VMMMMM `$Ifgd-kd_$$Iflr t`< p04 layt--.18:;CVMMMMM `$Ifgd-kd`$$Iflr t`< p04 layt-CDGPRSTVMMMMM `$Ifgd-kda$$Iflr t`< p04 layt-TUYlopVMMMMM `$Ifgd-kdb$$Iflr t`< p04 layt-VMMMMM `$Ifgd-kdrc$$Iflr t`< p04 layt-VMMMMM `$Ifgd-kdNd$$Iflr t`< p04 layt-VMMMMM `$Ifgd-kde$$Iflr t`< p04 layt-ÁāҁVMM@MM `$If^gd- `$Ifgd-kde$$Iflr t`< p04 layt-ҁӁԁՁցׁVMM@MM `$If^gd- `$Ifgd-kdf$$Iflr t`< p04 layt-VMMMMM `$Ifgd-kdNg$$Iflr t`< p04 layt-VQQQQQQQQgd-kd*h$$Iflr t`< p04 layt- ) 3BՅ  $Ifgd- !$Ifgd-gd-gd-gd-$a$gd-*+f]]T]T $Ifgd- !$Ifgd-kdi$$Ifl4\ H!@)@8 F04 lalf4yt-d[R[R $Ifgd- !$Ifgd-kdi$$Ifl4|\ H!@)@8` `F04 lalf4yt-؆ކd[R[R $Ifgd- !$Ifgd-kdrj$$Ifl4|\ H!@)@8  F04 lalf4yt- (f]T]T $Ifgd- !$Ifgd-kd/k$$Ifl4\ H!@)@8 F04 lalf4yt-()45f]T $Ifgd- #$Ifgd-kdk$$Ifl4\ H!@)@8 F04 lalf4yt-56<jz $Ifgd- !$Ifgd-rkdl$$Ifl40 @8 >+04 lalf4yt-jkzx $Ifgd- #$Ifgd-tkdJm$$Ifl40b@8b004 lalf4yt-x $Ifgd- #$Ifgd-tkdm$$Ifl4[0b@8b004 lalf4yt-. !$Ifgd-tkdxn$$Ifl4v0b@8b004 lalf4yt-./2EPGGGGG $Ifgd-kdo$$Ifl44JrH!p&@8N v(04 lalf4yt-‰ÉĉSNNNNNNNgd-kdo$$Ifl4rH!p&@8N v(04 lalf4yt-ĉʼnlj؉).9F O$Ifgd-gd-Mgd-$Ml&#$+D.X/gd- $$$gd-gd-)FGhi|}ĊŊۊ܊&'=>_`΋ϋ!"ABcʌ͌ 34@ABCIJLMP구구h-mHnHujh-Uh9`^jh9`^Uh? h-EHh-OJQJ h-CJh-5>*CJh-h-CJEHh-5B*phDFGKghWNNN O$Ifgd-kdp$$Ifl    F&"      0        4 lapyt-hil{||sss O$Ifgd-kdq$$Ifl    F&"  0        4 layt-|}|sss O$Ifgd-kdr$$Ifl    F&"  0        4 layt-ÊĊ|sss O$Ifgd-kds$$Ifl    F&"  0        4 layt-ĊŊɊڊۊ|sss O$Ifgd-kdt$$Ifl    F&"  0        4 layt-ۊ܊|sss O$Ifgd-kdu$$Ifl    F&"  0        4 layt-&|sss O$Ifgd-kdv$$Ifl    F&"  0        4 layt-&'+<=|sss O$Ifgd-kdw$$Ifl    F&"  0        4 layt-=>B^_|sss O$Ifgd-kdx$$Ifl    F&"  0        4 layt-_`d~|sss O$Ifgd-kdy$$Ifl    F&"  0        4 layt-|sss O$Ifgd-kdz$$Ifl    F&"  0        4 layt-|sss O$Ifgd-kd{$$Ifl    F&"  0        4 layt-͋΋|sss O$Ifgd-kd{|$$Ifl    F&"  0        4 layt-΋ϋӋ|sss O$Ifgd-kds}$$Ifl    F&"  0        4 layt-!|sss O$Ifgd-kdk~$$Ifl    F&"  0        4 layt-!"$ABPQRSabcd|wrhhhhhhhhh dgd-gd-gd-kdc$$Ifl    F&"  0        4 layt- deʌˌ̌͌ dgd-gd- Qdgd-Q & Fdgd-gd-BNOP)CEƀBLCd dgd-PQWXZ[_`yzÍčȍɍ67=>@ACDJKMNRSlm%&CDUVZ[abdeiklrshWLmHnHuhp mHnHu h-0J$jh-0J$Uh-mHnHuh-jh-UJBCfghi 9:XYpq)suvz{ď *LMefrswx~ŐƐǐȐߐ()67:Dfg޾ު޾hp mHnHuhWL0J$mHnHuhWLmHnHuh-OJQJ h-0J$h-mHnHujh-Uh-jh-0J$Uh-0J$mHnHuC͑ΑHIVWYcÒĒƒǒ˒̒/045`anoq~ٓؾؾhWL0J$mHnHuhWLmHnHuh-OJQJhp mHnHujh-Uh-0J$mHnHu h-0J$h-jh-0J$UFٓړޓߓh?h9`^hWL0J$mHnHu h-0J$jh-0J$Uh-jh-U 7 F,..))()()()()()000,P&P08$:p-/ =!["# $% DpC,..))()()()()() 0000,P&P0/ =!T"T#$8% 8$Dp? 000P&P/ =!["[#$8% Dp6,..))()()()()() 0000,&P/ =!T"T#$8% 8$@,..))()()()()() 0000,P&P/ =!T"T#$8% 8$Dp3,..))()()()()() 000,&P/ =!T"T#$8% 8$3,..))()()()()() 000,&P/ =!T"T#$8% 8$3,..))()()()()() 000,&P/ =!T"T#$8% 8$3,..))()()()()() 000,&P/ =!T"T#$8% 8$3,..))()()()()() 000,&P/ =!T"T#$8% 8$3,..))()()()()() 000,&P/ =!T"T#$8% 8$3,..))()()()()() 000,&P/ =!T"T#$8% 8$3,..))()()()()()00,&P0= /!8"#[$[% 8$0,..))()()()()()00,&P/ =!["[#$8% 8$3,..))()()()()()00,&P0= /!8"#[$[% 8$,/R / =!T"T#$8% 3 0/R / =!T"T#$8% P 4,..))()()()()()00,&P/ =!T"T#$8% P 8$3,..))()()()()() 000,&P/ =!T"T#$8% 8$7,..))()()()()() 000,&P/ =!T"T#$8% P 8$U$$If!vh#v%:V l4\,5%4f4yt-$$If!vh#v#vL#v#v#v:V 55L555/ / 4yt-T$$If!vh#v#vL#v#v#v:V 55L555/ / 4yt-Ty$$If!vh#v#vL#v#v#v:V 55L5554yt-T$$If!vh#v#vL#v#v#v:V 55L555/ / 4yt-T$$If!vh#v#vL#v#v#v:V 55L555/ / 4yt-Ty$$If!vh#v#vL#v#v#v:V 55L5554yt-T$$If!vh#v#vL#v#v#v:V 55L555/ / 4yt-T$$If!vh#v#vL#v#v#v:V 55L555/ / 4yt-Ty$$If!vh#v#vL#v#v#v:V 55L5554yt-Ty$$If!vh#v#vL#v#v#v:V 55L5554yt-Ty$$If!vh#v#vL#v#v#v:V 55L5554yt-Tx$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-x$$If!vh#v$:V l05$4yt-$$If!vh#v$:V l05$/ 4yt-$$If!vh#v$:V l05$/ 4yt-$$If!vh#v$:V l05$/ 4yt-}DyK _Toc328850541}DyK _Toc328850541}DyK _Toc328850542}DyK _Toc328850542}DyK _Toc328850543}DyK _Toc328850543}DyK _Toc328850544}DyK _Toc328850544}DyK _Toc328850545}DyK _Toc328850545}DyK _Toc328850546}DyK _Toc328850546}DyK _Toc328850547}DyK _Toc328850547}DyK _Toc328850548}DyK _Toc328850548}DyK _Toc328850549}DyK _Toc328850549}DyK _Toc328850550}DyK _Toc328850550}DyK _Toc328850551}DyK _Toc328850551}DyK _Toc328850552}DyK _Toc328850552}DyK _Toc328850553}DyK _Toc328850553}DyK _Toc328850554}DyK _Toc328850554}DyK _Toc328850555}DyK _Toc328850555}DyK _Toc328850556}DyK _Toc328850556}DyK _Toc328850557}DyK _Toc328850557}DyK _Toc328850558}DyK _Toc328850558}DyK _Toc328850559}DyK _Toc328850559}DyK _Toc328850560}DyK _Toc328850560}DyK _Toc328850561}DyK _Toc328850561}DyK _Toc328850562}DyK _Toc328850562}DyK _Toc328850563}DyK _Toc328850563}DyK _Toc328850564}DyK _Toc328850564}DyK _Toc328850565}DyK _Toc328850565}DyK _Toc328850566}DyK _Toc328850566}DyK _Toc328850567}DyK _Toc328850567}DyK _Toc328850568}DyK _Toc328850568}DyK _Toc328850569}DyK _Toc328850569}DyK _Toc328850570}DyK _Toc328850570}DyK _Toc328850571}DyK _Toc328850571}DyK _Toc328850572}DyK _Toc328850572}DyK _Toc328850573}DyK _Toc328850573}DyK _Toc328850574}DyK _Toc328850574}DyK _Toc328850575}DyK _Toc328850575}DyK _Toc328850576}DyK _Toc328850576}DyK _Toc328850577}DyK _Toc328850577}DyK _Toc328850578}DyK _Toc328850578}DyK _Toc328850579}DyK _Toc328850579}DyK _Toc328850580}DyK _Toc328850580}DyK _Toc328850581}DyK _Toc328850581}DyK _Toc328850582}DyK _Toc328850582}DyK _Toc328850583}DyK _Toc328850583}DyK _Toc328850584}DyK _Toc328850584}DyK _Toc328850585}DyK _Toc328850585$$If!vh#v#v#v:V l0555/ / / / /  / / 4yt-T$$If!vh#v#v#v:V l0555/ / / / / / / 4yt-T$$If!vh#v#v#v:V l0555/ / / / / / / 4yt-T$$If!vh#v#v#v:V l0555/ / / / / / / 4yt-T$$If!vh#v#v#v:V l0555/ /  / / / /  / 4yt-T$$Ifl!vh#v$ #vT#v:V l05$ 5T54alyt-$$Ifl!vh#v$ #vT#v:V l05$ 5T5/ 4alyt-$$Ifl!vh#v$ #vT#v:V l05$ 5T54alyt-$$Ifl!vh#v$ #vT#v:V l05$ 5T54alyt-$$Ifl!vh#v$ #v:V l05$ 54alyt-$$Ifl!vh#v$ #v:V l05$ 5/ 4alyt-$$Ifl!vh#v$ #v:V l05$ 54alyt-$$Ifl!vh#v~ #v #v:V l05~ 5 54alyt-$$Ifl!vh#v~ #v #v:V l05~ 5 5/ 4alyt-$$Ifl!vh#v~ #v #v:V l05~ 5 54alyt-$$If!vh#v#v#v :V l40555 / / / / /  / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / / / / / / / 4yt-$$If!vh#v#v#v :V l0555 / /  / / / /  / 4yt-$$Ifl!vh#v#v #v#vp:V l44055 55p4alf4yt-$$Ifl!vh#v#v #v#vp:V l4055 55p4alf4yt-$$Ifl!vh#v#v #v#vp:V l4055 55p4alf4yt-$$Ifl!vh#v #v #va#v:V l4405 5 5a54alf4yt-$$Ifl!vh#v #v #va#v:V l405 5 5a54alf4yt-$$Ifl!vh#v #v #va#v:V l405 5 5a54alf4yt-$$Ifk!vh#v#v#v#v#vT:V k455555T/ /  / /  / / 44 kakf4yt-$$Ifk!vh#v#v#v#v#vT:V k455555T/ /  / /  / / / 44 kakf4yt-$$Ifk!vh#v#v#v#v#vT:V k455555T/ /  / /  / / / 44 kakf4yt-$$Ifk!vh#v#v#v#v#vT:V k455555T/ /  / /  / / / 44 kakf4yt-$$Ifk!vh#vo#v#v#v#v:V k45o5555/ 44 kakf4yt-$$Ifk!vh#vo#v#v#v#v:V k45o5555/ /  / / / 44 kakf4yt-$$Ifk!vh#vo#v#v#v#v:V k45o5555/ /  / / / 44 kakf4yt-$$Ifk!vh#vo#v#v#v#v:V k45o5555/ /  / / / /  / 44 kakf4yt-$$If!vh#v<#v #v:V l0\ 5<5 54yt-$$If!vh#v<#v #v:V l0\ 5<5 54yt-$$If!vh#v<#v #v:V l0\ 5<5 54yt-$$If!vh#v<#v #v:V l0\ 5<5 54yt-$$If!vh#v<#v #v:V l0\ 5<5 54yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ / / / 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ / / /  / 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ /  / / 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ /  / 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ /  / 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/ /  / 4yt-$$If!vh#v<#v #v#v#vp:V l05<5 555p/  / / 4yt-$$Ifl!vh#v #vF#v#v:V l405 5F554alf4yt-$$Ifl!vh#v #vF#v#v:V l4|0++5 5F554alf4yt-$$Ifl!vh#v #vF#v#v:V l4|0++5 5F554alf4yt-$$Ifl!vh#v #vF#v#v:V l405 5F554alf4yt-$$Ifl!vh#v #vF#v#v:V l405 5F55/ 4alf4yt-$$Ifl!vh#v #v>+:V l405 5>+/ / 4alf4yt-$$Ifl!vh#vb#v0:V l405b504alf4yt-$$Ifl!vh#vb#v0:V l4[05b504alf4yt-$$Ifl!vh#vb#v0:V l4v05b504alf4yt-$$Ifl!vh#v#vN #vv#v(#v:V l44J055N 5v5(54alf4yt-$$Ifl!vh#v#vN #vv#v(#v:V l4055N 5v5(54alf4yt-A$$If!vh#v#v#v :V l 0    555 /  / / / /  /  / 4pyt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-$$If!vh#v#v#v :V l0    555 /  / / / / / /  4yt-ja 666666666vvv6666666666666666666666666666666666666666666666666hH666666666666666666666666666666666666666666666666666666666666666662 0@P`p2( 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p8XV~ OJPJQJ_HmH nH sH tH V`V -Normal d$CJEHOJPJQJ_HmH sH tH ` - Heading 11$ & FHUl&#$+D.X/@&-B*CJKHOJPJQJ_HmH phsH tH ~`~ - Heading 2.$ & Fdx&d @&P $@,CJOJPJQJ_HmH sH tH ` - Heading 3.$ & Fdx&d@&P(@&CJEHOJPJQJ_HmH sH tH ~`~ - Heading 4.$ & Fdx&d@&P$CJEHOJPJQJ_HmH sH tH n`n - Heading 5$ & Fdx@&$CJEHOJPJQJ_HmH sH tH D@D - Heading 6 & F<@&6L@L - Heading 7 & F<@& CJOJQJP@P - Heading 8 & F<@&6CJOJQJR @R - Heading 9 & F<@&56CJOJQJDA`D Default Paragraph FontRi@R 0 Table Normal4 l4a (k ( 0No List fof -Heading 1 Char1B*CJKHOJPJQJ^J_HmH phsH tH \o\ -Heading 2 Char(@,CJOJPJQJ^J_HmH sH tH `o` -Heading 3 Char,@&CJEHOJPJQJ^J_HmH sH tH \o!\ -Heading 4 Char(CJEHOJPJQJ^J_HmH sH tH \o1\ -Heading 5 Char(CJEHOJPJQJ^J_HmH sH tH PoAP -Heading 6 Char6EHOJPJQJ^JaJPoQP -Heading 7 CharCJEHOJPJQJ^JaJToaT -Heading 8 Char6CJEHOJPJQJ^JaJVoqV -Heading 9 Char"56CJEHOJPJQJ^JaJzOz -Note Table Border- & F XXdP^X`CJEHOJQJ\o\ -Note$ & Fd$CJEHOJPJQJ_HmH sH tH NoN -Graphic CJOJPJQJ_HmH sH tH o - Blank Page!$$9&#$./a$1@ B*CJ"EHOJPJQJ_HmH phsH tH bob -Bullet 1 & Fd$CJEHOJPJQJ_HmH sH tH xox -Bullet 2* & F d^`$CJEHOJPJQJ_HmH sH tH ^o^ - Chapter Headdp$CJ"EHOJPJQJ_HmH sH tH o -Chapter Number"$$&#$./a$)B*CJxOJPJQJ_HmH phsH tH non -Table Text Border PP^ CJOJPJQJ_HmH sH tH tot -Table Title Border!$(P^ CJOJPJQJ_HmH sH tH jo"j -Graphic with Callouts" CJ<OJPJQJ_HmH sH tH vo2v -Table Title No Border#$xx]x CJOJPJQJ_HmH sH tH JoAJ - Arial BlackCJOJQJkHmH sH uboRb -Caution%$ & Fd$CJEHOJPJQJ_HmH sH tH ob -Bullet Table Border& & F hP^ CJOJPJQJ_HmH sH tH TorT -Callout'dL$CJEHOJPJQJ_HmH sH tH >o> -SM/TM5@CJ EHOJQJkHP `P *-Footer ) (# CJOJPJQJ_HmH sH tH RoR )- Footer Char$CJOJPJQJ^J_HmH sH tH NoN -Registered Mark@CJ EHOJQJkH`-pTOC 1?,$ (# 0d&dP^`04@&B*CJOJPJQJ_HmHnHphsH tH uDOD -Blank 1-B*CJOJQJphbob -Step. & F Xd$CJEHOJPJQJ_HmH sH tH POP -Procedure Head /$x CJOJQJ`o` -Danger0$ & Fd$CJEHOJPJQJ_HmH sH tH fOf -Step Table Border1 & F XdP CJOJQJ`o"` - Extra Space2 & Fdt CJOJPJQJ_HmH sH tH do1d 4-Document Map Char)EHOJPJQJ^JaJfH q NY@BN 3- Document Map4-D M OJQJh`Rh-pTOC 25 (# d^+CJEH OJPJQJ_HmHnHsH tH u.@Q.-pTOC 3 6^4@r4 8-Header 7 !FoF 7- Header CharEHOJPJQJ^JaJjoj -Contents Title 9$.)B*CJ"OJPJQJ_HmH phsH tH VoV -Arial Black Number5B*CJ"EHOJQJkHVoV -Page Number TOC@CJOJQJkHmH sH uB"@B -Caption <$ x CJOJQJFOF - Product Name =dCJ0EHPOP - Document Type>d;@-CJOJQJtot -Copyright Heading?d@]$CJEHOJPJQJ_HmH sH tH dod - Statement@\dP]\$CJEHOJPJQJ_HmH sH tH BOB - Doc Info HeadA\P]\>O"> - Doc Info TextBEHbo2b -WarningC$ & Fd$CJEHOJPJQJ_HmH sH tH LOBL -Blank 2D B*CJOJQJphRoRR -LabelsE$a$$CJEHOJPJQJ_HmH sH tH |ob| - Form Head!F$$|d]|a$-B*CJ0EHOJPJQJ_HmH phsH tH JOrJ - Form SubheadG$a$6B*CJphNON - Regular TextHhB*CJOJQJph\o\ -BlankPageBullet&@ B*CJEHOJQJkHmH sH ufof - EvalHeadingsJd+5@3CJEHOJPJQJ_HmH sH tH >O> - InstructionsK B*phO - Client/DateiLd f &#$$d%d&d'd+D/@&NOPQ;@CJ$OJQJ`o` -Small ParagraphMd CJOJPJQJ_HmH sH tH \o\ - DocNormal Nd$CJEHOJPJQJ_HmH sH tH 2B@2 P- Body TextOsLoL O-Body Text CharEHOJPJQJ^JaJBOB - table heading Q((58"8 - table text R<<020 - Index BaseSoB -bulletT & F # p@ P !8dx*$>TTf^8` CJOJPJQJ_HmH sH tH OR -NumberedU$ & Fhdxx>Th.Tf^h`CJEHOJQJOb -bullet 3V & F (h p@ P !dxx*$>TTf^`CJEHOJQJZoqZ X-Body Text Indent CharCJOJPJQJ^JaJbC@b W-Body Text IndentXdxx^CJEHOJQJ^o^ Z-Body Text Indent 2 CharCJOJPJQJ^JaJnR@n Y-Body Text Indent 2 Zdx^`CJEHOJQJLOL - Table Text[HH((]H^HCJZOZ - Table Heading\HH<<]H^H 5OJQJ\O\ - TableHeading]HH<<]H^H5CJOJQJ0U`0 -0 Hyperlink>*B*FOF -Text_&d^& EHOJQJPOP - TableText2"`d&#$/PK![Content_Types].xmlN0EH-J@%ǎǢ|ș$زULTB l,3;rØJB+$G]7O٭V$ !)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 =3N)cbJ uV4(Tn 7_?m-ٛ{UBwznʜ"Z xJZp; {/<P;,)''KQk5qpN8KGbe Sd̛\17 pa>SR! 3K4'+rzQ TTIIvt]Kc⫲K#v5+|D~O@%\w_nN[L9KqgVhn R!y+Un;*&/HrT >>\ t=.Tġ S; Z~!P9giCڧ!# B,;X=ۻ,I2UWV9$lk=Aj;{AP79|s*Y;̠[MCۿhf]o{oY=1kyVV5E8Vk+֜\80X4D)!!?*|fv u"xA@T_q64)kڬuV7 t '%;i9s9x,ڎ-45xd8?ǘd/Y|t &LILJ`& -Gt/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 0_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!0C)theme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK]  56AC\msxy}ŁBde  H    H }    Q    " W    % TTTTTTTTT GGGGGkkkmm$>]u mQA 7jeSw)PsٓJYghijklmnoprstuvwxy}  A G c WZ eh &t0_77389P: =>OBT^jeee'ffugxgh1hThhZii)j.kklmm~nooppptwxxmy0zz{q{{{{|-CTҁ(5j.ĉFh|Ċۊ&=_΋!dKLMNOPQRSTUVWXZ[\]^_`abcdefqz{|~Um 79:<\ / K M N P p    ! A U q s t v   ! # C Q m o p r # ? A B D d u  ' C E F H h ')*,Lh,HJKMm !#CmOkmnp '*+-Mw A]`ac   ,7SVWYy$Hdghj7Milmo ),-/Oc!=@ACc///5B5M5666AB,Be\\\mn*nss t؁ X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%̕   T        7DFMPT[^c}:ADGNQVp)GY^ehovy~ Piv{,:j LZ38dr !!!! !!  !! !! !! t!8@0(  B S  ?x _Hlt520193607 _Toc460224419 _Toc328850541 _Toc475424428 _Toc476545683 _Hlt496488387 _Toc328850542 _Hlt483232697 _Toc328850543 _Toc448727301 _Toc448732592 _Toc475424430 _Toc476545684 _Toc328850544 _Toc328850545 _Toc448725556 _Toc454094797 _Toc464433666 _Toc328850546 _Toc448725557 _Toc454094798 _Toc464433667 _Toc328850547 _Toc448725558 _Toc454094799 _Toc464433668 _Hlt496488423 _Toc328850548 _Toc448725560 _Toc454094801 _Toc464433670 _Toc328850549 _Hlt471712041 _Toc448727304 _Toc448732595 _Toc475424433 _Toc328850550 _Toc448727312 _Toc448732603 _Toc472734310 _Toc328850551 _Toc472734311 _Toc328850552 _Hlt471796050 _Toc328850553 _Hlt483221416 _Toc328850554 _Toc448727314 _Toc448732605 _Toc475424443 _Toc328850555 _Toc475424446 _Toc476545697 _Toc328850556 _Toc448725567 _Toc454094806 _Toc464433675 _Toc328850557 _Toc448725569 _Toc454094808 _Toc464433677 _Hlt520193681 _Toc328850558 _Toc328850559 _Toc328850560 _Toc328850561 _Toc328850562 _Toc328850563 _Toc328850564 _Toc328850565 _Toc328850566 _Toc328850567 _Toc448725572 _Toc454094811 _Toc464433680 _Toc328850568 _Toc448727319 _Toc448732610 _Toc475424449 _Toc476545699 _Hlt520193943 _Toc328850569 _Toc328850570 _Toc328850571 _Toc328850572 _Toc448727321 _Toc448732612 _Toc328850573 _Toc328850574 _Hlt496488472 _Toc328850575 _Hlt496488470 _Toc448725586 _Toc454094826 _Toc464433694 _Hlt496488503 _Hlt496489229 _Hlt492279849 _Toc448725585 _Toc454094825 _Toc464433693 _Hlt496488484 _Hlt496488490 _Toc328850576 _Hlt497489186 _Toc328850577 _Toc328850578 _Hlt497489190 _Toc328850579 _Toc328850580 _Hlt520192270 _Toc328850581 _Toc328850582 _Toc475424461 _Toc476545706 _Toc497489258 _Toc328850583 _Toc328850584 _Toc328850585 _Toc460224420  !!!!H$H$H$H$&&&&&u(u(u(u()555C5O5O555I6I6n6666666B.B.BCEEEEGGGGGGILNPRT\\X`X`X`X`}`}`hhhhhn,n3n3npt t txxxxyyyyyyyyyzz {3|3|}}}$e@ @ "#$!+,%&'()*-./0123456789;<=:>?@ABCDEFGHIJKMNOPLQRSTWXUVY@Z[@mno\@]@^@abc_@`@de@fgh@ijklpqrstuvw    " !!!!V$V$V$V$&&&&&(((()M5O5O5O556_6m6n666666AAA,BCCCEEEEGGGGGHI@LNPBRU\\|`|`|`|`h h h h h hh*n2np t t t ttxyyyyyzzzzz(z{3|A|}}}((((@6@@@@@@@II`JjJL&LLL(M+MNNNNFOHOKOPO\ObOOOOOPPR RR(RTTIUSUUUVVVV\XfX1Y;Y[YdYzZZ[[ \\ggjj:mDmpr@I%T!\!%%''44>>~KKLL\OgOOOOOVVZZ["[&q/quu}}~~y333333333333333333333LLVVmXmX?YBYZZ[[\\` `jjABMP[_ąȅ6ACNR%VZekvzLswƈLj7fWNJˊ04oڋދ\ JR y w.j0Y3 'n (XdP+}# z':h&4-{(.)J֘}Kk,~&,, K-- vZ. FvFp%@/@Vꆸ1P` >oC@Zc `^``B*CJD^D`@. d^d`@ .. H^H`@ ...  t^`t@ .... ^`^`^`^`hh^h`o(.hh^h`o(.P^`PCJOJQJo(Danger:  ^ `CJOJQJo(Note@, ,^,`OJQJo("  X^X`OJQJo( hh^h`o(.h^`CJOJQJo(" hh^h`56B*CJOJQJ.X^X`56CJOJQJ.H^H`OJ QJ )^`OJ QJ )^`OJ QJ ()h^`OJ QJ h^`OJ QJ h^`OJ QJ h^`OJ QJ ^`OJPJQJ^Jo(-^`OJ QJ ^J o(hHop^p`OJ QJ o(hH@ ^@ `OJQJo(hH^`OJ QJ ^J o(hHo^`OJ QJ o(hH^`OJQJo(hH^`OJ QJ ^J o(hHoP^P`OJ QJ o(hH0^`0CJOJQJo(Note:hh^h`o(.hh^h`o(.hh^h`o(.P^`PCJOJQJo(Cautionh^`56B*CJOJQJo(.X^X`56CJOJQJo(.H^H`CJOJQJo()^`CJOJQJo()^`CJOJQJo(()h^`OJ QJ h^`OJ QJ h^`OJ QJ h^`OJ QJ P^`PCJOJQJo( Warning:hh^h`o(.4-{(w.(XY3 FvFP`Kk,@/@Vz' 4-{( ,,@ZcyK--+}#JRvZ.)Lh        p WL9`^YL?-@jjjjX@UnknownSABRE Employee G* Times New Roman5Symbol3. * Arial?. Arial Black7.@ Calibri5. *aTahomaA. Arial Narrow_ Times RomanTimes New RomanMSpecial Characters7Tms Rmn?= * Courier New;WingdingsA$BCambria Math"qh#qC#qC!T203QHX $P-2! xx TemplateAutomation Test Plan TemplateAutomation Test Plan TemplateQATutorial.com qatutorialX              Oh+'0 0 DP p |  Template Automation Test Plan TemplateQATutorial.com Automation Test Plan TemplateNormal qatutorial3Microsoft Office Word@G@>V@>V#q՜.+,D՜.+,@ hp  QATutorial.comC  Template Title\ 8@ _PID_HLINKSA;_Toc328850585; _Toc328850584;_Toc328850583;_Toc328850582;_Toc328850581;_Toc328850580;_Toc328850579;_Toc328850578;_Toc328850577;_Toc328850576;_Toc328850575;_Toc328850574;_Toc328850573;_Toc328850572;_Toc328850571;_Toc328850570;_Toc328850569;_Toc328850568;_Toc328850567;_Toc328850566;_Toc328850565;_Toc328850564;_Toc328850563;_Toc328850562;_Toc328850561;}_Toc328850560;w_Toc328850559;q_Toc328850558;k_Toc328850557;e_Toc328850556;__Toc328850555;Y_Toc328850554;S_Toc328850553;M_Toc328850552;G_Toc328850551;A_Toc328850550;;_Toc328850549;5_Toc328850548;/_Toc328850547;)_Toc328850546;#_Toc328850545;_Toc328850544;_Toc328850543;_Toc328850542; _Toc328850541  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./013456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnoqrstuvwyz{|}~Root Entry F@VData [1Table2{WordDocument^SummaryInformation(pDocumentSummaryInformation8xCompObjr  F Microsoft Word 97-2003 Document MSWordDocWord.Document.89q