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. When GIT cannot merge your data.






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






3. Stops when memory changes.






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






5. Function doesn't exist.






6. 2 Eyes + 2 Minds = AWESOME!






7. The default nickname for the remote repository.






8. No more than 40 hours to stop burnouts.






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






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






11. STOP!!






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






13. Link multiple projects together






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






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






16. Default branch within your repository.






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






18. Views all previous changes.






19. Adds files to the repository.






20. Code generation in a lib






21. Current view/ previous line.






22. Formatted code standards.






23. Takes information in the index and pushes it onto the stack.






24. Whats displayed to the screen






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






26. Quick program.






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






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






29. Set of all pending changes.






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






31. Meetings at the beginning of each iteration to produce a plan of programming tasks.






32. Plan out your code.






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






34. Application






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






36. Ask questions and obtain the details and requirements given.






37. A function that can load a library






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






39. Current line that is executing.






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






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






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






43. Downloads without merging.






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






45. NULL memory.






46. Functionality Tests.






47. Fix any problems and then repeat the process.






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






49. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






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