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. Black Box - The way the program works is internally unknown.






2. Puts all headers into a master header.






3. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






5. Simply a value.






6. Do not optimize until the very end.






7. A type of library that is used by the code






8. One of the linking methods (pragma comment)






9. You have to tell it to link






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






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






12. The default nickname for the remote repository.






13. Ignores files when pushing.






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






15. Undo changes made since your last commit.






16. Developers should be integrated and releasing code into the code repository every few hours.






17. STOP!!






18. Ability to withstand change and what the effects are.






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






20. CONSTANT






21. Function doesn't exist.






22. When a conflict is fixed.






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






24. Fix any problems and then repeat the process.






25. Allows consumers to try a system earlier and give early feedback.






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






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






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






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






30. Downloads without merging.






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






32. When GIT cannot merge your data.






33. Trying to access a location in memory that your computer cannot access.






34. Creates a copy of your current branch into a remote branch.






35. Are what function classes should include.






36. Quick program.






37. Separating out a section of code into a reusable function or class.






38. A function that can load a library






39. Views all previous changes.






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






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






42. Adds files to the repository.






43. Initialized heap memory.






44. Initialized stack memory.






45. 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






46. Input






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






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






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






50. The linking is already done internally