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. When a concrete class inherits from a pure interface.






3. Downloads your changes and then merges.






4. Makes a copy of your repository.






5. Initialized heap memory.






6. Create a test and then create a function.






7. Removes files from the repository.






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






9. When a conflict is fixed.






10. Classes build off of each other.






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






12. 2 Eyes + 2 Minds = AWESOME!






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






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






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






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






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






18. Breaks encapsulation boundaries.






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






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






21. Undo changes made since your last commit.






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






23. What is part of the current scope.






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






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






26. Figure out what is feasible. Decide whether to use API's or to write from scratch.






27. Functionality Tests.






28. Do not optimize until the very end.






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






30. Link multiple projects together






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






32. Italicized in UML.






33. Uploads changes to your current branch.






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






35. When a class is defined within another class.






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






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






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






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






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






41. NULL memory.






42. Formatted code standards.






43. Stand up meetings show who will be valuable and needed.






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






45. Views all previous changes.






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






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






48. Downloads without merging.






49. Ask questions and obtain the details and requirements given.






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