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. Code generation in a lib






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






3. The linking is already done internally






4. Variable doesn't exist.






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






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






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






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






9. No more than 40 hours to stop burnouts.






10. Will execute all code paths and boundary conditions.






11. Application






12. Undo changes made since your last commit.






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






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






15. Helps to eliminate unnecessary "include chaining."






16. Adds files to the repository.






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






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






19. 2 Eyes + 2 Minds = AWESOME!






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






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






22. Classes build off of each other.






23. Current view/ previous line.






24. Removes files from the repository.






25. Plan out your code.






26. One of the linking methods (pragma comment)






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






28. Freed heap memory.






29. Input






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






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






32. Written by the customers as things that the system needs to do for them.






33. Inheritance between object.






34. Initialized heap memory.






35. Whats displayed to the screen






36. Function doesn't exist.






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






38. Are what function classes should include.






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






40. Default branch within your repository.






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






42. STOP!!






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






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






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






46. Uploads changes to your current branch.






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






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






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






50. Functionality Tests.