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. Ask questions and obtain the details and requirements given.






2. Are what function classes should include.






3. Set of all pending changes.






4. Written by the customers as things that the system needs to do for them.






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






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






7. Formatted code standards.






8. You have to tell it to link






9. Figure out what is feasible. Decide whether to use API's or to write from scratch.






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






11. Breaks encapsulation boundaries.






12. When a conflict is fixed.






13. When doing a - precise task.






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






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






16. When GIT cannot merge your data.






17. NULL memory.






18. No more than 40 hours to stop burnouts.






19. Makes a copy of your repository.






20. Fix any problems and then repeat the process.






21. Default branch within your repository.






22. Downloads your changes and then merges.






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






24. Italicized in UML.






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






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






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






28. When a class is defined within another class.






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






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






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






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






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






34. Downloads without merging.






35. Input






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






37. Stops when memory changes.






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






39. Simply a value.






40. Undo changes made since your last commit.






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






42. Use only through the interface of the object.






43. Whats displayed to the screen






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






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






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






47. STOP!!






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






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






50. Link multiple projects together