Sunteți pe pagina 1din 22

IFPUG -September 2004 IFPUG-September 2004

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS


Paulo PauloGurevitz GurevitzCunha Cunha EDS EDS--Electronic ElectronicData DataSystems Systems Data DataEngineering EngineeringWest, West, Denver, Denver,CO COUSA USA Communications CommunicationsIndustry IndustrySolution SolutionCenter Center Don DonBeckett, Beckett,CFPS CFPS

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 COTS (Commercial 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.

Agenda

Presentation objectives/Introduction Case Study Determining the boundaries Identifying the Data Functions Identifying the Transaction Functions Estimating and project management considerations Q&A

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS - 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 PROJECTS Determining the Application Boundaries

One of the most complex activities in FP analysis FPA classes usually dont provide enough emphasis on the complexity of this activity Differentiate from Application and Project Look at a typical class example:

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Determining the Application Boundaries
Human Resources System User 1 Request and Displ ay Empl oyee Human Resources Infor matio Application n EQ
Employee Information ILF

Currency Application

APPLICATION BOUNDARY

Conversion Rates EIF

New Employee Information EI User 1 Employee Report EO User 1

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Determining the Application Boundaries
IFPUG CPM 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 (EIs, 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 (EIFs) Is dependent on the users external business view of the application. It is independent of and/or implementation considerations.

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study


Current Application Architecture, extracted from a very large corporation implementing a global solution package

1 2 3 APPL-1 4

APPL-A

APPL-B

APPL-2

6 9

8 APPL-C

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study


In this case the solution adopted is going to replace APPL-1 and APPL-2 as follows:

1 2 3 APPL-1 4

APPL-A

APPL-B APPL-2 7 8 APPL-C 6

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case 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-C Four boundaries are identified

BOUNDARY 1
APPL-A

GLOBAL APPL-C SOLUTION/ERP

APPL-B

10

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study Identifying the Application Boundaries BOUNDARY 2

APPL-A

GLOBAL SOLUTION/ ERP

11

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study Identifying the Application Boundaries BOUNDARY 3

APPL-B

GLOBAL SOLUTION/ ERP

12

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study Identifying the Application Boundaries BOUNDARY 4

APPL-C

GLOBAL SOLUTION/ ERP

13

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study


Identifying Functions
Complete the counting models for each boundary with the identified functions (EIs, EOs, EQs, ILFs and EIFs) Based on business requirements identified on scope statement For the Global Solution boundary we have:

Change interfaces 1 and 6 (External Outputs EO)

Receive interface 5 (External Input EI, 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

EI - Change

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study


Identifying Functions BOUNDARY BOUNDARY 1 1
EOInterface1 (Changed) GLOBAL SOLUTION EO - Interface 1 SISTEMA GLOBAL EO -Interface 6 (C) EO -Interface 6 APPL-C
ILF XPTO-1 ILF Change X PT OILF 1

APPL-A

APPL-C

APPL-A EQ Inquire XPTO-1 (C) EQ Inquire EI - Add, Change and Delete XPTO-1 XPTO-1 EI - Add, Change and Delete Delete XPTO-1 (Changed) EI 5 - Interface 5 (Add) EI - Interface APPL-B APPL-B EQ Inquire EQ Inquire XPTO-2 (C) XPTO-2 Delete EI - Add, Change and Delete XPTO-2 EI - Add, Change and Delete XPTO-2 (Changed) EQ Inquire

EOEO Report (Add) - Report

ILF XPTO-2 X Change P T ILF O X -2


PT ILF XPTO-3 OAdd 3

EI - Delete EQ Inquire (Add) EI Delete (Add) EI ADD (Add)

EI Change (Add)

15

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study

Summary of the count to adapt the Global Solution/ERP:


Function 1. Interface 1 2. Interface 6 3. Interface 5 4. Report 5. ADD XPTO-3 6. Change XPTO-3 7. Delete XPTO-3 8. Inquire XPTO-3 9. XPTO-1 10. XPTO-2 11. XPTO-3 12. ADD XPTO-1 13. Change XPTO-1 14. Delete XPTO-1 15. Inquire XPTO-1 16. ADD XPTO-2 17. Change XPTO-2 18. Delete XPTO-2 19. Inquire XPTO-2 Function Type EO EO EI EO EI EI EI EQ ILF ILF ILF EI EI EI EQ EI EI EI EQ Operation (Added, Changed or Deleted) C C A A A A A A C C A C C C C C C C C

16

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study


Identifying Functions For the APPL-C boundary we have to: Change Interface 7 (External Output EO) to a new format compatible with the ERP. Produce a new Interface 8 (External Output EO)

Change an ILF (XYZ-1) and corresponding updating and inquire functions. Change the reception of a file (External Interface File EIF) that is sent from APPL_B and is also changed as part of this project (Interface 9).
17

EI - Change

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study


Identifying Functions BOUNDARY 4 1
EO Interface 7 (Changed) EO - Interface EO Interface 8 (Add) 1 SISTEMA GLOBAL EO -Interface 6 APPL-C APPL-C GLOBAL APPL-A

ILF X PT OILF 1

SOLUTION/ERP EQ Inquire XPTO-1 EI - Add, Change and Delete Delete XPTO-1 EI- -Interface Interface95(Change) EIF APPL-B EQ Inquire XPTO-2 Delete EI - Add, Change and Delete XPTO-2

ILF XYZ-1

EO - Report

Change

X P T ILF O X -2

PT O3

EQ Inquire EI - Delete EIDelete (Change) EQ Inquire (Change)

APPL-B

EI ADD (Change) EI Update (Change)

18

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS Case Study


Summary of the count to adapt the APPL-C:
Function Type EO EO EI EI EI EQ EIF ILF Operation (Added, Changed or Deleted) C A C C C C C C

Function

1. Interface 7 2. Interface 8 3. ADD XYZ-1 4. Change XYZ-1 5. Delete XYZ-1 6. Inquire XYZ-1 7. Interface 9 8. XYZ-1

19

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS


Next Steps Determine functions complexities Calculate unadjusted function point size Calculate Adjusted FP sizes Estimate the projects size in FP Estimate Decommissioning of existing applications Calculate FP size of installed applications

20

DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS


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 Consider 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

Contact: Contact: pcunha@eds.com pcunha@eds.com (303) (303) 305-1775 305-1775 dmbeckett@msn.com dmbeckett@msn.com (360) (360) 779-2734 779-2734

22

S-ar putea să vă placă și