Test your basic knowledge |

SWA - Software Architecture

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Breaks encapsulation boundaries.






2. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






3. Puts all headers into a master header.






4. Do not optimize until the very end.






5. Code whatever it is you need to code.






6. Fix any problems and then repeat the process.






7. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






8. Figure out what is feasible. Decide whether to use API's or to write from scratch.






9. Ability to accept different types of parameters to bind to different implementations at run-time.






10. Portioning your changes to commit by inserting them into the index.






11. Freed heap memory.






12. Classes build off of each other.






13. When GIT cannot merge your data.






14. Valid input that the program is designed to process.






15. Functionality Tests.






16. When a concrete class inherits from a pure interface.






17. Will execute all code paths and boundary conditions.






18. Uploads all changes staged in the index list into the repository database.






19. 2 Eyes + 2 Minds = AWESOME!






20. Bookmark of a revised set with a title. For easy checkouts.






21. Application






22. Are what function classes should include.






23. Undo changes made since your last commit.






24. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






25. Invalid or unexpected input that the program is not designed to process.






26. When doing a - precise task.






27. Adds files to the repository.






28. Ignores files when pushing.






29. Input






30. Simply a value.






31. Use this to find a memory address or signiture in a dll






32. No man's land. Guard bytes before the after allocated heap memory.






33. Put this before a function name in a dll - and the function name will avoid name mangling






34. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






35. Downloads your changes and then merges.






36. Current view/ previous line.






37. How many objects that a source object can legitimately reference.






38. Downloads without merging.






39. Initialized stack memory.






40. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






41. Code generation in a lib






42. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






43. Having power over inheritance with the flexibility of composition.






44. Static in C++. Can span all instances of a class.






45. STOP!!






46. Create a test and then create a function.






47. Linking to dynamic libraries is usually handled by linking to an ____________.






48. CONSTANT






49. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






50. Default branch within your repository.