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. A measure of logical dependency.






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






3. Create a test and then create a function.






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






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






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






7. Removes files from the repository.






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






9. Do not optimize until the very end.






10. Default branch within your repository.






11. Formatted code standards.






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






13. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






14. Will execute all code paths and boundary conditions.






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






16. No more than 40 hours to stop burnouts.






17. Ask questions and obtain the details and requirements given.






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






19. Ignores files when pushing.






20. The default nickname for the remote repository.






21. One of the linking methods (pragma comment)






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






23. Input






24. Are what function classes should include.






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






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






27. Code whatever it is you need to code.






28. 2 Eyes + 2 Minds = AWESOME!






29. Use only through the interface of the object.






30. A type of library that is used by the code






31. Inheritance between object.






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






33. Initialized heap memory.






34. Uploads changes to your current branch.






35. Application






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






37. You have to tell it to link






38. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






39. Views all previous changes.






40. Simply a value.






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






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






43. Classes build off of each other.






44. Current view/ previous line.






45. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






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






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






48. Fix any problems and then repeat the process.






49. Plan out your code.






50. Downloads without merging.