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. Portioning your changes to commit by inserting them into the index.






2. Code generation in a lib






3. Link multiple projects together






4. Trying to access a location in memory that your computer cannot access.






5. Quick program.






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






7. When a conflict is fixed.






8. Bad! Don't ever use these types of variables!






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






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






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






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






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






14. About the interface to an object. Data contained within.






15. Initialized heap memory.






16. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






17. Code whatever it is you need to code.






18. The linking is already done internally






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






20. Downloads your changes and then merges.






21. No more than 40 hours to stop burnouts.






22. Breaks encapsulation boundaries.






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






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






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






26. You have to tell it to link






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






28. Italicized in UML.






29. Views all previous changes.






30. When a class is defined within another class.






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






32. What is part of the current scope.






33. NULL memory.






34. 2 Eyes + 2 Minds = AWESOME!






35. Default branch within your repository.






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






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






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






39. Undo changes made since your last commit.






40. Plan out your code.






41. Are what function classes should include.






42. A reference. Has and delete dynamic memory. implies ownership (Association does not).






43. Input






44. One of the linking methods (pragma comment)






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






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






47. Makes a copy of your repository.






48. Ignores files when pushing.






49. Create a test and then create a function.






50. Downloads without merging.