1. System Test Planning SYSTTPLAN 1 Location of Test Planning Responsibilities for Test Planning Results of Test Planning Structure of a Test Plan Test Definitions Identifying Objects to be tested Identifying Functions to be tested Definition of the Test Exit Criteria Definition of the Test Results Definition of the Test Phases Definition of the Test Tasks 2 3 6 7 5 4 8 9 10 12 Definition of the Test Responsibilities Definition of the Test Environment Definition of the Test Resources Test Efforts Test Efforts according to Activity Type Test Efforts according to Phases System Test Effort Estimation Effort for the Calendar Test Test Plan for the Calendar Test Test Planning Metrics Estimating with Test-Points 13 14 17 18 16 15 19 20 21 11 22

2. Location of Test Planning SYSTTPLAN-1 Test Planning Test Conception Test Spec. Test Execution Test Evaluation Test Plan Test Concept Test Cases Test Results Test Docum. Closure Init Result of Test Planning Test Planning Initiates the test project

3. Responsibilities for Test Planning SYSTTPLAN-2 T e s t P l a n n i n g Project Manager Test Manager Test Team Manager

4. Results of Test Planning SYSTTPLAN-3 T e s t p l a n u n g Plan for the Test Project Standards RequirementsResources

5. Structure of a Test Plan SYSTTPLAN-4 According to ANSI/IEEE-Standard 829 Test Plan Identifier Test Plan Introduction Test Objects or Items Test Features Test Restrictions Test Strategy Test Acceptance Criteria Regression Test Criteria Test Deliverables Testing Tasks Test Infrastructure and Environment Test Responsibilities Test Staffing Test Schedule Test Risks and Contingencies Approvals 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16.

6. Test Definitions SYSTTPLAN-5 Component or System to be tested. Feature of the Software to be tested. Rule for the decision, if a test has passed or not. A set of input values, execution preconditions, expected results and execution post conditions, developed for a particular test. Document specifying a set of test cases for a test item (objective, inputs, test actions, expected results, preconditions) Amount of logically related Test Cases executed together in one single session. Document specifying a sequence of actions for the test execution. Each unexpected Event during the Test. Chronological report of details about the test execution. Test Object: Test Feature : Acceptance Criteria: Test Case: Test Case Specification: Test: Test Scenario: Test Event: Test Log:

7. Identifying Objects to be tested SYSTTPLAN-6 Job Procedures Programs Reports System Imports Databases Files Messages System Exports

8. Identifying Functions to be tested SYSTTPLAN-7 Create Order Item Create Bill Log Order Check Request Check Customer Order Item Create Reserve Check Item Ordering System

9. Definition of the Test Exit Criteria SYSTTPLAN-8 All program branches always are tested by 85%.(branch coverage) Each Database or File is confirmed by 90% of its fields (data field coverage) Each Function is tested at least two times (function coverage) All results are checked by 99% if they match the expected values. (result coverage) 1. 2. 3. 4.

10. Definition of the expected Results SYSTTPLAN-9 Unit Test  Test path report  Test result report  Test coverage report  Error report Integration Test  Test execution report  Interface report  Test coverage report  Error report System Test  System Lists  System export reports  File / Database reports  GUI reports

11. Definition of the Test Phases SYSTTPLAN-10 Integration Test Unit Test Acceptance Test System Test 1. Phase 2. Phase 3. Phase 4. Phase

12. Definition of the Test Tasks SYSTTPLAN-11 Generation of the Test Databases Preparation of the System Inputs Preparation of the expected Results Description of the System Results Setup of the System Environment System Test

13. Definition of the Test Responsibilities SYSTTPLAN-12 Generation of the Test Databases Setup of the Test Environment Preparation of the expected Results Description of the Test Scenarios Lisa Robert Eva Harry

14. Definition of the Test Environment SYSTTPLAN-13 IBM Host 3090 Windows NT - Client Windows NT - Clients CICS DCOM RS 6000 Server

15. Definition of the Test Resources SYSTTPLAN-14 Test Tools Operating System Database System HumanSoftwareHardware Test Workstations Calculation Capacity Disk Capacity Tester User Representative

16. Test Efforts SYSTTPLAN-15 Test Design= n 1 Hours per Test Cycle / Test Run / Use Case Test Specification= n 2 Hours per Test Case Test Execution= n 3 Hours per Test Procedure + n 4 Hours per Test Test Evaluation= n 5 Hours per Test Protocol + n 6 Hours per Error Message Test Management= (n 1:6 ) * Overhead Factor 1 2 3 4 5

17. Test Efforts according to Activities SYSTTPLAN-16 Test Planning Test Design Test Spec Test Execution Test Evaluation 45% 40% 35% 30% 25% 20% 15% 10% 5% 0% Test PlanTest Concept Test Scenario Test Environment Test Cases Test Procedures Test Results Test Info Test Protocol Error Messages % Test Effort 8% 12% 40% 25% 15%

18. Tester Test Efforts according to Phases SYSTTPLAN-17 Test Planning and Design Unit Test Integration Test System Test 45% 40% 35% 30% 25% 20% 15% 10% 5% 0% DocumentsModule Programs Components Sub Systems Application Systems % Test Effort 20% 36% 24% 20% Developer Tester Developer

19. System Test Effort Estimation SYSTTPLAN-18 = Number for Transactions or Use Cases = Estimated Number of Test Cases per Transaction or Use Case = Estimated Effort per Test Case = Number of Sub Systems= Effort per Sub System = Number of User Interfaces= Effort per User Interface = Number of Databases / Files= Effort per Database = Number of System Interfaces= Effort per Interface = Quality Factor = 2 - Quality Grade (0:1) = Number of Repeats = Repeating Factor = 1 - Degree of Automation (%) = Overhead Factor = (%) T 1 T 2 T 3 S 1 S 2 S 3 S 4 A 1 A 2 A 3 A 4 QF NR RF OF System Test Effort = {[( T 1 * T 2 * T 3 ) * QF] * [NR * RF]} + {[(S 1 A 1 ) + (S 2 A 2 ) + (S 3 A 3 ) + S 4 A 4 )] * (1 + OF)}

20. Effort for the Calendar Test SYSTTPLAN-19 T 1 = 5 Use Cases T 2 = 3 Test Cases per Use Case T 3 = 0,5 Hours pro Test Case Quality = 0,5 S 1 = 1 Sub SystemA 1 = 8 Hours QF = 1,50 S 2 = 1 User InterfaceA 2 = 4 Hours NR = 3 Repetitions S 3 = 1 DatabaseA 3 = 12 Hours RF = 0,50 OF = 0,30 Calendar Testing Effort = {[(5 * 3 * 0,5) * 1,5] * [3 *0,50]} + {[8 + 4 + 12] * (1 + 0,3)} Calendar Testing Effort = {[7,5 * 1,5] * 1,5} + { 24 * 1,3} Calendar Testing Effort = { 11,25 * 1,5} + { 31,2} Calendar Testing Effort = 16,8 + 31,2 Calendar Testing Effort = 48 Hours

21. Test Plan for the Calendar Test SYSTTPLAN-20 Confirm that each Employ can manage a Calendar with 52 Weeks, 7 Days per Week and 12 Activities per Day A Calendar GUI, A Database with 4 Objects Calendar  Weeks  Days  Activities Client/Server with Calendar on Server Use Case oriented Test Design, Test Case Specification, Test Execution, Test Evaluation Crate Calendar, Create Week, Create Day, Insert and Delete Activities, Delete Calendar Execute all Use Cases with all Paths, Trigger all Error Messages, Try to cause all System Breakdowns 48 Person Hours Test Goal: Test Objects: Test Environment: Test Strategy: Test Phases: Use Cases: Test Amount: Test Effort:

22. +----------------------------------------------------------------------+ | C O N C E P T Q U A N T I T Y M E T R I C S | | Number of Text Documents analyzed =======> 1 | | Number of Text Lines analyzed =======> 575 | | Number of Text Titles analyzed =======> 9 | | Number of Text Segments analyzed =======> 25 | | Number of Sentences contained in texts =======> 396 | | Number of Bullet Points contained in text=======> 77 | | Number of Words used in texts =======> 1859 | | Number of Nouns used in texts =======> 371 | | Number of Verbs used in texts =======> 413 | | Number of Conditions used in texts =======> 34 | | Number of Requirements specified =======> 16 | | Number of User Interfaces specified =======> 8 | | Number of User Reports specified =======> 3 | | Number of Objects specified =======> 105 | | Number of Objects referenced =======> 287 | | Number of Predicates specified =======> 58 | | Number of numeric Constants specified =======> 51 | | Number of Literals specified =======> 0 | | Number of States identified =======> 16 | | Number of Actions identified =======> 93 | | Number of Rules identified =======> 50 | | Number of System Actors specified =======> 8 | | Number of Use Cases specified =======> 6 | | Number of Use Case Triggers specified =======> 1 | | Number of Use Case Steps specified =======> 39 | | Number of UseCase Preconditions specified=======> 6 | | Number of UseCase Postconditions specified======> 6 | | Number of UseCase Exceptions specified =======> 6 | | Number of UseCase Attributes specified =======> 120 | | Number of Test Cases extracted =======> 167 | | | C O N C E P T S I Z E M E T R I C S | | Number of Function-Points =======> 211 | | Number of Data-Points =======> 884 | | Number of Object-Points =======> 682 | | Number of Use Case Points =======> 146 | | Number of Test Case Points =======> 201 | +----------------------------------------------------------------------+ Requirement Metrics from the Text Analysis SYSTTPLAN-21

23. Test Metrics from the Test Documentation SYSTTPLAN-22

24. Roll of Testing in the System Life Cycle TESTTPLN-24 Problem Solution Req. Spec Syst- Test Prog- Test UML- Diag. Accp.- Test Prog Mod- Test Testdata Testcases System- Analysis System Specification System Design Code- Production WHITE-BOX GREY-BOX BLACK-BOX Dynamic Analysis Static Analysis