tailieunhanh - Lecture Software construction - Lecture 21: Software change, evolution and maintenance

It is impossible to produce system of any size which do not need to be changed. Once software is put into use, new requirements emerge and existing requirements changes as the business running that software changes. Parts of the software may have to be modified to correct errors that are found in operation, improve its performance or other non-functional characteristics. | Software Construction Lecture 21 Software Change, Evolution and Maintenance Software Evolution It is impossible to produce system of any size which do not need to be changed. Once software is put into use, new requirements emerge and existing requirements changes as the business running that software changes. Parts of the software may have to be modified to correct errors that are found in operation, improve its performance or other non-functional characteristics. All of this means that, after delivery, software systems always evolve in response to demand for change. Software change Software change is inevitable New requirements emerge when the software is used The business environment changes Errors must be repaired New equipment must be accommodated The performance or reliability may have to be improved A key problem for organisations is implementing and managing change to their legacy systems Software change strategies Software maintenance Changes are made in response to . | Software Construction Lecture 21 Software Change, Evolution and Maintenance Software Evolution It is impossible to produce system of any size which do not need to be changed. Once software is put into use, new requirements emerge and existing requirements changes as the business running that software changes. Parts of the software may have to be modified to correct errors that are found in operation, improve its performance or other non-functional characteristics. All of this means that, after delivery, software systems always evolve in response to demand for change. Software change Software change is inevitable New requirements emerge when the software is used The business environment changes Errors must be repaired New equipment must be accommodated The performance or reliability may have to be improved A key problem for organisations is implementing and managing change to their legacy systems Software change strategies Software maintenance Changes are made in response to changed requirements but the fundamental software structure is stable Architectural transformation The architecture of the system is modified generally from a centralised architecture to a distributed architecture Software re-engineering No new functionality is added to the system but it is restructured and reorganised to facilitate future changes These strategies may be applied separately or together Program evolution dynamics is the study of the processes of system change After major empirical study, Lehman and Belady proposed that there were a number of ‘laws’ which applied to all systems as they evolved There are sensible observations rather than laws. They are applicable to large systems developed by large organisations. Perhaps less applicable in other cases Program evolution dynamics Lehman’s laws Applicability of Lehman’s laws This has not yet been established They are generally applicable to large, tailored systems developed by large organisations It is not clear how they should .

• Kỹ thuật lập trình
• Software change
• Software construction
• Handbook Software construction
• Object oriented design
• Software design
• Software evolution
• Software change
• Software Engineering
• Importance of Software evolution
• Evolution Software processes
• Change implementation
• Maintenance echniques
• Maintenance management
• Lecture Software process improvement
• Bài giảng Cải tiến quy trình phần mềm
• Software process improvement
• Defect prevention
• Technology change management
• Process change management
• Software Problem
• Software Processes
• microsoft Project Management
• Specification
• Functional Specification
• Use Cases
• Lecture Software engineering
• Configuration management
• Change management
• Version management
• Configuration management planning
• Kỹ thuật phần mềm
• Software process
• Lecture Software Quality Assurance
• Software Quality Assurance
• Bài giảng Đảm bảo chất lượng phần mềm
• Software configuration management
• Change control process
• Configuration audit questions
• Lecture Software engineering II
• Bài giảng Kỹ thuật phần mềm II
• Synchronization control
• Configuration audit
• Measuring change activity
• Tracing requirements
• Requirement traceability
• Công nghệ phần mềm
• Nhập môn Công nghệ phần mềm
• Software process models
• Process activities
• Copingwith change
• Ciphers with Python
• ClearCase 7
• C#
• anaging Software Debt
• Building for Inevitable Change
• climate change scenarios
• earth sciences
• Research
• scientific research
• scientific reports
• Journal of Science and Technology
• The effect of D H aspect ratio change
• Energy characteristics of H type darrieus turbine
• Ansys Fluent software
• H type Darrieus turbine
• Project name Implementation Model
• Implementation Model
• Decomposition of the software
• Change Key
• Clear card
• Allergen Bioinformatics
• Recent Trends
• Developments
• Family Based Studies
• Complex Disorders
• Bioinformatics Software
• Forest ecosystem
• Climate change
• Environmental factors
• Light transmission
• Productivity of forest
• Hemisfer software