This document discusses automated function point analysis (eFPA) in SAP environments. It notes that eFPA provides faster, more transparent estimates than traditional FPA methods by counting software objects like transactions and data elements. eFPA maps these objects in SAP libraries and components to generate estimates. The document concludes that eFPA meets demands for standardized metrics that remain consistent over time and enables early project estimates.
Try MyIntelliAccount Cloud Accounting Software As A Service Solution Risk Fre...
Automated eFPA Provides Fast and Standardized Function Point Estimates for SAP Projects
1. Automated FPA (eFPA) in SAP
Environments
IWSM Mensura 2014
Cees Kuijpers
DutchSoft Technology
The Netherlands
| Automated FPA (eFPA) in SAP Environments 1
2. Content
1 Urgency of Effective Metrics
2 Characteristics of SAP projects
3 eFPA for SAP
4 Application eFPA in other Environments
5 eFPA Findings
6 Conclusions
| Automated FPA (eFPA) in SAP Environments 2
3. 1 Urgency of Effective Metrics
(Gartner)
Through 2015, >70% expect to reduce
their I&O costs by 25%
Managers require a clear understanding
of the costs and require means to
control them
It is to be expected that software metrics
will be applied more and more
Metrics should be based on components
that throughout the project are identified and
keep their same meaning and value (standard)
| Automated FPA (eFPA) in SAP Environments 3
4. 2 Characteristics of SAP projects
FPA rarely applied
Project Size based on Expert Estimate
Expertise is not validated or reusable
Most projects have large overdues
Size grows extremely during the project
| Automated FPA (eFPA) in SAP Environments 4
5. 2 Characteristics of SAP projects
Function Points Delivered at Project End
FPTs assumed at project start
| Automated FPA (eFPA) in SAP Environments 5
9,000.00
8,000.00
7,000.00
6,000.00
5,000.00
4,000.00
3,000.00
2,000.00
1,000.00
-
250 500 750 1000 2000 3000
Project Result Delivered
FPTs non SAP
Project Result Delivered
FPTs SAP
6. 3 eFPA for SAP
Similar to “E&Q FPA”
(Early and Quick Estimate method of Gartner)
E&Q Fundamental Priciples
Principle Explanation
Classification by analogy Similarity by size and/or overall functionality between new
and known software objects
Structured Aggregation Grouping of a certain quantity of lower level software
objects in one higher level software object
No given function/data correlation Data and transactional components assessed
autonomously
Multilevel Approach No discard of details, if available
No need of details, if unavailable
Use of a derivation table Each software object at each level is assigned a size value,
based on an analytically/statistically derived table
| Automated FPA (eFPA) in SAP Environments 6
7. 3 eFPA for SAP
SAP software components
Libraries with node structure
Distinction of business processes and
transactions
Classification possible
Aggregation possible
Masterdata seperately described
| Automated FPA (eFPA) in SAP Environments 7
8. 3 eFPA for SAP
Example of SAP objects information
| Automated FPA (eFPA) in SAP Environments 8
9. 3 eFPA for SAP
Comparison eFPA and IFPUG
eFPA counts data and transactional
components autonomously
IFPUG counts data within transactional
component to determine the weight factor
IFPUG FPA Weight Factor
determined by
User Functions
User Transactions RET, DET User Function TOTAL # FPA IFPUG
eFPA No weight factor
User Function
User Transactions Transactions Sub Count
Record Element Types (RET) Record Element Types Sub Count
Data Element Types (DET) Data Element Types Sub Count
User Function TOTAL # eFPA
| Automated FPA (eFPA) in SAP Environments 9
10. 3 eFPA for SAP
Estimation As a Service with automated tools
Automatic Recognition
Knowledge Base
Applications
Components
Business Processes
Business Transactions
Transactions Details System Objects
Standards (IFPUG +)
| Automated FPA (eFPA) in SAP Environments 10
Categorisation
System Objects
in SAP library
eFPA
Counting Objects within Selected Processes
Calculating Funtion Points
11. 4 Application eFPA in other Environments
Depends on input
Quality Requirement documents varies
In practice extra work has to be done
Completion Business Requirements
Professionalize Project Start Architecture
Till now we delivered eFPA estimates:
+/- 40 SAP estimates
+/- 30 Non SAP estimates
| Automated FPA (eFPA) in SAP Environments 11
12. 4 Application eFPA in other Environments
Estimation As a Service with automated
tools
Automatic Recognition
Knowledge Base
Applications
Components
Business Processes
Business Transactions
Transactions Details System Objects
Standards (IFPUG +)
| Automated FPA (eFPA) in SAP Environments 12
Categorisation
System Objects
in Client Specifications
Enhancing by hand *
*) Data Analysis
Function Analysis
eFPA
Counting Objects within Selected Processes
Calculating Funtion Points
13. 5 eFPA Findings
Variance IFPUG – eFPA between 5%-10%
eFPA can be better supported with automated
tools (from excel to BPM Tools)
eFPA faster (25%-75% less time spent
Estimate can be obtained from 15% to 40% of
project work (or less)
eFPA count is based on exact data
(software objects)
Human factor plays no role anymore
| Automated FPA (eFPA) in SAP Environments 13
14. 5 eFPA Findings
| Automated FPA (eFPA) in SAP Environments 14
90
80
70
60
50
40
30
20
10
0
Reliability Costs Response time Transparency Usability by
incomplete
input
Reusability of
results
Adjustability to
circumstances
Customer Perception of eFPA
15. 6 Conclusions
eFPA works faster
eFPA is transparent
No FPA certification needed
In depth design experience necessary
eFPA complies to the demand:
“components that throughout the project are identified
and keep their same meaning and value (standard)
eFPA enables Early Estimate “Time to Invest”
| Automated FPA (eFPA) in SAP Environments 15