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. NULL memory.






2. 2 Eyes + 2 Minds = AWESOME!






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






4. One of the linking methods (pragma comment)






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






6. Function doesn't exist.






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






8. No more than 40 hours to stop burnouts.






9. Classes build off of each other.






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






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. Undo changes made since your last commit.






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






14. Concept based on limiting the scope of modules to provide better structures.






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






16. Makes a copy of your repository.






17. Do not optimize until the very end.






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






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






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






21. Default branch within your repository.






22. CONSTANT






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






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






25. Try to find the flaws in your code.






26. Downloads your changes and then merges.






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






28. When a conflict is fixed.






29. Formatted code standards.






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






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






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






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






34. Functionality Tests.






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






36. When a concrete class inherits from a pure interface.






37. Always do the simplest design that could possibly work.






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






39. What is part of the current scope.






40. Input






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






42. Downloads without merging.






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






44. Are what function classes should include.






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






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






47. Plan out your code.






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






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






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