estimating packaged software - eric van der vliet - nesma najaarsbijeenkomst 2012
DESCRIPTION
TRANSCRIPT
© NESMA najaarsbijeenkomst 2012 1
Estimating packaged softwareThe first part of a framework : Implementations
NESMA working group “Estimating packaged software”
15-11-2012
© NESMA najaarsbijeenkomst 2012 2
IntroductionCurrent situation
There is no generic and independent framework for estimating the cost of packaged software for both implementation and maintenance
Each vendor and implementation partner uses its own proprietary techniques for estimation
It’s hard to compare estimates from different sources or to build up benchmark data for public reference
Scope of this presentation A generic framework for estimating the realisation stage of
packaged software implementationsAmbition
Iteratively expand the scope of this framework to the total scope of implementation and maintenance and
Give insight in how to implement this in an organisation15-11-2012
© NESMA najaarsbijeenkomst 2012 3
Scope Implementation of packaged software
Maintenance of packaged software
15-11-2012
Blueprint Realization Deployment
Run Event-driven maintenance
Planned maintenance
© NESMA najaarsbijeenkomst 2012 4
Packaged softwareGeneral aspects
15-11-2012
© NESMA najaarsbijeenkomst 2012 5
custom build
custom build2
15-11-2012
Generic architecture model package
Core module package (M1)
interfaces
Core module package (M2)
interfaces
configuration
Project Scope
configuration
1
6
5 4 5 5
1. ConfigurationStandard Industry best practice functionality, geared to the customer by configuration
2. Custom built functionalityOrganization specific functionality not inside package
3. Implemented modulesSubset of modules chosen
4. External interfacesInterfaces with other applications/data
5. Internal interfacesPackage proprietary interfaces
6. DataData conversions to use data from existing in/external systems
3
© NESMA najaarsbijeenkomst 2012 6
Differences packaged vs bespoke softwareAspect Packaged software Bespoke software
Functionality overdose exact fit
creation of functionality
configuration (bulk) and tailor made (missing parts)
completely bespoke
lifecycle cost usually cheaper mostly more expensive
size ability poor: a few aspect methods (RICEF, CEMLI)
good: detailed and global (FP’s, Cosmic, UCP, LOC)
estimate ability vague (supplier standards, no common methods)
good: market shared productivity rates
Benchmarking poor: due to size ability good: tooling; benchmark data available
cost engineering more complex due to different element types
mostly straightforward
popularity CxO fast growing only when necessary
15-11-2012
© NESMA najaarsbijeenkomst 2012 7
EPS-FrameworkEstimating Packaged Software
15-11-2012
© NESMA najaarsbijeenkomst 2012 8
EPS-FrameworkGeneric cost estimation model for packaged software
Implementation Maintenance
Two types of cost drivers Size dependent cost drivers
Size drivers Productivity drivers
Size independent cost drivers
Cost drivers are specific for each lifecycle stage
15-11-2012
Blueprint Realization Deployment
Run Event-driven maintenance
Planned maintenance
© NESMA najaarsbijeenkomst 2012 9
Cost drivers EPS-Framework applied to the realisation stage
15-11-2012
© NESMA najaarsbijeenkomst 2012 10
Size depedent cost driversSince...
where: size = almost linear dependent productivity = logarithmic dependent due to complexity expression
...our model exists of two size dependent cost drivers: size drivers, and productivity drivers
(*) effort = effort to realise functionality
15-11-2012
effort(*) = size x productivity
© NESMA najaarsbijeenkomst 2012 11
Size driversSize drivers measure the size of the package architecture
elements Each size driver can have its own size measure Each size driver has a delivery rate
15-11-2012
Package architecture elements: 1. Configuration2. Custom built functionality3. Implemented modules4. External interfaces5. Internal interfaces6. Data
© NESMA najaarsbijeenkomst 2012 12
Size drivers - continuedSize drivers measure the size of the package architecture elements
15-11-2012
Size dep. driver Size x Delivery rate = Effort
This adds up to a combined effort
© NESMA najaarsbijeenkomst 2012 13
Productivity driversCost-drivers that influence the effort are called productivity
drivers Productivity drivers are different for each stage The stages for implementation are blueprint, realization and
deployment
Examples of productivity drivers for the realisation stage are: Number of concurrent users Maturity of the packaged software technology Supplier of the packaged software Required system reliability Percentage of reusable components
In formula:
15-11-2012
Size dep. driver productivity driver x combined effort = total effort
© NESMA najaarsbijeenkomst 2012 14
Size independent driversCost-drivers that are independent of any type of sizing are
called size independent driversExamples are:
Licenses Hardware Data center floor space
15-11-2012
© NESMA najaarsbijeenkomst 2012
The cost estimation model
1515-11-2012
SizeDriver XSizedependentCost:
Size Effort= Delivery Rate1
Size Driver XSize Effort= Delivery Raten
. . .
Productivity Drivers
CombinedEffort
X
Total Effort
Sizeindependent Cost:
CostSizedependent
CostSize independent
Total Cost
© NESMA najaarsbijeenkomst 2012 16
Sizing methodsEstimating packaged software
15-11-2012
© NESMA najaarsbijeenkomst 2012 17
Sizing methodsRICEF
Reports, Interfaces, Conversions, Enhancements and FormsCEMLI
Configurations/Customization, Extensions, Modification, Localization and Integration
Configuration Points A Gartner proprietary technique to measure the configuration
activities in existing packaged software to realize new functionalities
COSMIC An ISO standardized functional sizing method
Function Point Analysis An ISO standardized functional size measurement method
15-11-2012
© NESMA najaarsbijeenkomst 2012 18
Applicability
15-11-2012
Method Configuration Custom Interfaces Data Modules
RICEF Yes, if the elements are defined
Yes, if the functionality is defined
Yes, if the elements are defined
Yes, if the elements are defined
No
CEMLI Yes, if the elements are defined
Yes, if the functionality is defined
Yes, if the elements are defined
Yes, if the elements are defined
No
Configuration points
Yes No Yes Yes No
COSMIC Yes, if the functionality is defined
Yes, if the functionality is defined
Yes, if the interface specifications are defined
Yes, if a data model is available
No
FPA Yes, if the functionality is defined
Yes, if the functionality is defined
Yes,only external interfaces
Yes, if a data model is available
No
© NESMA najaarsbijeenkomst 2012 19
Summary and next stepsPackaged software - Implementation
15-11-2012
© NESMA najaarsbijeenkomst 2012 20
SummaryA first step to define the EPS-frameworkCurrently defined for the realisation stageModel based on cost driversComplete scope including cost estimation
15-11-2012
© NESMA najaarsbijeenkomst 2012 21
Next stepsDefine an independent standard for estimating packaged
softwareVerify the model in practical casesDefine cost drivers for implementation and maintenance
Refine the model for implementation Enhance the model for maintenance
First release EPS-Framework for implementation
15-11-2012
© NESMA najaarsbijeenkomst 2012 22
Working group members Frank Vogelezang
Ordina – Proposal Management Center [email protected]
Eric van der Vliet Logica, now part of CGI – E&M Desk [email protected]
Hans Smit Atos [email protected]
Dirk Vandendaele Gartner Benelux [email protected]
15-11-2012
René Nijland Capgemini – Application
outsourcing [email protected]
John Hommes Sogeti Netherlands [email protected]
Karel van Straaten SNS Reaal [email protected]
Peter Bellen QSM Europe – Estimation [email protected]
© NESMA najaarsbijeenkomst 2012 23
NESMANEtherlands Software Metrics users Association
www.nesma.nl
@NesmaNL
NESMA-NL
15-11-2012