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. Default branch within your repository.






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






3. Allows you to switch your working copy to another branch.






4. Current view/ previous line.






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






6. Classes build off of each other.






7. Downloads your changes and then merges.






8. When GIT cannot merge your data.






9. Views all previous changes.






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






11. Formatted code standards.






12. 2 Eyes + 2 Minds = AWESOME!






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






14. STOP!!






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






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






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






18. Application






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






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






21. A measure of logical dependency.






22. One of the linking methods (pragma comment)






23. What is part of the current scope.






24. Adds files to the repository.






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






26. The default nickname for the remote repository.






27. Undo changes made since your last commit.






28. Are what function classes should include.






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






30. Helps to eliminate unnecessary "include chaining."






31. You have to tell it to link






32. Use only through the interface of the object.






33. Downloads without merging.






34. A function that can load a library






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






36. Will execute all code paths and boundary conditions.






37. Put this before a function name in a dll - and the function name will avoid name mangling






38. Code whatever it is you need to code.






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






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






41. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






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






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






45. NULL memory.






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






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






48. Code generation in a lib






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






50. Set of all pending changes.