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. Do not optimize until the very end.






2. Code generation in a lib






3. Portioning your changes to commit by inserting them into the index.






4. When doing a - precise task.






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






6. One of the linking methods (pragma comment)






7. You have to tell it to link






8. Simply a value.






9. Weak relationship between two classes. Almost always results in a #include.






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






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






12. NULL memory.






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






14. Whats displayed to the screen






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






16. Are what function classes should include.






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






18. A set of creation and initialization steps useful for a set of different related tests.






19. Formatted code standards.






20. STOP!!






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






22. What is part of the current scope.






23. Adds files to the repository.






24. When GIT cannot merge your data.






25. Helps to eliminate unnecessary "include chaining."






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






27. Initialized heap memory.






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






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






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






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






32. A measure of logical dependency.






33. Set of all pending changes.






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






35. The default nickname for the remote repository.






36. Use only through the interface of the object.






37. Puts all headers into a master header.






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






39. Views all previous changes.






40. Uploads changes to your current branch.






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






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






43. Application






44. Default branch within your repository.






45. Ability to withstand change and what the effects are.






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






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






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






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






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