FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
Document Title: Direct Interface Testing Specification - Pathway to HAPS
Document Type: Specification
Abstract: The purpose of this document is to define the Direct
Interface Test Specification for the Pathway/HAPS
interface.
Status: Issued
Distribution: Simon Palladino
Chris Pibworth
John Hunt
Grant Punchard (IT Services)
Bob Booth(PDA)
John Bruce(PDA)
Martin Renwick(PDA)
Mark Reader(POCL)
Library
Author: Habib Ziaullah
Comments to: Author
Comments by:
© 1997 ICL Pathway Ltd
© 1997 ICL Pathway Ltd
COMMERCIAL IN CONFIDENCE Page 0 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
0 Document control
0.1 Document history
Version Date Reason
0.1 21/04/97 Initial draft for comment
0.2 23/05/97 Comments included from PDA review meeting.
1.0 12/06/97 Comments included from PDA/POCL/Pathway meeting.
11 19/06/97 Comments included from PDA QA Review.
2.0 17/07/97 The Document version number has been changed to 2.0.
0.2 Approval authorities
Name Position Signature Date
Simon Palladino Testing & Integration
Manager (Pathway)
Mark Reader POCL
John Bruce PDA
0.3 Associated documents
Reference Vers Date Title Source
AP/IFS/001 1.0 10/3/97 Pathway to HAPS Interface
Specification
T.Peppin 1.0 7/2/97 Requirements Letter (iT Concept
2000)
PDA/TAS/HAPS/ 1.0 Pathway - HAPS DIT Requirements
WP/001
0.4 Abbreviations
AIS Application Interface Specification
AP Automated Payments
COMMERCIAL IN CONFIDENCE Page 1 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
APS Automated Payments Service
DIT Direct Interface Testing
FT File Transfer
0.5
HAPS (POCL) Host Automated Payments Service
PDA Programme Delivery Authority
POCL Post Office Counters Ltd
Changes in this version
Version 0.2 - Included details from ‘Pathway - HAPS Requirements’.
Version 1.0 - Included comments from meeting held at PDA Office, Feltham
on the 9" June 1997.
Version 1.1 - Tidied the last bullet point in Section 3.5.1 and removed Section
8 HAPS Tests.
Version 2.0 - Change of Version Number (2) only, to conform to Pathway
Standards for ‘Issued’ Documents.
COMMERCIAL IN CONFIDENCE Page 2 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
0.6
Table of content
3.1 Overview.
3.2 Architecture... eecee cece cece eeeececeeeeeeeeeeceeeneeeeseeesnsaseseneetetaceneneeeetets 7
3.3 FAD Codes... eee eceeccces cece ceeseseeeereeceeecseeneaeseeseceneneersesanereeusesesecevees 7
3.4 Steps
3.5 Testing Requirement. ............ cc ecceceeeeeeeeeeceeceeeeeeeeeeeeeeeeeeeneeeeeeeeeeeeee 8
3.5.1 Counter Level Tests... cece cccceeseeeeeseeseeeeerereeseseseseenenaeicee 8
3.5.2 File Level Tests....
3.5.3 Infrastructure Test
3.5.4 Documentation Required To Support The Tests.
4 Fault Reporting.............e cece cece cece cee cec cee eeceeceeeceeceeceesececseceesenseeaeeeseeeeeaee 11
5 Entry Criteria... cece cee ececeeeeeeeececeeeeecececeeeeeeeececeseeeeseseceeeeeeeeeeeseees 11
6 Success Criteria... eee ec eeececseseseeerceceeeeeceeeeeeeeceeeeeneeecesecseseeeeeseeeeers 11
7 Responsibilities... ee eee ee cece cee ce cee cesceeceeeeeeecseeeceeceesaeeeseesecaeeeeeeaees 12
7.1 Test Sigh Off... cceececcccccesceceseseseseeeesesceeseeeseeecscsesesecscsreeeesetecstateeseeee 12.
7.2 Test EX@CUtion...........cccceccceccececeseeceeeeeeseeceseseeeeeeesseeeeeeenseeseeeeeeeneese 12
COMMERCIAL IN CONFIDENCE Page 3 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
1 Introduction
This document details the Direct Interface Test Specification between
Pathway AP System and POCL HAPS System. It identifies the requirements
that will be used to accomplish direct interface testing between POCL and
Pathway, as such this document must be owned and approved by POCL,
Pathway and the PDA.
COMMERCIAL IN CONFIDENCE Page 4 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
2 Scope
The scope of Direct Interface Testing is to ensure that the system interface
between Pathway APS and POCL HAPS works at both the technical and
application level. It excludes end-to-end, model office rehearsal and model
Office test.
Direct Interface Testing only covers the transition of transaction data,
captured at the APS counter, from Pathway Central Systems to HAPS (shown
within dotted lines).
Legacy Systems HAPS APACHI
DPC AP
Clients
APS Counter Pathway Central System
Key:
Legacy represents the provision of the Automated Payments Service using
Systems Automated Payments Terminals, ECCO equipment or ALPS
equipment.
HAPS is the Host Automated Payments System operated by IT SERVICES
on behalf of POCL.
APACHI is the Automated Payments at Chesterfield Interface, the link to
POCL’s client accounting and settlement processes.
DPC is the Document Processing Centre, the location at which paper
Automated Payments sales vouchers are converted into electronic
format.
AP Clients is the base of Automated Payments Clients on behalf of whom
business is conducted at Post Office outlets.
APS is the Pathway Automated Payments Service at Post Office outlets.
Counter
Pathway represents the systems, located outside Post Office outlets, that
COMMERCIAL IN CONFIDENCE Page 5 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
Central process APS transactions and present them to the Pathway to HAPS
Systems interface.
3 Requirements
3.1
3.2
3.3
3.4
Overview
Direct interface testing is to ensure that the Pathway AP System and
the POCL HAPS System operate in accordance with the ‘Pathway to
HAPS Interface Specification’. Interface testing must satisfy a
successful file transfer taking place and ensure the contents of the files
includes data to support the Interface Specification. Thus the DIT
objective is to prove the interface only.
Architecture
Pathway will have a system test configuration consisting of a Sequent
Server (the Host) and a Correspondence Server supporting several
outlets, at least one outlet having more than one counter position. All
system testing will be carried out by Pathway testers under the
direction of the Pathway System Test Manager. It will encompass
operation at a variety of outlets & counter positions.
FAD Codes.
The valid FAD Code to be used in the testing interface file header
record is 9990771.
The valid outlet FAD codes to be used are dependant on the
Reference Data Project provided by POCL in Chesterfield. Outlets will
be constructed using these FAD codes and the information supplied to
HAPS prior to commencing Direct Interface Tests.
Steps
The tests encompass the following steps.
e Perform counter transactions on the Pathway test cells.
e Harvest the transactions on to the Oracle Host and generate a
transmission file.
e Send the transmission file from the Gateway PC at Feltham to the
Gateway PC at Farnborough via Wigan, making the AP
transmission file available to POCL HAPS.
e POCL HAPS rename the files to notify Pathway that the files have
been transferred successfully.
COMMERCIAL IN CONFIDENCE Page 6 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
e Check the integrity and content of the file conforms to the AIS.
3.5 Testing Requirements
3.5.1 Counter Level Tests
e A swiped magnetic card transaction, paid by cash.
e A keyed magnetic card transaction, paid by cash.
e A swiped magnetic card transaction, paid by cheque.
e Akeyed magnetic card transaction, paid by cheque.
e A swiped magnetic card transaction, paid by cash, that has
been reversed.
« Areversal of the above transaction.
e A keyed magnetic card transaction, paid by cheque, that has
been reversed.
« Reversal of the above transaction.
e Ascanned bar code transaction, paid by cash.
e A keyed bar code transaction, paid by cash.
e Ascanned bar code transaction, paid by cheque.
e A keyed bar code transaction, paid by cheque.
e A scanned bar code transaction, paid by cheque, that has
been reversed.
« Reversal of the above transaction.
e A keyed bar code transaction, paid by cash, that has been
reversed.
« Reversal of the above transaction.
e A magnetic card recovery transaction.
e A magnetic card fall back recovery transaction.
e A bar coded bill recovery transaction.
e A bar coded bill fall back recovery transaction.
The above transactions will be captured from more than one Post Office
outlet. Transactions will be for more than one client including multiple
schemes for a client that has many schemes. Counter transactions will
performed on different days although included in the same file. Additionally
some transactions will be captured at a Post Office outlet that has not had its
end of day marker set for seven days.
COMMERCIAL IN CONFIDENCE Page 7 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
3.5.2 File Level Tests
e Large transfer file (i.e. maximum size as defined in the
interface specification ref 0.2.4).
e Null transfer file (ie. header and trailer only).
e File of magnetic card transactions only. (Including reversed
and reversal transactions.)
e File of bar code transactions only. (Including reversed and
reversal transactions.)
e File of mixed magnetic card and bar code transactions.
(Including reversed and reversal transactions.)
« More than one transfer file.
e Duplicate transmission i.e. same file sent twice with the same
file name.
e Transfer file sent out of sequence.
e Break in transmission of transfer file.
e Re-transmission of above file to same gateway PC.
e Re-transmission of above file to alternative PC.
e File or a multiple number of files, containing one transaction
for each magnetic card and bar coded bill available at
Pathway.
3.5.3 Infrastructure Tests
e Hardware failures of encryption box, router, hub and gateway
PC.
e Password failure at the gateway PC.
e Operation with and without encryption devices.
e Digital signature verification.
COMMERCIAL IN CONFIDENCE Page 8 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS Version: 2.0
Date: 16/07/97
4
3.1.4 Documentation Required To Support The Tests
e Detailed transaction report per office per test day.
« APS reconciliation reports.
« Test timetable showing the days on which HAPS is required
for Direct Interface Testing.
e Test schedule showing the tests that will be performed on
each day, their sequence and their duration.
« Specific Automated Payments Clients lists to be provided by
POCL.
Fault Reporting
Each party will use its own fault reporting system. Pathway will log any
incidents using the fault reporting system PinICL. The incident number will be
passed back for future progression and clearance.
IT SERVICES will fax details of incidents raised to Pathway, if any incidents
are found to be software or hardware faults these will be entered into PinICL.
A copy of the PinICL report will be faxed to HAPS.
A weekly testing progress meeting to be held during DIT.
Entry Criteria
The criteria for entry to DIT are:
. All hardware installed, tested and commissioned as per
Pathway to HAPS Interface Specification, Reference 0.2.4.
COMMERCIAL IN CONFIDENCE Page 9 of 12
FUJ00058366
FUJ00058366
ICL Pathway Direct Interface Testing Specification - Ref: VI/SPE/0001
Pathway to HAPS vehate: 18/07/07
Test scripts produced for review.
Test schedule produced for review.
Test timetable produced for review.
6 Success Criteria
The criteria for successful completion of DIT are:
e Conformance to Interface Specification Reference 0.2.4.
. Successful transaction validation by HAPS.
. Technical performance of link.
. Test results are as expected and any differences successfully
resolved.
. No critical or severe incidents outstanding, as agreed by PDA,
Pathway and POCL outlet systems.
. All scheduled tests completed successfully or agreement
reached on any tests not performed.
7 Responsibilities
7.1 Test Sign off
This will be via a hand over meeting at which the interfacing systems will give
their
COMMERCIAL IN CONFIDENCE
Page 10 of 12
ICL Pathway Direct Interface Testing Specification -
Pathway to HAPS
FUJ00058366
FUJ00058366
Ref: VI/SPE/0001
Version: 2.0
Date: 16/07/97
approvals as follows:
. POCL - Mark Reader
. PDA - John Bruce
. Pathway - Simon Palladino
7.2 Test Execution
IT Services - Testing Support:
Grant Punchard and Sheena Kilcast (Tel:!
IT Services- Fault Fixing and Technical Support:
Mike Hoare (Tel:I
Grant Punchard (T:
ICL Pathway
Habib Ziaullah (Tel
Marcia Petterson (Tel:;
COMMERCIAL IN CONFIDENCE
Page 11 of 12