Mind map
Requirements
Map content
Requirements
Good code written following best practices, such as TDD.
- Small amounts of refactoring
- Collapsing heirarchy.
- Good, technical-debt free, expandable code!
- Extract method
- Consolidate conditional expression for the sake of comprehension.
- Extract class if there's enough functionality worth creating a class out of it.
- Decompose conditionals by creating small functions out of the functionality that the conditional is checking for.
- Collapsing heirarchy.
- Small amounts of refactoring
Bad Code written haphazardly; non-systemic and without regard for integrated refactoring.
- Bloating
- Extract class, extract sub-class, extract methods, replace parameters with methods
- Object-Orientation Abuses
- Use polymorphism, push down methods, etc.
- Change Preventers
- Extract class, move methods/fields.
- Dispensables
- Inline class, move method, extract method.
- Couplers
- Move methods, bidirectional to unidirectional association, inline class, etc.
- Bloating
Information
- Description
- Mind Map on Requirements, created by Hammad ur Rehman on 31/07/2024.
- Created by
- Hammad ur Rehman
- Views
- 0
- Rating