Software change - ESSeRE

More documents

Recommendations

Info

Key points ● ● ● The process of evolution is driven by requests for changes from system stakeholders. Software re-engineering is concerned with restructuring and re-documenting software to make it easier to change. The business value of a legacy system and its quality should determine the evolution strategy that is used. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 21 Slide 60
Page 1 and 2:
Software evolution: Software Change
Page 3 and 4:
Topics covered ● ● Strategies f
Page 5 and 6:
Software change strategies ● ●
Page 7 and 8:
Spiral model of evolution Specifica
Page 9 and 10: Lehman’s laws Law Continuing chan
Page 11 and 12: Software maintenance ● ● ● Mo
Page 13 and 14: Types of maintenance ● ● ● Ma
Page 15 and 16: Distribution of maintenance effort
Page 17 and 18: Maintenance costs ● Cost-effectiv
Page 19 and 20: Maintenance cost factors ● ●
Page 21 and 22: Maintenance prediction ● Maintena
Page 23 and 24: Change prediction ● ● ● Predi
Page 25 and 26: Process metrics ● ● Process mea
Page 27 and 28: Change identification and evolution
Page 29 and 30: Change implementation Proposed chan
Page 31 and 32: Urgent change ● ● ● It’s us
Page 33 and 34: Architectural evolution ● ● The
Page 35 and 36: Legacy systems distribution D e s k
Page 37 and 38: User Interface Distribution ● ●
Page 39 and 40: Key points ● Software change stra
Page 41 and 42: System re-engineering ● ● ● R
Page 43 and 44: Forward and re-engineering S ystem
Page 45 and 46: Reengineering process activities
Page 47 and 48: Reengineering cost factors ● ●
Page 49 and 50: System quality and business value H
Page 51 and 52: Business value assessment ● ● A
Page 53 and 54: Business process assessment ● ●
Page 55 and 56: Environment assessment 2 ©Ian Somm
Page 57 and 58: Application assessment 2 Programmin
Page 59: Key points ● ● ● ● Software
show all

Software change - ESSeRE

Create successful ePaper yourself

Delete template?

Save as template?