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. Code generation in a lib






2. Inheritance between object.






3. Freed heap memory.






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






5. Create a test and then create a function.






6. Application






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






8. STOP!!






9. The linking is already done internally






10. Makes a copy of your repository.






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






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






13. Fix any problems and then repeat the process.






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






15. Try to find the flaws in your code.






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






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






18. Downloads your changes and then merges.






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






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






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






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






23. Plan out your code.






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






25. Whats displayed to the screen






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






27. Uploads changes to your current branch.






28. When a conflict is fixed.






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






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 we remove redundant or obsolete designs and replace them with a new.






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






33. Stops when memory changes.






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






35. Undo changes made since your last commit.






36. Formatted code standards.






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






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






39. Use only through the interface of the object.






40. Current view/ previous line.






41. One of the linking methods (pragma comment)






42. The default nickname for the remote repository.






43. Italicized in UML.






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






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






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






47. Breaks encapsulation boundaries.






48. No more than 40 hours to stop burnouts.






49. Helps to eliminate unnecessary "include chaining."






50. When doing a - precise task.






text/x-generic sidebar1.php ( HTML document, ASCII text, with very long lines, with CRLF line terminators )