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. The process of deciding which function definition to link during run-time.






2. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






3. Use only through the interface of the object.






4. Create a test and then create a function.






5. Function doesn't exist.






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






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






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






9. When a conflict is fixed.






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






11. Uploads changes to your current branch.






12. Current line that is executing.






13. What is part of the current scope.






14. 2 Eyes + 2 Minds = AWESOME!






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






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






17. Stops when memory changes.






18. Are what function classes should include.






19. Fix any problems and then repeat the process.






20. Removes files from the repository.






21. CONSTANT






22. Whats displayed to the screen






23. Set of all pending changes.






24. Formatted code standards.






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






26. Views all previous changes.






27. Initialized heap memory.






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






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






30. Breaks encapsulation boundaries.






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






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






33. STOP!!






34. Current view/ previous line.






35. Functionality Tests.






36. Adds files to the repository.






37. A measure of logical dependency.






38. Puts all headers into a master header.






39. Code whatever it is you need to code.






40. No more than 40 hours to stop burnouts.






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






42. Classes build off of each other.






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






44. Simply a value.






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






46. When a class is defined within another class.






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






48. Plan out your code.






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests