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. Puts all headers into a master header.






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






3. Functionality Tests.






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






5. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






6. Stand up meetings show who will be valuable and needed.






7. Concept based on limiting the scope of modules to provide better structures.






8. When doing a - precise task.






9. Link multiple projects together






10. Current line that is executing.






11. A collection of memory addresses for all virtual functions in an objects class hierarchy.






12. Variable doesn't exist.






13. Ensure a class only has one instance - and provide a global point of access to it






14. Whats displayed to the screen






15. Initialized stack memory.






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






17. Views all previous changes.






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






19. Ability to treat a class object as a function by overloading the () operator.






20. Code whatever it is you need to code.






21. Bad! Don't ever use these types of variables!






22. Are what function classes should include.






23. Allows you to switch your working copy to another branch.






24. Do not optimize until the very end.






25. A pointer or reference. One object needs to know about the other object to work.






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






27. CONSTANT






28. When a class is defined within another class.






29. A measure of logical dependency.






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






31. Use only through the interface of the object.






32. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






33. Makes a project compile in order of who is dependent on what






34. Stops when memory changes.






35. Connection between a local brand and a remote branch.






36. Code generation in a lib






37. When GIT cannot merge your data.






38. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






39. Removes files from the repository.






40. Current view/ previous line.






41. Initialized heap memory.






42. Set of all pending changes.






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






44. Copies all changes from one branch into another branch.






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






46. NULL memory.






47. Input






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






49. What is part of the current scope.






50. STOP!!