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. Function doesn't exist.






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






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






4. Try to find the flaws in your code.






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






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






7. A function that can load a library






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






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






10. Removes files from the repository.






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






12. Plan out your code.






13. Do not optimize until the very end.






14. Ignores files when pushing.






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






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






17. Downloads your changes and then merges.






18. Stops when memory changes.






19. Makes a copy of your repository.






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






21. When a class is defined within another class.






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






23. Keeps a team using a similar naming convention for things.






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






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






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






27. Undo changes made since your last commit.






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






29. Are what function classes should include.






30. You have to tell it to link






31. When GIT cannot merge your data.






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






33. Views all previous changes.






34. When doing a - precise task.






35. Whats displayed to the screen






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






37. Current view/ previous line.






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






39. Creates a spin-off of a repository for concurrent development.






40. When we remove redundant or obsolete designs and replace them with a new.






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






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






43. Current line that is executing.






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






45. Create a test and then create a function.






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






47. When a conflict is fixed.






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






49. Freed heap memory.






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