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. When a class is defined within another class.






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






3. Default branch within your repository.






4. Functionality Tests.






5. Whats displayed to the screen






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






7. Formatted code standards.






8. Quick program.






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






10. One of the linking methods (pragma comment)






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






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






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






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






15. Plan out your code.






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






17. CONSTANT






18. Uploads changes to your current branch.






19. Code generation in a lib






20. Input






21. Adds files to the repository.






22. Undo changes made since your last commit.






23. Current line that is executing.






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






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






26. Ignores files when pushing.






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






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






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






30. Downloads without merging.






31. Breaks encapsulation boundaries.






32. A function that can load a library






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






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






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






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






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






38. NULL memory.






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






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






41. When GIT cannot merge your data.






42. Treating a derived class's data members like it's base class's.






43. Try to find the flaws in your code.






44. Initialized stack memory.






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






46. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






47. Classes build off of each other.






48. Code whatever it is you need to code.






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






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