oO
FUJITSU
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
COMMERCIAL IN CONFIDENCE
POL00033109
POL00033109
Document Title:
Document Reference:
Release:
Abstract:
Document Status:
Author & Dept:
External Distribution:
Security Risk
Assessment
Confirmed
Approval Authorities:
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
REQ/GEN/ACS/0765
Release specific
This document comprises the Acceptance Report for HNG-X Release 2.
It provides details of the Acceptance status of all POL requirements.
associated with the Acceptance Gateway of this Release. It is for
submission to the HNG-X Release 2 Acceptance Board.
Draft
Dave Cooke
HNG-X Acceptance Manager
Steve Wiseall, Graham Bevan
Liz Tuddenham, lan Trundell
NO
lame Role ignature
Steve Wiseall POL Acceptance Manager See Dimensions for record
Dave Cooke FS HNG-X Acceptance Manager See Dimensions for record
See HNG-X Reviewers/Approvers Matrix (PGM/DCM/ON/0001) for guidance on who should approve.
© Copyright Post Office Limited
2010
COMMERCIAL IN CONFIDENCE.
UNCONTROLLED IF PRINTED OR LOCALLY
STORED
Ref: REQ/GEN/ACS/0765
Version: 0.3
Date: 15-July-2010
Page No: 1 of 28
POL00033109
POL00033109
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 4
FUJITSU COMMERCIAL IN CONFIDENCE E&
0 Document Control
0.1 Table of Contents
oO BOCUMENT CONTRO La cnsewenmcmnnnen nner 2
0.1 Table of Contents
0.2 Document History
0.3 Review Details .
0.4 Associated Documents (Internal & External) .
0.5 Abbreviations
0.6 Glossary.
0.7 Changes Expected
0.8 Accuracy....
0.9 Security Risk Assessment..
4 INTRODUCTION
44
12
1.3 Acceptance Board assessment checklist
2 REVIEW OF STATUS OF ACCEPTANCE CRITERIA .......s:sessssessesesserseserseserseeee V1
2.4 Functional Criteria for assessment at the R2 Acceptance Gateway
2.2 Non-Functional Criteria for assessment at the R2 Acceptance Gateway . 13
2.3 Delayed Test status. 15
2.3.1 Delayed Test Status, 15
2.4 iled Status . 18
Use Case Fails
2.4.2 Testable Non-Functional Fail 21
2.5 Failed POL Requirements / not subject to Acceptance 22
2.6 Additional defects identified during R2 testing . 22
3 REVIEW OF STATUS OF ACCEPTANCE INCIDENTS........c:ssssssessssesseseeseeeeseeee 2D
3.1 Acceptance Incidents summary
3.2 Rectification Target timescales for Low Severity Al:
3.2.1 Target Rectification timescales
A APPLICABLE POL REQUIREMENTS AND ACCEPTANCE CRITERIA............ 25
B DEFINITION OF ACCEPTANCE METHODS ..........s:ssssssssssssssssssrseseeseesereeeeeeene 28
C DEFINITION OF ACCEPTANCE INCIDENT SEVERITY............cccsessssessseseeeeeeee QZ
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY Date: 15-July-2010
STORED PageNo: 2o0f 28
POL00033109
POL00033109
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 aj
FUJITSU COMMERCIAL IN CONFIDENCE
D ACCEPTANCE BOARD RECOMMENDATION OPTIONS. ..........cccscseseseeeee
0.2 Document History
Version No. I Date Summary of Changes and Reason for Issue Associated Change -
CP/PEAK/PPRR
Reference
01 09-Jul-2010 Initial version
02 14-Jul-2010 Updates following informal joint review:-
* — Section 0.3 — revisions to review list
* Section 1 — minor revisions and added note that
Generic Acceptance Process is in review and not yet
baselined
+ — Updates to defects and Al details
03 45-Jul-2010 Updates following joint review.
Issued to Acceptance Board
© Copyright Post Office Limited COMMERCIAL IN ‘CONFIDENCE Ref REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED PageNo: 3o0f 28
POL00033109
POL00033109
ACCEPTANCE REPORT FOR HNG-X RELEASE 2 aj
COMMERCIAL IN CONFIDENCE
FUJITSU
0.3 Review Details
See HNG-X Reviewers/Approvers Matrix (PGM/DCM/ION/0001) for guidance on completing the lists below. You
may include additional reviewers if necessary, but you should generally not exclude any of the mandatory reviewers
shown in the matrix for the document type you are authoring.
Review Comments by
david.cooke@
Review Comments to
Mandatory Review
Role
Name
RMGADocumentManagementé GRO
POL HNG-X R2 Programme Manager
Graham Bevan
FS HNG-X R2 Project Manager David Hinde
POL HNG-X R2 Acceptance Manager Steve Wiseall
POL HNG-X Design Authority lan Trundell
FS HNG-X Solution Architect
Gareth Jenkins
POL HNG-X Testing Manager
James Brett
HNG-X Testing Manager
Debbie Richardson
Option:
Role Name
RMGA Commercial Director Guy Wilkerson
POL HNG-X Senior Contracts and Service Manager Liz Tuddenham
FS HNG-X Senior Project Manager David Court
distribution list to a minimum
Position/Role Name
POL Head of Projects Mark Burley
POL HNG-X Testing Manager Lee Farman
HNG-X Programme Manager
Alan D’Alvarez
POL Release Manager
Chris Taylor
FS RMG BU Chief Technology Officer
Amit Apte
(* ) = Reviewers that returned comments
© Copyright Post Office Limited GCNIANEOT. bi Seema Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 4 of 28
POL00033109
POL00033109
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 =
FUJITSU COMMERCIAL IN CONFIDENCE
0.4 Associated Documents (Internal & External)
Reference Version Date Title Source
PGM/DCM/TEM/0001 I 5.0 03 June 2009 RMGA HNG-X Generic Document Dimensions
(DO NOT REMOVE) Template
REQ/GEN/PRO/0735 I 0.3 30 June 2010 HNG-X Generic Acceptance Process I Dimensions
Unless a specific version is referred to above, reference should be made to the current approved
versions of the documents.
0.5 Abbreviations
Abbreviation Definition
0.6 Glossary
Term Definition
0.7 Changes Expected
© Copyright Post Office Limited COMMERCIAL IN ‘CONFIDENCE Ref REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED PageNo: 5 of 28
POL00033109
POL00033109
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
0.8 Accuracy
Fujitsu Services endeavours to ensure that the information contained in this document is correct but, whilst every
effort is made to ensure the accuracy of such information, it accepts no liability for any loss (however caused)
sustained as a result of any error or omission in the same.
0.9 Security Risk Assessment
Security risks have been assessed and it is considered that there are no security risks relating specifically to this
document.
© Copyright Post Office Limited CEAMANEOT, th RememaSEEE Ref REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED PageNo: 6 of 28
POL00033109
POL00033109
o ACCEPTANCE REPORT FOR HNG-X RELEASE 2 4
FUJITSU COMMERCIAL IN CONFIDENCE
1. Introduction
This document comprises the HNG-X Acceptance Report to the HNG-X Acceptance Board for the
assessment of the progression through Release 2 Acceptance Gateway.
The basis for HNG-X Acceptance is defined in REQ/GEN/PRO/0735 — HNG-X Generic Acceptance
process and some sections are reproduced within this report.
[Note: This document is in review and has not yet been agreed / baselined, Any text and references
used in this document are taken from the version shown in section 0.4.]
The HNG-X Requirements and HNG-X Acceptance Criteria are contained in the HNG-X Requirements
Catalogue and represent POL DOORS archive v2.08.
Those HNG-X Acceptance Criteria allocated (in the HNG-X Acceptance Plan) to HNG-X Release 2 are
contained in Appendix A.
The definition of the HNG-X Acceptance Methods is contained in Appendix B.
The definition of the Acceptance Incident Severity is contained in Appendix C.
1.1. Scope
The purpose of this Acceptance Board is: -
‘To agree the Acceptance status of the relevant Release (HNG-X Release 2) and provide a
recommendation to the ‘Joint Release Authorisation Board’.’ The proposed options that this Board can
select from are described in Appendix D.
This recommendation is based on an assessment of the status of the applicable POL Requirements on
Fujitsu and Acceptance Criteria and of the stage progression criteria for the Release 2 Acceptance
Gateway.
The primary assessment concerns the status of all Acceptance Incidents, the workarounds required and
all applicable HNG-X Rectification Plans or target rectification timescales as follows:
Progression through the HNG-X Release 2 Acceptance Gateway shall occur once all of the
following have been satisfied for the HNG-X Acceptance Criteria allocated to achieving
progression through the respective HNG-X Acceptance Gateway:
(a) subject to sections 5.4.1.4 and section 6 of REQ/GEN/PRO/0735 (which refers to dispute
handling, defect aggregation and delayed tests), all such HNG-X Acceptance Criteria have been
achieved;
(b) there are no outstanding HNG-X High Severity Acceptance Incidents;
(c) the number of outstanding HNG-X Medium Severity Acceptance Incidents is five or fewer
and:-
i. an agreed workaround exists for each of them
ii. an agreed HNG-X Rectification Plan exists for each of them unless, exceptionally, the
parties agree that this is not required
(d) there is an agreed workaround for all outstanding HNG-X Low Severity Acceptance
Incidents except for those which the Parties agree do not require a workaround, and:-
© Copyright Post Office Limited CEAMANEOT, th RememaSEEE Ref REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED PageNo: 7 of 28
POL00033109
POL00033109
o ACCEPTANCE REPORT FOR HNG-X RELEASE 2 4
FUJITSU COMMERCIAL IN CONFIDENCE
i. there exists a target timescale for rectification except where the parties agree that this
is not required
(e) details of all Non Incidents are recorded, although they shall have no impact upon
Acceptance Gateway progression
These together with other supporting factors are summarised in the following checklist for Release 2
Acceptance.
It should be noted that there are also defects that have been identified during Release 2 testing that are
not linked to POL Requirements and which are not the subject of Acceptance Incidents. These have
been reviewed as part of the overall Release 2 defect deferral process and the status and significance of
these will be available for consideration at the Release Authorisation Board.
1.2 HNG-X Rectification Plans
All Acceptance Incidents will have an agreed workaround except those for which the Parties agree such a
workaround is not required.
Each Low Severity Acceptance Incident will have a target timescale for rectification except those for
which the Parties agree such a target timescale is not required.
Each Medium Severity Acceptance Incident will have an HNG-X Rectification Plan except where the
Parties agree that a rectification plan is not required. Each rectification plan will include:-
(a) A statement of the operational impact and any necessary temporary procedures to be
adopted by the users
(b) A description of how the rectification is to be achieved; and
(c) A timetable for the rectification
The rectification plans for each of the Medium Severity Acceptance Incidents are contained in section
41.
© Copyright Post Office Limited CEAMANEOT, th RememaSEEE Ref REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED PageNo: 8 of 28
POL00033109
POL00033109
ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
COMMERCIAL IN CONFIDENCE
foe)
FUJITSU
1.3 Acceptance Board assessment checklist
References in this table refer to the HNG-X Generic Acceptance Process REQ/GEN/PRO/0735.
Section Progression conditions or Criteria Status at Release 2
reference Acceptance Gateway
5.4.1 Progression through the Acceptance Gateway shall
occur once all of the following have been satisfied:
5.4.1 (a) subject to paragraph 5.4.1.4, (concerning Delayed I Confirmed.
Tests) all the Acceptance Criteria allocated in the All R2 Acceptance Criteria have
Acceptance Plan have been achieved; ip
been assessed.
5.4.1 (b) there are no outstanding High Severity Acceptance I Confirmed.
Incidents; There are no High Severity Als.
5.4.1 (c) the number of outstanding Medium Severity I Confirmed.
Acceptance Incidents is within the limits agreed for The number of Medium Als is
that release and an agreed workaround and target a
rectification plan exists for each of them .
This is within the limit agreed for
Release 2 (Five or fewer).
5.4.1 (d) there is an agreed workaround and target rectification I Confirmed.
plan for all outstanding Low Severity Acceptance P
Incidents except for those which the Parties agree do oe number of Low Severity Als
not require a workaround or rectification plan. °
The workarounds and
rectification plans are agreed
and are detailed in section 4.2.1
5.4.1.4 Progression through the Acceptance Gateway is
subject to the following considerations: -
5.4.1.4 (a) If, following investigation by Fujitsu, an Acceptance I Acknowledged.
Incident is found to have been caused solely by a Details of defects identified
fault or deficiency in anything other than those during R2 testing that have not
elements of the Release provided by Fujitsu, it shall Stees a a cerisequeries of
not count towards the thresholds identified in ji ;
paragraph 5.4.1. eed 2 are detailed in section
© Copyright Post Office Limited
2010
COMMERCIAL IN CONFIDENCE.
STORED
Ref: REQ/GEN/ACS/0765
Version:
UNCONTROLLED IF PRINTED ORLOCALLY _ Date:
Page No: 9 of 28
0.3
15-July-2010
.
FUJITSU
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
POL00033109
POL00033109
COMMERCIAL IN CONFIDENCE
Section
reference
Progression conditions or Criteria
Status at Release 2
Acceptance Gateway
5.4.1.4 (b) & (c)
Acceptance Incidents that are agreed to result from
the same failure or deficiency, or to affect the same
operational process or business function, may be
aggregated into a single Acceptance Incident for the
purposes of the thresholds identified in paragraph
5.4.1.
The aggregation of two or more Acceptance
Incidents into a single Acceptance Incident shall be
proposed by the Fujitsu Acceptance Manager and
agreed by the Post Office Acceptance Manager, such
agreement not to be unreasonably withheld.
There are no Aggregated Als.
5.4.1.4 (d) If, other than as a result of a Default of Fujitsu I Acknowledged.
Services, it is impossible for a test to be carried out
when scheduled in the Acceptance Plan then that a ae 8 an oeptance
test becomes known as a "Delayed Test". Delayed These are aelaied th section
Tests will be carried out as soon as reasonably 23
practicable. a“
6 Acceptance Dispute Process Confirmed.
There are no unresolved
Acceptance Disputes
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 15-July-2010
STORED PageNo: 10 of 28
POL00033109
POL00033109
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
2 Review of status of Acceptance Criteria
This section shows the status of the POL requirements for the Release 2 Acceptance Gateway. The
Requirements and Acceptance Criteria for Release 2 comprise functional requirements expressed as new
and changed Use Cases and ‘non-functional’ requirements, all of which are grouped under 11 areas of
Business Change formalised via a series of Commercial Terms (CT) documents. The tables below show
the status of the acceptance criteria for the requirements introduced via these CTs.
2.1 Functional Criteria for assessment at the R2 Acceptance
Gateway
There are 31 Use Cases which are new or changed at Release 2. Acceptance testing comprises the
subset of testing that addresses those ‘sections’ of a use case — i.e. a Primary, Sub-flow, Variation or
Exception that have changed at Release 2. The test status of these new or changed sections is as
follows:-
Count of Status Number of: - Acceptance Status of New / Changed UC sections
Commercial Terms reference New /INew // Delayed I Failed Failed Passed
Changed I Changed I Tests (Deferred Fix)
Use Use (No POL
Cases Case (see 2.4.1) Business
sections impact)
(see 2.5)
CT755a High Value Referrals 1 3 1 1 1
CT772a PING —- Transaction 6 28 28
Acceptance
CT778 PAF-Lite 2 7 7
CT779 Policing Methods of 16 32 4 28
Payment
CT781 Streamline Observation 5 27 27
Rectifications
CT797 Improved Stock 2 4 4
Adjustments
CT805 Policing Plastic Refunds 4 9 9
Grand Total 36 110 5 1 104
See Note
Note: Some Use Cases are impacted by more than on CT.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 11 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
Key to Status
Failed (Deferred Fix) — This indicates that a Use Case has one or more defects associated with it, but
that the resolution of these defects have been agreed to be deferred to beyond start of Pilot.
Failed - This status indicates that a Use Case has a defect associated with it that has not yet been
resolved. See section 2.4.1.
Applicable defects are represented as Acceptance Incidents in section 3.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 15-July-2010
STORED Page No: 12 of 28
POL00033109
POL00033109
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 re
FUJITSU COMMERCIAL IN CONFIDENCE
2.2 Non-Functional Criteria for assessment at the R2
Acceptance Gateway
Commercial Terms I Verification I Delayed Test I Failed Failed Passed Grand Total
reference Method
(see 2.3) (Deferred Fix) (No POL impact)
(see 2.4.2) (see 2.5)
CT755a_ High Value I Test 1 1
Referrals
CT772a PING -IDR 1 13 14
Transaction
Acceptance Test 2 1 10 13
CT778 PAF-Lite DR 41 1
Test 2 2
C1779 Policing I Test 1 1
Methods of Payment
CT781 Streamline I DR 1 1
Observation
Rectifications Test 2 1 3
CT797 Improved Stock I Test 1 1
Adjustments:
CT805 / CT853 Policing I Test 1 1
Plastic Refunds
CT762a Date I DR 4 1
Calculation
Test 2 2
CT798 Offline Banking I Test cs 4
Validation
cTso2 / CT846 / I SOF 3 3
CT855 Moneygram
Test 5 5
CT815 / CT838 I DR 3 3
Vocalink
Test 41 7 8
Totals 13 1 50 64
Key to Status
Delayed / Deferred Test —- This identifies the number of criteria that are subject to ‘deferred test’ status.
See section 2.3.
Failed (Deferred Fix) — Each Failed Criteria that is subject to a deferred fix is shown in section 2.4.
Applicable defects are represented by an Acceptance Incident in section 3
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 13 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
Failed (No POL impact) - This status indicates that a criterion has one or more defects associated with it
that has not yet been resolved, but the defect does not have any POL Business Impact and does not
result in an Al. These defects are described in section 2.4.4.1.
Statement of Fact
The nature of the SOF acceptance criteria are such that they are self evident statements that do not
require any formal evidence. As such it has been assumed that they are Passed, and this status has
been advised to the POL stakeholder. If there is evidence of any non-conformance then a defect will be
raised and the requirement will be set to failed.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 15-July-2010
STORED Page No: 14 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
2.3 Delayed Test status
Section 5.4.1.4 of REQ/GEN/PRO/0735 acknowledges that there may be circumstances when previously
scheduled testing that was targeted for completion by this Acceptance Gateway cannot now take place.
Providing that this is not due to a contractual default by Fujitsu, and the parties agree, then the tests
associated with a POL requirement may be delayed. Fujitsu are still obliged to carry out these ‘Delayed
Tests’.
For this Acceptance Gateway, Either Fujitsu or Joint Test Team has requested that tests associated with
the following requirements are given this ‘Delayed Test’ status. Quality Centre does not record this status
and so the current QC status is shown for each criterion.
2.3.1. Delayed Test Status
The Joint Test Team has advised that testing of the following criteria will not complete before the R2
Acceptance Board. Accordingly they are to be given ‘Delayed Test’ status.
Original Original Object text Acceptance Criteria Verification I Status / Impact
Object Id Method
ARC-2259 I Re CR1962-01 In order to I Acceptance Criteria as I TST Tests blocked as currently
introduce Transaction per requirement. unable to carry out end to
Acknowledgements in s . 1 end test of the ETL to
advance of POLSAP it has Verffioatiart that this POLFS and matching
been identified that a requirement hats been process — awaiting Logica
change needs to be made evldone d Ps J me to provide data
to the ETL to POL-FS sien Malai
Functional Specification / Pe
AIS to use Account
Reference ID instead of
Client Reference to
populate the Assignment
field, for all detail records
on this interface.
ARC-2274 I TA-36-01 The TA feed I Verification that this I TST This is target to be run by
should allow credits and I requirement has been 30/07/10.
debits in the same file to I satisfied will be
cater for MOP entries and I evidenced by the End Note that there are no
adjustments. to End Test report examples in Release 2 of
negative TA files that would
result in a positive MOP so
this is a lower priority.
MIG-3269 I The Stock Adjustments I Appropriate migration I TST The five main migration /
functionality shall be I test/scenarios run to introduction tests have all
enabled via ref data I prove this passed.
products at a branch so I functionality. These There is one remaining test
that it can be deployed I should include both . .
gradually through model I products being relating a Horizon cours
office and the use of I enabled and actively o Telovio. OncoMmpIenon
piloting. disabled y .
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY Date: 15-July-2010
STORED Page No: 15 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 re
FUJITSU COMMERCIAL IN CONFIDENCE
Original Original Object text Acceptance Criteria Verification I Status / Impact
Object Id Method
MIG-3260 I The Offline Banking I Appropriate migration I TST Five of the main migration /
functionality for HNG-X I test/scenarios run to introduction tests have all
Release 2 shall only be I prove this passed.
available once Release 2 I functionality. These
has been fully rolled out to I should include both There is one remaining test
which is delayed awaiting
all Counters. It is enabled I products being ‘ex
via POL Reference Data enabled and actively binrtiention frei tte POL.
disabled ref data team.
ARC-2200 I TA-32-01 Solution I Review of OLA DR Details of any OLA changes
supported by changes to associated with PING are
OLA with Fujitsu. Controls due to be provided by POL
to be in place relating to and then reviewed with FS
management of non (Customer Services).
delivery and control
failures.
POS-NFR- I It is a requirement that I Review and approval I DR The required document has
335 Fujitsu will provide the I by POL of the revised been updated and provided
Post Office Postal I Postal Services to POL for assessment.
Services Reference Data I Reference Data
team with details of the I specification There are no known issues.
Reference Data changes I (DES/APP/MAN/0002)
required to define Postal
Services that use the
Simple Destination
Address Capture option.
ARC-2286 I Fujitsu are required to I Tests that successfully I TST 18 tests have passed and 1
update and conform to the I demonstrate is blocked.
the Streamline AIS I conformance to the q
(DES/APP/AIS/0009) to I Streamline AIS as use eet es
reflect the changes in I (DES/APP/AIS/0009) pl y P ,
the associated reference
version 21 of I the data has expired. This is
Streamline Direct due to bi dated to all
Communication Technical testing to con ete 0 allow
Specification 9 pipe:
ARC-2288 I Fujitsu to enhance the I Tests that successfully I TST 18 tests have passed and 1
Chip card handling I demonstrate the is blocked.
counter process such that I correct AID version
a default AID version I number are sent to 7
number is used when no I Streamline in all cases previously passed, but now
match is found in Pin Pad al fee amare d baer
reference data. This .
default value shall be due to be updated to allow
configurable for each testing to complete.
allowable AID via
reference data
This requirement has
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 16 of 28
POL00033109
POL00033109
ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
COMMERCIAL IN CONFIDENCE
.
FUJITSU
Original Original Object text Acceptance Criteria Verification I Status / Impact
Object Id Method
ARC-2284 I Post Office Ltd requires I Review and approval I DR The required document has
the specification and I by POL of the revised been updated and provided
functionality of the AP- I AP-ADC Reference to POL for assessment.
ADC date difference I Manual i
function (see ARC-2140) I (DES/GEN/MAN/0002) There are no known issues.
to be added to the AP-
ADC Reference Manual
(DES/GEN/MAN/0002)
ARC-2289 I Implement additional I As per Requirement TST This is subject to defect
functionality in AP-ADC (in 14014 / PC0201508.
Rd This relates to a_ test
ZZ_SessionReceiptsFields associated with an ADC
variable) to allow selected rn bh
data to be captured as an script which is sending the
gered Ma ot a 20 of a Clydesdale Bank tothe
fields that will be output on Telsconme Web server In
the coresponding receipt order to access the
service. The sort code /
account number are not
being recognised by the
Web server.
ARC-2290 I ‘Introduce additional I As per Requirement TST See entry against ARC-
functionality in AP-ADC (In 2289
the form a new
ZZ_ReportFields variable)
to allow selected data to
be stored as a list of AP-
ADC fields (in the same
format as ZZ_IncFields)
and made available to
subsequent reports via the
REPORT_XML database
field
ARC-2291 I Introduce a Change I As per Requirement TST See entry against ARC-
Product mechanism / 2289
function which enables a
generic AP-ADC script to
switch to a specific AP
product / transaction once
the AP product is
determined
ARC-2346 I The solution shall correctly I Response code 85 is I TST 16 tests have passed and 2
handle response code 85 I handled a specified in are Not complete.
“no reason to decline", inI the LISS = 2008-1 . ‘
accordance with the LISS I version 1.9 standard Completion of I testing I is
2008-1 version 19 awaiting the implementation
standard of a revised baseline.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 15-July-2010
STORED PageNo: 17 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
2.4 Failed Status
This status identifies those Use Cases or non-functional criteria where one or more applicable defects
have been identified. Details of each of these requirements are shown below. Applicable defects
associated with these failed Requirements are shown as Acceptance Incidents and contained in
section 3.
2.4.1. Use Case Fails
Section 2.1 identifies that some Use Cases have the status of failed. The associated defects which are
directly linked to the Release 2 Use Case sections in Quality Centre are: -
CT reference Use Case Use Case Defect Acceptance Status
Reference section
reference
CT0755a GLB-2221 GLB-2294 Defect 13243 / This is subject to Al-R2-001
High Value Settlement by PC0194727 (Low).
‘eferrals Debit /Credit
ep ' 28 tests have This defect concerns the
passed and 4 need to retain the HNG-X
have failed. response code of 10 of a
recovered referral DCS
transaction. At present the
response code reverts to
01 after recovery.
CT0779 Policing GLB-5902 GLB-5905 Defect 13956 / This defect is subject to Al-
Methods of Pco200903 R2-002 (Low) and Al-R2-
Payment peli aaa 003 (Low)
Check Defect 13958 / ;
Pc0200904 This defect concerns the
enabling / disabling of
15 tests have settlement buttons.
passed and 1 has
failed. Initial testing of the fixes
has commenced and the fix
is targeted for inclusion in
R2.
CT0779 Policing RSS-11 RSS-205 Defect 13956 / This defect is subject to Al-
Methods of ‘Add Retail Pco200903 R2-002 (Low) and Al-R2-
Payment Product to 003 (Low)
Basket Defect 13958 /
Pc0200904 This defect concerns the
enabling / disabling of
2 tests have settlement buttons.
passed and 1 has
failed. Initial testing of the fixes
has commenced and the fix
is targeted for inclusion in
R2.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY Date: 15-July-2010
STORED Page No: 18 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 re
FUJITSU COMMERCIAL IN CONFIDENCE
CT reference Use Case Use Case Defect Acceptance Status
Reference section
reference
CT0779 Policing GLB-270 GLB-272 Defect 13956 / This defect is subject to Al-
Methods of Pco200903 R2-002 (Low) and Al-R2-
Payment 003 (Low)
Transact Defect 13958 /
Customer Pco200904 This defect concerns the
Basket enabling / disabling of
15 tests have settlement buttons.
passed and 1 has
failed. Initial testing of the fixes
has commenced and the fix
is targeted for inclusion in
R2.
CT0779 Policing GLB-242 GLB-244 Defect 13956 / This defect is subject to Al-
Methods of Pco200903 R2-002 (Low) and Al-R2-
Payment 003 (Low)
Add Settlement Defect 13958 /
item to Basket Pc0200904 This defect concerns the
enabling / disabling of
18 tests have settlement buttons.
passed and 1 has
failed. Initial testing of the fixes
has commenced and the fix
is targeted for inclusion in
R2.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY Date: 15-July-2010
STORED Page No: 19 of 28
POL00033109
POL00033109
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
2.4.1.1 Additional Functional defects identified during R2 testing
The following defects have been identified during R2 testing and which are agreed as indirectly relating to
Release 2 functionality. They are not linked to any R2 Use Case sections in Quality Centre.
CT reference Use Case Use Case Defect Acceptance Status
Reference section
reference
CT0779 Defect 13957 / This defect is subject to Al-
Policing Method of PCo200888 R2-004 (Low).
Payment
When Policing MOP's
Product 31608 is enabled
the Session receipt for
Offline Banking
transactions does not
contain the following
SortCode
AccountNumber
ChequeNumber
If the product is disabled,
the details appear correctly
on the Session receipt.
Initial testing of the fixes
has commenced and the fix
is targeted for inclusion in
R2.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 20 of 28
POL00033109
POL00033109
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 re
FUJITSU COMMERCIAL IN CONFIDENCE
2.4.2 Testable Non-Functional Fails
Section 2.2 identifies those non-functional criteria that have failed. They are shown below:-
cT DOORS I Requirement text Acceptance Criteria I Verification I Acceptance Status
reference I ID Method
CT772a ARC- TA-40-01 Where no I Acceptance Criteria TST This defect is subject to
PING 2205 Transaction as per requirement. Al-R2-005 (Low) and Al-
Acknowledgement R2-006 (Low).
Verification that this
requirement has.
been satisfied will be
evidenced by the
End to End Test
files are found when
Fujitsu attempts to
process them
(which must be after
a given time as
Defects are 13952 /
PC0200843 and 13983 /
PC0201173.
specified in the AIS report This concerns the
and referenced in alerting of non-delivery of
TA-39-01) Fujitsu TA files.
should raise an Alert
(Times to be Fix is available and is
specified in the scheduled for Release
Als). 2.11 (September 2010).
POL has advised that
Note: The OLA will PING is scheduled to go
document what to live on 16th October
do where there are 2010.
no TA’s. The AIS
will document any
timings
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 21 of 28
POL00033109
POL00033109
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
2.5 Failed POL Requirements / not subject to Acceptance
incidents
Details of those failed Release 2 Acceptance Criteria that are not subject to an Al are listed below. This is
due to POL's assessment that the associated defects do not have any POL Business Impact.
CT reference Use Case Use Case Defect Acceptance Status
Reference section
reference
cT0755a GLB-2221 GLB-5535 Defect 13349 / This defect concerns an
High Value Settlement b: PC0195981 error in the Debit Card
Referrals Debit Voradie. emulator used by Test
QC status is systems only.
Failed
Assessed by POL as
4 tests have having No POL Business
passed and 2 Impact — No Al required.
have failed.
2.6 Additional defects identified during R2 testing
During Release 2 testing a number of defects were identified that relate to the current live service rather
than being introduced by Release 2 functionality or changes. These defects are not the subject of
Release 2 Acceptance but are recorded here and will be provided to the POL and FS live support teams
for operational assessment and prioritisation. Resolution will be agreed as part of the standard live
service defect management processes.
D:\PROFILES\cooked
My Documents\My Dc
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED PageNo: 22 of 28
POL00033109
POL00033109
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
3 Review of status of Acceptance Incidents
The Acceptance Incidents listed below have been raised because the acceptance evidence has
failed to demonstrate that the HNG-X Acceptance Criteria have been achieved.
3.1 Acceptance Incidents summary
The following number of Als have been raised: -
Acceptance Incident Severity
Low 6
Medium [')
High 0
3.2 Rectification Target timescales for Low Severity Als
Post Office and Fujitsu have assessed all of the Release 2 Low Severity Als. Agreements have been
reached on the target timescale for rectification and this is expressed either in the form a time period or
as target release. In some cases a target rectification time is not required, either because the defect is
now closed, is for progression by POL or it is agreed that no rectification is required.
The target timescales are:-
1. Release 2 - These defects have not yet completed R2 testing. They remain targeted for R2.
2. Release 2 Maintenance - target timescale is October 2010
3. Release 3 - target timescale is November 2010 / January 2011
Indicative timescales for these releases are shown above however these are subject to change and will
be formally agreed via the joint programme reviews (for the Functional releases) and via the Release
Management Form (for the maintenance releases).
The total number of individual Low Severity Als associated with these Target Releases / timescales is
summarised below and detailed in the embedded document below.
Target Release / Timescales Totals
Release 2 3
Release 2 Maintenance 2
Release 3 1
Total I 6
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 23 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 re
FUJITSU COMMERCIAL IN CONFIDENCE
3.2.1 Target Rectification timescales
The specific target rectification timescales for each of the Acceptance Incidents is recorded in the
embedded WORD document here.
D:\PROFILES\cooked
My Documents\My Dc
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 24 of 28
POL00033109
POL00033109
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
A Applicable POL Requirements and Acceptance
Criteria
The POL Requirements and Criteria, contained in the HNG-X Requirements Catalogue - POL DOORS
archive v2.08, and associated with Release 2 are contained in the embedded spreadsheet.
D:\PROFILES\cooked
My Documents\My Dc
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED Page No: 25 of 28
POL00033109
POL00033109
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
B Definition of Acceptance Methods
The set of HNG-X Acceptance methods are defined in Appendix D of REQ/GEN/PRO/0735 HNG-X
Generic Acceptance Process and reproduced below.
Type
HNG-X HNG-X Acceptance Criteria that cannot be objectively verified by a test of HNG-X
Document may be satisfied by Post Office undertaking a HNG-X Document Review. The
Review outcome of any such review will be documented by Post Office in the HNG-X
Acceptance Tracking Document. Fujitsu Services will supply a list of documents
(and any specific references within such documents) for Post Office review,
which may satisfy the agreed HNG-X Acceptance Criteria.
HNG-X HNG-X Acceptance Criteria may be satisfied by Post Office participating in an
Design HNG-X Design Walkthrough led by Fujitsu Services of the Fujitsu Services’
Walkthrough I design. The outcome of any such HNG-X Design Walkthrough will be
documented by Post Office in the HNG-X Acceptance Tracking Document.
HNG-X Tests that are owned and managed by Fujitsu Services with significant
Solution Test I Collaborative support from Post Office, for the purpose of verifying that the Fujitsu
Services’ solution for the HNG-X System satisfies the relevant HNG-X
Acceptance Criteria. The collaborative team will produce a joint test report
presenting the results of the tests.
HNG-X Tests that are run and managed by Post Office with significant collaborative
Release support from Fujitsu Services, for the purpose of verifying that the HNG-X
Validation Release satisfies the relevant HNG-X Acceptance Criteria. The combined team
will produce a joint test report presenting the results of the tests and provide
evidence on any areas of non conformance.
Post Office shall specify any need beyond the level of support that Fujitsu
Services are required to provide under normal operational practice (such as a
report etc). Duration, nature and characteristics to be agreed in advance between
Post Office and Fujitsu Services and will take place during Live Pilot or
exceptionally during Live Monitoring. The total duration of HNG-X Monitoring and
the obligations on Fujitsu Services to produce data/reports to support Post Office
monitoring to be agreed between Post Office and Fujitsu Services (each acting
reasonably and in good faith) for a particular HNG-X Requirement.
HNG-X Where the solution to an HNG-X Acceptance Criterion is self-evident and does
Statement of I Not lend itself to formal proving,
Fact
HNG-X Relates to HNG-X Acceptance Criterion that represents an ongoing contractual
Statement of I obligation for HNG-X.
Obligation
Other Used by exception, to be agreed between the Parties.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 15-July-2010
STORED Page No: 26 of 28
POL00033109
POL00033109
o ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
C Definition of Acceptance Incident Severity
The definition of the severity of an HNG-X Acceptance Incident is defined in Appendix A of
REQ/GEN/PRO/0735 HNG-X Generic Acceptance Process and reproduced below.
High The HNG-X Acceptance Incident was caused by the introduction of changes arising
from Project HNG-X and/or the Associated Change Activities that are subject to the
HNG-X Acceptance Process and results in a defect that would render a key element of
one or more of the Business Capabilities and Support Facilities or a key element of the
Infrastructure unfit for operational use, which could include:
a) not allowing Post Office to undertake one or more Transaction types;
b) not allowing Post Office to undertake one or more Transaction types using the
required business inputs or generating the required business outcome;
c) creating system performance issues which are in, or are likely to cause a, breach
of Service Level Targets.
Medium The HNG-X Acceptance Incident was caused by the introduction of changes arising
from Project HNG-X and/or the Associated Change Activities that are subject to the
HNG-X Acceptance Process and results in a defect that would not prevent operation of
one or more of the Business Capabilities and Support Facilities or elements of the
Infrastructure, but would cause problems in the operational use of one or more
Transaction types.
Low The HNG-X Acceptance Incident was caused by the introduction of changes arising
from Project HNG-X and/or the Associated Change Activities that are subject to the
HNG-X Acceptance Process and results in a defect that does not cause any adverse
operational impact in the use of the Business Capabilities and Support Facilities or an
element of the Infrastructure, or the HNG-X Acceptance Incident can be addressed by
a workaround without any adverse operational impact for Post Office.
Non An incident raised by either Party which, following investigation is found:
Incident
> not to be a defect;
> not to have resulted from the introduction of changes arising from Project HNG-X
and/or the Associated Change Activities that are subject to the HNG-X
Acceptance Process; or
» not to fall within the high, medium or low categories set out in this column.
© Copyright Post Office Limited CEAMANEOT, th RememaSEEE Ref REQ/GEN/ACS/0765
2010 Version: 0.3
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 15-July-2010
STORED PageNo: 27 of 28
POL00033109
POL00033109
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 4
FUJITSU COMMERCIAL IN CONFIDENCE
D Acceptance Board recommendation
options
It is proposed that the decision of the HNG-X Acceptance Board should comprise one of
the following options: -
1. Proceed through Acceptance Gateway.
i. Acceptance Gateway criteria have all been met.
ii. There no Acceptance Incidents that would prevent progression through this
Acceptance Gateway
2. Proceed through Acceptance Gateway
i. Not all Acceptance Criteria have been met and consequently there are
Acceptance Incidents.
ii. The severity of these Acceptance Incidents is within the limits for progression
through this Acceptance Gateway.
iii. Each Acceptance Incident has an agreed workaround.
iv. Where required by the contract, all Acceptance Incidents have an agreed
rectification plan or a target timescale for rectification
3. Proceed at risk through Acceptance Gateway
i. Not all Acceptance Criteria have met and consequently there are Acceptance
Incidents.
ii. The severity of these Acceptance Incidents is within the limits for progression
through this Acceptance Gateway.
iii. One or more workaround, rectification plan or target timescale, is not yet agreed.
4. Donot proceed through Acceptance Gateway
i. Not all Acceptance Criteria have been met and consequently there are
Acceptance Incidents.
ii. The severity of these Acceptance Incidents exceeds the limits for progression
through this Acceptance Gateway
iii. Remedial actions are required to address the Acceptance Incidents and / or
workarounds.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.3.
UNCONTROLLED IF PRINTED OR LOCALLY Date 1-July-2010
STORED Page No: 28 of 28