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. Uploads changes to your current branch.






2. 2 Eyes + 2 Minds = AWESOME!






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






4. Makes a copy of your repository.






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






6. When doing a - precise task.






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






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






9. Plan out your code.






10. Default branch within your repository.






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






12. Puts all headers into a master header.






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






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






15. Initialized stack memory.






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






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






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






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






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






21. Adds files to the repository.






22. Simply a value.






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






24. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






25. Formatted code standards.






26. Downloads without merging.






27. One of the linking methods (pragma comment)






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






29. Will execute all code paths and boundary conditions.






30. Current view/ previous line.






31. Use only through the interface of the object.






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






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






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






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






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






37. Italicized in UML.






38. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






39. When GIT cannot merge your data.






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






41. A function that can load a library






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






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






44. Breaks encapsulation boundaries.






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






46. Initialized heap memory.






47. Freed heap memory.






48. Variable doesn't exist.






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






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