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. Try to find the flaws in your code.






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






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






4. When a class is defined within another class.






5. Breaks encapsulation boundaries.






6. Fix any problems and then repeat the process.






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






8. Helps to eliminate unnecessary "include chaining."






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






10. Do not optimize until the very end.






11. A measure of logical dependency.






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






13. Are what function classes should include.






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






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






16. Formatted code standards.






17. Initialized heap memory.






18. Keeps a team using a similar naming convention for things.






19. Function doesn't exist.






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






21. Uploads changes to your current branch.






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






23. Undo changes made since your last commit.






24. Removes files from the repository.






25. Current view/ previous line.






26. Puts all headers into a master header.






27. NULL memory.






28. Makes a copy of your repository.






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






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






31. A reference. Has and delete dynamic memory. implies ownership (Association does not).






32. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






33. Functionality Tests.






34. Quick program.






35. Downloads your changes and then merges.






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






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






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. How many objects that a source object can legitimately reference.






40. Default branch within your repository.






41. Simply a value.






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






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






44. The default nickname for the remote repository.






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






46. Downloads without merging.






47. Italicized in UML.






48. Initialized stack memory.






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






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