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 reference. Has and delete dynamic memory. implies ownership (Association does not).






2. NULL memory.






3. Will execute all code paths and boundary conditions.






4. STOP!!






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






6. Use only through the interface of the object.






7. A function that can load a library






8. Try to find the flaws in your code.






9. Current line that is executing.






10. No more than 40 hours to stop burnouts.






11. Simply a value.






12. 2 Eyes + 2 Minds = AWESOME!






13. Whats displayed to the screen






14. Removes files from the repository.






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






16. The linking is already done internally






17. Puts all headers into a master header.






18. Are what function classes should include.






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






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






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






22. Views all previous changes.






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






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






25. Formatted code standards.






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






27. Makes a copy of your repository.






28. Stops when memory changes.






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






30. Functionality Tests.






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






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






33. Written by the customers as things that the system needs to do for them.






34. When doing a - precise task.






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






36. Link multiple projects together






37. Plan out your code.






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






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






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






41. The default nickname for the remote repository.






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






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






44. Default branch within your repository.






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






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






47. Breaks encapsulation boundaries.






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






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






50. Ability to treat a class object as a function by overloading the () operator.