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. Ability to withstand change and what the effects are.






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






3. Whats displayed to the screen






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






5. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






6. Plan out your code.






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






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






9. Current line that is executing.






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






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






12. A measure of logical dependency.






13. The default nickname for the remote repository.






14. Application






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






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






17. Puts all headers into a master header.






18. Are what function classes should include.






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






20. Do not optimize until the very end.






21. Breaks encapsulation boundaries.






22. Fix any problems and then repeat the process.






23. How many objects that a source object can legitimately reference.






24. Uploads changes to your current branch.






25. Classes build off of each other.






26. Create a test and then create a function.






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






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






29. No more than 40 hours to stop burnouts.






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






31. CONSTANT






32. Stops when memory changes.






33. STOP!!






34. Quick program.






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






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






37. When a class is defined within another class.






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






39. Simply a value.






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






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






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






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






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






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






46. Set of all pending changes.






47. Views all previous changes.






48. Default branch within your repository.






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






50. NULL memory.