SEF20 Code Smells
Across
- 4. Every time you create a subclass one hierarchy, you have to create a subclass in another hierarchy is the code smell ______ Inheritance Hierarchies
- 5. Classes that have too many fields (instance variables), i.e., store too much state
- 7. A field is only set/used in certain situations
- 9. Other contributor, besides Fowler, to code smells
- 13. The class is all fields (data members), getters, and setters, but nothing else
- 14. Most switch statements should be replaced by _________
- 16. There is a program entity (class, method, parameter, code fragment, statement, variable) that is unused in the system
- 18. The code smell where a class needs data from another class, and has to go through a long chain of calls to get to it
- 19. Bunches of data that always hang around together
- 20. Primitive types are used when an object is needed
- 22. Code that was over-generalized in an attempt to predict future needs
- 25. A subclass doesn’t use all the inherited methods or data
- 26. The code smell where one method is too interested in other classes
Down
- 1. One class is commonly changed in different ways for different purposes
- 2. A class that is not doing enough
- 3. Where code is repeated
- 6. Code smell category that hinder further changing or developing the system are change-_________
- 8. Too much code in one method
- 10. Where two classes are too tightly coupled to each other
- 11. Code smell category for where code does not fully exploit the possibilities of object-oriented design is Object-Orientation ______
- 12. A class exists just to delegate to another class
- 15. A code smell indicates the need for a _____
- 17. Code smell category for an entity that has grown so large or long it can't be effectively handled
- 21. Code smell category for code or classes that should be removed
- 23. Code smell category of lowering coupling, and problems that you get when trying to do so
- 24. Detecting code smells is primarily based on developer _______