DETERMINING THE SIZE OF ERP IMPLEMENTATION PROJECTS. Paulo Gurevitz Cunha EDS EDS --Electronic Data Systems Data Engineering West,

(1)

DETERMINING THE SIZE OF ERP

IMPLEMENTATION PROJECTS

DETERMINING THE SIZE OF ERP

Paulo Gurevitz Cunha

EDS - Electronic Data Systems Data Engineering West,

Denver, CO USA

Paulo Gurevitz Cunha

EDS - Electronic Data Systems Data Engineering West,

Denver, CO USA

IFPUG-September 2004

IFPUG

(2)

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.

(3)

Agenda

•

Presentation objectives/Introduction

•

Case Study

•

Determining the boundaries

•

Identifying the Data Functions

•

Identifying the Transaction Functions

•

Estimating and project management considerations

•

Q&A

(4)

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

(5)

PROJECTS – 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

(6)

Human Resources Application Employee Information ILF New Employee Information EI Currency Application Employee Report EO Human Resources System Conversion Rates EIF Request and Displ ay Empl oyee Infor matio n EQ User 1 User 1 User 1 APPLICATION BOUNDARY

(7)

DETERMINING THE SIZE OF ERP IMPLEMENTATION

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 user’s external business view of the application. It is independent of and/or implementation considerations.

(8)

DETERMINING THE SIZE OF ERP IMPLEMENTATION

PROJECTS – Case Study

APPL-2 APPL-C APPL-B APPL-1 APPL-A 6 7 8 4 3 2 1

Current Application Architecture, extracted from a very large

corporation implementing a global solution package

(9)

9

In this case the solution adopted is going to replace APPL-1 and

APPL-2 as follows:

APPL-2 APPL-C APPL-B APPL-1 APPL-A 6 7 4 3 1 8 2

(10)

BOUNDARY 1

• 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

GLOBAL SOLUTION/ERP APPL-C

APPL-B APPL-A

(11)

BOUNDARY 2

APPL-A

GLOBAL SOLUTION/

ERP

(12)

BOUNDARY 3

APPL-B

GLOBAL SOLUTION/

ERP

(13)

BOUNDARY 4

PROJECTS – Case Study

APPL-C

GLOBAL SOLUTION/

ERP

(14)

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.

(15)

BOUNDARY 1

SISTEMA GLOBAL APPL-C APPL-B APPL-A ILF X PT O-1 ILF X P T O -2 ILF X PT O-3 EI - Delete EO -Interface 6 EO - Interface 1 EO - Report EI - Interface 5 EQ – Inquire

EI - Add, Change and Delete XPTO-1

EQ – Inquire XPTO-1 Delete

EI - Add, Change and Delete XPTO-2 EQ – Inquire XPTO-2 Delete

BOUNDARY 1

GLOBAL SOLUTION APPL-C APPL-B APPL-A EI - Change ILF XPTO-1 Change ILF XPTO-2 Change ILF XPTO-3 Add

EI - Add, Change and Delete XPTO-1 (Changed)

EI - Add, Change and Delete XPTO-2 (Changed) EQ – Inquire XPTO-2 (C) EO–Interface1 (Changed) EI - Interface 5 (Add) EO -Interface 6 (C) EO –Report (Add) EQ – Inquire XPTO-1 (C)

(16)

•

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

C EI 17. Change XPTO-2 C EI 16. ADD XPTO-2 C EQ 15. Inquire XPTO-1 C EI 14. Delete XPTO-1 C EI 13. Change XPTO-1 C EI 12. ADD XPTO-1 A ILF 11. XPTO-3 C ILF 10. XPTO-2 C ILF 9. XPTO-1 A EQ 8. Inquire XPTO-3 A EI 7. Delete XPTO-3 A EI 6. Change XPTO-3 A EI 5. ADD XPTO-3 A EO 4. Report A EI 3. Interface 5 C EO 2. Interface 6 C EO 1. Interface 1

Operation (Added, Changed or Deleted)

Function Type Function

(17)

DETERMINING THE SIZE OF ERP

•

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).

(18)

BOUNDARY 1

Identifying Functions

SISTEMA GLOBAL APPL-C APPL-B APPL-A ILF X PT O-1 ILF X P T O -2 ILF X PT O-3 EI - Delete EO -Interface 6 EO - Interface 1 EO - Report EI - Interface 5 EQ – Inquire

EI - Add, Change and Delete XPTO-1

EQ – Inquire XPTO-1 Delete

EI - Add, Change and Delete XPTO-2 EQ – Inquire XPTO-2 Delete

BOUNDARY 4

EI - Change APPL-C APPL-B GLOBAL SOLUTION/ERP ILF XYZ-1 Change EI–Delete (Change) EQ – Inquire (Change) EI – ADD (Change)

EIF - Interface 9 (Change) EO – Interface 7 (Changed)

(19)

Summary of the count to adapt the APPL-C:

C ILF 8. XYZ-1 C EIF 7. Interface 9 C EQ 6. Inquire XYZ-1 C EI 5. Delete XYZ-1 C EI 4. Change XYZ-1 C EI 3. ADD XYZ-1 A EO 2. Interface 8 C EO 1. Interface 7 Operation (Added, Changed or Deleted) Function Type Function

(20)

DETERMINING THE SIZE OF ERP

Next Steps

•

Determine functions complexities

•

Calculate unadjusted function point size

•

Calculate Adjusted FP sizes

•

Estimate the project’s size in FP

•

Estimate Decommissioning of existing applications

•

Calculate FP size of installed applications

(21)

DETERMINING THE SIZE OF ERP

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

(22)

Q&A

Contact:

[email protected]

(303) 305-1775

[email protected]

(360) 779-2734

Contact:

[email protected]

(303) 305-1775

[email protected]

(360) 779-2734