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. Set of all pending changes.






2. Initialized stack memory.






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






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






5. Makes a copy of your repository.






6. Adds files to the repository.






7. Removes files from the repository.






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






9. A measure of logical dependency.






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






11. Plan out your code.






12. Italicized in UML.






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






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






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






16. Classes build off of each other.






17. Uploads changes to your current branch.






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






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






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






21. Initialized heap memory.






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






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






24. When a conflict is fixed.






25. Ignores files when pushing.






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






27. Connection between a local brand and a remote branch.






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






29. The default nickname for the remote repository.






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






31. The linking is already done internally






32. Code generation in a lib






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






34. Simply a value.






35. What is part of the current scope.






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






37. Current view/ previous line.






38. NULL memory.






39. Variable doesn't exist.






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






41. Default branch within your repository.






42. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






43. Downloads your changes and then merges.






44. Try to find the flaws in your code.






45. Formatted code standards.






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






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






48. Current line that is executing.






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






50. Link multiple projects together