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. No more than 40 hours to stop burnouts.






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






3. Downloads without merging.






4. What is part of the current scope.






5. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






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






7. Initialized heap memory.






8. Plan out your code.






9. Simply a value.






10. Functionality Tests.






11. When GIT cannot merge your data.






12. When a conflict is fixed.






13. Variable doesn't exist.






14. Try to find the flaws in your code.






15. Ignores files when pushing.






16. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






17. Stops when memory changes.






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






19. Function doesn't exist.






20. Helps to eliminate unnecessary "include chaining."






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






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






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






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






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






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






27. Whats displayed to the screen






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






29. Undo changes made since your last commit.






30. Code whatever it is you need to code.






31. Set of all pending changes.






32. You have to tell it to link






33. Default branch within your repository.






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






35. Black Box - The way the program works is internally unknown.






36. Initialized stack memory.






37. One of the linking methods (pragma comment)






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






39. When a concrete class inherits from a pure interface.






40. When doing a - precise task.






41. Freed heap memory.






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






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






44. Allows you to switch your working copy to another branch.






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






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






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






48. Makes a copy of your repository.






49. Views all previous changes.






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