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. The default nickname for the remote repository.






2. Will execute all code paths and boundary conditions.






3. Ignores files when pushing.






4. Stops when memory changes.






5. When doing a - precise task.






6. The linking is already done internally






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






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






9. NULL memory.






10. Concept based on limiting the scope of modules to provide better structures.






11. Simply a value.






12. Plan out your code.






13. Code generation in a lib






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






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






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






17. Quick program.






18. Current view/ previous line.






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






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






21. Variable doesn't exist.






22. Do not optimize until the very end.






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






24. Initialized stack memory.






25. Makes a copy of your repository.






26. About the interface to an object. Data contained within.






27. A function that can load a library






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






29. Uploads changes to your current branch.






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






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






32. Freed heap memory.






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






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






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






36. Set of all pending changes.






37. STOP!!






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






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






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






41. Use only through the interface of the object.






42. Developers should be integrated and releasing code into the code repository every few hours.






43. No more than 40 hours to stop burnouts.






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






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






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






47. Black Box - The way the program works is internally unknown.






48. Fix any problems and then repeat the process.






49. Classes build off of each other.






50. Formatted code standards.