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. A measure of logical dependency.






2. Variable doesn't exist.






3. A set of creation and initialization steps useful for a set of different related tests.






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






5. Removes files from the repository.






6. One of the linking methods (pragma comment)






7. Code whatever it is you need to code.






8. The default nickname for the remote repository.






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






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






11. Formatted code standards.






12. Black Box - The way the program works is internally unknown.






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






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






15. Stops when memory changes.






16. Fix any problems and then repeat the process.






17. Application






18. About the interface to an object. Data contained within.






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






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






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






22. Weak relationship between two classes. Almost always results in a #include.






23. Input






24. Adds files to the repository.






25. Views all previous changes.






26. When doing a - precise task.






27. Default branch within your repository.






28. STOP!!






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






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






31. When GIT cannot merge your data.






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






33. Breaks encapsulation boundaries.






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






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






36. Plan out your code.






37. Functionality Tests.






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






39. Current line that is executing.






40. Whats displayed to the screen






41. Downloads without merging.






42. Always do the simplest design that could possibly work.






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






44. What is part of the current scope.






45. The process of deciding which function definition to link during run-time.






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






47. Set of all pending changes.






48. Helps to eliminate unnecessary "include chaining."






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






50. Use only through the interface of the object.