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. No man's land. Guard bytes before the after allocated heap memory.






2. Simply a value.






3. Inheritance between object.






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






5. Current line that is executing.






6. Italicized in UML.






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






8. Use only through the interface of the object.






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






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






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






12. NULL memory.






13. CONSTANT






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






15. When doing a - precise task.






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






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






18. When a class is defined within another class.






19. Makes a copy of your repository.






20. Put this before a function name in a dll - and the function name will avoid name mangling






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






22. Stops when memory changes.






23. Undo changes made since your last commit.






24. You have to tell it to link






25. Whats displayed to the screen






26. Breaks encapsulation boundaries.






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






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






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






30. Do not optimize until the very end.






31. Initialized heap memory.






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






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






34. STOP!!






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






36. When a conflict is fixed.






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






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






39. Removes files from the repository.






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






41. Classes build off of each other.






42. Set of all pending changes.






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






44. Adds files to the repository.






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






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






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






48. Downloads your changes and then merges.






49. Copies all changes from one branch into another branch.






50. Freed heap memory.







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