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. Quick program.






2. Makes a copy of your repository.






3. Default branch within your repository.






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






5. Set of all pending changes.






6. Code whatever it is you need to code.






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






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






9. Use this to find a memory address or signiture in a dll






10. When a class is defined within another class.






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






12. Inheritance between object.






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






14. Ensure a class only has one instance - and provide a global point of access to it






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






16. Initialized stack memory.






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






18. Classes build off of each other.






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






20. Adds files to the repository.






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






22. No more than 40 hours to stop burnouts.






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






24. Helps to eliminate unnecessary "include chaining."






25. Formatted code standards.






26. Are what function classes should include.






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






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






29. 2 Eyes + 2 Minds = AWESOME!






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






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






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






33. When GIT cannot merge your data.






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






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






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






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






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






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






40. Valid input that the program is designed to process.






41. Removes files from the repository.






42. Freed heap memory.






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






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






45. Allows consumers to try a system earlier and give early feedback.






46. When you type in an object - you can see its attributes.






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






48. Initialized heap memory.






49. Downloads without merging.






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