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. Invalid or unexpected input that the program is not designed to process.






2. Inheritance between object.






3. Variable doesn't exist.






4. Makes a copy of your repository.






5. Create a test and then create a function.






6. Initialized heap memory.






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






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






9. NULL memory.






10. Concept based on limiting the scope of modules to provide better structures.






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






12. Are what function classes should include.






13. A reference. Has and delete dynamic memory. implies ownership (Association does not).






14. Try to find the flaws in your code.






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






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






17. Ignores files when pushing.






18. Formatted code standards.






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






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






21. CONSTANT






22. Stops when memory changes.






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






24. Removes files from the repository.






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






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






27. You have to tell it to link






28. Undo changes made since your last commit.






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






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






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






32. Functionality Tests.






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






34. Quick program.






35. When a conflict is fixed.






36. Puts all headers into a master header.






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






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






39. Simply a value.






40. Bookmark of a revised set with a title. For easy checkouts.






41. Use only through the interface of the object.






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






43. When doing a - precise task.






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






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






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






47. Italicized in UML.






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






49. Classes build off of each other.






50. Downloads your changes and then merges.