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. Figure out what is feasible. Decide whether to use API's or to write from scratch.






2. Try to find the flaws in your code.






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






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






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






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






7. Ignores files when pushing.






8. Undo changes made since your last commit.






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






10. Default branch within your repository.






11. A function that can load a library






12. CONSTANT






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






14. Uploads changes to your current branch.






15. Views all previous changes.






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






17. The linking is already done internally






18. What is part of the current scope.






19. Set of all pending changes.






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






21. Application






22. The default nickname for the remote repository.






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






24. Breaks encapsulation boundaries.






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






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






27. Makes a copy of your repository.






28. Whats displayed to the screen






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






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






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






32. Puts all headers into a master header.






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






34. Downloads your changes and then merges.






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






36. Functionality Tests.






37. Inheritance between object.






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






39. Fix any problems and then repeat the process.






40. Downloads without merging.






41. Code whatever it is you need to code.






42. Initialized stack memory.






43. A measure of logical dependency.






44. Function doesn't exist.






45. Initialized heap memory.






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






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






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






49. Current view/ previous line.






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