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






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






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






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






5. Link multiple projects together






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






7. Downloads without merging.






8. Functionality Tests.






9. Variable doesn't exist.






10. When doing a - precise task.






11. CONSTANT






12. The linking is already done internally






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






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






15. What is part of the current scope.






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






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






18. A measure of logical dependency.






19. 2 Eyes + 2 Minds = AWESOME!






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






21. Try to find the flaws in your code.






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






23. Function doesn't exist.






24. Undo changes made since your last commit.






25. When GIT cannot merge your data.






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






27. Puts all headers into a master header.






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






29. Application






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






31. You have to tell it to link






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






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






34. Ignores files when pushing.






35. No more than 40 hours to stop burnouts.






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






37. Default branch within your repository.






38. Adds files to the repository.






39. Makes a copy of your repository.






40. Downloads your changes and then merges.






41. Helps to eliminate unnecessary "include chaining."






42. Current line that is executing.






43. When a class is defined within another class.






44. Ensure a class only has one instance - and provide a global point of access to it






45. Classes build off of each other.






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






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






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






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






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