Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 18 views

    Wconomics of SoftwareTesting

    Uploaded by

    mukesh427
    The document discusses the evolution of software development and testing from 1960 to 1995, noting an increase in software size, complexity, and importance of testing. It provides information on economics of software development life cycle testing and compares the costs and defects of normal versus testing-focused SDLC approaches. Various testing strategies, methods, and factors are presented, including the need to address risks through a testing strategy that reduces their impact at each development phase.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd

    Wconomics of SoftwareTesting

    Uploaded by

    mukesh427
    18 views4 pages
    The document discusses the evolution of software development and testing from 1960 to 1995, noting an increase in software size, complexity, and importance of testing. It provides information on economics of software development life cycle testing and compares the costs and defects of normal versus testing-focused SDLC approaches. Various testing strategies, methods, and factors are presented, including the need to address risks through a testing strategy that reduces their impact at each development phase.

    Original Description:

    Wconomics of SoftwareTesting

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the evolution of software development and testing from 1960 to 1995, noting an increase in software size, complexity, and importance of testing. It provides information on economics of software development life cycle testing and compares the costs and defects of normal versus testing-focused SDLC approaches. Various testing strategies, methods, and factors are presented, including the need to address risks through a testing strategy that reduces their impact at each development phase.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    18 views4 pages

    Wconomics of SoftwareTesting

    Uploaded by

    mukesh427
    The document discusses the evolution of software development and testing from 1960 to 1995, noting an increase in software size, complexity, and importance of testing. It provides information on economics of software development life cycle testing and compares the costs and defects of normal versus testing-focused SDLC approaches. Various testing strategies, methods, and factors are presented, including the need to address risks through a testing strategy that reduces their impact at each development phase.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 4

    Development and Software Evolution

    Characteristic Software Size Degree of SW Complexity 1960 Small Low Small Ad hoc Ad hoc Few Little Few 1970 Moderate Medium Medium Moderate Primitive Some Some Few 1995 Very Large High Large Sophisticated Emerging Many Significant Many

    Software Testing

    Size of SW Development Team Development methods and standard Testing methods and standard Independent Test Organization Recognition of Testings importance Number of Testing Professional

    Economics of Testing
    Number of defects

    Common Computer Problem


    Cost of testing

    Problem: Failure to define testing objectives Testing at the wrong phase in the life cycle Use of ineffective test techniques

    Coding Errors 36% Optimum testing Quantity Analysis and Design Errors 64% Under testing over testing

    Extend of testing

    Economics of SDLC Testings


    Normal SDLC
    Accumulated Testing Cost 0 0 0 480 1680 Accumulated Errors/1000 loc 20 40 60 12 0 Requirement = 20ERR Design = 20ERR Code = 20ERR Testing, reduce 80% ERR Production 0 Defects Cost detect for: Requirement Code Testing Production

    Discussion
    Diasumsikan setiap fase SDLC terdapat 30 error banding biaya yang digunakan yang dikeluarkan untuk menghasilkan product zero defects dengan normal SDLC dan SDLC Testing? link

    SDLC Testing
    Accumulated Testing Cost 10 25 42 182 582 Accumulated Errors/1000 loc 10 15 18 4 0

    =1 = 10 = 100

    The Structured Approach to Testing


    Life Cycle Phase Requirement Verification Activities Determine verification approach Determine adequacy of requirements Generate functional Test Data Determine consistency of design with requirements Determine adequacy of design Generate structural and functional test data Determine consistency with design Determine adequacy of implementation Generate structural and functional test data for Programs Test application system Place Tested system into production Modify and retest

    Testing Life Cycle

    Design

    Program (Build/Construction) Test Installation Maintenance

    Verification is the process of evaluating a system/component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase (IEEE/ANSI) Validation is the process of evaluating a system/component during or at the end of the development process to determine whether it satisfies specified requirements (IEEE/ANSI)

    Basic Form of Testing


    Full Testing
    starts no later than the requirement phase and continues through acceptance testing

    Partial Testing
    begins any time after functional design has been completed, with less than optimal influence on requirements and functional design

    Endgame Testing
    is highly validation oriented, with no influence on requirements or functional design

    Audit-Level Testing
    is a barebones audit plans, procedures, and products for adequacy, correctness, and compliance to standards.

    Computer System Strategy Risk


    A risk is a condition that can result in a loss A risk is related to the probability of a loss The risk is always exists, although the loss may not occur Risk can not be eliminated, but the impact of the loss can be reduced The most effective methods to reduce the impact of the loss is testing Types of strategic risk
    Incorrect result, unauthorized transaction, lost of integrity offile, processing can not be reconstructed, lost of continuity of processing, degradation of services for user, security, unreliable result, difficulties to use and operate, unmaintainable program, not portable, not be able to interconnect, unacceptable performance level

    Test Strategy
    A strategy must address the risks and present a process that can reduce those risks Two component of Testing Strategy
    Test Factor - The risk or issue that needs to be addressed as part of the test strategy.
    Correctness, authorization, file integrity, audit trail, continuity of process, service levels, access control, compliance, reliability, ease of use, maintainability, portable, coupling, performance, ease of operation

    Test Phase - The phase of the SDLC in which testing will occur

    Note:
    The risk associated with testing will be called Test Factors Not all test factors will be applicable The test phase will vary based on the testing methodology used

    Developing Test Strategy


    Select and rank test factor Identify the system development phase Identify the business risk associated with the system under development Place risks in the matrix

    Strategic/Tactical Testing Cube


    The testing methodology cube represents a detailed work program for testing application system The tactics add the test plans, test criteria, testing techniques and testing tools used in validating and verifying the SW system under development A detailed testing work program is important to ensure that the test factors have been adequately addressed at each phase. The first and most important dimensions are the test factors

    Testing Cube

    You might also like