Estimating Software Maintenance Costs

13,481 views 8 slides Jul 28, 2018
Slide 1
Slide 1 of 8
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8

About This Presentation

In Software Engineering under Software cost estimation


Slide Content

Estimating Software Maintenance Costs BY K.LALITHAMBIGA IIMsc(Computer Science & Information Technology) Department of CS&IT NS College of Arts and Science Theni.

Estimating Software Maintenance Costs Software maintenance typically requires 40 to 60 percent, and in some cases as much as 90 percent, of the total lifecycle effort devoted to a software product. The major concerns about maintenance during the planning phase of a software projects are estimating the number of maintenance programmers that will be needed and specifying the facilities required for maintenance. A widely used rule of thumb for the distribution of maintenance activities is 60% -Enhancement 20% -Adaptation 20% -Corrections

In survey 487 business data processing installations, Lientz and Swanson determined that typical level of effort devoted to software maintenance was around FOR EXAMPLE: If a maintenance programmer can maintain 32KDSI, then two a maintenance programmers are required to main 64 KDSI: FSPm =(64KDSI)/(32 KDSI/FSP)=2 FSPm 50% of total lifecycle effort, The distribution of maintenance activities was 51.3% for enhancement , 23.6% for adaptation, 21.7% for repair and 3.4% for others(LIE80).

Boehm suggests that maintenance effort can be activity ratio , which is the number of source instruction to be added and modified in any given time period divided by the total number of instructions: Number of programmer –months required for maintenance in the corresponding time period: In enhancement is provided by an effort adjustment factor EAF, which recognizes that the effort multipliers for maintenance may be different from the effort multipliers used for development: ACT=( DSI added+ DSI modified )/ DSI total PMm =ACT * MMdev PMm =ACT *EAF* MMdev

Maintenance Effort Distribution

Source Instruction per maintenance programmer(Adapted from BOE81)

For Example Heavy emphasis on reliability and the use of modern programming practices during development may reduce the amount of effort required for maintenance, while low emphasis on reliability and modern practices during development may increase the difficulty of maintenance. FSP - Fulltime Software Personnel KSDI -Kilo delivered Source Instruction ACT -Activity ratio DSI -Delivered Source Instruction PM -Programmer Months EAF -Effort Adjustment Factor

Thankyou !!!