Test effort estimation

11,959 views

Published on

0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
11,959
On SlideShare
0
From Embeds
0
Number of Embeds
26
Actions
Shares
0
Downloads
714
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

Test effort estimation

  1. 1. Test Effort Estimation<br />
  2. 2. Why Test Effort Estimation<br />Expected Testing outcome<br />Effort <br />
  3. 3. Estimate of what ??<br />
  4. 4. Resources<br />Time<br />Skill<br />
  5. 5. Who does the Test Estimation?<br />
  6. 6. “Test Manager”<br />
  7. 7. Steps in Test Effort Estimation<br />1<br />2<br />3<br />4<br />5<br />6<br />7<br />
  8. 8. Identifying the Components to be Tested<br />1<br />
  9. 9. Common Components<br />GUI Controls<br />Screens<br />Functions<br />Reports<br />
  10. 10. Identifying a Test Strategy<br />2<br />
  11. 11. On what basis test strategies are formed?<br />
  12. 12. Based on the components indentified <br />
  13. 13. TestStrategy1<br />Functionality1<br />TestStrategy2<br />TestStrategy3<br />Functionality12<br />TestStrategy4<br />
  14. 14. Identifying the tasks to be performed<br /><ul><li>One time task
  15. 15. Repetitive activities</li></ul>3<br />
  16. 16. <ul><li>One time tasks</li></ul>Preparing test strategy<br />Understanding customer requirements<br />Establishing communication plan<br /><ul><li>Repetitive tasks
  17. 17. Identifying test condition
  18. 18. Developing Test cases
  19. 19. Generating Test Data
  20. 20. Reviewing test condition, test case, test data
  21. 21. Executing test cases
  22. 22. Reporting test results</li></li></ul><li>Computing software size<br />Based on complexity<br />4<br />
  23. 23. Levels of complexity<br /><ul><li>Low complexity
  24. 24. Web applications
  25. 25. Desktop applications
  26. 26. Medium complexity
  27. 27. Two tier/three tier application
  28. 28. High complexity
  29. 29. Multitier applications</li></li></ul><li>Estimating Test Effort<br />1<br />I<br />N<br />P<br />U<br />T<br />S<br />2<br />5<br />Test Effort<br /><ul><li>Durations
  30. 30. Infrastructure
  31. 31. Resources
  32. 32. Expertise requires</li></ul>3<br />4<br />
  33. 33. The estimate of test effort <br />Forwarded To<br />Management Team<br />Accept<br />Reject<br />
  34. 34. Preparing test plan based on inputs<br />6<br />
  35. 35. Test plan is prepared based on:<br />Scope of testing<br />Risk involved<br />Test completion criteria<br />Deliverables at different stages<br />Scope of defect management<br />Requirements for the test environment<br />
  36. 36. Validating the estimate at the end of project<br />All assumptions are re-validated<br />Done after the project <br />Determines if the estimate is correct<br />
  37. 37. Challenges <br /><ul><li>Lack of clarity
  38. 38. Inaccurate estimation
  39. 39. Delay in project delivery
  40. 40. Lack of proper test planning
  41. 41. Lack of testing expertise
  42. 42. Selection of wrong test data
  43. 43. Lack of proper planning for the test environment</li></li></ul><li>Test effort estimation techniques<br /><ul><li>Function Point (FP)
  44. 44. Constructive Cost Model (COCOMO)
  45. 45. Test Point Analysis(TPA)</li></li></ul><li>Function Point Analysis<br />Function points are a unit measure for software<br />It involves breaking the <br />system into small components<br />which in turn identifies the<br />function points <br />
  46. 46. The size of application is calculated using 5 major components<br /><ul><li>External Inputs
  47. 47. External Outputs
  48. 48. External Inquires
  49. 49. Internal Logical Files
  50. 50. External Interface Files</li></li></ul><li>Benefits of FPA<br />Language and technology independent<br />Estimate cost, effort, schedules of projects that use prototype and spiral models<br />Helps in project estimation<br />
  51. 51. COCOMO Model<br />It categorized software products into three classes<br />Organic systems<br />“refers to simple projects developed by a few experienced team”<br />Semidetached systems<br />“refers to intermediate projects between organic and embedded”<br />Embedded systems<br />“refers to complex projects”<br />
  52. 52. COCOMO model equation<br />Effort =a1 * (KLOC)<br />Tdev=b1*(Effort)<br /><ul><li>KLOC – the estimated kilo lines of code
  53. 53. a1, a2, b1, b2 are constants for different categories of software products
  54. 54. Tdev is the estimated time to develop the software in ‘months’
  55. 55. Effort is the total development effort required to produce the software in ‘programmer months’.</li></ul>a2<br />b2<br />
  56. 56. Benefits of TPA<br />Analyst independent<br />Tests quality characteristics<br />
  57. 57. Thank you<br />

×