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. Will execute all code paths and boundary conditions.






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






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






4. Do not optimize until the very end.






5. Formatted code standards.






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






7. Current view/ previous line.






8. When GIT cannot merge your data.






9. Set of all pending changes.






10. Initialized stack memory.






11. Input






12. Whats displayed to the screen






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






14. Initialized heap memory.






15. 2 Eyes + 2 Minds = AWESOME!






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






17. You have to tell it to link






18. Try to find the flaws in your code.






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






20. Fix any problems and then repeat the process.






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






22. What is part of the current scope.






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






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






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






26. Freed heap memory.






27. A measure of logical dependency.






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






29. Inheritance between object.






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






31. Uploads changes to your current branch.






32. When a conflict is fixed.






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






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






35. STOP!!






36. Undo changes made since your last commit.






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






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






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






40. Having power over inheritance with the flexibility of composition.






41. One of the linking methods (pragma comment)






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






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






44. Plan out your code.






45. Ability to withstand change and what the effects are.






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






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






48. Puts all headers into a master header.






49. Helps to eliminate unnecessary "include chaining."






50. NULL memory.