L7 Flashcards
What is software evolution?
The process of developing, maintaining, and updating software for various reasons.
This process is complex and entails inherent risks.
What is refactoring?
The process of restructuring an existing code, altering its internal structure without changing its external behavior.
What are the outcomes of software evolution?
- Bugs are fixed
- Useless code removed
- Bad code improved
- Complexity is reduced
What are the indicators of software devolvement?
- Band-aid fixes
- Shortcuts
- Poorly thought out design
- Undocumented changes
List examples of improving readability in refactoring.
- Removing magic constants
- Making variable names more informative
- Decomposing overly long methods
What are some ways to improve understandability in refactoring?
- Reorganizing the class hierarchy
- Removing dead or unused code
- Fixing design
What methods can be employed to improve flexibility in refactoring?
- Improving interfaces
- Improving APIs
- Changing architecture
When is refactoring needed? (list at least three reasons)
- Code is duplicated
- A method is too long
- A loop is too long or too deeply nested
Fill in the blank: Code _______ are indicators of potential issues or areas of improvement in software code.
[smells]
What does refactoring at the data level involve?
Restructuring the way data is organized or represented in the code.
What is refactoring at the statement level focused on?
Improving individual statements or expressions within methods.
What does refactoring at the routine level involve?
Restructuring entire methods or routines for improved readability and maintainability.
What does refactoring at the class level entail?
Restructuring and improving the organization of code within a class.
What does refactoring at the system level involve?
Making changes to the overall architecture and structure components of a software.
