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. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






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






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






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






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






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






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






8. Helps to eliminate unnecessary "include chaining."






9. What is part of the current scope.






10. Formatted code standards.






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






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






13. Italicized in UML.






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






15. No more than 40 hours to stop burnouts.






16. Default branch within your repository.






17. Quick program.






18. Initialized stack memory.






19. Code whatever it is you need to code.






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






21. Functionality Tests.






22. CONSTANT






23. Input






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






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






26. When a class is defined within another class.






27. Link multiple projects together






28. Breaks encapsulation boundaries.






29. Views all previous changes.






30. Trying to access a location in memory that your computer cannot access.






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






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






33. Stops when memory changes.






34. Are what function classes should include.






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






36. Classes build off of each other.






37. Downloads your changes and then merges.






38. Adds files to the repository.






39. When a conflict is fixed.






40. You have to tell it to link






41. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






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






43. Undo changes made since your last commit.






44. When GIT cannot merge your data.






45. Code generation in a lib






46. One of the linking methods (pragma comment)






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






48. Application






49. Ensure a class only has one instance - and provide a global point of access to it






50. Try to find the flaws in your code.