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 more than 40 hours to stop burnouts.






2. Stops when memory changes.






3. Breaks encapsulation boundaries.






4. Inheritance between object.






5. A measure of logical dependency.






6. Code whatever it is you need to code.






7. No man's land. Guard bytes before the after allocated heap memory.






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






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






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






11. Classes build off of each other.






12. Current view/ previous line.






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






14. Code generation in a lib






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






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






17. Ignores files when pushing.






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






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






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






21. Removes files from the repository.






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






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






24. Fix any problems and then repeat the process.






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






26. Try to find the flaws in your code.






27. Initialized stack memory.






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






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






30. Plan out your code.






31. Variable doesn't exist.






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






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






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






35. Default branch within your repository.






36. Downloads without merging.






37. CONSTANT






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






39. Uploads changes to your current branch.






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






41. Current line that is executing.






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






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






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






45. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






46. When doing a - precise task.






47. The linking is already done internally






48. 2 Eyes + 2 Minds = AWESOME!






49. Set of all pending changes.






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