All rights reserved.

Tertiary and Vocational Education Commission

NVQ Level 05 –Semester II
Information & Communication Technology

Software Testing K72T001M05 Three Hours

Answer Sheet

Question 01

1) Characteristics of Software:
a) Software is engineered, not manufactured in the classical sense.
b) Software can be upgrade or modified
c) Correctness
d) Reliability
e) Flexibility
f) Security
g) Usability
h) Maintainability
i) Portability
j) Integrity
k) Efficiency
l) Extensibility
m) Maintainability

2) A fault in a program which causes the program to perform in an unintended or unanticipated

manner.

3) Verification is a review without actually executing the process while validation is checking
the product with actual execution. For instance, code review and syntax check is
verification while actually running the product and checking the results is validation.

Question 02
1)
I. Requirement analysis
II. Test Planning
III. Test Case development (Test Case Designing)
IV. Test Environment Setup
V. Test Execution
VI. Test Cycle Closure

Page 1 of 5
2)
1) Delphi Technique
2) Work Breakdown Structure (WBS)
3) Three Point Estimation
4) Functional Point Method

1) Delphi Technique: This is one of the widely used software testing estimation technique. In
the Delphi Method is based on surveys and basically collects the information from
participants who are experts. In this estimation technique each task is assigned to each team
member & over multiple rounds surveys are conduct unless & until a final estimation of
task is not finalized. In each round the thought about task are gathered & feedback is
provided. By using this method, you can get quantitative and qualitative results. In overall
techniques this technique gives good confidence in the estimation. This technique can be
used with the combination of the other techniques.

2) Work Breakdown Structure (WBS): A big project is made manageable by first breaking
it down into individual components in a hierarchical structure, known as the Work
breakdown structure, or the WBS. The WBS helps to project manager and the team to
create the task scheduling, detailed cost estimation of the project. By using the WBS
motions, the project manager and team will have a pretty good idea whether or not they’ve
captured all the necessary tasks, based on the project requirements, which are going to need
to happen to get the job done. In this technique the complex project is divided into smaller
pieces. The modules are divided into smaller sub-modules. Each sub-modules are further
divided into functionality. And each functionality can be divided into sub-functionalities.
After breakdown the work all functionality should review to check whether each & every
functionality is covered in the WBS. Using this you can easily figure out the all task needs
to completed & they are breakdown into details task so estimation to details task would be
easier than estimating overall Complex project at one shot.

3) Three Point Estimation: Three point estimation is the estimation method is based on
statistical data. It is very much similar to WBS technique, task are broken down into
subtasks & three types of estimation are done on this sub pieces.

Optimistic Estimate (Best case scenario in which nothing goes wrong and all conditions are
optimal.) = A
Most Likely Estimate (most likely duration and there may be some problem but most of the
things will go right.) = M
Pessimistic Estimate (worst case scenario which everything goes wrong.) = B
Formula to find Value for Estimate (E) = A + (4*M) + B / 6
Standard Deviation (SD) = = (B – A)/6

4) Functional Point Method: Functional Point is measured from a functional, or user, point of
view.
It is independent of computer language, capability, technology or development
methodology of the team. It is based on available documents like SRS, Design etc.
Page 2 of 5
 In this FP technique we have to give weightage to each functional point. Prior to start actual
estimating tasks functional points are divided into three groups like Complex, Medium &
Simple. Based on similar projects & Organization standards we have to define estimate per
function points.

Total Effort Estimate = Total Function Points * Estimate defined per Functional Point

Question 03

1) There are four test levels

a. Unit/component/program/module testing
b. Integration testing
c. System testing
d. Acceptance testing

Unit testing: Testing performed on a single, stand-alone module or unit of code.

Integration testing: Testing performed on groups of modules to ensure that data and
control are passed properly between modules.
System testing: Testing a predetermined combination of tests that, when executed
successfully meets requirements.
Acceptance testing: Testing to ensure that the system meets the needs of the organization
and the end user or customer (i.e. validates that the right system was built).

2) Testing whether software is compatible with other elements of a system with which it
should operate. Eg:- browsers, operating systems or hardware

Question 04
1)
a. Boundary Value Analysis (BVA)
b. Equivalence Class Partitioning
c. Decision Table based testing
d. Cause-Effect Graphing Technique
e. Error Guessing
f. State transition testing
g. Use case testing
h. Domain testing
i. Exploratory testing
j. All-pairs testing

2) White box testing technique involves selection of test cases based on an analysis of the
internal structure (Code coverage, branches coverage, paths coverage, condition coverage
etc.) of a component or system. It is also known as Code-Based testing or Structural
testing.

Page 3 of 5
 Different types of white box testing are:
a. Statement Coverage
b. Decision Coverage

Question 05

1) A test case is a document, which has a set of test data, preconditions, expected results and
postconditions, developed for a particular test scenario in order to verify compliance against
a specific requirement.

2) In contrast to reviews follow a formal process. A typical formal review process consists of
six main phases:
1. Planning
a. The review process for particular review process begins with “Request for Review”
by the author to moderator. The moderator is often assign to take care of scheduling
if review that means the time, date, venue, agenda & invitation of review is made by
moderator.
b. On a project level, the project planning needs to allow time for review & rework
activities, providing engineers with time to thoroughly participate in review.
c. For more formal reviews, the moderator always perform an entry check & defines
formal exit criteria.

2. Kick-off
a. An optional step in review process in kick-off meeting the goal of these meeting is
to get everybody on same wavelength regarding document under review and to
commit to time that will be spent on checking.
b. Also the result of entry check and exit criteria are discussed in case of more formal
review.
c. Role assignment, checking rate, the pages to be check process changes & possible
other questions regarding formal reviews are also discuss during this meeting.

3. Preparation
a. The participants who are individually on document under review using the related
documents, procedure rules & checklist proper. The individual participant identify
defects according to their understanding of document & role.
b. All issues are recorded preferably using logging form spelling mistakes are recorded
on document under review but not mentioned during review meeting.
c. A critical success factor for thorough preparation is no. of pages checked per hour,
these is called Checking Rate.
4. Review meeting
Logging Phase:
Discussion Phase
Page 4 of 5
 Decision Phase
During logging phase, the issues e.g. defects that have been identified during preparation
phase are mention phase by phase, reviewer by reviewer & are logged either by author or
recorder. A separate person like recorder or scriber is present in logging phase to log defects
encouraged during review process.
To ensure process & efficiency, no real discussion, the items are logged & then handled in
discussion phase. A detailed discussion on whether or not an issue is defects is not
meaningful, as it is much more efficient to simply log it & proceed to next defect.
During logging phase the focus is on logging as many defects as possible within certain
time frame. To ensure these, moderator tries to keep good logging rate i.e. no. of defects
logged per minute.
As chairperson of discussion meeting the moderator takes care of peoples issues. All the
defects logged in previous phase are discussed in detail during discussion phase.
At the end of meeting a decision on document under review has to be made by participant
based on formal exit criteria. The most important exit criteria is no. of critical or major
effect is avg. no. of major or critical defect found per page.

5. Rework
Based on defects detected, author will improve document under review step-by-step. Not
every defect i.e. found leads to rework. It is the author’s responsibility to judge if defects
has to be fixed. If no. of defects per page exceeds the exit criteria then only the rework
should be conducted for author.

6. Follow-up.
The moderator is responsible for ensuring that satisfactory action have been taken on all
logged defects, process improvement suggestion & change request. Although the moderator
checks to make sure that author has taken action an all defects, it is not necessary for
moderator to check all corrections in detail for more formal review type moderator checks
only for complains to exit criteria i.e. during follow-up moderator keeps track on those
errors which are encountered during logging phase & their elimination process.

Page 5 of 5