Test Design

Specifications
Automated Teller Machine System
(ATMS)
Independent Verification and Validation

Version: 1.0.0
Date: 20/11/2017
 Document control
Document Name ATMS Test Design Specification (Iteration 1)
Reference Number ATMS_TDS_1
Version 1.0.0
Project Code XYZ_ATMS
Status In-use
Date Relapsed 20th November 2017

Name Position Signature

Prepared By: Test Analyst
Mohamad Muzakhir Hakim Beta Dudes Co
Lai Man Chung

Reviewed By: Test Lead

Lean Win Leng Beta Dudes Co
Approved By: Test Manager
Amirul Fitri bin Roslin Beta Dudes Co

Version History
Version Release Date Section Amendments
1.0.0 20/11/2017 All Original document

Distribution list
Release Controlled Recipient Issues Return
Version Department
Date Copy On Name Date Date
1.0.0 20/11/2017 01 Beta Dudes Co 20/11/2017
QA Dept.
1.0.0 20/11/2017 02 Beta Dudes Co 20/11/2017
Test Team
1.0.0 20/11/2017 03 XYZ Bank 20/11/2017
Table of Contents
Document control........................................................................................................................................1

Version History...........................................................................................................................................1

Distribution list............................................................................................................................................2

Table of Contents........................................................................................................................................3

1.0 Introduction.........................................................................................................................................4

1.1. Purpose........................................................................................................................................4

1.2. Scope...........................................................................................................................................4

1.3. Reference.....................................................................................................................................4

2.0 Test Design..........................................................................................................................................5

2.1. Features to be tested.....................................................................................................................5

2.2. Approach Refinements....................................................................................................................

2.2.1 F001 Start Up......................................................................................................................5

2.3. Test Identification.......................................................................Error! Bookmark not defined.

2.3.1 Start Up...............................................................................................................................5

2.4. Feature Pass/Fail Criteria.............................................................................................................5

2.5. Test Deliverables........................................................................Error! Bookmark not defined.

1. Introduction

1.1. Purpose
This test design specification supports the following objectives:

a. To identify the test items covered

b. To further refine the test approach from Test Plan
c. To define the sources of the information used to prepare the plan
d. To identify the general cases of test to be executed

1.2. Scope
The Test Design Specifications (TDS) cover Session Verification features developed in
ATMS

1.3. Reference
The following IEEE Standards have been referenced in preparation of this document:
a. IEEE 829-2008 Standard for Software and System Test Documentation.

The following documents provide the test basis for this test design:

a. ATMS Software Requirements Specification

b. ATMS System Design Specification
 2. Test Design

2.1. Features to be tested

The following table contains the features to be tested based on ATMS Software Requirement
Spesifications (SRS) for this iteration. Listed together are the function ID and its
corresponding functions and estimated risk level.

Table 2.1: Features to be tested

Function ID Function Risk Level

F001 Start Up High

2.2. Approach Refinements

As discussed in Test Plan, test cases for ATMS will be designed using five techniques which are
covered in this section. Techniques are applied based on suitability of techniques according to
nature of features.

The techniques that will be applied are as follows:

1. Equivalence Partitioning (EP): it will used to spill PIN verification into possible partitions
for test.

2. Boundary Value Analysis (BVA): it will test the boundary values of the PIN input.

3. Decision Table Testing (DTT): it will be used to cover the major branches of decision.

4. State Transition Test (STT): it will be used to test the major states of ATMS.

5. Use Case Testing (UCT)

Nature of feature as below

 F001 Start Up – Switch on the system to make services available for use.
 2.2.1. F001 Start Up

Five techniques are identified for designing test for this feature, including:
1. Equivalence Partitioning (EP)

2. Boundary Value Analysis (BVA)

3. Decision Table Testing (DTT)

4. State Transition Test (STT)

5. Use Case Testing (UCT)

Equivalence Partitioning is used to split amount of banknotes in ATM into possible partitions for test.
Boundary Value Analysis will test the boundary values for the banknotes amount. Decision Table is
used to cover major branches of decision. State Transition testing will test for major states of ATMS.
 A. Equivalence Partitioning

Equivalence Partitioning Boundary Value Analysis

INPUT
Valid
Valid
0 <= IAB < 2147483646
Initial
Amount of Valid
Banknotes(IAB) IAB = 2147483647
Invalid

Invalid

IAB > 2147483647

OUTPUT

0 2147483646
Valid
Valid
Initial
Amount of 0 <= IAB < 2147483646
Banknotes (IAB)
2147483646 2147483646
Invalid
Valid

IAB = 2147483647

2147483646 9999999999
Invalid

IAB > 2147483647

Initial Amount of Banknotes Equivalence Partition & Boundary Value Analysis

 0 2147483646 2147483646 9999999999
ValidValidInvalid

0 <= IAB < 2147483647 IAB > 2147483647

IAB = 2147483647

Initial Amount of Banknotes Equivalence Partition

Test Condition Test Condition Test Test Coverage Example of

ID Coverage ID Test Data
TCON-01-001 0 <= IAB < 2147483646 TCOV-01-001 0 <= IAB < 2147483646 1034564771
(Valid)
TCON-01-002 IAB = 2147483646 TCOV-01-002 IAB = 2147483646 2147483646
(Valid)
TCON-01-003 IAB > 2147483646 TCOV-01-003 IAB > 2147483646 3147483564
(Invalid)
TCON-01-004 Valid IAB TCOV-01-004 Valid IAB (valid output) 21345677
TCON-01-005 Invalid IAB TCOV-01-005 Invalid IAB (invalid 4123432546
output)
Initial Amount of Banknotes Equivalence Partitioning Test Conditions & Coverage
 B. Boundary Value Analysis

0 21474836452147483646 21474836462147483647 9999999999

ValidValidInvalid

0 <= IAB < 2147483647 IAB > 2147483647

IAB = 2147483647

Initial Amount of Banknotes Boundary Value Analysis

Test Condition Test Condition Test Test Coverage Example of

ID Coverage ID Test Data
TCON-01-006 IAB = 0 TCOV-01-006 IAB = 0 (Invalid) No input
TCON-01-007 IAB = 2147483645 TCOV-01-007 IAB = 2147483645 2147483645
(Valid)
TCON-01-002 IAB = 2147483646 TCOV-01-002 IAB = 2147483646 2147483646
(Valid)
TCON-01-008 IAB = 2147483647 TCOV-01-008 IAB = 2147483647 3147483567
(Invalid)
TCON-01-009 IAB = 9999999999 TCOV-01-009 IAB = 9999999999 9999999999
(Invalid)
TCON-01-004 Valid IAB TCOV-01-004 Valid IAB (valid output) 21345677
TCON-01-005 Invalid IAB TCOV-01-005 Invalid IAB (invalid 4123432546
output)
Initial Amount of Banknotes Boundary Value Analysis Test Conditions & Coverage
 C. Decision Table Testing

Test Condition ID Test Condition

TCON-01-010 Valid Initial Amount of Banknote
TCON-01-011 Error Message
TCON-01-012 System Resume
Start Up Decision Table Test Condition

Condition TCOV-01-006 TCOV-01-007

Valid Initial Amount of Balance Y N
Output
Error Message N Y
System Resume Y N
Start Up Decision Table

D. State Transitioning Testing

Start Up State Transition Diagram

The test condition for state transition testing is as follows:

i. TCON-01-013 Start Up State Transition
State / Input On (O)
Off (S1) S2/PS
Start Up State Table

Test Coverage ID Test Coverage

TCOV-01-008 S1 to S2 with input O
Start Up State Coverage
 E. Use Case Testing

Start Up Use Case

Test Condition Test Condition Test Coverage Test Coverage Test Data
ID ID
TCON-01-013 Main flow TCOV-01-009 Main flow - Press On button
- Input 300 $20
banknote
- System On and
Idle state
TCON-01-014 Alternate flow – TCOV-01-010 Alternate flow – - Invalid initial
Invalid Initial Invalid Initial amount of cash =
Amount of cash Amount of cash *300
2.3. Test Identification

Test Case ID Description Test Coverage ID Test Condition ID

TC-01-001 Verify initial amount of TCOV-01-001 TCON-01-001
banknote (IAB = 0) TCOV-01-005 TCON-01-005
TCOV-01-006 TCON-01-006
TC-01-002 Verify initial amount of TCOV-01-001 TCON-01-001
TCOV-01-004 TCON-01-004
banknote (IAB = TCOV-01-007 TCON-01-007
2147483645)
TC-01-003 Verify initial amount of TCOV-01-002 TCON-01-002
TCOV-01-004 TCON-01-004
banknote (IAB =
2147483646)
TC-01-004 Verify initial amount of TCOV-01-003 TCON-01-003
TCOV-01-005 TCON-01-005
banknote (IAB = TCOV-01-008 TCON-01-008
2147483647)
TC-01-005 Verify initial amount of TCOV-01-003 TCON-01-003
TCOV-01-005 TCON-01-005
banknote (IAB = TCOV-01-009 TCON-01-009
9999999999)
TC-01-006 Start Up Main Flow TCOV-01-006 TCON-01-010
TCON-01-012
TCOV-01-008 TCON-01-012
TCOV-01-009 TCON-01-013
TC-01-007 Start Up Alternate Flow TCOV-01-007 TCON-01-011
- Invalid Initial TCOV-01-010 TCON-01-014
Amount of cash
Start Up Test Identification

2.4 Feature Pass/ Fail Criteria

Each feature must satisfy the following criteria in order to pass:

i. Pass all its test cases.
ii. 0% calculation error if the feature involves money transaction.
iii. No deadlock.
iv. Fulfill its requirement.
2.5 Test Deliverables

The following documents will be generated by the system test group and will be delivered
after test completion.

Test documentation:
i. Test Plan
ii. Test Item Transmittal Report
iii. Test Design Specification.
iv. Test Case Specifications.
v. Test Procedure Specifications.
vi. Test Logs.
vii. Test Incident Reports.
viii. Test Summary Report.
ix. Test Completion Report.