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. Creates a spin-off of a repository for concurrent development.






2. Uploads changes to your current branch.






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






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






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






6. Static in C++. Can span all instances of a class.






7. Set of all pending changes.






8. Function doesn't exist.






9. Initialized stack memory.






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






11. Do not optimize until the very end.






12. Breaks encapsulation boundaries.






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






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






15. When a class is defined within another class.






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






17. Application






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






19. Always do the simplest design that could possibly work.






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






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






22. STOP!!






23. Default branch within your repository.






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






25. Whats displayed to the screen






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






27. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






28. Views all previous changes.






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






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






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






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






33. A function that can load a library






34. A measure of logical dependency.






35. Variable doesn't exist.






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






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






38. One of the linking methods (pragma comment)






39. Create a test and then create a function.






40. Link multiple projects together






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






42. No more than 40 hours to stop burnouts.






43. Code whatever it is you need to code.






44. CONSTANT






45. Current view/ previous line.






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






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






48. Freed heap memory.






49. The linking is already done internally






50. Are what function classes should include.