System reconstruction
- Architecture is not eternal. Architecture also has a life cycle. It will also experience the process of birth, development, peak, decline, and death.
What is refactoring?
- An adjustment to the internal structure of software.
- The purpose is to improve the understandability and reduce the cost of modification without changing the observable behavior of the software.
Method to realize
- Use a series of refactoring techniques to adjust the structure of the software without changing its observable behavior.
Reconstruction concept:
- Achieve large-scale changes step by step using a large number of small steps that maintain the behavior of the software.
Early System Advantages
- Fast development
- Low code complexity
- Code specifications are kept intact
- Strictly focus on development specifications and will not allow code that endangers the architectural design to be generated
- The above factors lead to low difficulty and low cost of adding functions.
late system
- Has all the disadvantages of a morning system
-
- Code specification complexity is high
-
- Incomplete code specifications
-
- Many requirements or functions exceed the architectural design
-
- Adding new functions takes into account more, involves more modules, and affects the whole body.
- When it is discovered that an existing architecture system can no longer meet the current iteration speed, reconstruction work is required.
Micro refactoring
- Use some refactoring methods to micro-refactor the code with "bad smell"
Refactoring process
Determine the problem points, determine the refactoring function and scope→Old architecture design and logical sorting→Stability guarantee→Performance guarantee→Conflict issues in the requirements process