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. Makes a project compile in order of who is dependent on what






2. Initialized heap memory.






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






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






5. Fix any problems and then repeat the process.






6. Simply a value.






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






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






9. Italicized in UML.






10. Initialized stack memory.






11. Ignores files when pushing.






12. Uploads changes to your current branch.






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






14. The default nickname for the remote repository.






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






16. Removes files from the repository.






17. NULL memory.






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






19. CONSTANT






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






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






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






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






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






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






26. STOP!!






27. Makes a copy of your repository.






28. Plan out your code.






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






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






31. Downloads without merging.






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






33. Set of all pending changes.






34. A function that can load a library






35. Quick program.






36. Variable doesn't exist.






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






38. No more than 40 hours to stop burnouts.






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






40. You have to tell it to link






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






42. Function doesn't exist.






43. Do not optimize until the very end.






44. Try to find the flaws in your code.






45. Stops when memory changes.






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






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






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






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






50. The linking is already done internally