1. Testing in SDLC

2. COURSE CONTENT - Summary Part 1 – Life Cycle / Processes / SDLC Part 2 – LC Management in Turkcell

3. Part 1 - COURSE CONTENT 1 – What is Life Cycle? 2 – What is process? 3 – Processes in Software Development Life Cycle (SDLC) 3 – SDLC in Turkcell 4 – Examples

4. What is Life Cycle ?

5. What is process? A path of succession of states through which a system passes Procedure, routine; course of action; advance; summons to court; program which uses some of a multitasking computer's system resources (Computers); projecting part in an organism Sequence of interdependent and linked procedures which, at every stage, consume one or more resources (employee time, energy, machines, money) to convert inputs (data, material, parts, etc.) into outputs. These outputs then serve as inputs for the next stage until a known goal or end result is reached.

6. Software Development Life Cycle (SDLC)

7. Software Development LC in Turkcell Request (Creation of Proposal & Domain Selection) Security& Compliance Approval Classification (FT or Projects) Request Improvement Document PMO  Project Manager Appointment Resource Management Analyse – Analyse Review Design – TDD Review Development – Code Review Test – Test Plan Review Deployment - RM BabySitting Period ???

8. Analyze Request Document Improving Request Document Analysis Document

9. Analysis Analysis is the process of examining Business and operation teams requests in details and determining which solutions will be applied to systems and how they are related to each other. Analysis Review Review process for Analyse Document with all project resourceses to detect if there is any involved or conflict issues.

10. Design – TDD review Problem - Solution compliance Effect and affected systems Compliance with standards The solution domain and the integration with other systems

11. Software Development Using a specific technology and infrastructure to provide the most effective and high quality solution

12. Code review Compliance with standards Compliance with design Information sharing between domain and team High qualified products and applications Early detection of bugs

13. Test Plan Review Control of test topics will be focused and run as a scope of the project Ensure to be used systems and its test groups matched Control of what kind of tests to be operated and by which method Test Whole test aktvities for project content; -Unit Test - Functional Test - Regression Test -User Acceptance Testetc.

14. Software Testing Process to determine that if the product has expected quality or not. If not, process used to ensure the delivery of the desired quality.

15. Purposes of Software Testing Improve customer satisfaction Protect the reputation of the company Finding bugs Time and cost saving

16. Reasons of Bugs Lack of communication Lack of development tools Lack of documentation Change Requests Insufficent analysis Coding defects Hardware problems Time pressure

17. Transfer to Operation Production Deployment request is opened AD, TDD, ODD, Test Reports are included into the request

18. Production Defects Analy sis Softw are Test Softw are Test Defect Severity Defect Resolution Time Critical7 days High15 days Medium30 days Low45 days PROD Code Defect PROD Analyse Defect

19. Request (Creation of Proposal & Domain Selection) Security& Compliance Approval Classification (FT or Projects) Request Improvement Document PMO  Project Manager Appointment Resource Management Analyse – Analyse Review Design – TDD Review Development – Code Review Test – Test Plan Review Deployment - RM BabySitting Period PhaseOut SDLC in TURKCELL

20. Part 2 - COURSE CONTENT LC Management in Turkcell 1 – Test Library Creating test case library and rules to be followed in preparing the test case 2 – Test Lab Scenario sets which will be held for the test 3 – Test Issue Error notification 4 – Dashboard Reporting of test data

21. TEST LIBRARY Test library; Application LifeCycle Management module that we write our test cases

22. WHAT IS A TEST CASE? A test case in software engineering is a set of conditions or variables under which a tester will determine whether an application or software system is working correctly or not.

23. TEST LIBRARY BENEFITS Security Easy accessibility Reusability Reporting

24. TEST CASE STANDARDS The purpose of the test case must have been written Test data should contain sufficient information Steps should be enough and understandable. Test results of the control method must be specified

25. TEST TYPES Unit Testing Functional Testing Integration Testing Interface Testing Destructive Testing Boundary Testing Documentation Testing Security Testting Performans / Stress Testing End-To-End Testing Adhoc Testing User Acceptance Testing

26. TEST CASE PRIORITIZATION Stands all the tests if scenario is not realized If test case is one of the basic scenario of product or service. Affects only a specific part of the product or service If the scenario has no functional effect (cosmetic scenarios).

27. TEST LAB The module containing the test case sets in order to test a particular product or service

28. TEST SET TYPES Unit Test Smoke Test Functional Test Business Analyst Test UAT Test Post Deployment Test

29. TEST SET STANDARDS Must be associated with the test request Choose the correct type of test phase Smoke Testing must be done. Fonksiyonel Testing must be done. Negative test should be done. Performans test must be done. Regression test set must be established Security test must be done

30. TEST ISSUE Topic is considered as the test issue If application or service produce an incorrect, unexpected results or present performance or security breaches

31. TEST ISSUE TYPES Code Defect Compiling Defect Label Defect Migration Defect Performans Defect Vendor Defect

32. TEST ISSUE STANDARDS Test data used must be specified Screenshot of the error must be attached Detailed logs should be given Error analysis of the scenario should be told

33. DASHBOARD In the Dashboard module, you create view and manage graphs, standard reports, and Excel reports for analyzing Quality Center data. You also create dashboard pages that display multiple graphs side-by- side.

34. ABOUT THE DASHBOARD MODULE The Analysis View tab contains a tree in which you organize all of your analysis items. Analysis items can be any of the following analysis types: graphs, standard reports, and Excel reports. The Dashboard View tab contains a tree in which you organize dashboard pages. In Dashboard pages you arrange multiple graphs that you created in the analysis tree, and display them in a single view.

35. EXAMPLE OF REPORT OUTPUT

36. EXAMPLE OF DASHBOARD OUTPUT

37. Management Board Sunum 15 Ağustos 2011 Management Board Sunum 15 Ağustos 2011