oO
FUJITSU
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
COMMERCIAL IN CONFIDENCE
POL00033102
POL00033102
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.1
Date: 09-July-2010
Page No: 1 of 31
POL00033102
POL00033102
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 4
FUJITSU COMMERCIAL IN CONFIDENCE
0 Document Control
0.1 Table of Contents
DOCUMENT CONTROL
Table of Contents
Document History
Review Detail:
Associated Documents (Internal & External)
Abbre'
Glossary
Changes Expe: .
Accuracy ....
Security Risk Assessment ..
INTRODUCTION...
ic Io
BE = ISISISISISIRISII
as [e0 Loo Na fom lends feo lo I
1.3. Acceptance Board assessment checklist
2 REVIEW OF STATUS OF ACCEPTANCE CRITERIA .........essssesseeeee 1
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 (Deferred) Test status ..
2.3.1 Delayed Test Status.
2.4 Failed Status
2.4.1 Use Case Fai
2.4.2 Testable Non-Functional Fail
2.5 Additional defects identified during R2 te:
ing
3 REVIEW OF STATUS OF ACCEPTANCE INCIDENTS...........cseceeee
3.
3.1 Acceptance Incidents summary
3.2 Acceptance Incident Aggregation
3.2.1 Aggregated Als from Agreed Deferrals
3.2.2 Aggregated Als from non-testable criteria .
3.2.3 Aggregated Als from testable criteria .
3.3 Acceptance Incident — overall total.....
4 HNG-X RECTIFICATION PLANS & TARGET TIMESCALES.
41 Rectification Plans for Medium Severity Als...
42 Rectification Target timescales for Low Severity Als 24
4.2.4 Target Rectification timescales ....
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY Date: 09-July-2010
STORED PageNo: 20f 31
POL00033102
POL00033102
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 “
FUJITSU COMMERCIAL IN CONFIDENCE E&
A APPLICABLE POL REQUIREMENTS AND ACCEPTANCE CRITERIA............ 26
B DEFINITION OF ACCEPTANCE METHODS ..........ccssssssseseseesereseseseseeseeeseseneenee 27
C DEFINITION OF ACCEPTANCE INCIDENT SEVERITY..........c:sccsescseseeseeeeeeee 28
D ACCEPTANCE BOARD RECOMMENDATION OPTIONS ........c:ccsssssssesseseeeeeee 29
0.2 Document History
Version No. I Date Summary of Changes and Reason for Issue Associated Change -
CP/PEAK/PPRR
Reference
04 09-Jul-2010 Initial version
© Copyright Post Office Limited COMMERCIAL IN ‘CONFIDENCE Ref REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 3 of 31
POL00033102
POL00033102
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 aj
FUJITSU COMMERCIAL IN CONFIDENCE
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
Review Comments to david.cooke¢ & RMGADocumentManagement
Mandatory Review
Role Name
HNG-X Programme Manager Alan D’Alvarez
HNG-X Solution Architect Pete Jobson
POL HNG-X R2 Programme Manager Graham Bevan
POL HNG-X R2 Acceptance Manager Steve Wiseall
POL HNG-X Design Authority lan Trundell
HNG-X Testing Manager Debbie Richardson
POL HNG-X Testing Manager Lee Farman
Option:
Role Name
Head of Programmes — Private Sector Business Unit Mike Wood
HNG-X Release 1 Manager Geoff Butts
RMGA Commercial Director Guy Wilkerson
POL HNG-X Senior Contracts and Service Manager Liz Tuddenham
ed for Informatior le this
distribution list to a minimum
Position/Role Name
POL Head of Projects Mark Burley
(* ) = Reviewers that retuned comments.
© Copyright Post Office Limited COMMERCIAL IN ‘CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED Page No: 4of 31
POL00033102
POL00033102
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, 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.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 5 of 31
POL00033102
POL00033102
oO ACCEPTANCE REPORT FOR HNG-X RELEASE 2 4
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.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 6 of 31
POL00033102
POL00033102
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.
The HNG-X Requirements and HNG-X Acceptance Criteria are contained in the HNG-X Requirements
Catalogue and represent POL DOORS archive v2.07.
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 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 deferred 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:-
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
© Copyright Post Office Limited CEAMANEOT, th RememaSEEE Ref REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 7 of 31
POL00033102
POL00033102
o ACCEPTANCE REPORT FOR HNG-X RELEASE 2 4
FUJITSU COMMERCIAL IN CONFIDENCE
These together with other supporting factors are summarised in the following checklists for AG4.
It should be noted that there are also defects that are not linked to POL Requirements and which are not
the subject of Acceptance Incidents. A separate assessment of the status and significance of these has
been undertaken and this 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.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 8 of 31
POL00033102
POL00033102
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
reference
Progression conditions or Criteria
Status at Release 2
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
Tests) all the Acceptance Criteria allocated in the
Acceptance Plan have been achieved;
Confirmed.
All R2 Acceptance Criteria have
been assessed.
5.4.1 (b)
there are no outstanding High Severity Acceptance
Incidents;
Confirmed.
There are no High Severity Als.
5.4.1 (c)
the number of outstanding Medium Severity
Acceptance Incidents is within the limits agreed for
that release and an agreed workaround and target
rectification plan exists for each of them
Confirmed.
The number of Medium Als is
zero.
This is within the limit agreed for
Release 2 (Five or fewer).
5.4.1 (d)
there is an agreed workaround and target rectification
plan for all outstanding Low Severity Acceptance
Incidents except for those which the Parties agree do
not require a workaround or rectification plan.
Confirmed.
The number of Low Severity Als
is (2).
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
Incident is found to have been caused solely by a
fault or deficiency in anything other than those
elements of the Release provided by Fujitsu, it shall
not count towards the thresholds identified in
paragraph 5.4.1.
Acknowledged.
Details of existing R1 defects
identified during R2 testing are
detailed in section 2.5
© Copyright Post Office Limited
2010
COMMERCIAL IN CONFIDENCE.
Ref: REQ/GEN/ACS/0765
Version: 01
UNCONTROLLED IF PRINTED OR LOCALLY _ Date:
Page No: 9 of 31
STORED
09-July-2010
.
FUJITSU
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
POL00033102
POL00033102
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 a (2) Acceptance
test becomes known as a "Deferred Test". Deferred These are aelalied in 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.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED PageNo: 10 of 31
POL00033102
POL00033102
ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
(oe)
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 1 I New I I Failed Failed Passed
Changed I Changed (Deferred
Use Use Case I Fix) (or Blocked)
Cases sections
CT755a High Value Referrals 1 3 2 1
CT772a PING — Transaction 6 28 28
Acceptance
CT778 PAF-Lite 2 7 Spaabih aed 3
CT779 Policing Methods of 16 32 3 28
Payment
CT781 Streamline Observation 5 27 1 19
Rectifications
1 Failed & Blocked
CT797 Improved Stock 2 4 4
Adjustments
CT805 Policing Plastic Refunds af 9 2 7
Grand Total 36 110 9 90
See Note 1 Blocked/ Failed
10 Blocked
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.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED Page No: 11 of 31
POL00033102
POL00033102
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
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.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED Page No: 12 of 31
foe)
FUJITSU
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
COMMERCIAL IN CONFIDENCE
POL00033102
POL00033102
2.2 Non-Functional Criteria for assessment at the R2
Acceptance Gateway
Commercial _ Terms I Verification Delayed Test I Failed Failed Passed I Grand
reference Method Total
(see 2.3) (Deferred Fix) I (No POL
impact)
(see 2.4.2)
(see 2.4.2.1)
CT755a_ High Value I Test 1 1
Referrals
CT772a PING -IDR 14.NC 14
Transaction
Acceptance Test 2NC 1 10 16
2NR
CT778 PAF-Lite DR 1NC 41
Test 2 2
CT779 Policing I Test 1 41
Methods of Payment
CT781 Streamline I DR 4NC 1
Observation
Rectifications Test 2 - Blocked 1 3
Tests
CT797 Improved Stock I Test 1NC 41
Adjustments.
CT805 / CT853 Policing I Test 1 1
Plastic Refunds
CT762a Date I DR 4NC 1
Calculation
Test 2 2
CT798 Offline Banking I Test 3NC 4
Validation
1NR
cTso2 / CT846 /IDR 1NC 41
CT855 Moneygram
SOF 4 4
Test 4 —with POL 6 7
CT815 / CT838 I DR 3NC 3
Vocalink
Test 8 8
Totals 27NC 4 36 70
3NR
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED Page No: 13 of 31
POL00033102
POL00033102
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE
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
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.
I
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.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED Page No: 14 of 31
POL00033102
POL00033102
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
2.3 Delayed (Deferred) 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 — this is known in the contract as a ‘Deferred Test’.
Fujitsu are still obliged to carry out these ‘Deferred Tests’.
For this Acceptance Gateway, Either Fujitsu or Joint Test Team has requested that tests associated with
the following requirements are given this ‘Deferred 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 ‘Deferred Test’ status.
Original Original Object text Acceptance Criteria I Verification I Status / Impact
Object Id Method
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED Page No: 15 of 31
POL00033102
POL00033102
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 /
High Value PC0194727 This defect concerns the
Referrals Settlement by need to retain the HNG-X
Debit /Credit
response code of 10 of a
recovered referral DCS
transaction. At present the
response code reverts to
01 after recovery.
—
cT0755a GLB-2221 GLB-5535 Defect 13349 / This defect concerns an
High Value PC0195981 error in the Debit Card
Referrals Bee odie emulator used by Test
enh cred QC status is systems only.
Failed
Assessed by POL as
having No POL Business
Impact — No Al required.
CT0779 Policing GLB-5902 GLB-5905 Defect 13956 / Fix informally tested —
Methods of P, PC0200903 Target at 2.07.20
erform Basket
Payment complexity
Check Defect 13958 /
Pco200904 Fixed / Awaiting
confirmation — Targeted at
2.07.20
CTO0779 Policing RSS-205 GLB-5905 Defect 13956 / Fix informally tested -
Methods of ‘: PC0200903 Target at 2.07.20
Add Retail
Payment Product to
Basket Defect 13958 /
Pco200904 Fixed / Awaiting
confirmation — Targeted at
2.07.20
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED ORLOCALLY Date: 09-July-2010
STORED Page No: 16 of 31
POL00033102
POL00033102
oo 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-272 GLB-5905 Defect 13956 / Fix informally tested —
Methods of PC0200903 Target at 2.07.20
Payment
Transact Defect 13958 /
CT0805 Policing Customer Pco200904 Fixed / Awaiting
Plastic Refunds Basket confirmation — Targeted at
2.07.20
CT0781 Streamline I GLB-2221 GLB-4848 Defect 13969 / I Expected to be passed
Observation Settlement By PC0201024
rectifications Debit/ Credit
Defect & Peak
Closed
Qc status is
Failed
CT0781 Streamline I GLB-2221 GLB-4862 Defect 13969 / I Expected to be passed
Observation Settlement B PC0201024
rectifications Debit/ Credit y
Defect & Peak
Closed
Qc status is
Failed
T0779 Policing GLB-242 GLB-244 Defect 13956 / Fix informally tested —
Methods of Pco200903 Target at 2.07.20
Payment Add Settlement
Item to Basket Defect 13958 /
CT0805 Policing PCo200904 Fixed / Awaiting
Plastic Refunds confirmation — Targeted at
2.07.20
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version 0.4
UNCONTROLLED IF PRINTED ORLOCALLY Date: 09-July-2010
STORED Page No: 17 of 31
POL00033102
POL00033102
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 is targeted for
Policing Method of PC0200888 inclusion in R2.07.20
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.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED Page No: 18 of 31
.
FUJITSU
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
COMMERCIAL IN CONFIDENCE
POL00033102
POL00033102
2.4.2
Testable Non-Functional Fails
Section 2.2 identifies those non-functional criteria that have failed. These break down as follows:-
. (4) test criteria are classed as ‘Failed / Deferred Fix’ and are subject to Acceptance Incidents and
are shown in the table below.
. Oy} are classed as Failed but the associated defect has been assessed by POL as not having any
business impact. These are not subject to any Acceptance incidents and are contained section
2.4.2.1.
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 Defect =13952 /
PING 2205 Transaction as per requirement. PC0200843
Acknowledgement
files are found when
Fujitsu attempts to
process them
(which must be after
a given time as
specified in the AIS
and referenced in
TA-39-01) Fujitsu
should raise an Alert
(Times to be
specified in the
Als).
Note: The OLA will
document what to
do where there are
no TA’s. The AIS
will document any
timings
Verification that this
requirement has
been satisfied will be
evidenced by the
End to End Test
report
Fix is available and is
scheduled for Release
2.11 (September 2010).
POL have advised that
PING may not go live
until October 2010.
—
© Copyright Post Office Limited
2010
UNCONTROLLED IF PRINTED OR LOCALLY
COMMERCIAL IN CONFIDENCE.
STORED
Ref:
Version:
Date:
Page No:
REQ/GEN/ACS/0765
0.1
09-July-2010
19 of 31
POL00033102
POL00033102
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
2.4.2.1 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 and
contained in the embedded spreadsheet below. This is due to POL's assessment that the associated
defects do not have any POL Business Impact.
2.5 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 Docurrents\My Dc
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED Page No: 20 of 31
POL00033102
POL00033102
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
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 (2)
Medium
High
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED Page No: 21 of 31
POL00033102
POL00033102
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
3.2 Acceptance Incident Aggregation
REQ/GEN/PRO/0735 (5.4.1.4) recognises that HNG-X Acceptance Incidents that are agreed to result
from the same failure or deficiency, or to affect the same operational process or business function and will
be addressed by one fix or a combination of fixes, may be aggregated into a single HNG-X Acceptance
Incident for the purposes of the thresholds identified in section 1.2. The following sections contain details
of all of the individual Acceptance Incidents and then identifies where aggregation has occurred.
[Note: For R2 there may not be any aggregated Als]
3.2.1 Aggregated Als from Agreed Deferrals
3.2.2 Aggregated Als from non-testable criteria
3.2.3. Aggregated Als from testable criteria
3.3 Acceptance Incident — overall total
The overall status of all Acceptance Incidents is as follows: -
Severity Total
Low (2)
Medium
High
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 22 of 31
POL00033102
POL00033102
oo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
FUJITSU COMMERCIAL IN CONFIDENCE €&
4 HNG-X Rectification Plans & Target timescales
The rectification planned for the Medium severity Als are described below.
4.1 Rectification Plans for Medium Severity Als
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED Page No: 23 of 31
POL00033102
POL00033102
ACCEPTANCE REPORT FOR HNG-X RELEASE 2 7
(oe)
FUJITSU COMMERCIAL IN CONFIDENCE
4.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
oP YN
Specific time period — mainly associated with non-functional defects (typically establishment of
processes or document provision)
Release 2 Maintenance — target timescale is October 2010
Release 3 - target timescale is November 2010 / January 2011
Release 3 Maintenance / Release 4 - target timescale is TBA
Future — this is used for any defects that are agreed as requiring rectification after the releases
named above.
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
Specific time period
Release 2 Maintenance
Release 3
Release 3 Maintenance / Release 4
Future
POL to Action
Rectification timescales not required
(Defects / Als closed)
Total
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED Page No: 24 of 31
POL00033102
POL00033102
eo ACCEPTANCE REPORT FOR HNG-X RELEASE 2 re
FUJITSU COMMERCIAL IN CONFIDENCE
4.2.1 Target Rectification timescales
The specific target rectification timescales for each of the Acceptance Incidents is recorded in the
embedded WORD document here.
[To be supplied]
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED PageNo: 25 of 31
POL00033102
POL00033102
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.07, and associated with Release 2 are contained in the embedded spreadsheet.
This contains references to any Concessions.
© Copyright Post Office Limited COMMERCIAL IN CONFIDENCE Ref: REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 26 of 31
POL00033102
POL00033102
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.1
UNCONTROLLED IF PRINTED ORLOCALLY _ Date: 09-July-2010
STORED Page No: 27 of 31
POL00033102
POL00033102
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.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED Page No: 28 of 31
POL00033102
POL00033102
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. Do not 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 CEAMANEOT, th RememaSEEE Ref REQ/GEN/ACS/0765
2010 Version: 0.1
UNCONTROLLED IF PRINTED OR LOCALLY _ Date: 09-July-2010
STORED PageNo: 29 of 31
POL00033102
POL00033102
fe) ACCEPTANCE REPORT FOR HNG-X RELEASE 2
FUJITSU COMMERCIAL IN CONFIDENCE
E Closed Acceptance Incidents
The following tables contain summary details of Acceptance Incidents that have been raised as part of Acceptance Gateway 3 but have
now been closed. In addition there are some Als that are to be resolved by POL or where it has been agreed that no rectification is
required. These are shown in a separate table
Al reference Al summary Defect Peak Affected Reason for
requirements closure
© Copyright Post Office Limited eee Ref. REQ/GEN/ACS/0765
Version: 0.1
2010
Date: 06-July-2010
UNCONTROLLED IF PRINTED OR LOCALLY STORED Page No: 30 of 31
FUJITSU
ACCEPTANCE REPORT FOR HNG-X RELEASE 2
COMMERCIAL IN CONFIDENCE
POL00033102
POL00033102
F Acceptance Incidents to be progressed by POL
The following tables contain summary details of Acceptance Incidents that were to be progressed by POL or where rectification has been
agreed as not required.
Al reference
Al summary
Defect
Peak
Affected
requirements
Reason
© Copyright Post Office Limited
2010
COMMERCIAL IN CONFIDENCE
UNCONTROLLED IF PRINTED OR LOCALLY STORED
Ref:
Version:
Date:
Page No
REQ/GEN/ACS/0765
0.1
06-July-2010
31 of 31