CPSC 480 Code Smells

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