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. Simply a value.






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






3. Try to find the flaws in your code.






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






5. Will execute all code paths and boundary conditions.






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






7. STOP!!






8. No more than 40 hours to stop burnouts.






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






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






11. Set of all pending changes.






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






13. Fix any problems and then repeat the process.






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






15. When doing a - precise task.






16. Breaks encapsulation boundaries.






17. When a class is defined within another class.






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






19. Inheritance between object.






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






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






22. Default branch within your repository.






23. Ignores files when pushing.






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






25. Use only through the interface of the object.






26. One of the linking methods (pragma comment)






27. Puts all headers into a master header.






28. Input






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






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






31. Italicized in UML.






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






33. Meetings used to create a release plan - which will lay out the overall project.






34. The default nickname for the remote repository.






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






36. The linking is already done internally






37. Functionality Tests.






38. CONSTANT






39. NULL memory.






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






41. Plan out your code.






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






43. Initialized heap memory.






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






45. Create a test and then create a function.






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






47. Bookmark of a revised set with a title. For easy checkouts.






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






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






50. Classes build off of each other.