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. Initialized stack memory.






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






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






4. When GIT cannot merge your data.






5. Downloads your changes and then merges.






6. What is part of the current scope.






7. A measure of logical dependency.






8. You have to tell it to link






9. Try to find the flaws in your code.






10. Formatted code standards.






11. Ignores files when pushing.






12. Current view/ previous line.






13. Variable doesn't exist.






14. Functionality Tests.






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






16. Views all previous changes.






17. When a conflict is fixed.






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






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






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






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






22. A function that can load a library






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






24. Stops when memory changes.






25. Initialized heap memory.






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






27. One of the linking methods (pragma comment)






28. Invalid or unexpected input that the program is not designed to process.






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






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






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






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






33. Italicized in UML.






34. Whats displayed to the screen






35. Will execute all code paths and boundary conditions.






36. Code whatever it is you need to code.






37. 2 Eyes + 2 Minds = AWESOME!






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






39. Create a test and then create a function.






40. Code generation in a lib






41. Current line that is executing.






42. Makes a copy of your repository.






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






44. Fix any problems and then repeat the process.






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






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






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






48. Default branch within your repository.






49. Plan out your code.






50. Quick program.