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. No man's land. Guard bytes before the after allocated heap memory.






2. The default nickname for the remote repository.






3. Use only through the interface of the object.






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






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






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






7. Makes a copy of your repository.






8. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






9. Default branch within your repository.






10. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






12. Uploads changes to your current branch.






13. A function that can load a library






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






15. When a conflict is fixed.






16. NULL memory.






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






18. Will execute all code paths and boundary conditions.






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






20. Breaks encapsulation boundaries.






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






22. Ignores files when pushing.






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






24. CONSTANT






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






26. Removes files from the repository.






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






28. Functionality Tests.






29. One of the linking methods (pragma comment)






30. Initialized heap memory.






31. Link multiple projects together






32. You have to tell it to link






33. Create a test and then create a function.






34. Views all previous changes.






35. Try to find the flaws in your code.






36. Code whatever it is you need to code.






37. Initialized stack memory.






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






39. Freed heap memory.






40. Adds files to the repository.






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






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






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






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






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






46. Simply a value.






47. Current view/ previous line.






48. Puts all headers into a master header.






49. Formatted code standards.






50. When a class is defined within another class.