3460:421 OOP S22 Software Design

5. One feature of a good design is _____ cohesion
6. In design, we define the overall _____
8. One of the C++ access specifiers
9. Another name for the layer equivalent to a class
10. The lowest layer of a system
17. In a good design, it is easy to add _____
18. Software design must satisfy _____ requirements
19. Another name for the layer equivalent to a directory
21. In a good design, it is easy to _____ bugs
22. In software design, we create a specification of a software artifact using a set of primitive _____
23. One feature of a good design is _____ coupling
24. _____ _____, which comes from structured programming, asks the question, "What are the functions?"
25. In design, we create a _____ of a software artifact
27. In _____-level design, we are closer to analysis

1. In software design, we create a specification of a software artifact that is subject to _____
2. One feature of a good design is a consistent, _____ vocabulary
3. In class design with more than a single class, we have to determine the _____ of the classes
4. The layer right below a system
7. _____-_____ _____, which comes from object-oriented programming, asks the question, "What are the classes?"
11. Design primarily involves making choices between _____
12. In a good design, it is easy to determine the _____ of bugs
13. In _____ design, we determine what classes exist and what methods they have
14. A good design has the _____ efficiency
15. Treat as the same layer as a method
16. In good design, errors are handled _____
20. In low-level design, we are closer to _____
26. Software design is the _____ of defining software methods, functions, objects