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. Create a test and then create a function.






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






3. Link multiple projects together






4. Current line that is executing.






5. Italicized in UML.






6. Downloads without merging.






7. Try to find the flaws in your code.






8. Makes a copy of your repository.






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






10. Fix any problems and then repeat the process.






11. 2 Eyes + 2 Minds = AWESOME!






12. When GIT cannot merge your data.






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






14. Application






15. Formatted code standards.






16. Undo changes made since your last commit.






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






18. Uploads changes to your current branch.






19. Code generation in a lib






20. Initialized stack memory.






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






22. You have to tell it to link






23. Creates a copy of your current branch into a remote branch.






24. When doing a - precise task.






25. Set of all pending changes.






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






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






28. A measure of logical dependency.






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






30. Quick program.






31. Whats displayed to the screen






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






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






34. Do not optimize until the very end.






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






36. Functionality Tests.






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






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






39. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






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






42. When a conflict is fixed.






43. When a class is defined within another class.






44. NULL memory.






45. A function that can load a library






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






47. Function doesn't exist.






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






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






50. CONSTANT