IFPUG-September 2004 DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS Paulo Gurevitz unha EDS EDS --Electronic Data Systems Data Engineering West, Denver, O O USA USA ommunications Industry Solution enter Don Don Beckett, FPS
Presentation Objectives The presentation will show how all FP principals apply when counting the size of projects to implement ERPs (Enterprise resource planning software), like SAP, PeopleSoft, etc or any in-house developed or OTS (ommercial Off-The Shelf Software) solution. The presentation will also show how determining the boundaries of the count is the most complex activity in projects of this type illustrating this with a case study. Objective IS NOT determining the size of the ERP installed. 2
Agenda Presentation objectives/introduction ase Study Determining the boundaries Identifying the Data Functions Identifying the Transaction Functions Estimating and project management considerations Q&A 3
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS - Introduction Implementing an ERP is like an enhancement project (FP counting type) Involves adding, changing and deleting functionality Steps involve determining the boundaries, counting data and transaction functions and calculating unadjusted and adjusted function point sizes, like any other project. Focus of the presentation on determining the boundaries and identifying data and transaction functions What is different then? 4
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS Determining the Application Boundaries One of the most complex activities in FP analysis FPA classes usually don t provide enough emphasis on the complexity of this activity Differentiate from Application and Project Look at a typical class example: 5
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS Determining the Application Boundaries Human Resources System User 1 Request and Displ ay Empl oyee Human Resources Infor Application matio n Employee Information ILF EQ urrency Application New Employee Information User 1 APPLIATION BOUNDARY Employee Report EO User 1 onversion Rates F 6
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS Determining the Application Boundaries IFPUG PM 4.2 Definition: The application boundary indicates the border between the software being measured and the user It defines what is external to the application Is the conceptual interface between the internal application and the external user Acts as a membrane through which data processed by transactions (s, EOs and EQs) pass into and out from the application Encloses the logical data maintained by the application (ILFs) Assists in identifying the logical data referenced by but not maintained within this application (Fs) Is dependent on the user s external business view of the application. It is independent of and/or implementation considerations. 7
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study urrent Application Architecture, extracted from a very large corporation implementing a global solution package APPL-1 1 2 3 4 APPL-A APPL-B APPL-2 7 6 9 8 APPL- 8
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study In this case the solution adopted is going to replace APPL-1 and APPL-2 as follows: APPL-1 1 2 3 4 APPL-A APPL-B APPL-2 7 8 6 9 APPL- 9
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Identifying the Application Boundaries The project includes decommissioning application APPL-1 and APPL-2 and enhancing the global solution (or ERP) and applications APPL-A, APPL-B and APPL- Four boundaries are identified BOUNDARY 1 APPL-A APPL- GLOBAL SOLUTION/ERP APPL-B 10
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Identifying the Application Boundaries BOUNDARY 2 APPL-A GLOBAL SOLUTION/ ERP 11
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Identifying the Application Boundaries BOUNDARY 3 APPL-B GLOBAL SOLUTION/ ERP 12
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Identifying the Application Boundaries BOUNDARY 4 APPL- GLOBAL SOLUTION/ ERP 13
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Identifying Functions omplete the counting models for each boundary with the identified functions (s, EOs, EQs, ILFs and Fs) Based on business requirements identified on scope statement For the Global Solution boundary we have: hange interfaces 1 and 6 (External Outputs EO) Receive interface 5 (External Input, that updates the ILF XPTO-1) Produce a new report (External Output EO) Modify two existing ILFs (XPTO-1 and XPTO-2) and corresponding functions to update it and inquire from it. Add a new ILF (XPTO-3) and corresponding functions to update it and inquire from it. 14
- hange APPL- DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study EO -Interface 6 () EO -Interface 6 APPL- EO EO Report - Report (Add) Identifying Functions BOUNDARY 1 1 EO Interface1 (hanged) APPL-A GLOBAL SOLUTION EO - Interface 1 SISTEMA GLOBAL APPL-A EQ Inquire XPTO-1 () EQ Inquire ILF XPTO-1 XPTO-1 - Add, hange and Delete XPTO-1 ILF - Add, hange and Delete hange Delete X XPTO-1 (hanged) PT - Interface 5- Interface 5 (Add) O- ILF 1 ILF XPTO-2 APPL-B X APPL-B EQ Inquire hange P XPTO-2 EQ Inquire XPTO-2 () T Delete ILF O - Add, hange and Delete X -2 XPTO-2 ILF XPTO-3 - Add, hange and Delete XPTO-2 O- Add 3 (hanged) EQ Inquire - Delete EQ Inquire (Add) Delete (Add) hange (Add) ADD (Add) 15
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Summary of the count to adapt the Global Solution/ERP: Function Function Type Operation (Added, hanged or Deleted) 1. Interface 1 EO 2. Interface 6 EO 3. Interface 5 A 4. Report EO A 5. ADD XPTO-3 A 6. hange XPTO-3 A 7. Delete XPTO-3 A 8. Inquire XPTO-3 EQ A 9. XPTO-1 ILF 10. XPTO-2 ILF 11. XPTO-3 ILF A 12. ADD XPTO-1 13. hange XPTO-1 14. Delete XPTO-1 15. Inquire XPTO-1 EQ 16. ADD XPTO-2 17. hange XPTO-2 18. Delete XPTO-2 19. Inquire XPTO-2 EQ 16
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Identifying Functions For the APPL- boundary we have to: hange Interface 7 (External Output EO) to a new format compatible with the ERP. Produce a new Interface 8 (External Output EO) hange an ILF (XYZ-1) and corresponding updating and inquire functions. hange the reception of a file (External Interface File F) that is sent from APPL_B and is also changed as part of this project (Interface 9). 17
- hange DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Identifying Functions BOUNDARY 14 EO Interface 7 (hanged) APPL- EO - Report EO -Interface 6 - Delete APPL- ILF XYZ-1 hange EO Interface EO - Interface 8 (Add) 1 SISTEMA GLOBAL APPL-AGLOBAL EQ Inquire SOLUTION/ERP XPTO-1 ILF - Add, hange and Delete Delete X XPTO-1 PT - Interface 5 O- F - Interface 9 (hange) ILF 1 APPL-B X EQ Inquire P XPTO-2 T Delete ILF O X -2 PT O- 3 - Add, hange and Delete XPTO-2 EQ Inquire EQ Inquire (hange) APPL-B Delete (hange) ADD (hange) Update (hange) 18
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS ase Study Summary of the count to adapt the APPL-: Function Function Type Operation (Added, hanged or Deleted) 1. Interface 7 2. Interface 8 3. ADD XYZ-1 4. hange XYZ-1 5. Delete XYZ-1 6. Inquire XYZ-1 7. Interface 9 8. XYZ-1 EO EO EQ F ILF A 19
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS Next Steps Determine functions complexities alculate unadjusted function point size alculate Adjusted FP sizes Estimate the project s size in FP Estimate Decommissioning of existing applications alculate FP size of installed applications 20
DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJETS Estimating and project management considerations Determine project management strategy Number of projects Platforms Subcontracting vs Internal development groups Project constraints (duration, effort ($), resources) Add up FP sizes that belong to the same project onsider percentages of sizes on different platforms and projects ERP Installation and customizing (not measurable in FP) Data conversion (also measured in FP) 21
Q&A ontact: pcunha@eds.com (303) 305-1775 dmbeckett@msn.com (360) 779-2734 22