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. Concept based on limiting the scope of modules to provide better structures.






2. Ignores files when pushing.






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






4. Breaks encapsulation boundaries.






5. Invalid or unexpected input that the program is not designed to process.






6. Code generation in a lib






7. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






8. Link multiple projects together






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






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






11. Try to find the flaws in your code.






12. A measure of logical dependency.






13. Undo changes made since your last commit.






14. You have to tell it to link






15. What is part of the current scope.






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






17. Will execute all code paths and boundary conditions.






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






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






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






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






22. Inheritance between object.






23. Use only through the interface of the object.






24. Function doesn't exist.






25. NULL memory.






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






27. Formatted code standards.






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






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






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






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






32. Freed heap memory.






33. Downloads your changes and then merges.






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






35. A function that can load a library






36. When a class is defined within another class.






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






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






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






40. Adds files to the repository.






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






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






43. Input






44. Code whatever it is you need to code.






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






46. Makes a copy of your repository.






47. Current line that is executing.






48. Fix any problems and then repeat the process.






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






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







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