7/30/2019 Wconomics of SoftwareTesting

1/4

Software Testing

Development and Software Evolution

Characteristic 1960 1970 1995

Software Size Small Moderate Very LargeDegree of SW Complexity Low Medium High

Size of SW Development Team Small Medium Large

Development methods and standard Ad hoc Moderate Sophisticated

Testing methods and standard Ad hoc Primitive Emerging

Independent Test Organization Few Some Many

Recognition of Testings importance Little Some Significant

Number of Testing Professional Few Few Many

Economics of Testing

Problem:

Failure to define testing

objectives

Testin at the wron

Number of defects Cost of testing

phase in the life cycle

Use of ineffective test

techniquesUnder testing over testing

Optimum testing

Extend of testing

Quantity

Common Computer Problem

Coding Errors

36%

Analysis and Design

Errors 64%

7/30/2019 Wconomics of SoftwareTesting

2/4

Economics of SDLC Testings

Normal SDLC

Accumulated

Testing Cost

Accumulated

Errors/1000

loc

0 20

SDLC Testing

Accumulated

Testing Cost

Accumulated

Errors/1000

loc

10 10Requirement = 20ERR

0 40

0 60

480 12

1680 0

25 15

42 18

182 4

582 0

Design = 20ERR

Code = 20ERR

Testing, reduce 80% ERR

Production 0 Defects

Cost detect for:

Requirement Code = 1

Testing = 10

Production = 100

Discussion

Diasumsikan setiap fase SDLC terdapat 30

error banding biaya yang digunakan yangdikeluarkan untuk menghasilkan product zero

Testing? link

The Structured Approach to Testing

Life Cycle

Phase

Verification Activities

Requirement Determine verification approach

Determine adequacy of requirementsGenerate functional Test Data

Determine consistency of design with requirements

Design Determine adequacy of design

Generate structural and functional test data

Determine consistency with design

Program

(Build/Construction)

Determine adequacy of implementation

Generate structural and functional test data for Programs

Test Test application system

Installation Place Tested system into production

Maintenance Modify and retest

Testing Life Cycle

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)

7/30/2019 Wconomics of SoftwareTesting

3/4

Basic Form of Testing

Full Testing

starts no later than the requirement phase and continuesthrough acceptance testing

Partial Testing begins any time after functional design has been completed,

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

re uce

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 ofservices for user, security, unreliable result, difficulties to use and operate, un-

maintainable program, not portable, not be able to interconnect,

unacceptable performance level

Test Strategy

A strategy must address the risks and present a processthat 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. , , , ,

process, service levels, access control, compliance, reliability, ease ofuse, maintainability, portable, coupling, performance, ease ofoperation

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

7/30/2019 Wconomics of SoftwareTesting

4/4

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 applicationsystem

The tactics add the test plans, test criteria, testing

and verifying the SW system under development

A detailed testing work program is important toensure that the test factors have been adequately

addressed at each phase. The first and most important dimensions are the

test factors

Testing Cube