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. Code generation in a lib






2. You have to tell it to link






3. The default nickname for the remote repository.






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






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






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






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






8. Current line that is executing.






9. When we remove redundant or obsolete designs and replace them with a new.






10. Inheritance between object.






11. Formatted code standards.






12. The linking is already done internally






13. Simply a value.






14. Whats displayed to the screen






15. Undo changes made since your last commit.






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






17. 2 Eyes + 2 Minds = AWESOME!






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






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






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






21. What is part of the current scope.






22. NULL memory.






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






24. Views all previous changes.






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






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






27. Do not optimize until the very end.






28. Stand up meetings show who will be valuable and needed.






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






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






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






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






33. Puts all headers into a master header.






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






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






36. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






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






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






40. Downloads without merging.






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






42. Input






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






44. Create a test and then create a function.






45. Initialized heap memory.






46. Uploads changes to your current branch.






47. Makes a copy of your repository.






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






49. Stops when memory changes.






50. When GIT cannot merge your data.







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