Transcript Prog - ABS

Programming Team
Agenda
•
•
•
•
•
•
•
•
Responsibilities of Programming Team
Team Structure
Development / Test Clients
Technical Requirements
Functional Requirements
Development Approach / Strategy
Work Plan
Issues / Concerns
Responsibilities
• To develop ABAP programs specified by:
– Process Teams
– Tech Team
• To coordinate the development of nonABAP programs w/ IT Dept
• To maintain database of func/tech specs,
programs, test data & output
Team Structure
Bong
Magnaye
ABS-CBN Team Lead
King Diaz
Anna Griño
Chris Dukay
ABAP Consultant
ABAP Consultant
ABAP Consultant
(Conversion)
Rodel Dulay
Chinitz
Stevens
Emilie
Montalban
ABS-CBN (OTC)
ABS-CBN (RTP)
ABS-CBN
(OTC)
...
Dev’t / Test CLIENTS
• DEV 400 for ABAP development / testing
• Client Copy from 300 to 400
• All Client-Dependent Transport Requests
should also be exported to 400
• DEV 300 for testing of programs w/ no
posting
Technical Requirements
• Transport of new Config to DEV 400
• Set-up / installation of printer(s) to be used
for identified Forms
• Access to OSS
Functional Requirements
• Complete functional specifications w/ emphasis on:
– “Testing Requirements” part
– Interface Requirements
– Report Requirements
– All scenarios / conditions / exceptions
• A “Standard Header” will be used for internal reports
• A standard color scheme will be followed for every
report
• Every Master data update in client 300 should also be
reflected in client 400
Testing Requirements
Test Data Creation:
Scenario
Tranx Code Screen Desc Field Desc Valid Values Function Key
Interface
Input/Output File Layout:
Field #
Description Type
Field
Length
Position in
Line
Notes
Interface
Data Mapping:
Tranx
Code
Dynpro SAP
Table
Field
Field
Desc
Ext File /
Table
Name
Ext
System
Field
Field
Desc
Func Notes /
Calc /
Translations
Standard Header / Color
Program No.
Date Time
Company
Report Title
Date
Sub-total
Grand Total
Page No.
Reports
Field Descriptions:
Tranx
Code
Dynpro SAP
Table
Field
Field
Desc
Field Type Field
Length
Field Func Notes /
Desc/ Calc /
Locn Translations
Dev’t Approach / Strategy
• Signed-off functional specifications (hardcopy) should be
received by the Prog Team Lead
• Team Lead will assign the program to the developer
• Team / Prog Leader will review the func specs
• Developer will create technical specs
• Team / Prog Leader will review and sign off the technical
specs
• Developer will code and test the program
• Team / Prog Leader will review / sign off the code /
program; developer will issue the transport request for QAS
• Process team will do the system test
Dev’t Approach / Strategy
• Prog leader will be assigned to each Process team
• Regular (weekly) meeting will be scheduled per Process
team for status reporting / clarification of functional specs
• For minor questions, the developer will just approach the
designer anytime; no need to schedule a meeting
Dev’t Approach / Strategy
• Listing / Status of programs per team are documented in
the MDM under the programming team:
– ABAP Schedule / Status
• The technical specs and program status are documented
per team in the MDM under the programming team:
– JER programming technical specs
– OTC programming technical specs
– RTP programming technical specs
Work Plan
PRIORITY 1 Programs
Team # Dev
# Prog
Signed- Total
Mandays off
Mandays unassigned
4
Avail
Func
Specs
4
JER
0
1
28
22
OTC
1:2
13
13
2
116
0
RTP
1:1
15
10
2
109
24
Comp Remarks
letion
1 program
–assigned
3rd/4th
wkJan
4th wk
- Jan
Includes 1
medium
program
Issues / Concerns
• Prioritization of programs: integration team requirements
over process team as specified in the Consolidated List of
FMS Programs
• Signed-off functional specs: prog team will only
acknowledge if provided w/ a signed-off copy
• Every update in the Priority no. of program by the Process
team should be relayed to the prog team leader
• The Priority specified in the functional specs does not
match w/ that of the Consolidated List of FMS Programs
• Completeness of Functional specs as specified by the Prog
Team
Issues / Concerns
• Lack of Manpower
• ABS-CBN developers have other load aside from ABAP
programs
• Programming should have started last October based on
the original schedule