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. Connection between a local brand and a remote branch.






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






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






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






5. Initialized stack memory.






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






7. When GIT cannot merge your data.






8. Downloads your changes and then merges.






9. Classes build off of each other.






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






11. NULL memory.






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






13. STOP!!






14. Fix any problems and then repeat the process.






15. Will execute all code paths and boundary conditions.






16. Whats displayed to the screen






17. You have to tell it to link






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






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






20. Views all previous changes.






21. Ignores files when pushing.






22. Current view/ previous line.






23. Allows consumers to try a system earlier and give early feedback.






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






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






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






27. Puts all headers into a master header.






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






29. Creates a copy of your current branch into a remote branch.






30. Are what function classes should include.






31. Removes files from the repository.






32. Input






33. Separating out a section of code into a reusable function or class.






34. Formatted code standards.






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






36. Makes a copy of your repository.






37. 2 Eyes + 2 Minds = AWESOME!






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






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






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






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






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






43. The default nickname for the remote repository.






44. Default branch within your repository.






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






46. Simply a value.






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






48. Downloads without merging.






49. Valid input that the program is designed to process.






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