2 testing throughout software lifecycle

Testing throughout Software Lifecycle
 Testing in Software Development
 Testing and Development
 The Waterfall Model
 The V-Model
 The W-Model
 The V&V in the W-Model
 Test Levels
 Test Types

Testing in Software development
 During Development
 Rigorous testing of systems and documentation can help
to increase quality and reduce risk.
 Risk can be reduced if defects are found and corrected
before system is released.

Testing in Development Lifecycle
 During System Operation
 Testing is necessary during system operation to detect
new defects.
 In General
 Testing may also be required to meet legal requirements
and industry-specific standards.
 Testing is mandated by all quality standards (ISO 9000)
and SW Development standards (CMMI).

Testing Throughout Software Lifecycle

Testing and Development
 Testing is not isolated , test activities are related to
software development activities.
 Software development life cycle models describe:
 Phases of software development life cycle.
 The order in which those phases are executed.
 Different lifecycle models need different approaches of
testing.

The Waterfall Model
 The waterfall model is the classic and most common
software development life cycle model.
 Each phase must be completed in its entirety before
the next phase can begin.
 One of the inherent dangers of the waterfall model is
that it clearly shows that testing only happens after
coding is completed.

The Waterfall Model
Requirements
Analysis
Design
Code
Test

 The V-Model

The V-Model
Requirements
Analysis
Design
Code Component test
Integration test
System test
Acceptance test

The V-Model
Requirements
specification
System
specification
System Design
Code
Component test
Integration test
System test
Acceptance test
Unit Design
Test Strategy
Planning and
Risk Analysis
Test Analysis
and Design
Test Implementation
Unit Testing
Acceptance TC
System TC
Integration TC
Component TC

The V-Model
 The V-Model includes four testing levels
corresponding to the four development levels.
 Development work products (Ucs,SRS,SDD,…etc) are
the basis for testing
 Test preparation is not on the critical path of the
project.
 V-Model is a waterfall model. However, organizations
adapt it to iterative and agile testing.

 The V-Model
 The W-Model

The W-Model
 The W-Model is a variant of the v-model that focuses
on early testing (Verification and validation

The W-Model
Requirements
specification
System
specification
System Design
Code
Component test
Integration test
System test
Acceptance test
Unit Design
Review
Unit Testing
Review
Review
Review
Review
Defects

 The V-Model
 The W-Model
 The (V & V) in the W-Model.

The V&V in the W-Model
 Verification
 “Are we building the system right”?
 The process of evaluating a system or component
 Validation
 “Are we building the right system” ?
 Determination of the correctness of the products of software
development with respect to the user needs and requirements
 Early Testing
 Discovering defects in system specification and design.
 Early testing improves system analysis and design and defects
found there is much more cheaper and easier to fix.

 The V-Model
 The W-Model
 Test Levels

Test Levels
Component Test
Integration test
System test
Acceptance
Test

Test Levels
 Component Testing
 Testing of individual items (e.g. modules, programs,
objects, classes, etc.)
 Searches for defects in, and verifies the functioning of
software that are separately testable.
 usually as part of the coding phase, in isolation from
other development items and the system as a whole.

Test Levels
 Integration testing
 Testing the interfaces between major and minor items
within an application which must interact with each
other.
 May include non-functional elements (Performance).
 Focuses on the integration itself not the functionality.
 Integration levels
 Component integration
 System integration

Test Levels
 Integration Testing
 Integration testing follows the following approaches
 System Architecture (such as top-down and bottom-
up).
 Functional tasks, transaction processing sequences, In
order to reduce the risk of late defect discovery,
integration should normally be incremental rather
than “big bang”.

Test Levels
 System testing
 All types of testing to be carried out once a whole system
has finished development and can be tested as a
complete entity.
 Carried by independent test team.

Test Levels
 Acceptance Testing
 All types of testing to be carried out to ensure a
development is ready to be deployed into the business,
operational or production environment.
 Types of acceptance testing
 User acceptance testing (UAT). (fitness for use)
 Operational (acceptance) testing. (Backup/Restore)
 Contract & regulation acceptance testing. (Deal, Legal)
 Alpha and beta (or field) testing.

 The V-Model
 The W-Model
 Test Levels
 Test Types

Test Types
Functional
• “What” the system does
• Drawn from requirements & specifications.
Non-
Functional
• Performance , Load , Stress , Usability
• Maintainability , Portability
Structural
• White Box Testing
• Performed at all levels
Related to
Changes
• Re-Testing
• Regression Testing

2 testing throughout software lifecycle

2 testing throughout software lifecycle

Recommended

More Related Content

What's hot (20)

Viewers also liked (6)

Similar to 2 testing throughout software lifecycle (20)

Recently uploaded (20)

2 testing throughout software lifecycle