Pathway
FUJ00078024
FUJ00078024
Ref: Risk 49
PATHWAY RISK RESPONSE Version: I
Date: 20/12/95
Document Title:
Document Type:
Abstract:
Distribution:
Document Status:
Document Predecessor:
Associated Documents:
Author:
Approval Authority:
Signature/Date:
Comments To:
Comments By:
PATHWAY RISK RESPONSE
RISK: PWAY000049
Risk Response
This paper provides an initial response to the risk
raised against the Pathway proposal concerning the
development of EPOS.
BA issue - BA/POCL Risk Owners :
Pathway Quality and Risk Management Director
Issued
BA/POCL Risk Register, Version 7, 20th November
1995
JCC Dicks
M H Bennett, Director Quality and Risk Management
M H Bennett
N/A
COMMERCIAL IN CONFIDENCE
Page 0 of 5
FUJ00078024
FUJ00078024
Pathway Ref: — Risk 49
PATHWAY RISK RESPONSE Version: I
Date: 20/12/95
0.1 CONTENT
0.1.1 DOCUMENT HISTORY
Version I Date Reason
1 19/12/95 Externally published
0.1.2 ASSOCIATED DOCUMENTS
Version I Date Title Source
08/06/95 Pathway response Pathway
1 17/11/95 EPOS/OSS Functional Specification I Pathway
1 1/12/95 EPOS/OSS Implementation Plan
1 Sep 1995 Distributed Software Management in I ARTS
Retail
5 19/10/95 BA/POCL Risk Register BA/POCL
0.1.3 ABBREVIATIONS
ARTS Association for Retail Technology Standards
BA Benefits Agency
EPOS Electronic Point of Sale
Oss Operational Support Services
POCL Post Office Counters Limited
SSR Statement of Service Requirements
COMMERCIAL IN CONFIDENCE
Page 1 of 5
FUJ00078024
FUJ00078024
Pathway Ref: — Risk 49
PATHWAY RISK RESPONSE Version: I
Date: 20/12/95
1. INTRODUCTION
This paper provides the response to a specific risk identified by BA/POCL from the
Pathway Proposal concerning the development of the EPOS package.
2. STATEMENT OF THE RISK
“The EPOS package appears to need significant development to meet the POCL
requirements. The timescale of Q1, 1996 may not be achievable.”
3. PATHWAY RESPONSE
3.1 Functional Specification
Pathway has produced and developed the Functional Specification for EPOS and
OSS in direct and specific response to the requirements from the SSR, the schedules
and the POCL Applications stream meetings.
3.2. Implementation Plan
Pathway has established an associated Implementation Plan which analyses the
forms and modules to be implemented together with estimates of the development
work involved.
Pathway has committed resources to the implementation of EPOS and OSS.
This implementation plan will:
1. Define the API and business application components to be developed
1. Estimate the size and complexity of each component
1. Estimate the time and resource required to implement each component
COMMERCIAL IN CONFIDENCE
Page 2 of 5
FUJ00078024
FUJ00078024
Pathway Ref: — Risk 49
PATHWAY RISK RESPONSE Version: I
Date: 20/12/95
3.3. Elements of the EPOS/OSS implementation
The EPOS/OSS functionality will be provided using the layered software architecture
shown. The TMS API is that provided by Riposte.
WINDOWS NT
TMS - RIPOSTE
<— msarl
<— _aPladaption layer
EPOS Oss
if Wf Vt i
POCL COUNTER APPLICATIONS
JL__TL_JT_JL_T_T
Figure I: EPOS'OSS software architecture
—<— ocr ari
3.3.1. POCL Counter Applications
This set of application modules includes the actual business functionality of the
EPOS/OSS functional specification, comprising the Counter and Office functions and
Transactions . It is expected that the business applications will be developed using
Visual Basic.
3.3.2 EPOS/OSS
This will comprise an “umbrella” set of function modules which will fit logically
between business applications and Riposte. This will:
¢ Provide a logical separation between Riposte and the POCL Counter Applications
e Provide the set of EPOS/OSS objects
e Provide a set of Business Application Support Objects and Functions
e Provide the Serve Customer functionality
The EPOS/OSS layer functions will be produced in C/ C++.
COMMERCIAL IN CONFIDENCE
Page 3 of 5
FUJ00078024
FUJ00078024
Pathway Ref: — Risk 49
PATHWAY RISK RESPONSE Version: I
Date: 20/12/95
3.4 Summary of EPOS/OSS Development Resource (Man days)
Counter and Office Functions 206
Transactions 46
Serve Customer Application 50
Business Application Support Objects 232
General EPOS/OSS Objects 134
Total 668
4 PLANS TO ADDRESS THE RISK
Pathway will:
e produce implementation specifications for EPOS and OSS
¢ maintain specifications under review with POCL from time to time as required
e implement EPOS and OSS after confirmation of specification by POCL
Given Pathway’s understanding of the earliest probable procurement timetable,
delivery in Q2 1996 will provide for the operational and live trials.
5. SUMMARY
Pathway has a well defined specification for EPOS and OSS and will implement it in
time for the operational and live trials.
COMMERCIAL IN CONFIDENCE
Page 4 of 5