FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref: CR/ACS/009
Acceptance Specification Version: 3.0
Date: 27/11/98
Document Title The ICL Pathway to TIP Interface Acceptance Test
Document Type Acceptance Specification
Abstract This document describes the Acceptance Test for the ICL
Pathway to TIP Interface
Status APPROVED
Author P. John Pope
Approval By 27/11/98
Distribution Pathway Management Team
Test & Integration Manager
Pathway Library
POCL/DSS Horizon Test Manager
PDA tba
Recommended ICL Pathway Test Authority(ies) Test Manager
for Approval Manager
Signature
Name P. John Pope
Date
Approved For and behalf of ICL For and behalf of Authority(ies)
Pathway
Signature
Name
Date
0. DOCUMENT CONTROL
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 1 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface V Ref.: SR/Acsioos
ifi i ersion:
Acceptance Specification Date. 27/11/98
0.1 DOCUMENT HISTORY
Version Date
0.1
1.0
11
1.2
1.3
2.0
3.0
0.2
(10)
1/5/97
12/5/97
26/5/97
3/4/98
29/4/98
9/10/98
27/11/98
Reason
First draft for internal ICL Pathway review
Issued for joint review
Revised following PDA/ICL Pathway Review
Re-issued to reflect introduction of New Release 2 and
changes to test condition naming and content.
Re-issued to reflect requested substitution of
Acceptance Trial for three Acceptance Criteria
Revised following PDA/ICL Pathway Review
Revised following further Review Comments received
24/11/98
ASSOCIATED DOCUMENTS
Reference
Acceptance
Standard
Acceptance
Standard
Authorities’
Agreement
POCL
Agreement
DSS
Agreement
Authorities’
Agreement
Authorities’
Agreement
DSS
Agreement
DSS
Agreement
Version Date Title Source
0.1 13/09/96 Standard for Raising and Pathway
Progressing Acceptance
Incidents.
1.2 13/7/98 Standard for documenting Pathway
Acceptance Specifications
7.2 22/5/97 Acceptance Procedures DSS/POCL
Schedule (A)AO7
7.2 22/5/97 Acceptance Procedures POCL
Schedule (P)A11
7.2 22/5/97 Acceptance Procedures DSS
Schedule (D)A11
8.1 8/3/98 Requirements Schedule I DSS/POCL
(A)BO4
8.1 8/3/98 Solutions Schedule Pathway
(A)BOS
8.1 8/3/98 Requirements Schedule DSS
(D)A15
8.1 8/3/98 Solutions Schedule Pathway
(D)A16
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 2 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface V Ref.: SR/Acsioos
if; i ersion:
Acceptance Specification Date. 27/11/98
(11) POCL 8.0 13/11/97 Requirements Schedule © POCL
Agreement (P)A15
(12) POCL 8.1 8/3/98 Solutions Schedule Pathway
Agreement (P)A16
(13) CR/FSP/004 4.0 30/9/97 Service Architecture Pathway
Design Document
(14) PA/STR/009 2.0 24/2/98 Release Contents Pathway
Definition for Pathway
New Release 2
(15) VI/TSC/142 1.0 1/7/98 Release 2 Direct Interface ICL
Test Script (v11) Pathway
(16) TIIFS/001 (1)5.3 11.5.98 ICL Pathway to TIP POCL
Application Interface
(2)6.4 toa Specification
(17) PCL/TST/CLR 2.0 28/8/98 DIT Closure Report for Horizon
/001 New Release 2 Programme
(18) tba MOT Closure Report for
New Release 2
(19) tba E to E Closure Report for
New Release 2
(20) tba tba - document describing
procedures for operational
support of the ICL
Pathway to TIP interface
(21)
(22)
(23)
(24)
(25)
(26)
(27)
0.3. ABBREVIATIONS
BT Business Thread
DIT
Direct Interface Test
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
CONTRACT CONTROLLED
Printed on: 4/25/2022
Page 3 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
ifi i Version: 3.0
Acceptance Specification Date. 27/11/98
DSS Department of Social Security
E2E End to End (testing)
HLTP High Level Test Plan
MOT Model Office Test
PDA Programme Delivery Authority
POCL Post Office Counters Ltd
TIP Transaction Information Processing
0.4 CHANGES IN THIS VERSION
This version includes changes as a result of POCL further Quality Review
Comments and subsequent discussions.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 4 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref: CR/ACS/009
Acceptance Specification Version: 3.0
Date: 27/11/98
0.56 TABLE OF CONTENT
0. DOCUMENT CONTROL.........ccccssssssssesssssessseesssssersseesenssessseeseseneseneesseeeeeanenes 2
0.1 DOcuMeENT HisTORV....
0.2 ASSOCIATED DOCUMENTS.
0.3 ABBREVIATIONS...
0.4 CHANGES IN THIS VERSION.
0.5 TABLE OF CONTENT..
1. PURPOSE & SCOPE...
2. ACCEPTANCE INCIDENTS. .........cccccccscsssessesssssssessesseesenesessseeseneneseneneeenaeane 6
3. ACCEPTANCE PERIOD............sscscssssssesesssesssessssesesssessseesesseesesesesenanseseeesanseees 7
4. DELIVERABLES & SERVICES 7
5. ACCEPTANCE CRITERIA. 7
5.1. ACCEPTANCE CRITERIA AND TEST CONDITIONG.......... 8
5.1.1 Description of tests conducted by Acceptance Trial. 8
5.1.2 Description of tests conducted by Acceptance Revie' 8
5.3 CRITERIA FOR LATER ACCEPTANC! 0
5.4 CRITERIA SUMMARY....... 0
6. ACCEPTANCE INCIDENT SEVERITY..........scsscscssssssssssssesessssesseeeseseeeeeeeeeees 11
6.1 HIGH SEVERITY INCIDENTS.
6.2 MEDIUM SEVERITY INCIDENTS.
6.3 LOW SEVERITY INCIDENTS...
7. TEST DATA.L...cceececscscecseeceeeceeeseceseeecesesaseseeesaseseeneeesesssessaeesaseseseeeeneeenananenes 12
8. AUTHORITY RESPONSIBILITIES. ...........cccccsccsssseetscecesnetssenesensneneeneeee 12
8.1 APPOINT TEST MANAGER .
8.2 I ACCEPTANCE INCIDENT REPORTS. 12
8.3. ACCEPTANCE INCIDENT ANALYSIS REPORTS. 2
8.4. ATTENDANCE AT TRIALS AND REVIEWS. 2
8.5 MANAGEMENT AND Co-ORDINATION. 3
8.6 —- PROGRESS REVIEWS....sccscssestssentne
9. CONTRACTOR RESPONSIBILITIES
10.
ACCEPTANCE TRIAL TEST CONDITIONS.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 5 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
ifi i Version: 3.0
Acceptance Specification Date. 27/11/98
1. PURPOSE & SCOPE
This document describes the Acceptance Test for the ICL Pathway to TIP
Interface in accordance with the Acceptance Procedures that are set out in the
Schedules referred to in section 0.2 and also in the Pathway document “Standard
for Documenting Acceptance Specifications”. This Test will determine that the
ICL Pathway to TIP Interface meets all the Acceptance Criteria that are agreed in
the Acceptance Specification and that are within the scope of the “Pathway
Release Contents Specification” document for New Release 2, if applicable.
Schedule C3
Policies & Standards
Customer Service
Education Levels
POCLIDSS POCLIDSS POCLDSS
Implementation Implementation Implementation
Training Service Rollout
a DSS Interface TIP Interface MIS Interface
= PAS cMs
Help Desks = 2 g
Reference 3
Data H
2
POCL
Infrastructure
ApS
BES ‘opcs pone EPOSS
Figure1-1: This Acceptance Test in relation to others
2. ACCEPTANCE INCIDENTS
The standard and method for originating, progressing and resolving Acceptance
Incidents shall be as described in the associated Document “Standard for
Raising and Progressing Acceptance Incidents”.
3. ACCEPTANCE PERIOD
The Acceptance Period for the Acceptance Tests, which comprise the
Operational Trial, is as determined by schedule BO7 of the AUTHORITIES’
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 6 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
ifi i Version: 3.0
Acceptance Specification Date. 27/11/98
Agreement.
The Pathway programme plan details the schedule for the ICL Pathway to TIP
Interface Acceptance Test.
4. DELIVERABLES & SERVICES
This section details the Deliverables and Services that are the subject of this
Acceptance Test and as defined by the related Agreements.
Deliverable or Contract Method
Service. Reference
Pathway to TIP POCL Agreement Schedule A15 - I Acceptance Review
Interface Requirements
Table of Deliverables and Services.
5. ACCEPTANCE CRITERIA
This section lists the identifier of each Acceptance Criterion that will be
demonstrated by the Acceptance Test. It also lists the Acceptance Test
Conditions that are used to determine whether (or not) the Acceptance Criterion
has been met together with the applicable test Phase, Technical Test, or Live
Trial.
Acceptance Criteria are split into three sets of tables according to the nature of
the acceptance method, one set for those tested by Acceptance Trial, a second
for those tested by Acceptance Review and a third which lists those criteria which
are for Acceptance at a later release. The Release on which Acceptance is to be
conducted is defined by reference to the Release Contents Description included
in the Associated Documents section of the Acceptance Specification.
Exceptionally, it may be necessary for one particular Acceptance Criterion to be
tested by a combination of trial and review in which case there are entries for
Trial and Review.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 7 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
Acceptance Specification Version: 3.0
Date: 27/11/98
5.1 ACCEPTANCE CRITERIA AND TEST CONDITIONS
Conformance of the ICL Pathway to TIP Interface Acceptance Criteria will be
demonstrated through Acceptance Trials and/or Acceptance Reviews.
Tests conducted by Acceptance Trials comprise practical tests using prepared
test scripts. If applicable the Test Condition(s) appropriate to a criterion are
specified in section 5.1.1 together with a description of the test. Detailed
composition of the test in terms of sequences of Test Conditions is contained in
Section 10. In the tables in section 5.1.1 the rows labelled Function Run Entry
will be populated immediately prior to the running of the Acceptance Trials ina
working version of the Acceptance Specification. These will provide invigilators
with references to the checklists used to monitor the progress of the testing. The
order of running of Test Conditions will not necessarily correspond to the order
presented in HLTPs because of the “physicalisation” of the testing. The Function
Run Entry will allow the invigilator to read across from the criterion to the
checklist.
Tests conducted by Acceptance Review comprise typically document reviews,
site visits or presentations. If applicable the Test Condition(s) are described in
section 5.1.2.
5.1.1 Description of tests conducted by Acceptance Trial
No tests are conducted by Acceptance Trial
5.1.2 Description of tests conducted by Acceptance Review
The table below shows which Acceptance criteria are to be met by Acceptance
Review. Each Acceptance Test will use the latest baselined version of any
document referred to in section 0.2 or below.
Requirement Id 831
Criterion 1
Derivation Requirements
Criterion Description I The CONTRACTOR shall support interfaces from TMS
and Outlets to Transaction Information Processing (TIP)
Test Condition That operational procedures for the support of the ICL
Pathway to TIP Interface are defined.
That the E2E, MOT and DIT test reports contains no
non-conforming entries for ICL Pathway specific
elements relating to the Pathway to TIP Interface as
defined by the TIP AIS
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 8 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
ICL Pathway
The ICL Pathway to TIP Interface
FUJ00001464
FUJ00001464
Ref.:
Version:
Date:
CR/ACS/009
3.0
Acceptance Specification
P Sp 27/11/98
Method
Document Review
References
(20) tba - procedures document
(19) E2E Test Closure Report
(18) MOT Closure Report
(17) DIT Closure Report
(16) ICL Pathway to TIP Application Interface
Specification
Phase
Operational trial
Requirement Id 880
Criterion 1
Derivation Requirement
Criterion Description
Transaction data from the Outlet to TIP (via TMS) shall
be as specified by POCL. (See requirement 831.)
Test Condition
That the E2E, MOT and DIT test reports contains no
non-conforming entries for ICL Pathway specific
elements relating to the Pathway to TIP Interface as
defined by the TIP AIS
Method
Document Review
References
(19) E2E Test Closure Report
(18) MOT Closure Report
(17) DIT Closure Report
(16) ICL Pathway to TIP Application Interface
Specification
Phase
Operational Trial
Requirement Id 893
Criterion 3
Derivation Requirements
Criterion Description
The EPOSS Transaction log and the Transaction data
sent to TIP shall include:
(a) the Authorised Payment Id passed by CAPS to PAS;
(b) the NINO of the Beneficiary, as opposed to any
agent;
(c) the Agency Code provided by CAPS
Test Condition
That the Pathway to TIP AIS provides for the above.
Method Document Inspection
References (16) ICL Pathway to TIP Application Interface
Specification
Phase Operational Trial.
5.3 CRITERIA FOR LATER ACCEPTANCE
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
Printed on: 4/25/2022
CONTRACT CONTROLLED Page 9 of 14
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
Acceptance Specification Version: 3.0
Date: 27/11/98
The table below shows which Acceptance Criteria are for Acceptance at a later
level of specification.
Requirement Id 831
Criterion 3 (this includes what was 4)
Derivation Requirements
Criterion Description I The CONTRACTOR shall support the TIP / TMS
interface for authorisation data:- provide the capability
for reconciliation between POCL and its Clients by
ensuring TIP receives a copy of all original authorisation
data via TMS as specified on an individual Client basis
by POCL.
Reason No clients requiring authorisation data are supported at
Release 2.
5.4 CRITERIA SUMMARY
Req ID Criterion Trial Review Later
Acceptance
831 1 v
831 3-4 v
880 1 v
893 3 v
6. ACCEPTANCE INCIDENT SEVERITY
This section identifies the guidelines to be applied during the analysis of
Acceptance Incidents, in order to establish the severity of such Acceptance
Incidents.
6.1 HIGH SEVERITY INCIDENTS
Failure to meet an Acceptance Criterion which would have a substantive impact
on the service received by the Customer, e.g. failure to pay benefits to the right
person, at the right place, at the right time.
Failure to meet an Acceptance Criterion which would have a major impact on the
ability of the AUTHORITY or AUTHORITIES to perform their business, or where
there was a major impact on the resources of the AUTHORITY or AUTHORITIES
necessary to overcome that impact on their business, e.g. failure to support
accurate POCL accounting.
Failure to meet an Acceptance Criterion which would impact the security of the
service where there is no acceptable procedural workaround.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 10 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
Acceptance Specification Version: 3.0
Date: 27/11/98
Consistent failure to meet Minimum Acceptable Thresholds for Service Levels,
e.g. where particular transactions do not meet the minimum Acceptable
Threshold under normal loading.
6.2 MEDIUM SEVERITY INCIDENTS
Failure to meet an Acceptance Criterion which is visible to the Customer and is
likely to give rise to an adverse public perception of the service, but does not
substantively impact the service received by the Customer, e.g. incorrect spelling
on a receipt.
Failure to meet an Acceptance Criterion which would have a medium impact on
the ability of the AUTHORITY or AUTHORITIES to perform their business, or
where there was a medium impact on the resources of the AUTHORITY or
AUTHORITIES necessary to overcome that impact on their business, e.g. non-
production of a weekly report, resulting in its manual transcription, which causes
additional resource or effort at every outlet of the average duration of one hour
per week per outlet.
Occasional failure to meet Minimum Acceptable Thresholds for Service Levels,
e.g. at peak loading, some transactions fail to meet Minimum Acceptable
Thresholds, but on average all transactions within the service do achieve
Minimum Acceptable Thresholds.
6.3 LOW SEVERITY INCIDENTS
Failure to meet an Acceptance Criterion that is neither visible to nor has
substantive impact on the service received by the Customer e.g. presentational,
style and other cosmetic faults that are only visible to the user.
Failure to meet an Acceptance Criterion which would have a minor impact on the
ability of the AUTHORITY or AUTHORITIES to perform their business, or where
there was a minor impact on the resources of the AUTHORITY or AUTHORITIES
necessary to overcome that impact on their business, e.g. non-production of a
weekly report, resulting in its manual transcription, which causes additional
resource or effort at ten or fewer outlets of the average duration of one hour per
week per outlet.
Failure to meet an Acceptance Criterion which would impact the security of the
service but where the workaround is as secure as the original solution (i.e. the
only impact on risk is in ensuring that the workaround is performed, but where
procedures have been agreed and are in place).
7. TEST DATA
Test data including any operator entered scripts that are required to run the
Acceptance Test are defined below.
Business Test Thread: not applicable
High Level Test Plan(s): not applicable
Organisation: not applicable
8. AUTHORITY RESPONSIBILITIES
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 11 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
Acceptance Specification Version: 3.0
Date: 27/11/98
This section describes the AUTHORITY’s or AUTHORITIES’ Responsibilities in
relation to this Acceptance Test. Particular Acceptance Tests may also require
additional participation and responsibility by the AUTHORITY or AUTHORITIES.
8.1 APPOINT TEST MANAGER
The AUTHORITY or AUTHORITIES shall nominate a Test Manager and other
representatives to review the tests prior to commencement of the test.
8.2 ACCEPTANCE INCIDENT REPORTS
The nominated representatives and Test Manager shall be diligent in raising
complete, accurate and timely Acceptance Incident Reports as set out within this
Acceptance Specification.
8.3. ACCEPTANCE INCIDENT ANALYSIS REPORTS
The Test Manager shall be diligent in returning signed Acceptance Incident
Analysis Reports with their decision (e.g. Accept, Reject, Discuss) normally
within five working days, or when urgency is requested by Pathway, within two
working days of receipt from Pathway. A copy of all correspondence will be
faxed to reduce delay.
8.4 ATTENDANCE AT TRIALS AND REVIEWS
The nominated representatives shall at their discretion attend Acceptance Test
Trials and Reviews including repeat Tests at reasonable times and reasonable
locations and with reasonable advance notice by Pathway.
8.5 MANAGEMENT AND CO-ORDINATION
The Test Manager shall be the single point of communication and co-ordination
with Pathway’s nominated Test Manager for all matters concerning this
Acceptance Test from its initial planning through to Acceptance.
8.6 PROGRESS REVIEWS
Unless otherwise waived by both parties, Pathway’s Test Manager and the
AUTHORITY’s or AUTHORITIES’ Test Manager shall meet each week to review
the progress and actions of both parties until Acceptance of the Acceptance Test
is achieved. The time and location of review meetings will be scheduled with at
least two week’s advance notice by Pathway.
9. CONTRACTOR RESPONSIBILITIES
The Contractor shall nominate a Test Manager for each Test who shall be the
single point of communication and co-ordination with the AUTHORITY’s or
AUTHORITIES’ Test Manager for all matters concerning this Acceptance Test
from its initial planning through to Acceptance.
Upon receipt of a signed Acceptance Incident Analysis Report from the
AUTHORITY or AUTHORITIES, where correction is required to be re-tested
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 12 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref.: CR/ACS/009
ifi i Version: 3.0
Acceptance Specification Date. 27/11/98
within the same phase of Acceptance Test, the Contractor will return the
amended component(s), on average, within 4 days. This will include re-testing
necessary as per the agreed test strategies.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
CONTRACT CONTROLLED Page 13 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual
obligations between ICL Pathway and the DSS and/or POCL.
FUJ00001464
FUJ00001464
ICL Pathway The ICL Pathway to TIP Interface Ref: CR/ACS/009
af i Version: 3.0
Acceptance Specification Date. 27/11/98
10. ACCEPTANCE TRIAL TEST CONDITIONS
None
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: 4/25/2022
Page 14 of 14
Nothing contained herein shall be deemed or construed as affecting existing contractual obligations or creating new contractual obligations between ICL Pathway and the DSS and/or POCL