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. 2 Eyes + 2 Minds = AWESOME!






2. Code generation in a lib






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






4. Views all previous changes.






5. Makes a copy of your repository.






6. Current view/ previous line.






7. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






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






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






10. Simply a value.






11. Classes build off of each other.






12. Adds files to the repository.






13. Function doesn't exist.






14. Freed heap memory.






15. Are what function classes should include.






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






17. Breaks encapsulation boundaries.






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






19. Inheritance between object.






20. Undo changes made since your last commit.






21. A measure of logical dependency.






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






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






24. Uploads changes to your current branch.






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






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






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






28. Try to find the flaws in your code.






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






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






31. Stops when memory changes.






32. Plan out your code.






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






34. Italicized in UML.






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






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






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






38. You have to tell it to link






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






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






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






42. Formatted code standards.






43. Removes files from the repository.






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






45. Application






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






47. Variable doesn't exist.






48. Helps to eliminate unnecessary "include chaining."






49. Current line that is executing.






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests