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. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






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






3. You have to tell it to link






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






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






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






7. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






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






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






10. Views all previous changes.






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






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






13. Try to find the flaws in your code.






14. CONSTANT






15. Adds files to the repository.






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






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






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






19. Initialized heap memory.






20. Are what function classes should include.






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






22. Downloads without merging.






23. 2 Eyes + 2 Minds = AWESOME!






24. Uploads changes to your current branch.






25. When a class is defined within another class.






26. One of the linking methods (pragma comment)






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






28. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






29. Current line that is executing.






30. Link multiple projects together






31. Functionality Tests.






32. Current view/ previous line.






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






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






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






36. Breaks encapsulation boundaries.






37. Stops when memory changes.






38. Uploads all changes staged in the index list into the repository database.






39. Create a test and then create a function.






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






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






42. Makes a project compile in order of who is dependent on what






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






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






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






46. Function doesn't exist.






47. No more than 40 hours to stop burnouts.






48. Ignores files when pushing.






49. Downloads your changes and then merges.






50. Will execute all code paths and boundary conditions.