ICL
Pathway
FUJ00119619
FUJ00119619
End to End Service Ref: RS/ACS/oo1
Version: 1.0
Acceptance Specification Date: 24/12/98
Document Title
Document Type
Abstract
Status
Author
Approval By
Distribution
Recommended
for Approval
Signature
Name
Date
Approved
Signature
End to End Service Acceptance Test.
Acceptance Specification
This document describes the Acceptance Test for End to End
Service
Issued
John C C Dicks
8/1/99
Pathway Management Team
Test & Integration Managers
Pathway Library
POCL/DSS Horizon Library
Jeff Austen
PDA tba
ICL Pathway Test Manager Authority(ies) Test Manager
For and behalf of ICL For and behalf of Authority(ies)
Pathway
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORMAT ]
CONTRACT CONTROLLED Page 1 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/08
Name
Date
o_. DOCUMENT CONTROL
ll DOCUMENT HISTORY
Version Date Reason
03
0.4
0.5
0.6
0.7
0.8
1.0
Last version relative to Release 1e
New Release 2 Version for review
New Release 2 Version for approval
New Release 2 Version for approval
New Release 2 Version for approval. Inclusion of R928
New Release 2 Version for approval
Title
Standard for Raising and
Progressing Acceptance
Incidents.
Source
Pathway
Standard for documenting Pathway
Acceptance Specifications
Acceptance Procedures
Schedule (A)Ao7
Acceptance Procedures
Schedule (P)An
Acceptance Procedures
Schedule (D)Au
Requirements Schedule
1/5/97
30/3/98
23/7/98
30/10/98
13/11/98
and updates to R938 Criteria
10/12/98
24/12/98 Approvals version.
ASSOCIATED DOCUMENTS
Reference Version Date
Acceptance Ou 13/09/96
Standard
Acceptance 1.2 13/7/98
Standard
Authorities’ 7.2 22/5/97
Agreement
POCL 7.2 22/5/97
Agreement
DSS 72 22/5/97
Agreement
Authorities’ 8. 8/3/98
Agreement
(A)Bo4.
DSS/POCL
POCL
DSS
DSS/POCL
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
Printed on: [ DATE \*
Page 2 of 30
FUJ00119619
FUJ00119619
Ic. End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
Reference Version Date Title Source
(8) Authorities’ 81 8/3/98 Solutions Schedule Pathway
Agreement (A)Bo5
(9) DSS 81 8/3/98 Requirements Schedule DSS
Agreement (D)A15,
(io) DSS 8.1 8/3/98 Solutions Schedule Pathway
Agreement (D)A16
(u) POCL 8.0 13/u/97__—_ Requirements Schedule POCL
Agreement (P)A15
(iz) POCL 81 8/3/98 Solutions Schedule Pathway
Agreement (P)A16
(13) CR/FSP/oog 4.0 30/9/97 — Service Architecture Pathway
Design Document
(44) PA/STR/oog 2.0 24/2/98 Release Contents Pathway
Definition for Pathway
New Release 2
(15) BP/IFS/006 1.6 16/4/96 POCL Interface DSS/POCL
Requirements For
BA/POCL System
(36) TI/IFS/oo1 5.1¢ 17/2/98 Pathway to TIP POCL
Application Interface
Specification
(17) BP/IFS/oo7 33¢ 2/2/98 Reference Data to Pathway POCL
(Reference Data Project
Application Interface
Specification)
(8) LF/BRD/oo1 1.0 20/5/98 Business Requirements POCL /
Definition - Logistics Pathway
Feeder Service
(a9) AP/IFS/oo1 2.0 30/10/97 Pathway to HAPS Interface Pathway
Specification
(20) RS/POL/ooz 3.0 8/10/96 Pathway Security Policy Pathway
(21) RS/PRO/o30 0.2 4/8/98 Evidential Information - Pathway
Production & Certification
PACE Procedures
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
Printed on: [ DATE \*
Page 3 of 30
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
Reference Version Date Title Source
(22) 2.0 14/5/96 Service Provider Solutions Pathway
Document
(23) 3.2 20/2/98 — Service Provider Solutions Pathway
Document
(24) VI/TSC/110 1.0 30/1/98 Pathway Release 2 Systems Pathway
Management HLTP
(25) VI/STR/o06 2.0 24/10/97 Revisions To The Testing & Pathway
Integration Approach For
Pathway Release 2.0
(26) 0720HL~1.DO 0.2 18/798 End to End Interface POCL/DSS
Cc Testing High Level Test
Plan, BA/POCL Nile
Release 2.0
Testco~1.xls 7/10/98 BPS
(27) tba End to End Interface POCL/DSS
Testing Test Report
(28) CR/FSP/oog = 5.1 23/7/98 Service Architecture Pathway
Design Document
(29) Pathway Customer Service Pathway
DPA Procedure
(30) As_cavoidoc ou. 4/12/98 Acceptance Specification I DSS / POCL
draft Consolidated Caveats
0.3 ABBREVIATIONS
ALPS Automated London Post office System
APS Automated Payment Service
BES Benefit Encashment Service
BT Business Thread
CAPS Customer Accounting and Payments Strategy
CMS Card Management Service
DIT Direct Interface Test
DPA Data Protection Act
DSS Department of Social Security
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
Printed on: [ DATE \*
Page 4 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
Ic. End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
E2E End to End
EFTPOS Electronic Funds Transfer at Point of Sale
HAPS Host APS
HLTP High Level Test Plan
MOR Model Office Rehearsal
OBCS Order Book Control Service
OPS Office Platform Service
PAS Payment Authorisation Service
PDA Programme Delivery Authority
POCL Post Office Counters Ltd
SMS Systems Management Service
TMS Transaction Management Service
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 5 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
ICL End to End Service Ref.: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
FUJ00119619
FUJ00119619
0.4 CHANGES IN THIS VERSION
Version for approval. Caveats document added to references.
0.5 CHANGES FORECAST
Updates to the Associated Documents table.
0.6 GENERAL CAVEAT
Approval of this Acceptance Specification is subject to the relevant caveats in the
extant version of Acceptance Specification Consolidated Caveats.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 6 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
0.5 TABLE OF CONTENT
0. DOCUMENT CONTROL ......csssessesssseesessesseeeseesecssessesensesesssessesseessenseeeeees 2
Ll DOcUMENT HIsTORY sed
0.2. ASSOCIATED DOCUMENTS 2
03 ABBREVIATIONS........+++ 4
0.4 CHANGES IN THIS VERSION. 6
0.5 CHANGES FORECAST . 6
0.6 GENERAL CAVEAT.. 6
0.5 TABLE OF CONTENT ....ccscsessssssesesesesscsesesscueseseecseeueasansnssucacsnsusnesesrsesnsacseseeneneaeeseee 7
1. PURPOSE & SCOPE .....ssscsssssessessessesesseseesessesscsessseesssesssnessesseseessseeseesesseeases 8
2. ACCEPTANCE INCIDENTS........c:ccsccsscsssessesscessessssesscseseseeeseessesesenscnsseeneeeee 8
3. ACCEPTANCE PERIOD ....csccssssssssssssscsssscsssscsssscsssscsssscssssccssscesssecsseessseesssees 9
4. DELIVERABLES & SERVICES .......cssssscssssessesseseeseesessecessesesseesseneesessenseseeneees 9
5. ACCEPTANCE CRITERIA ........cccccscesscesseesecseeseecseeesesseeeenseeeeeeeneneeceeesseeees 10
54 ACCEPTANCE CRITERIA AND TEST CONDITIONS.........00++
5.11 Description Of Tests Conducted By Acceptance Trial.
5.1.2 Description of tests conducted by Acceptance Review
5.2 CRITERIA FOR LATER ACCEPTANCE
5.3. CRITERIA SUMMARY..........eese000
6. ACCEPTANCE INCIDENT SEVERITY
61 HIGH SEVERITY INCIDENTS. ......cssscesssseesessessesseseesesssseesessesssseesessssvessessansseesressseese 2O
6.2 MEDIUM SEVERITY INCIDENTS
63 Low SEVERITY INCIDENTS
7. TEST DATA ...ssscsssssssscsssrssssensscsssecerorsscsencnsssoacscssscsssnonenesssaroressscesnanesasscssoes 27
8. AUTHORITY RESPONSIBILITIES.
8.1 APPOINT TEST MANAGER
8.2 ACCEPTANCE INCIDENT REPORTS ......e0000
83 ACCEPTANCE INCIDENT ANALYSIS REPORTS.
8.4 ATTENDANCE AT TRIALS AND REVIEWS
85 MANAGEMENT AND CO-ORDINATION .
8.6 PROGRESS REVIEWS ....-.seessee00e
9. CONTRACTOR RESPONSIBILITIES .......ccsscscsessesescssesssssesesesseteeseeseeeees 28
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 7 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
1o. ACCEPTANCE TRIAL TEST CONDITIONS...
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 8 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref.: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
1. PURPOSE & SCOPE
This document describes the Acceptance Test for End to End Service 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 End to End Service 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 POCLDSS POCLIDSS
Implementation Implementation Implementation
“Training Service Rollout
fs DSS Interface TIP Interface MIS Interface
a PAS ems
5 2
Help Desks < &
Reference
Data
Reconciliation
POC,
Infrastructure
APS
HAPS: ate
Figurei-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”.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 9 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
3 ACCEPTANCE PERIOD
The Acceptance Period for the Acceptance Tests, which comprise the Operational
Trial, is as determined by schedule Bo7 of the AUTHORITIES’ Agreement.
The Pathway programme plan details the schedule for the End to End Service
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
End-to-End Service I Requirements Schedule (A)Boq. Acceptance Trial
Requirements Schedule (D)A15 Acceptance Review
Requirements Schedule (P)A15
Table of Deliverables and Services.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 10 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
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.
5.1. ACCEPTANCE CRITERIA AND TEST CONDITIONS
Conformance of the End to End Service 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 in a 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.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 11 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
ICL End to End Service Ref.: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
FUJ00119619
FUJ00119619
5.11 Description Of Tests Conducted By Acceptance Trial
There are no Tests to be conducted by Acceptance Trial. However, a
comprehensive Test based upon the End to End element of Integration Test is
included under the Acceptance Review heading.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 12 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
5.1.2 Description of tests conducted by Acceptance Review
The table below shows which Acceptance criteria are to be met by Acceptance
Review. Acceptance Tests will use the versions of any relevant documents (as
referenced from section 0.2) contained in the approved version of the Acceptance
Specification.
‘I 831
I 5 through 7 (POCL only)
Requirement
5) The POCL Interfaces documentation shall cover: data
content in logical groupings, physical layouts, controls
(including security), timings, volumes, technical
interface specifications (initially options and
constraints), configuration management, and
contingency arrangements. Versions of the POCL
Interfaces documentation containing the existing
interfaces shall be made available to the
CONTRACTOR within three (3) months after
execution hereof.
I (6) The POCL Interfaces documentation shall not initially
cover further potential interfaces in respect of:
(a) EFTPOS;
(b) reconciliation and exception reporting;
(c) operational management information;
(d) performance monitoring;
(e) inspection of Transaction and Event logs for audit
and security purposes;
(f) transitional arrangements in relation to the
automated payments / ALPS host;
(g) transitional arrangements in relation to 'cash
account processing’.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 13 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Refi: RS/ACS/oot
Version: 1.0
Pathway Acceptance Specification Date: 24/12/08
(7) The detailed format of all interfaces shall be agreed by
POCL.
(5) Scope of interface documents is satisfactory.
Documents for existing interfaces are provided
(6) No test required
(7) Interface documents are agreed
Document review
(5) Reference (15) is obsolete; References (16), (17), (18)
(a9)
(6) None
(7) References (16), (17), (18) (19)
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 14 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Refi: RS/ACS/oot
Version: 1.0
Pathwoy Acceptance Specification Date: 24/12/98
ou
1,2
Requirement
(1) The Services shall maintain accounting and reporting
integrity in the Services and Service Infrastructure,
including any changes as defined in Schedule Aos5
[Change Control] of the AUTHORITIES’ Agreement.
Such integrity shall cover implementation of changes,
reverting to previous states (should this prove
necessary, for example in fall-back and Recovery), co-
existing before and after states (e.g. if simultaneous
implementation does not occur) and reporting across
change boundaries (e.g. using appropriate Reference
Data versions for each part of a report).
Changes approved via Change Control are incorporated
Software distribution is capable of roll back (“regression”)
Document and reports inspection
Contractor presentation
Letter J Dicks to M Reade 9 March.
Report from (24) (particularly SDo3 and SD21)
Presentation (Reporting Across Change Boundaries)
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT I
Printed on: [ DATE \*
CONTRACT CONTROLLED Page 15 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
925,
B
Letter Pat Kelsey to Jim Morley 23/7/97, (25)
The performance of the End to End element of Integration
Test.
The overall objectives for E2E, in association with Model
Office Rehearsal, centre on the bringing together of the IT
functionality across all the participating systems, with the
operational and business procedures, to form an overall
business system. E2E and MOR activities are planned and
scripted together, run on the same environment, and
involve the same personnel. E2E forms a natural extension
of DIT. It is run in parallel with, but separate from, MOR.
The E2E agreed test report contains no non-conforming
entries for Pathway-specific elements.
Note: Pathway has the right of approval of the HLTP and
the associated Test Report as it affects the Pathway
elements.
Review of the test report (27)
(26)
Technical Test
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 16 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
928
1,2
Requirement
1. The CONTRACTOR shall provide to the AUTHORITY
copies of the Service Architecture Design Document by
a date consistent with the project plan agreed by the
parties, such that the date does not adversely impact
contractual milestones as defined in Clause 605.1 of the
Authorities Agreement.
2. The Service Architecture Design Document shall be
updated to ensure information is always current.
A satisfactory document has been developed and
maintained
Document inspection
(13) plus associated agreement letter of 15/1/98 most recent
agreed version
(28) most recent maintained version
Operational trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 17 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
ICL End to End Service Ref.: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
FUJ00119619
FUJ00119619
938
3
Requirement
The CONTRACTOR shall provide all Services to support
the functional specification.
This criterion is not applicable to Pathway.
See response to Requirement 938 criterion 1 (DSS
Interface)
Not applicable
Not applicable
Not applicable
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 18 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Refi: RS/ACS/oot
Version: 1.0
Pathwoy Acceptance Specification Date: 24/12/98
938
4 through 8
(4) The CONTRACTOR shall ensure that any information
supplied under the Data Protection Act 1984 is
accurate and that assurances can be given as to the
integrity of that information.
(5) The CONTRACTOR shall deliver any information
requested under the Data Protection Act 1984 to the
requesting body, person or DSS as appropriate.
OUTLINE SERVICE REQUIREMENTS
(6) The Data Protection Act 1984 became law from 11
November 1987. All subsequent alterations and reviews
to this law shall be integrated and adhered to.
(7) The CONTRACTOR shall record all written requests
for a data protection print from a Customer,
representative or DSS within forty (40) days of receipt
of the request, and deal with queries raised within a
timescale to be agreed with the AUTHORITIES by a
date consistent with the project plan agreed by the
parties, such that the date does not adversely impact
contractual milestones as defined in Clause 605.1 of the
Authorities Agreement, such agreement not to be
unreasonably withheld or delayed.
(8) All information provided under the Data Protection
Act 1984 shall be available to facilitate inspection.
Details of a request and response made under the Data
Protection Act 1984 shall be retained consistent with the
Data Protection Act 1984 requirements.
(4), (6) and (8) not applicable to Pathway
See response to Requirement 938 criterion 1.
(5), (7) Pathway refers requests from members of the
public to DSS in accordance with agreement of 13 March
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
Printed on: [ DATE \*
CONTRACT CONTROLLED Page 19 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref.: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
1998.
Document inspection
Same as 938/4-8 (End-to-End Acceptance Specification)
(20) Section 9.2; (29)
Operational trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 20 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
950
ithrough 9
Requirement
(a)
(2)
The CONTRACTOR shall provide an overview
document which describes and summarises the
solutions they are proposing in response to the
requirements documents sent to them. It shall be
written in such a way that it logically links back to the
requirements.
This document shall include aspects of the overall end
to end solution which are not explicitly defined in the
individual responses to requirements.
The document shall be text biased and not exceed 35
pages. It may be supported by annexes which could
include flow diagrams of the technical solution and the
support processes. It shall be provided on floppy
diskette in Word 6 (12 point) format accompanied by
three hard copies.
The format is to cover the following:
DSS
This shall describe CMS and PAS and shall include the
following topics:
(a) Hardware proposed and sizing;
(b) physical locations of central sites;
(c) Software proposed;
(d) network (including topology, protocols);
(e) external interfaces (including CAPS and POCL
systems);
) resilience and availability;
) security;
) fallback and Recovery;
) scalability.
POCL
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORMAT ]
CONTRACT CONTROLLED Page 21 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
(6) An end to end description of how the POCL Service
Infrastructure shall operate covering all Outlets. This
shall cover the solutions for OP, TMS, SM, APS, BES,
EPOSS and OBCS and shall include the following
topics:
(a) Hardware proposed (with expected utilisation);
(b) physical locations of central sites;
(c) Software proposed (including operating system,
middleware and Application Software);
(d) Wide Area Network (including topology,
protocols, message authentication);
(e) security (including any key management);
(£) external interfaces (including POCL and Client
systems);
fallback and Recovery;
resilience and availability;
scalability;
system management.
Technical Interfaces
(7) A description of how all the components of the Service
Infrastructure interact with each other and with other
systems such as CAPS and Post Office Group
accounting systems.
Benefit Payment Service
(8) This shall draw together the specific solutions to CMS,
PAS and BES into an integrated end to end picture of
how the Benefit Payment Service shall work. This shall
draw together the specific solutions to:
(a) Card design;
(b) responsibilities;
(c) security;
(d) fraud investigation;
(e) contingency.
Provision of Services
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 22 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
FUJ00119619
FUJ00119619
(c)
(d)
(e)
(9) An end to end description of how the solutions shall be
implemented and shall include:
Roll Out through to Steady State Service;
migration of existing automation and services;
training and Documentation;
Customer education and marketing;
support Services, specifically help facilities.
(10) The report shall be written at a level directed at
Programme Team members who have a knowledge of
the solution proposed.
A document was provided
Document inspection
(22) Original delivery at time of contract
(23) Last update
Operational trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORMAT ]
CONTRACT CONTROLLED Page 23 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
End to End Service Ref.: RS/ACS/oo1
Version: 1.0
Acceptance Specification Date: 24/12/98
951
1 through 3
Requirement
(a)
(2)
The CONTRACTOR shall develop and maintain the
Service Architecture Design Document, a document
describing the design of the Service Architecture.
As a minimum the Service Architecture Design
Document shall specify:
(a) the major components, provided directly or sub-
contracted, used in providing the Services;
(b) the functionality within the major components;
(c) the interfaces between the major components;
(a) the Service Levels required across the interfaces
to meet the objectives of the overall Services;
(e) all the interfaces with the Service Environment
and with other parties’ computer systems.
The audience for the Service Architecture Design
Document shall be technical staff within the
AUTHORITIES. The Service Architecture Design
Document shall be self contained, though it is
expected that it references other documents to provide
further levels of detail as appropriate. The level of
detail within the Service Architecture Design
Document shall be such that it gives a thorough
background to the construction of the Services and the
rationale for the approach. It is anticipated that the
Service Architecture Design Document shall be
between 200 and 400 pages in length.
A satisfactory document has been developed and
maintained
Document inspection
(13) plus associated agreement letter of 15/1/98 most recent
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORMAT ]
CONTRACT CONTROLLED Page 24 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
ICL End to End Service
Acceptance Specification
Ref.:
Version:
Date:
FUJ00119619
FUJ00119619
RS/ACS/oo1
1.0
24/12/98
agreed version
(28) most recent maintained version
Operational trial
973
1
Requirement
The Services may, during the lifetime of the Related
Agreements or at termination, need to be replaced or
supplemented with services provided by other suppliers. It
shall therefore be both technically and commercially viable
for the Services to be replaced by and/or interfaced to
services from other suppliers. To support this, the
CONTRACTOR shall declare all internal interfaces
between separate Services within the overall Service
Architecture (including those between PAS and CMS, PAS
and the POCL Infrastructure Services, CMS and the POCL
Infrastructure Services). For each interface the
CONTRACTOR shall provide an interface specification
covering the same properties and to the same level of
detail as requirements 934-940 and 942.
described level of detail
Internal interfaces have been declared and specified at the
Document inspection
(13), (28) Appendix B
Operational trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
Printed on: [ DATE \*
Page 25 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
5.2 CRITERIA FOR LATER ACCEPTANCE
There are no Acceptance Criteria for Acceptance at a later level of specification.
5.3. CRITERIASUMMARY
835 “7 v
ou 1,2 v
925 B v
928 1,2 v
938 3 No test
938 4-6, 8 No test
938 Z v
950 1-10 v
951 13 v
93 1 v
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 26 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
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.
64 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.
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.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 27 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
6.3. LOWSEVERITY 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 (but see R925/13 and (26))
Organisation: Not applicable
8. AUTHORITY RESPONSIBILITIES
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.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 28 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
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 I 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 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: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 29 of 30
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119619
FUJ00119619
ICL End to End Service Ref: RS/ACS/oo1
Version: 1.0
Pathwoy Acceptance Specification Date: 24/12/08
1o. ACCEPTANCE TRIAL TEST CONDITIONS
None, but see Review Criterion 925/13.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORMAT ]
Page 30 of 30
Nothing contained herein shall be deemed or consrucd ay affecting existing contractual obligations or creating new contractual obligations between ICL
Pathway and the DSS and/or POCL.