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. Makes a copy of your repository.






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






3. Variable doesn't exist.






4. Set of all pending changes.






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






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






7. When GIT cannot merge your data.






8. STOP!!






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






10. Are what function classes should include.






11. No man's land. Guard bytes before the after allocated heap memory.






12. A measure of logical dependency.






13. Italicized in UML.






14. Uploads changes to your current branch.






15. Whats displayed to the screen






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






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






18. Use only through the interface of the object.






19. When a conflict is fixed.






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






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






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






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






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






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






26. Create a test and then create a function.






27. When doing a - precise task.






28. A function that can load a library






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






30. Ignores files when pushing.






31. Default branch within your repository.






32. Downloads without merging.






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






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






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






36. Puts all headers into a master header.






37. Application






38. CONSTANT






39. Link multiple projects together






40. Simply a value.






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






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






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






44. Initialized stack memory.






45. Invalid or unexpected input that the program is not designed to process.






46. Stops when memory changes.






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






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






49. Adds files to the repository.






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