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. Meetings at the beginning of each iteration to produce a plan of programming tasks.






2. A measure of logical dependency.






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






4. No more than 40 hours to stop burnouts.






5. Code generation in a lib






6. Set of all pending changes.






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






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






9. Plan out your code.






10. What is part of the current scope.






11. Stops when memory changes.






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






13. Whats displayed to the screen






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






15. 2 Eyes + 2 Minds = AWESOME!






16. Valid input that the program is designed to process.






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






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






19. Undo changes made since your last commit.






20. Downloads without merging.






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






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






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






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






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






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






27. Ignores files when pushing.






28. Makes a copy of your repository.






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






30. Create a test and then create a function.






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






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






33. Do not optimize until the very end.






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






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






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






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






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






39. Helps to eliminate unnecessary "include chaining."






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






41. Will execute all code paths and boundary conditions.






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






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






44. Adds files to the repository.






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






46. Application






47. Variable doesn't exist.






48. Simply a value.






49. Quick program.






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