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. Bookmark of a revised set with a title. For easy checkouts.






2. Function doesn't exist.






3. Makes a project compile in order of who is dependent on what






4. Default branch within your repository.






5. Removes files from the repository.






6. When a conflict is fixed.






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






8. Downloads without merging.






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






10. You have to tell it to link






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






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






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. When you type in an object - you can see its attributes.






16. Adds files to the repository.






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






18. When doing a - precise task.






19. Current line that is executing.






20. Functionality Tests.






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






22. When we remove redundant or obsolete designs and replace them with a new.






23. Freed heap memory.






24. Formatted code standards.






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






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






27. Whats displayed to the screen






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






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






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






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






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






33. Helps to eliminate unnecessary "include chaining."






34. Do not optimize until the very end.






35. Set of all pending changes.






36. No more than 40 hours to stop burnouts.






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






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






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






40. A measure of logical dependency.






41. Puts all headers into a master header.






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






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






44. Classes build off of each other.






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






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






47. Breaks encapsulation boundaries.






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






49. Uploads changes to your current branch.






50. 2 Eyes + 2 Minds = AWESOME!