Ass|gnment Ŵ2 5CL

1est|ng Documentat|on
ż1ype the document subt|t|eŽ
Ma[ 5a|fu||ah kha||d
5abeen Iava|d
5habnam Abbas
Anbreen kausar

MCSŴ17 | AsslanmenL 2 2

SOFTWARE TESTING DOCUMENTATION
Assignment Objective
1. Survey Testing Documentation Practices in vogue at any major software firm.
Moreover, presents any sample templates of different organization for test documentation
available.

Abstract
1Ŧ Testing is an important part of developmental process. Ìn waterfall model it is a
distinct phase whereas as in other processes it is embedded into the process. "The basic
idea of testing involves the execution of software and the observation of its behavior or
outcome. Ìf a failure is observed, the execution record is analyzed to locate and fix the
fault(s) that caused the failure. Otherwise, it indicates that the software under testing is
more likely to fulfill its designated functions¨ (1 p. 67). The effective testing needs a formal
process support and effective execution of testing requires sound planning and
documentation.
2Ŧ Ìn pursuant to the assignment objective, several software firm including Microsoft,
ÌBM, Sun micro systems, Nokia and Mozilla were considered. The information available
through company websites and other indirect sources was collected and analyzed. These
sources only provide very broad information about the software Testing Tools and
Techniques used by these firms for software testing and specific information about testing
documentation they maintained is not directly available.
Assumption
Ŧ While details of testing and testing documentation in vogue at various firms are
confidential, several indirect sources indicate that most of the software firms use Custom
Testing Documentation Standards. Moreover, these practices are greatly influenced by
IEEE Testing Documentation Standard 829 (2) (3).

IEEE - 829 (1998/2008) -Test Documentation Standard
Ŧ The standard deals with testing process and testing documentation. Ìt describes a
set of basic test documents that are associated with the dynamic aspects of software
testing (i.e. the execution of procedures and code). Ìt also defines the use and contents of
related test documentation (Test Design, Test Case, Test Procedure, Anomaly Report, Test
Log, Level Test Report, Ìnterim Test Report, and Master Test Report). While the documents
MCSŴ17 | AsslanmenL 2

described in the standard focus on dynamic testing, several of them may be applicable to
other testing activities.
3Ŧ This standard applies to all software-based systems. Ìt applies to systems and
software being developed, acquired, operated, maintained, and/or reused [e.g., legacy,
modified, Commercial-Off-the-Shelf (COTS), Government-Off-the-Shelf (GOTS), or Non-
Developmental Ìtems (NDÌs)]. When conducting the test process, it is important to examine
the software and its interactions with the other parts of the system. This standard identifies
the system considerations that test processes and tasks address in determining system and
software correctness and other attributes (e.g., completeness, accuracy, consistency, and
testability), and the applicable resultant test documentation. CIause 5 of the standard is
inventory of the test documentation identified as needed based on the testing tasks. The
process selection of contents is covered in CIauses 6&7 whereas cIauses 8 -17 give out
recommended test document contents. The purpose and outline structure are presented in
subsequent sections.
Ŧ This standard uses the concept of integrity IeveIs to determine the recommended
minimum testing tasks to be performed. The inputs and outputs of the indicated testing
tasks identify the test documentation needed. High integrity software requires a larger set of
test processes, a more rigorous application of testing tasks, and as a result, more test
documentation. The standards specify four integrity levels (1-4).

Basic Software Test Documents (4)
7Ŧ The documents outlined in this standard cover test planning, test specifications, and
test reporting.

MCSŴ17 | AsslanmenL 2


MCSŴ17 | AsslanmenL 2 3


1



1
llaure Laken from lLLLŴ829Ŵ1998ţ sLlll appllcable ln Lhe conLexL of new sLandard lLLLŴ829Ŵ2008
Figure 2: Test Documentation Review
MCSŴ17 | AsslanmenL 2

a. Master Test PIan (MTP) The purpose of the Master Test Plan (MTP) is to
provide an overall test planning and test management document for multiple
levels of test (either within one project or across multiple projects). A test plan
shall have the following structure:
MASTER TEST PLAN OUTLINE
1. Ìntroduction
1.1. Document identifier
1.2. Scope
1.3. References
1.4. System overview and key features
1.5. Test overview
1.5.1 Organization
1.5.2 Master test schedule
1.5.3 Ìntegrity level schema
1.5.4 Resources summary
1.5.5 Responsibilities
1.5.6 Tools, techniques, methods, and metrics
2. DetaiIs of the Master Test PIan
2.1. Test processes including definition of test levels
2.1.1 Process: Management
2.1.1.1 Activity: Management of test effort
2.1.2 Process: Acquisition
2.1.2.1: Activity: Acquisition support test
2.1.3 Process: Supply
2.1.3.1 Activity: Planning test
2.1.4 Process: Development
2.1.4.1 Activity: Concept
2.1.4.2 Activity: Requirements
2.1.4.3 Activity: Design
2.1.4.4 Activity: Ìmplementation
2.1.4.5 Activity: Test
2.1.4.6 Activity: Ìnstallation/checkout
2.1.5 Process: Operation
2.1.5.1 Activity: Operational test
2.1.6 Process: Maintenance
2.1.6.1 Activity: Maintenance test
2.2. Test documentation requirements
2.3. Test administration requirements
2.4. Test reporting requirements
3. GeneraI
3.1. Glossary
3.2. Document change procedures and history

b. LeveI Test PIan(s) Specifies for each LTP the scope, approach,
resources, and scheduIe of the testing activities for its specified IeveI of
MCSŴ17 | AsslanmenL 2 7

testing. Identify the items being tested, the features to be tested, the testing
tasks to be performed, the personneI responsibIe for each task, and the
associated risk(s). In the titIe of the pIan, the word "LeveI" is repIaced by
the organization's name for the particuIar IeveI being documented by the
pIan (e.g., Component Test PIan, Component Integration Test PIan, System
Test PIan, and Acceptance Test PIan). The outIine is as foIIow:-
LEVEL TEST PLAN OUTLINE
1. Introduction
1.1. Document identiIier
1.2. Scope
1.3. ReIerences
1.4. Level in the overall sequence
1.5. Test classes and overall test conditions
2. Details for this level of test plan
2.1 Test items and their identiIiers
2.2 Test Traceability Matrix
2.3 Features to be tested
2.4 Features not to be tested
2.5 Approach
2.6 Item pass/Iail criteria
2.7 Suspension criteria and resumption requirements
2.8 Test deliverables
3. Test management
3.1 Planned activities and tasks; test progression
3.2 Environment/inIrastructure
3.3 Responsibilities and authority
3.4 InterIaces among the parties involved
3.5 Resources and their allocation
3.6 Training
3.7 Schedules, estimates, and costs
3.8 Risk(s) and contingency(s)
4. General
4.1 Quality assurance procedures
4.2 Metrics
4.3 Test coverage
4.4 Glossary
4.5 Document change procedures and history

c. LeveI Test Design. The purpose of the LTD is to specify any refinements of the
test approach (LTP Section 2.5) and to identify the features to be tested by this
design and its associated tests. The outline is as follow:-

MCSŴ17 | AsslanmenL 2 8

LLVLL 1L51 DL5IGN CU1LINL
1Ŧ Introduct|on
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
2Ŧ Deta||s of the Leve| 1est Des|gn
2Ŧ1Ŧ leaLures Lo be LesLed
2Ŧ2Ŧ Approach reflnemenLs
2ŦŦ 1esL ldenLlflcaLlon
2ŦŦ leaLure pass/fall crlLerla
2Ŧ3 1esL dellverables
3Ŧ Genera|
Ŧ1Ŧ Clossarv
Ŧ2Ŧ uocumenL chanae procedures and hlsLorv

d. LeveI Test Case. The purpose of the LTC is to define (an appropriate level of
detail) the information needed as it pertains to inputs to and outputs from the
software or software-based system being tested. The LTC includes all test
case(s) identified by the associated segment of the LTD (if there is one). The
outline is as follow:-
LLVLL 1L51 CA5L CU1LINL
1Ŧ Introduct|on (once per document)
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
1ŦŦ ConLexL
1Ŧ3Ŧ noLaLlon for descrlpLlon
2Ŧ Deta||s (once per test case)
2Ŧ1Ŧ 1esL case ldenLlfler
2Ŧ2Ŧ Cb[ecLlve
2ŦŦ lnpuLs
2ŦŦ CuLcome(s)
2Ŧ3Ŧ LnvlronmenLal needs
2ŦŦ Speclal procedural requlremenLs
2Ŧ7Ŧ lnLerŴcase dependencles
3Ŧ G|oba| (once per document)
Ŧ1Ŧ Clossarv
Ŧ2Ŧ uocumenL chanae procedures and hlsLorv


MCSŴ17 | AsslanmenL 2 9

e. LeveI Test Procedure. The purpose of an LTP is to specify the steps for
executing a set of test cases or, more generally, the steps used to exercise a
software product or software-based system item in order to evaluate a set of
features. The outline is as follow:-
LvL 1LS1 Þ8CCLuu8L Cu1lnL
1Ŧ Introduct|on
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
1ŦŦ 8elaLlonshlp Lo oLher procedures
2Ŧ Deta||s
2Ŧ1Ŧ lnpuLsţ ouLpuLsţ and speclal requlremenLs
2Ŧ2Ŧ Crdered descrlpLlon of Lhe sLeps Lo be Laken Lo execuLe Lhe LesL cases
3Ŧ Genera|
Ŧ1Ŧ Clossarv
Ŧ2Ŧ uocumenL chanae procedures and hlsLorv

MCSŴ17 | AsslanmenL 2 10

f. LeveI Test Log. The purpose of the LTL is to provide a chronological record of
relevant details about the execution of tests. An automated tool may capture all
or part of this information. The outline is as follow:-
LLVLL 1L51 LCG CU1LINL
1Ŧ Introduct|on
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
2Ŧ Deta||s
2Ŧ1Ŧ uescrlpLlon
2Ŧ2Ŧ AcLlvlLv and evenL enLrles
3Ŧ Genera|
Ŧ1Ŧ Clossarv

g. AnomaIy Report OutIine. The purpose of the AR is to document any event that
occurs during the testing process that requires investigation. This may be called a
problem, test incident, defect, trouble, issue, anomaly, or error report. The outline
is as follow:-
ANCMAL¥ kLÞCk1 CU1LINL
1Ŧ Introduct|on
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
2Ŧ Deta||s
2Ŧ1Ŧ Summarv
2Ŧ2Ŧ uaLe anomalv dlscovered
2ŦŦ ConLexL
2ŦŦ uescrlpLlon of anomalv
2Ŧ3Ŧ lmpacL
2ŦŦ CrlalnaLor's assessmenL of uraencv (see lLLL 10Ŵ199 ż81Ž)
2Ŧ7Ŧ uescrlpLlon of Lhe correcLlve acLlon
2Ŧ8Ŧ SLaLus of Lhe anomalv
2Ŧ9Ŧ Concluslons and recommendaLlons
3Ŧ Genera|
Ŧ1 uocumenL chanae procedures and hlsLorv

h. LeveI Interim Test Status Report OutIine. The purpose of the LÌTSR is to
summarize the results of the designated testing activities and optionally to
provide evaluations and recommendations based on these results. Ìt is
MCSŴ17 | AsslanmenL 2 11

customary to replace the word "Level¨ in the title of the document with the
organization's name for the particular test level, e.g. Acceptance Ìnterim Test
Status Report. There is one defined format for the LÌTSR for each test level
identified by the organization. They may vary greatly in the level of detail. The
outline is as follow:-
LLVLL IN1LkIM 1L51 51A1U5 kLÞCk1 CU1LINL
1Ŧ Introduct|on
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
2Ŧ Deta||s
2Ŧ1Ŧ 1esL sLaLus summarv
2Ŧ2Ŧ Chanaes from plans
2ŦŦ 1esL sLaLus meLrlcs
3Ŧ Genera|
Ŧ1Ŧ uocumenL chanae procedures and hlsLorv

i. LeveI Test Report OutIine. The purpose of the LÌTSR is to summarize the
results of the designated testing activities and to provide evaluations and
recommendations based on these results. Ìt is customary to replace the word
"Level¨ in the title of the document with the organization's name for the particular
test level, e.g., Acceptance Ìnterim Test Status Report. There is one defined
format for the LÌTSR for each test level identified by the organization. They may
vary greatly in the level of detail. The outline is as follow:-
LLVLL 1L51 kLÞCk1 CU1LINL
1Ŧ Introduct|on
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
2Ŧ Deta||s
2Ŧ1Ŧ Cvervlew of LesL resulLs
2Ŧ2Ŧ ueLalled LesL resulLs
2ŦŦ 8aLlonale for declslons
2ŦŦ Concluslons and recommendaLlons
3Ŧ Genera|
Ŧ1Ŧ Clossarv
Ŧ2Ŧ uocumenL chanae procedures and hlsLorv

MCSŴ17 | AsslanmenL 2 12

j. Master Test Report OutIine The purpose of the Level Test Report (LTR) is to
summarize the results of the designated testing activities and to provide
evaluations and recommendations based on these results. Ìt is customary to
replace the word "Level¨ in the title of the document with the organization's name
for the particular test level, e.g., Acceptance Test Report. There is one LTR for
each test level defined by the organization or project. Small projects may merge
reports for multiple levels. They may vary greatly in the level of detail of
documentation (e.g., a Unit Test Report may simply be a statement that it passed
or failed, whereas an Acceptance Test Report may be much more detailed). The
outline is as follow:-
MA51Lk 1L51 kLÞCk1 CU1LINL
1Ŧ Introduct|on
1Ŧ1Ŧ uocumenL ldenLlfler
1Ŧ2Ŧ Scope
1ŦŦ 8eferences
2Ŧ Deta||s of the Master 1est keport
2Ŧ1Ŧ Cvervlew of all aaareaaLe LesL resulLs
2Ŧ2Ŧ 8aLlonale for declslons
2ŦŦ Concluslons and recommendaLlons
3Ŧ Genera|
Ŧ1Ŧ Clossarv
Ŧ2Ŧ uocumenL chanae procedures and hlsLorv

Software Testing At Microsoft (2)
8Ŧ Microsoft takes a unique approach to software testing compared to industry norms.
We have more test engineers than developers, and we emphasize software engineering
skills with all testers. This unique approach goes all the way down to the title we give
testers: Software Development Engineer in Test (SDET). By design, this title is virtually the
same as the Software Development Engineer title used for developers. Microsoft recruits
500 Test Engineer every year and have very comprehensive training program for Test
Engineers (2 p. 73).
9Ŧ Microsoft hasn't wholeheartedly adopted any of Process Ìmprovement programs like
CMMÌ, 6 Sigma, ÌSO - 9000 and Lean. Microsoft continues to take process improvement
programs seriously and often will "test" programs to get a better understanding of how the
process would work on Microsoft products. For example, Microsoft has piloted several
projects over the past few years using approaches based on Six Sigma and Lean. The
MCSŴ17 | AsslanmenL 2 1

strategy in using these approaches to greatest advantage is to understand how best to
achieve a balance between the desire for quick results and the rigor of Lean and Six Sigma
(2 p. 47).
10Ŧ Microsoft claims that its development process, the documentation of steps along the
way, the support its management team has for quality processes, and the
institutionalization of development process in documented and repeatable processes (as
well as document results) are all elements of the core ÌSO standards and that, in most
cases, it meets or exceeds these.
11Ŧ Microsoft follows a custom standard for test documentation. Exact details are not
available in open literature. However, it can be inferred that it uses a customized set of
standards for testing and test documentation which coincide with ÌSO/ÌEC 29119 (Part-3).
The later has been derived from ÌEEE-829-2008 test documentation standard (3).
12Ŧ Test TempIates. As mentioned earlier, companies use custom test documentation
standards which are greatly influenced by the ÌEEE standards, the templates for test
documents in most of the cases are same as of ÌEEE presented in earlier sections. For the
sake of completeness, templates from Extreme Software Testing Ìnc are presented in as
per Annex A to this document. Software test tempIates from NASA (5) (6) (9) (10) and
others (7) (8) are submitted in soft form. These templates are available at following links.

ConcIusion
1Ŧ Having presented the glimpses of testing process in vogue at Microsoft and on the
basis of research of testing processes of ÌBM and Sun Micro Systems, it can be inferred
that these software giants are using their customized standards for testing documentation.
These standards are based on ÌSO/ÌEC 29119 (Part-3) which itself is derived from ÌEEE-
829-1998 standard. Most of the firms have customized the standards to achieve quick
results while maintaining the rigor of these standards.








MCSŴ17 | AsslanmenL 2 1


1Ŧ Ieffţ 1|anŦ 5oftwote Ooolltv £ooloeetloo 1estlooţ Ooolltv Assotooceţ ooJ lmptovemeotŦ
2Ŧ A|anţ ÞagenŦ ow we test 5oftwote At MlctosoftŦ sŦlŦ ť MlcrosofLţ 2008Ŧ
Ŧ lSC/lLC 29119 SofLware 1esLlnaŦ żCnllneŽ żClLedť aprll 2ţ 2011ŦŽ
hLLpť//sofLwareLesLlnasLandardŦora/lndexŦphpŦ lSC/lLC 29119Ŧ
Ŧ ILLLŴ829ţ 5oftware Lng|neer|ng 1echn|ca| Comm|ttee of ILLL computerŦ l£££ 5tooJotJ fot 5oftwote 1est
uocomeototlooŦ 2008Ŧ
3Ŧ Codard space fllahL cenLerŦ 5oftwote ossotoocetŦ żCnllneŽ żClLedť Apr 23ţ 2011ŦŽ hLLpť//swŴ
assuranceŦasfcŦnasaŦaov/dlsclpllnes/quallLv/checkllsLs/pdf/sofLware_LesL_planŦpdfŦ
Ŧ Codard Space lllahL cenLerŦ CoJotJ 5poce lllobt ceotetŦ żCnllneŽ żClLedť Apr 23ţ 2011ŦŽ hLLpť//swŴ
assuranceŦasfcŦnasaŦaov/dlsclpllnes/quallLv/documenLs/pdf/sofLware_quallLv_assurance_planŦpdfŦ
7Ŧ llorldaƌs SLaLewlde SvsLems Lnalneerlna Ŧ llotlJoƌs 5totewlJe 5vstems £ooloeetloo Ŧ żCnllneŽ żClLedť Apr 23ţ
2011ŦŽ hLLpť//wwwŦflorldalLsŦcom/SLMÞ/llles/Þul_8eporL/Apx!ŦpdfŦ
8Ŧ exLreme SofLware 1esLlnaŦ e\tteme 5oftwote 1estlooŦ żCnllneŽ żClLedť Aprlll 23ţ 2011ŦŽ
hLLpť//exLremesofLwareLesLlnaŦcom/Ŧ
9Ŧ SofLware 1esL Þlan Ŵ nASAŦ 5oftwote 1est lloo Ŵ NA5AŦ żCnllneŽ żClLedť 0 23ţ 2011ŦŽ hLLpť//swŴ
assuranceŦasfcŦnasaŦaov/dlsclpllnes/quallLv/checkllsLs/pdf/sofLware_LesL_planŦpdfŦ
10Ŧ SofLware 1esL 8eporL Ŵ nASAŦ 5oftwote 1est kepott Ŵ NA5AŦ żCnllneŽ żClLedť 0 23ţ 2011ŦŽ hLLpť//swŴ
assuranceŦasfcŦnasaŦaov/dlsclpllnes/quallLv/checkllsLs/pdf/sofLware_LesL_reporLŦpdfŦ


MCSŴ17 | AsslanmenL 2 13

Annex A
TEST TEMPLATES
SAMPLE - A MASTER SOFTWARE TEST PLAN DOCUMENT (8)
CONTENTS
1. Ìntroduction
1.1. Purpose
1.2. Background
1.3. Scope
1.4. Project Ìdentification
2. Software Structure
2.1. Software Risk Ìssues
3. Test Requirements
3.1 Features Not to Test
3.2 Metrics
4. Test Strategy
4.1. Test Cycles
4.2. Planning Risks and Contingencies
5.1. Testing Types
5.1.1. Functional Testing
5.1.2. User Ìnterface Testing
5.1.3. Configuration Testing
5.1.4. Ìnstallation Testing
5.1.5. Volume Testing
5.1.6. Performance Testing
4.2. Tools
6. Resources
6.1. Staffing
6.2 Training Needs
7. Project Milestones
MCSŴ17 | AsslanmenL 2 1

8. Deliverables
8.1. Test Assets
8.2. Exit criteria
8.3. Test Logs and Defect Reporting
9. References


MCSŴ17 | AsslanmenL 2 17

SAPMLE - TEST STRATEGY DOCUMENT
CONTENTS
A good test strategy is the most important and can in some cases repIace aII test pIan
documents.
1. ÌNTRODUCTÌON
1.1 PURPOSE
1.2 FUNCTÌONAL OVERVÌEW
1.3 CRÌTÌCAL SUCCESS FACTOR
1.4 TESTÌNG SCOPE (TBD)
Ìnclusions
Exclusions
1.5 TEST COMPLETÌON CRÌTERÌA
2. TÌMEFRAME
3. RESOURCES
4.1 TESTÌNG TEAM SETUP
4.2 HARDWARE REQUÌREMENTS
4.3 SOFTWARE REQUÌREMENTS
5. APPLÌCATÌON TESTÌNG RÌSKS PROFÌLE
6. TEST APPROACH
6.1 STRATEGÌES
6.2 GENERAL TEST OBJECTÌVES:
6.3 APPLÌCATÌON FUNCTÌONALÌTY
6.4 APPLÌCATÌON ÌNTERFACES
6.5 TESTÌNG TYPES
6.5.1 Stability
6.5.2 System
6.5.3 Regression
6.5.4 Ìnstallation
6.5.5 Recovery
MCSŴ17 | AsslanmenL 2 18

6.5.6 Configuration
6.5.7 Security
7. BUSÌNESS ARES FOR SYSTEM TEST
8. TEST PREPARATÌON
8.1 TEST CASE DEVELOPMENT
8.2 TEST DATA SETUP
8.3 TEST ENVÌRONMENT
8.3.1 Database Restoration Strategies.
9. TEST EXECUTÌON
9.1 TEST EXECUTÌON PLANNÌNG
9.2 TEST EXECUTÌON DOCUMENTATÌON
9.3 PROBLEM REPORTÌNG
10. STATUS REPORTÌNG
10.1 TEST EXECUTÌON PROCESS
10.2 PROBLEM STATUS
11. HANDOVER FOR USER ACCEPTANCE TEST TEAM
12. DELÌVERABLES
13. APPROVALS
14. APPENDÌXES
14.1 APPENDÌX A (BUSÌNESS PROCESS RÌSK ASSESSMENT)
14.2 APPENDÌX B (TEST DATA SETUP)
14.3 APPENDÌX C (TEST CASE TEMPLATE)
14.4 APPENDÌX D (PROBLEM TRACKÌNG PROCESS)

MCSŴ17 | AsslanmenL 2 19


SAMPLE - TEST EVALUATION REPORT DOCUMENT
CONTENTS
1. Objectives
2. Scope
3. References
4. Ìntroduction
5. Test Coverage
6. Code Coverage
7. Suggested Actions
8. Diagrams

SAMPLE - QA PLAN DOCUMENT
CONTENTS

1. ÌNTRODUCTÌON
1.1. OVERVÌEW OF PROJECT X
1.2. PURPOSE OF THÌS DOCUMENT
1.3. FORMAL REVÌEWÌNG
1.4. OBJECTÌVES OF SYSTEM TEST
1.4.1. QUALÌTY ASSURANCE ÌNVOLVEMENT
2. SCOPE AND OBJECTÌVES
2.1. SCOPE OF TEST APPROACH - SYSTEM FUNCTÌONS
2.1.1. ÌNCLUSÌONS
2.1.2. EXCLUSÌONS
2.2. TESTÌNG PROCESS
2.3. TESTÌNG SCOPE
2.3.1. FUNCTÌONAL TESTÌNG
2.3.2. ÌNTEGRATÌON TESTÌNG
MCSŴ17 | AsslanmenL 2 20

2.3.3. PERFORMANCE TESTÌNG
2.3.4. REGRESSÌON TESTÌNG
2.3.5. LOAD/STRESS TESTÌNG
2.3.6. BUSÌNESS (USER) ACCEPTANCE TEST
2.4. BUÌLD TESTÌNG
2.4.1. ENTRANCE CRÌTERÌA
2.4.2. EXÌT CRÌTERÌA
3. TEST PHASES AND CYCLES
UNÌT TESTÌNG (CONDUCTED BY DEVELOPMENT):
ÌNTEGRATÌON/FUNCTÌONALÌTY TESTÌNG:
REGRESSÌON TESTÌNG:
NEGATÌVE / POSÌTÌVE TESTÌNG:
AD HOC TESTÌNG:
PERFORMANCE TESTÌNG:
3.1. ORGANÌZATÌON OF SYSTEM TESTÌNG CYCLES
3.2. SOFTWARE DELÌVERY
3.3. FORMAL REVÌEWÌNG
4. SYSTEM TEST SCHEDULE
5. RESOURCES - TESTÌNG TEAM
5.1. HUMAN
5.2. HARDWARE
HARDWARE COMPONENTS REQUÌRED
5.3. SOFTWARE TEST ENVÌRONMENT SOFTWARE
ERROR MEASUREMENT SYSTEM
6. ROLES AND RESPONSÌBÌLÌTÌES
6.1. MANAGEMENT TEAM
6.2. TESTÌNG TEAM SETUP
6.3. BUSÌNESS TEAM
6.4. DEVELOPMENT TEAM
MCSŴ17 | AsslanmenL 2 21

7. ERROR MANAGEMENT & CONFÌGURATÌON MANAGEMENT
8. STATUS REPORTÌNG
8.1. STATUS REPORTÌNG
9. ÌSSUES, RÌSKS, AND ASSUMPTÌONS
9.1. ÌSSUES/RÌSKS
9.2. ASSUMPTÌONS
10. FORMAL SÌGNOFF
11. ERROR REVÌEW
11.1. PURPOSE OF ERROR REVÌEW TEAM.
11.2. ERROR REVÌEW TEAM MEETÌNG AGENDA.
11.3. CLASSÌFÌCATÌON OF BUGS
11.4. PROCEDURE FOR MAÌNTENANCE OF ERROR MANAGEMENT SYSTEM.
11.5. QUALÌTY ASSURANCE MEASURES
(Ì) DATES.
(ÌÌ) EFFORT.
(ÌÌÌ) VOLUME.
(ÌV) QUALÌTY.
(V) TURNAROUND.

MCSŴ17 | AsslanmenL 2 22

SAMPLE - USER ACCEPTANCE TEST (UAT) PLAN TABLE OF
CONTENTS
1. ÌNTRODUCTÌON
1.1 PURPOSE
1.2 FUNCTÌONAL OVERVÌEW
1.3 CRÌTÌCAL SUCCESS FACTORS
1.4 UAT SCOPE
1.5 TEST COMPLETÌON CRÌTERÌA
2. TÌMEFRAME
3. RESOURCES
3.1 TESTÌNG TEAM
3.2 HARDWARE TESTÌNG REQUÌREMENTS
3.3 SOFTWARE TESTÌNG REQUÌREMENTS
4. TEST APPROACH
4.1 TEST STRATEGY
4.2 GENERAL TEST OBJECTÌVES:
4.3 BUSÌNESS AREAS FOR SYSTEM TEST
4.4 APPLÌCATÌON ÌNTERFACES
5. TEST PREPARATÌON
5.1 TEST CASE DEVELOPMENT
5.2 TEST DATA SETUP
5.3 TEST ENVÌRONMENT
6. UAT EXECUTÌON
6.1 PLANNÌNG UAT EXECUTÌON
6.2 TEST EXECUTÌON DOCUMENTATÌON
6.3 ÌSSUE REPORTÌNG
7. HANDOVER FOR UAT ACCEPTANCE COMMÌTTEE
8. ACCEPTANCE COMMÌTTEE
9. DELÌVERABLES
MCSŴ17 | AsslanmenL 2 2

10. APPROVALS
11. APPENDÌXES
11.1 APPENDÌX A (TEST CASE TEMPLATE)
11.2 APPENDÌX B (SEVERÌTY STRATEGY)
11.3 APPENDÌX C (ÌSSUE LOG)

MCSŴ17 | AsslanmenL 2 2

SAMPLE - SOFTWARE RISK MANAGEMENT DOCUMENT
CONTENTS

1. Ìntroduction
2. Terminology.
3. Risk Sources
4. Understanding the Risk
5. Risk Management Process Flow
5.1 Ìdentifying the Risk
5.2 Analyze Risk
5.3 Risk Planning
5.4 Risk Tracking
5.5 Risk Controlling
5.6 Retiring Risks
6. Status Strategy:
7. Process Dependencies
8. Process Summary
9. Approvals
10. Appendixes
10.1 Appendix A 'Top 10 List template'.

MCSŴ17 | AsslanmenL 2 23

SAMPLE - SOFTWARE LOAD TEST PLAN TABLE OF
CONTENTS
1. Ìntroduction
1.1 Purpose
1.2 Background
1.3 Scope
1.4 Project Ìdentification
2. Test Requirements
3. Test Strategy
3.1 Test objective
3.2 Type of test and type of virtual user
3.3 Test Approaches and Strategies
3.3.1 System analysis
3.3.2 Define the detailed testing check list
3.3.3 Developing Test Scripts
3.3.4 Creating test scenario
3.3.5 Monitoring Performance
3.3.6 Analyzing test result
3.4 Other Considerations
4. Resources
4.1 Workers
4.2 System
5. Project Milestones
6. Deliverables
6.1 Test Configuration
6.2 Test Logs
6.3 Test Reports

$ %#%$% &%%  8832039 -0.9;0   $:7;0 %0893 4.:2039,943 !7,.9.08 3 ;4:0 ,9 ,3 2,47 8419,70 172  

4704;07 57080398 ,3 8,250 9025,908 41 /1107039 47,3,943147 9089 /4.:2039,943 ,;,,-0   -897,.9  %0893 8 ,3 25479,39 5,79 41 /0;0452039, 574.088  3 ,9071, 24/0 9 8 ,

/893.9 5,80070,8 ,8 3 4907 574.08808 9 802-0//0/ 394 90 574.088  %0 -,8. /0, 41 90893 3;4;08 90 00.:943 41 8419,70 ,3/ 90 4-807;,943 41 98 -0,;47 47 4:9.420  1 , 1,:70 8 4-807;0/  90 00.:943 70.47/ 8 ,3,0/ 94 4.,90 ,3/ 1 90 1,:9 8  9,9 .,:80/ 90 1,:70  90780  9 3/.,908 9,9 90 8419,70 :3/07 90893 8 24700941:198/083,90/1:3.9438  5  %00110.9;090893300/8,1472, 574.088 8:55479 ,3/ 0110.9;0 00.:943 41 90893 706:708 84:3/ 5,333 ,3/ /4.:2039,943   3 5:78:,39 94 90 ,8832039 4-0.9;0  80;07, 8419,70 172 3.:/3 .748419  

 $:3 2.74 889028  4, ,3/ 4, 070 .438/070/  %0 31472,943 ,;,,-0 974: .425,3 0-8908 ,3/49073/70.9 84:7.08 ,8 .40.90/ ,3/,3,0/  %080 84:7.08 43 574;/0 ;07 -74,/ 31472,943 ,-4:9 90 8419,70 %0893 %448 ,3/ %0.36:08:80/-908017281478419,7090893,3/850.1.31472,943,-4:990893 /4.:2039,943902,39,30/8349/70.9,;,,-0  88:25943  0 /09,8 41 90893 ,3/ 90893 /4.:2039,943 3 ;4:0 ,9 ;,74:8 1728 ,70

.431/039,  80;07, 3/70.9 84:7.08 3/.,90 9,9 2489 41 90 8419,70 1728 :80 :8942 %0893 4.:2039,943 $9,3/,7/8  4704;07  9080 57,.9.08 ,70 70,9 31:03.0/ - %08934.:2039,943$9,3/,7/        

:20398 9.84/0130890:80.3/.7/ /0.70 .:94341574.0/:70 342. 809 41 -..3/.088 .943  9 /08.98 41 8419.7-08 .3/. 9089 /4.:2039.:20398 .943 %089083 %089.4/0 9.   %0894.884.850.2.:2039.#05479 %089 4 0.943$9.80 %089!74.439039841 70.:2039.3/ 90893 /4. .0/:708.3/.9 .8.8907%089#05479 090/4.3/.90/ 9 90 /3.90/9089/4.0%089#05479 39072%089#05479 .8 9 90893 574.70 90893  0 9000.7/  %0 89.

 $¾¾–°¯ °   .

07./08. 8419.70 -.-094 490790893.70 -03 /0.90893  80.3/ 8419.-0.3/.908   %8 89.39.7/ .7-0/390 89.7/14.6:70/  4507.2.9.3/.5508 94 .3/.419022..55.30/  ..90/  2.0450/  .:843/3.5508 94 889028 .80/ 889028  9 ..

.08808  ..88 94 -0 50714720/  %0 35:98 .3/ 4907 .43..//70883/090723388902.943 41 90893 9.-9  . 11 90 $01  %$  4.88  .3/ 4:95:98 41 90 3/.94389.:7.4.8 300/0/ -.42203/0/ 232:2 90893 9.55.. 708:9  2470 9089 /4..08     .943300/0/ 390798419.80/ 43 90 90893 9.943 %089.438/07.4250903088  .08808.3/ .8..3/ 8419.943899049075.070/3 .3/9.7/:808 90 .:20398    %0/4.4. 2470 7474:8 .39940.47 70:80/ 0   0.3/.04:9 70.  24/10/  42207.88  %0 574.3/983907.7/8850.4390398 %05:75480.9:70.9028 8 ( 03.798419088902 %889.943  .:2039..3/.:80  41 90 89.0790895.3/ 90897054793    .7057080390/3 8:-806:03980.-0 708:9.059 41 39079 0.1.:2039.3/ 90 .99089574.:2039.3/ 9089.70.  .$419.70706:708.9438   %8 89.114:7390790.88.:203984:930/39889.943 /03910/ .70780941 9089 574.42203/0/9089/4.  .43903988 .3/..3/..333 9089850..43/:.0452039.:808 .7//039108 9088902.55.088800.997-:908 0   .94341.3/.8.9438 .088 9825479.:808  070.08 94 /0907230 9070...:2039.8 .3/4:930897:.90/ 90893 9.4388903.7/ 8 3.0732039 11 90 $01  %$  47 43 0.88/0391909089/4.230 908419.39 9089 /4.93909089574.93088 .70 .4770.7/.70%0894.:2039.03947 41 90 9089 /4.

 $¾¾–°¯ °   .

  .

 $¾¾–°¯ °   .

0         – f °€¯   ¾f½½nf  ° n° €° ¾f° f    .:2039. :70%0894.943#0.

 $¾¾–°¯ °   .

9:70 $%#%$%! &%  3974/:.08 41 9089 0907 93 430 5740.8  09.943    .088:22.450   #010703.9 47 .059    ./0 .8907 %089 !.3   %089574.3 8.3 %!  8 94 574.98   9089 5.02039419089011479   !74.36:08 2094/8 .890790898.9.333 .0/:0   390790.088. 9089 5.3/2097..07.:/3/0139434190890.:2039 147 2:950 0.943.8907%089!..9.9!.9.07.0452039    .9.3339089   !74.088083.3 %!  %0 5:75480 41 90 .08   !74.0.6:8943    ..9.0880.9:708   %0894.08.9.02039 /4.0    7.6:89438:554799089   !74.3.3 4.3/010.9.9389.07.84190.08   $89024.943   4.3.  ...943.9083    .7   #085438-908   %448 90.   #084:7.9%089    .088$:55    .8907 %089 !.9.9.0901443897:.943   .3.9#06:7020398    .7488 2:950 5740.02039    .088.9.:2039/039107   $.92502039.3/ 9089 2.02.3.9.

9.943    .4:9   !74.108 147 0.9.943706:7020398   %089.943.08  .09089   %089/4.30574.0%089!.:2039.3903..0 41 .9./23897.7   4..9089   !74.   488.0    .450  .9.:2039.908 147 98 850.943706:7020398   %0897054793706:7020398  0307.088 507..3 8  $50..088.3/8947  -  0.5574.. %! 90 8.3.  7084:7.0/:708.9 507.0/:0 41 90 90893 .0.3/ 8.3.3903.10/ 0.

 $¾¾–°¯ °   .

9089.  9025.07.9:70894-090890/ 9090893 9.8808.0/ - 90 47..03904.88.3 425430393907..-9.0.8  .:20390/ - 90 5.3 0  42543039%089!.9:70894-090890/  0.3/4..04190895..3/907/0391078  %089%7.3  90 47/ 0.97  0.0   %089..3 $8902 %089!.3 .:.08   0.:2039/039107   $.943%089!.0  8 705.3/.943 8 3.90/ 78 8  3 90 990 41 90 5.79.943   4.884.806:03.0%089!.7 0.059..3/ 90 .90893 /0391909028-0390890/ 9010.3.450   #010703.8147980. 9.9:70834994-090890/  5574.8144  '%$%! &%  3974/:..07.0 -03 /4.3.88 94 -0 50714720/  90 50784330 7085438-0 147 0.20 147 90 5.43/9438  09.3 %04:9308.3  %0899028.

  $:8503843.3.1...7432039..9.7907.3/9.-08  %0892.330/.07.7907.02039  !.889089574708843  3.3/708:25943706:7020398  %089/0.908.

..08.3.439303.4.79083.884.88:7.0574.:2039.1. 8   0307.  ":.3/8947  .5574.9.9:70894-090890/-98 /083.4.4..0/:708.:9479  39071.0/:08 0892..  0.07.370130203984190 9089.7  4.3/907.8144   .943  %7.90/90898 %04:9308.3/.3/94/03919010.30574..0%089083 %05:754804190%894850.08.33  $.243905.4898  #8 8 .3/.9:70  #085438-908.908 .3/98.3/.897:.8  %089.0  488.317. %!$0.0/  #084:7.0/:708  097.943  .

 $¾¾–°¯ °   .

0 %089 .8 9 5079.884.38 94 35:98 94 .  90 31472.80 8  /03910/ - 90 .943 300/0/ .3/ 4:95:98 1742 90 8419..80/ 88902 -03 90890/  %0 % 3.80  %0 5:75480 41 90 % 8 94 /0130 . 9089 .0 41 /09.90/ 802039 41 90 % 1 9070 8 430  %0 4:9308.8144  I@@.:/08 .70 -.I@@-D@-  ° n°   n¯ ° °€    n½     €  °n ¾   f¾€   @ ¾ ¾–°    f ¾  ¾    ½½fn €° ¯ °¾   @ ¾ °€nf°    f ½f¾¾$€fn f  @ ¾  f  ¾   ° f   ¾¾f   n¯ °nf°– ½n  ¾f° ¾   /  0.557457.3 .70 47 8419..90 0.

D@-  ° n°%°n ½  n¯ °%   n¯ ° °€    n½     €  °n ¾   .

°    -f°€ ¾n½°   f¾%°n ½  ¾nf¾ %   @ ¾nf¾  °€     © n    °½¾   n¯ %¾%   °°¯ °f° ¾   ½ nf½n f  ¯ °¾   °  nf¾  ½ ° °n ¾   f%°n ½  n¯ °%   ¾¾f   n¯ °nf°– ½n  ¾f° ¾   .

 $¾¾–°¯ °   .

:.3 %! 8 94 850.:93 .9:708 %04:9308.0%089!74.90 . 8419.1 90 89058 147 00.0/:70 %0 5:75480 41 .80/ 88902 902 3 47/07 94 0.808 47  2470 0307.9 47 8419.70 -.70 574/:.0  0. 809 41 9089 ..  90 89058 :80/ 94 007.80 . 809 41 10..8144  I@@9.

DD@-  ° n°   n¯ ° °€    n½     €  °n ¾    f°¾½ ½n  ¾   f¾   °½¾ ½¾ f° ¾½ nf  ¯ °¾      ¾n½°€ ¾ ½¾ f °  n   ¾nf¾ ¾   ° f   ¾¾f   n¯ °nf°– ½n  ¾f° ¾   .

 $¾¾–°¯ °   .

:943 41 90898  3 .30. 475.-0.8144  -.-4:9 9000.0889.943 %82.74344.#05479 :930 %05:754804190#894/4..8.9 4.:78/:739090893574..:942.. 574-02 90893.59:70 .0/.8144  I@@D@-  ° n°   n¯ ° °€    n½     €  °n ¾   f¾    ¾n½°   nf°   ° ° ¾   ° f   ¾¾f    342.0%0894 %05:754804190%894574.1  0.79419831472.:2039..9 974:-0 88:0 .90/ 944 2.70../0./039 /010.943 %04:9308. .39 /09.342.9706:7083.47/41 700.9@D@-  ° n°   n¯ ° °€    n½     €  °n ¾   f¾   ¯¯f   f f°¯f ¾n     .089.0399. 4707747705479 %04:930 8..

°     ¾n½°€f°¯f   ¯½fn   –°f#¾f¾¾ ¾¾¯ °€– °n%¾    %    ¾n½°€ n n fn°   f¾€ f°¯f   .

039072%089$9.9:8#05479 :930 %0 5:75480 41 90 %$# 8 94 8:22..80/ 43 9080 708:98  9 8 .9438 .3/ 45943.90/ 90893 .70 90 708:98 41 90 /083.°n¾°¾f°  n¯¯ ° f°¾   ° f  n¯ °nf°– ½n  ¾f° ¾    0.42203/. 94 574./0 0.908 .3/ 70..9438 -.9.:.

 $¾¾–°¯ °   .

0 41 /09..7 94 705.9:8 #05479  %070 8 430 /0130/ 1472.9 147 90 %$# 147 0.3.:2039 9 90 47.9 3 90 0.3..7 9089 0.8144  I-@..:. 9089 0.79.0 90 47/ 0.0 /03910/ - 90 47.7 70.0  3 90 990 41 90 /4.  %0 4:9308.0  0   .20 147 90 5.943  %0 2.0 39072 %089 $9.3.. ..943 8 3.@@@@D9@D@-  ° n°   n¯ ° °€    n½     €  °n ¾   f¾   @ ¾¾f¾¾¯¯f   .:8942.059.

914790%$#1470.:203999047.041/09..7 94 705.3/ 94 574. .0  0   .0 3909904190/4.79.20147905.943 %02.70 90 708:98 41 90 /083..059.3.90890.f°– ¾€¯½f°¾   @ ¾¾f¾¯ n¾   ° f   n¯ °nf°– ½n  ¾f° ¾    0.0 90 47/ 0.943 83.908 .0 39072 %089 $9.8144  I@@9@D@-  ° n°   n¯ ° °€    n½     €  °n ¾   f¾     € ¾ ¾¾    f  ¾ ¾¾   f°f € n¾°¾   .3/ 70.3.:.42203/..:8942..93900.90/ 90893 .9438 -.9:8 #05479  %070 8 430 /0130/ 1472.:..3.80/ 43 9080 708:98  9 8 .0/03910/-9047.9438 . %04:9308./0 0.7 9089 0.9.0 %089 #05479 :930  %0 5:75480 41 90 %$# 8 94 8:22..770.

°n¾°¾f°  n¯¯ ° f°¾   ° f   ¾¾f   n¯ °nf°– ½n  ¾f° ¾  .

 $¾¾–°¯ °   .

.08  %0 2.90890. 2070 7054798 147 2:950 0.3...9438 .9.943475740.:.-02:. .0/ %0 4:9308.3.059.42203/.3.:.059.89.:2039.f¾ @ ¾ ½     €ff–– –f  ¾ ¾¾   f°f € n¾°¾   .7 9089 0.3/ 94 574.7 94 705.80/ 43 9080 708:98  9 8 .0/0130/-9047..0%089 #05479  %070 8 430 %# 147 0.3.880/ 471./0 0.995.:8942.9438 -.3.2470/09.9 $2.0 0   ..908 .70 90 708:98 41 90 /083.0/ 070. 41 /4.  ..&39%089#054792.20 147 90 5.3/ 70.8907%089#05479 :930  %0 5:75480 41 90 0.90/ 90893 .09047/ 0..8.7 70.0 %089 #05479 %#  8 94 8:22.5740.:203999047.825-0.9020399.943 83.9 3 90 0.0 3909904190/4.943 0  .@@@9@D@-  ° n°   n¯ ° °€    n½     €  °n ¾   f¾€ .79.0%089#054792.98 2.0 41 /09.8144  .

80/ 43 $ $2.700.7:98   %089 33007 0.3/341490 574.83 9400.3/ 0.288074:8.79:.90 8.4393:08 94 9.748419 .98 4.790/.70/943/:89734728  0 ..5574.-09907:3/0789.748419 70.:36:0.07.0 . /43 94 90 990 0 . 5740.748419 .0452039330073%089 $% /083 989908.5574.°n¾°¾f°  n¯¯ ° f°¾   ° f   ¾¾f   n¯ °nf°– ½n  ¾f° ¾  $419.425.250  .5574.0 9089078$419.748419 574/:. 90 .20 .045078  .748419    .42570038.  $     .8 90 $419..0 574.2 147 %089 330078 5    .3  %0 .07 .8 5490/ 80.33 5747.7090893 .08.020395747. 9089078  %8 :36:0 .02039 5747.3/ 0 025.045078  .7 .80 8419. 408 .088 2574.948419..89 10 0.08 -.07 90 5.3/ .78 :83 .3/4190390895747.341!74.0882574..3  .98  47 0./4590/.088 4:/ 47 43 ..70%08939.70 0.70 0330073 88 9 .280    $2.07 0.7484199.3 /0.0 97.748419.289409.3/ 0. .0 2470 9089 0330078 9.0452039 33007 990 :80/ 147 /0.

 $¾¾–°¯ °   .

3/.90 3 :83 9080 .:2039 708:98  . .9 9 :808 .897.07  9 .:2039.943 ..3/ 9089 /4.0452039 574...998/0.3/$$2.3/ 4 -089 94 .9  3 2489 .9089 ..3..08808  .08808 . .:20390/ .8 .0.088 90/4.70 .43.9434189058..289.  90 8:55479 98 2.9. 5     .8 147 6:.-0 3 4503 907..:8942 89./.0 8 94 :3/0789.00/89080    .:2039.0452039574.0-0900390/08701476:.3.0.943  ...470 $  89.943 41 /0.748419 1448 .-0 574.7/ 147 9089 /4.9 574.5574.70 349 .2 .8 0 .:2039.-.08 94 70.748419.708:98.8 /4.3 -0 310770/ 9.:89420/ 809 41 89.3/ 9.7/8 .088 3 /4.4390 .3/. 0020398 41 90 .02039 90...9:70  40.3/.3/ 7050.39.3/ 90 3899:943.3.9 /09..7/8 147 90893 .808 920098470./0 9 $ .3/90747410. .

9081742$        .9144338   43.3/.79   %0.7090899025.3/ $:3 .943  %080 89..8 5073309498/4.70:83907 .9 .74 $89028  9 .70780.9081479089 /4.3/ 49078    .7070.3 57080390/ 9025808 41 90893 574.0/1742   9089/4.088 3 .943 89.4250903088 9025.7/814790893/4.  !.7/8.9438 4790 8.808.:2039.7/8 909025.:843   .990808419.20.908.908174297020$419.84157080390/30. 41 90893 574.70%08933.0/-9089..:2039.80/ 43 $ .708.8-003/07.708:-2990/384191472 %0809025.3/.88 41 7080.4:0 .3/ 4390 -.:89420/ 89.3/..3 -0 310770/ 9.041...:20398324894190.398.425.70.08808 41  .7.7/     %089%025..7/8 .:2039 $419.908 82039430/0.:89429089/4.707 .:2039.3/.308:80.-0.70.3/.907..748419 .94389.70 -..7057080390/3.931:03.

7/8          .3/.:89420/ 90 89.7/8 94 .0 6:.0/ 1742    89.79   ..3/.3/. 9801 8 /07.39.0.339074741908089. 708:9802..7/  489 41 90 1728 .0 .  !.

 $¾¾–°¯ °   .

n¾€    $.n¾€ ¾   .f°–° °–@ ¾°– .   €€ @f° €f .f¾¾f°n f° ¯½ ¯ °   f° 9f– ° J  ¾€f .

€f @ ¾°–  °°  .

 f½   ½ $$¾€f  ¾°–¾f° f –$°  ½½ $.

     €f °–° °–@ n°nf.

¯¯ €n¯½  f° f €€f @ ¾ n¯ °f°     f ¾½fn €–n °  €f f¾¾f°n   °°  .

 ½  ½ $$¾ f¾¾f°n –¾€n °f¾f –$ ¾n½° ¾$f$n n¾¾$½ €$¾€f % ¾%½f° ½ €    f ½fn –n °   f ½fn –n °   °°  .

 ½  ½ $$¾ f¾¾f°n –¾€n °f¾f –$ ¾n½° ¾$f$ n¯ °¾$½ €$¾€f %f%f¾¾f°n %½f° ½ €    f ¾f  ¾ ¯¾°–° °–  f ¾f  ¾ ¯¾°–° °–  °°  .

 ½   ½ $$ € f¾ n¯$.9$ ¾$9% ½$½ ½ €    O ¯ €f @ ¾°–  O ¯ €f @ ¾°–  °°  .

 ½   ½ $$  ¯ ¾€f  ¾°– n¯$   €f @ ¾9f° - €f @ ¾9f° -  °°  .

   ½ $$¾ f¾¾f°n –¾€n °f¾f –$ ¾n½° ¾$f$n n¾¾$½ €$¾€f % ¾%½f° ½ €   €f @ ¾ ½ - €f @ ¾ ½ -  °°  .

   ½ $$¾ f¾¾f°n –¾€n °f¾f –$ ¾n½° ¾$f$n n¾¾$½ €$¾€f % ¾% ½ ½ €     .

 $¾¾–°¯ °   .

70#888:08   %089#06:7020398  0.0%0893   %448       #084:7.08   $9.333#88.08    !.9/0391.3300/8   !740.8  %089$97.90   %089.943   $419..9:70    $419.330 %$%%!%$ $! $%#$ %#%$%! &%    %%$  3974/:.74:3/   $..113   %7.90894308       .943.%0893     &80739071..943%0893     '4:20%0893     !071472.450                !740.3.943%0893    389.08    %0893%508                   :3.3/439303..0%0893    431:7.943   !:75480   .9:7084994%089  097.70$97:.

 $¾¾–°¯ °  .

7907.07.3/010.9#054793  #010703.08    .           %08948. 0.-08   %08988098   9.

 $¾¾–°¯ °   .

:20398            %# &%  !&#! $  &%  '#'   #%$&$$% #  %$%$ ! %    3..338420.$! %$%$%#% &%  %%$ 44/9089897..90895..07  .0.:8438 .39.3/.-9    $8902    #0708843     389.943     #0..4.808705.:8438                            %$% !% #%#  %# #$ &#$  %$%%$%&!  ###"&#%$  $ %##"&#%$  !!% %$%#$$!#  %$%!!#   $%#%$   #%$% %'$  !!% &% % !!% %#$ %$%%!$        $9.90890248925479.3 /4.

 $¾¾–°¯ °   .

943     $0.-.80#08947.943$97.9.   431:7.:79            &$$$#$ #$$%%$% %$%!#!#%    %$%$' !% %$%%$%&! %$%'# %      .9008            %$%&%  %$%&% !  %$%&%  &%%  !# #! #%  $%%&$#! #%    %$%&% !# $$    !# $%%&$            '# #&$#!%%$%% '#$ !!# '$ !!$      !! &$$$!# $$#$$$$$%    !! %$%%$%&!       !! %$%$%!%    !! !# %#!# $$    .

 $¾¾–°¯ °   .

07.07.9.7.9438  .08  $.0    4/04.08  3974/:.943  %0894.0   $:0890/. $! %$%'&% #! #% &%  %%$   -0.28   $! "! &%  %%$   %# &%     '#' !# %   !&#! $ %$ &%     ##'      %'$ $$%%$%     "&%$$&#' '%  $ ! %'$     $ ! %$%!!#  $$%&% $     &$ $    &$ $    %$%!# $$    %$%$ !     &% %$%     %#% %$%  .450   #010703.

 $¾¾–°¯ °   .

   !# #%$%    ##$$ %$%      .

$%#$$%$%      &$$$ &$# !%%$%   &%$%       %##%#    %#%#   %$%!$$$ &%%$%  &%' !%  %#% .

&% %%$% ##$$ %$% %'.

! $%'%$%  %$% !# #%$%    #%  $$%%$%$   $ %#'#    ##'     $$%%$%$&   #$ &#$ %$%%   &    ##  ## ! %$#"&#      $ %#%$%'# %$ %# ## #$&#%$$%  # $#$! $%$   %%   %$%%$%&!   &$$$%         ' !%% .

 $¾¾–°¯ °   .

 ## #%  &#% %   $%%&$#! #%    $%%&$#! #%    $$&$ #$$ $$&!% $   $$&$.

#$$   $$&!% $   #$   ## ##'      !&#! $ ## ##'%     ## ##'%%     $$%  &$     !# &# #% ## #%$$%    "&%$$&#$&#$  %$     #%   ' &  ' "&%     ' %&## &    .

 $¾¾–°¯ °   .

$! &$#!%%$% &% !%   %%$                                                       %# &%  !&#! $  &%  '#'   #%$&$$% #$ &%$ ! %$% !% #%#  %# #$ &#$ %$%%     ##%$%#"&#%$ $ %#%$%#"&#%$ %$%!!#   %$%$%#%  #%$% %'$  &$$$#$ #$$%%$% !!% %#$ %$%!#!#%      %$%$' !% %$%%$%&! %$%'# % &%&%   !&%&%     %$%&%  &%%  $$&#! #%   '# #&%!% %% !% %% '#$  .

 $¾¾–°¯ °    .

    !!# '$ !!$      !! %$%$%!%    !! $'#%$%#%     !! $$&      .

 $¾¾–°¯ °   .

08   !74.02039!74.90     ..3/390#8   #8.0#8 #8!.0884             /0391390#8  3.3 #8439743 #0973#88      $9.90   !74.3.8   5503/08    5503/ %45 899025.$! $ %##$% &%  %%$   3974/:..7  5574.333 #8%7.08     &3/0789.9:8$97.0880503/03.943  %072344   #8$4:7.088$:22.

 $¾¾–°¯ °   .

08.9438 #084:7.0.74    439473!071472.90  %0894-0.3/95041.9008      $8902.90894308  0.943 %089#06:7020398  %089$97.450 !740...74:3/  $.9390898.03.9/0391..0453%089$.08  47078 $8902       !740.7598    70.943  !:75480  .0/90893.0    3.:807 %0895574.0    %50419089.07.3/$97.943  %08948  %089#054798 .3.88    013090/09.9.89    0.3.39089708:9                      907438/07.79:.$! $ %# %$%!%   %%$                     3974/:.-08  %089431:7.

 $¾¾–°¯ °   .

Sign up to vote on this title
UsefulNot useful