Transcript Interface Test Plan (Part of RICE Testing) - ABS

Interface Development
Create
Interface FS
for New
Interfaces
Program
Development
(Code, Review,
Unit Test)
Create / Update SAP
Technical
Specifications
RICE
Test
INTEGRATION
PROCESS TEAM
FMS PROGRAMMING
Review /
Update
Phase I
Interface FS
for
Phase II
Reqts
Create / Update
Legacy System
Technical
Specifications
Program
Development
(Code, Review,
Unit Test)
PROCESS TEAM
PROCESS TEAM
Update
Phase I
Interface
FS for
P1E
IA
Configuration
TEST
S
T
R
E
S
S
(End-2-End
Testing)
T
E
S
T
System
Test
LEGACY TEAM
Create /
Update IA
Specifications
S
A
P
IA
Testing (as
needed)
BASIS TEAM
PROCESS TEAMS
BASIS
TEAM
P1 ENHANCEMENT
TEAM
PROCESS TEAMS
DEVELOPMENT / PROCESS / TECH TEAMS
NOTE: Timeline excludes International & CPI
PROCESS TEAMS
TECH TEAM
Shared Ownership
INTERFACE OWNERS
Data Stream
BUDGET
(IT)
MiguelK, BongM
(P2 Process)
FI
TFO
OyanE, BongM
FI
JoyceP
FRMS
RioB, BongM
FI / LO
JoyceP
PAYROLL
IJMS
CecilleA, BongM
CecilleA, BongM
FI / LO
FI
JoyceP
JoyceP
ITS
AlvinS, BongM
LO
JoyceP
TMS
RioB, BongM
JoyceP
CMS2
DodjieP, BongM
LO
LO
HR
CecilleA, BongM
FI
EIS
MiguelK, BongM
FI
JoyceP
JoyceP
PowerBundle (?)
LO – Logistics c/o LodyY and MeleP
(P1 Enhancements)
JoyceP
N/A
N/A
FI – Finance c/o MelCC, IreneC, ElbertC
Team Expectations
P2 PROCESS TEAMS / P1 Enhancement Team
 Ensure quality of functional specification documents turned over to
Development (clear, specific, illustrative)
 Ensure all known business scenarios / requirements and
dependencies are taken into account
2 dimensions to cover:
- Business events
- Timing
 Ensure END-TO-END processing is included in INTEGRATION
TESTING
DOCUMENT DELIVERABLES
Functional Specification Documents (New or Updated)
Interface Test Plan (Part of RICE Testing)
End-to-End Test Plan (Part of Integration Testing)
Team Expectations
DEVELOPMENT TEAMS (IT LEGACY & SAP Programming)
 Ensure complete understanding of functional specifications, avoid
assumptions
 Ensure programs satisfy functional specifications
 Ensure good program design practices are followed
 Ensure controls are included in technical design
• control totals (ex. Number of records / amount sent to SAP, or
extracted from SAP)
• results of processing (ex. No. of records loaded to SAP / rejected)
• no inadvertent duplication of data transfers
 Ensure all transactions time-wise are covered by select conditions (for
extracts)
 Ensure programs are completely component tested (including
performance) and system tested before turning over to INTEG Test
DOCUMENT DELIVERABLES
Technical Specification Documents
Team Expectations
BASIS TEAM
•
•
•
Ensure guidelines on assignment of interface program ID’s are
followed.
Ensure inventory of interfaces are complete and up to date.
Document changes to IA as necessary
DOCUMENT DELIVERABLES
Inventory of Interfaces
Document of changes to IA
Interface Development
Create
Interface FS
for New
Interfaces
Program
Development
(Code, Review,
Unit Test)
Create / Update SAP
Technical
Specifications
RICE
Test
S
A
P
INTEGRATION
PROCESS TEAM
FMS PROGRAMMING
PROCESS TEAM
TEST
Review /
Update
Phase I
Interface FS
for
Phase II
Reqts
Create / Update
Legacy System
Technical
Specifications
Program
Development
(Code, Review,
Unit Test)
System
Test
LEGACY TEAM
(End-2-End
Testing)
PROCESS TEAM
Create /
Update IA
Specifications
Update
Phase I
Interface
FS for
P1E
S
T
R
E
S
S
T
E
S
T
IA
Testing (as
needed)
IA
Configuration
BASIS TEAM
G
O
L
I
V
E
!
BASIS
TEAM
PROCESS TEAMS
P1 ENHANCEMENT
TEAM
Oct 12
NOTE: Timeline excludes International & CPI
11/12
12/3
12/21
Jan 14
CBS
Budget
TFO
FRMS
Payroll
CMS2
ITS