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. Italicized in UML.






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






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






4. Helps to eliminate unnecessary "include chaining."






5. The default nickname for the remote repository.






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






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






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






9. Breaks encapsulation boundaries.






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






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






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






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






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






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






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






17. Create a test and then create a function.






18. Downloads your changes and then merges.






19. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






20. Linking to dynamic libraries is usually handled by linking to an ____________.






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






22. Link multiple projects together






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






24. Current line that is executing.






25. Ask questions and obtain the details and requirements given.






26. Plan out your code.






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






28. Simply a value.






29. Freed heap memory.






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






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






32. Are what function classes should include.






33. Variable doesn't exist.






34. Default branch within your repository.






35. STOP!!






36. The linking is already done internally






37. Will execute all code paths and boundary conditions.






38. Puts all headers into a master header.






39. Removes files from the repository.






40. A measure of logical dependency.






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






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






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






44. When GIT cannot merge your data.






45. Whats displayed to the screen






46. Try to find the flaws in your code.






47. CONSTANT






48. Current view/ previous line.






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






50. Quick program.






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests