Software change - ESSeRE

More documents

Recommendations

Info

Application assessment 1 Factor Understandability Documentation Questions How difficult is it to understand the source code of the current system? How complex are the control structures that are used? Do variables have meaningful names that reflect their function? What system documentation is available? Is the documentation complete, consistent and up-to-date? Data Is there an explicit data model for the system? To what extent is data duplicated in different files? Is the data used by the system up-to-date and consistent? Performance Is the performance of the application adequate? Do performance problems have a significant effect on system users? ©Ian Sommerville 2004 <strong>Software</strong> Engineering, 7th edition. Chapter 21 Slide 56
Application assessment 2 Programming language Configuration management Test data Personnel skills Are modern compilers available for the programming language used to develop the system? Is the programming language still used for new system development? Are all versions of all parts of the system managed by a configuration management system? Is there an explicit description of the versions of components that are used in the current system? Does test data for the system exist? Is there a record of regression tests carried out when new features have been added to the system? Are there people available who have the skills to maintain the application? Are there only a limit ed number of people who understand the system? ©Ian Sommerville 2004 <strong>Software</strong> Engineering, 7th edition. Chapter 21 Slide 57
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: Environment assessment 2 ©Ian Somm
Page 59 and 60: Key points ● ● ● ● Software
show all

Software change - ESSeRE

Create successful ePaper yourself

Delete template?

Save as template?