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






2. Code whatever it is you need to code.






3. Inheritance between object.






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






5. Link multiple projects together






6. Formatted code standards.






7. Views all previous changes.






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






9. Quick program.






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






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






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






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






14. Input






15. Whats displayed to the screen






16. When GIT cannot merge your data.






17. The default nickname for the remote repository.






18. Helps to eliminate unnecessary "include chaining."






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






20. Default branch within your repository.






21. Current line that is executing.






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






23. Functionality Tests.






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






25. Function doesn't exist.






26. Breaks encapsulation boundaries.






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






28. Variable doesn't exist.






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






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






31. Use only through the interface of the object.






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






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






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






35. Current view/ previous line.






36. Stops when memory changes.






37. When you type in an object - you can see its attributes.






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






39. No more than 40 hours to stop burnouts.






40. Plan out your code.






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






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






43. Downloads your changes and then merges.






44. Ignores files when pushing.






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






46. Puts all headers into a master header.






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






48. Undo changes made since your last commit.






49. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






50. One of the linking methods (pragma comment)