RICE Objects Definition

February 27, 2010 · Filed Under Software Estimating, Software Sizing · Comment 

RICE is SAP Terminology (R)eports, (I)interfaces, (C)onversions, (E)nhancements

Reports: Number of formatted and organized presentations of data, including output forms.
Interfaces: Number of boundaries across which two independent systems meet and act on or communicate with each other
Conversions: Number of processes that transfer or copy data from an existing system to load production systems.
Enhancements (Extensions): Number of programs that are in addition to an existing standard program.



Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.




Churn Rate For On-Demand (Software as a Service) Solutions

February 23, 2010 · Filed Under IT Estimating · 1 Comment 

From an email I received from Frontrange Solutions looking at tradeoffs of internal versus SaaS.

“Though many are jumping on the on-demand bandwagon, many are also jumping off.  Churn rates for on-demand are as high as 30 percent while renewal rates with on-premise software stand in the 80 percent range. There must be a reason an increasing number of organizations that tried on-demand applications have returned to an on-premise solution.  For reasons such as:

  • total cost of ownership
  • ease of customization
  • control of data
  • process automation options
  • user-interface
  • disaster recovery

What this doesn’t seem to show is whether those who drop out of SaaS go to an internal solution or just stop doing that SaaS function. This needs more study.

After the recent disaster where the building where we host our mission critical applications (with its backup generators, etc) was without electricity for two days, we are actually investigating getting our email and other functions out onto a data center ourselves.  It is more expensive since we have already invested in infrastructure and IT services.  But it may be worthwhile for disaster recovery.  Of course the questions of what if the data center has a disaster itself, how do we keep long term backups, etc. are still unanswered.



Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.




Impacts on Software Productivity

February 12, 2010 · Filed Under Software Estimating · Comment 

The following summarize the impacts on effective technology (propensity for productivity) of some technology and environment factors.

Parameter Relative Contribution Parameter Relative Contribution
Security Requirements 347% Resource Dedication 25%
Rehost from Development to Target 93% Process Volatility 24%
Analyst Capabilities 71% Specification Level – Reliability 22%
Programmer Capabilities 67% Logon thru Hardcopy Turnaround 22%
Time Constraints 60% Real Time Code 21%
Practices and Methods Experience / Process Improvement 47% Test Level 21%
Requirements Volatility 47% Host System Volatility 19%
Product Reusability 44% Target System Volatility 16%
Analyst’s Application Experience / Application Class Complexity 40% Host Development System Experience / Complexity 15%
Automated Tools Use 35% Multiple Site Development 24%
Memory Constraints 33% Terminal Response Time 13%
Modern Development Practices 31% Special Display Requirements 11%
Programmer’s Language Experience / Language Complexity 30% Target System Experience / Complexity 7%
Resource & Support Location 28% QA Level 6%

For more complete discussion see my book on Software Sizing, Estimation and Risk Management.



Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.