Your SlideShare is downloading. ×
Test effort estimation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Test effort estimation

8,548
views

Published on


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

No Downloads
Views
Total Views
8,548
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
580
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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