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. Use only through the interface of the object.






2. You have to tell it to link






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






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






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






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






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






8. Breaks encapsulation boundaries.






9. Inheritance between object.






10. Current line that is executing.






11. Downloads your changes and then merges.






12. The default nickname for the remote repository.






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






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






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






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






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






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






19. 2 Eyes + 2 Minds = AWESOME!






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






21. Create a test and then create a function.






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






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






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






25. Black Box - The way the program works is internally unknown.






26. The linking is already done internally






27. Ignores files when pushing.






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






29. Formatted code standards.






30. Link multiple projects together






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






32. Removes files from the repository.






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






34. Initialized stack memory.






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






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






37. Try to find the flaws in your code.






38. Are what function classes should include.






39. Variable doesn't exist.






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






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






42. STOP!!






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






44. Initialized heap memory.






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






46. No more than 40 hours to stop burnouts.






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






48. A type of library that is used by the code






49. Views all previous changes.






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