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. Function doesn't exist.






2. Views all previous changes.






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






4. Uploads changes to your current branch.






5. Removes files from the repository.






6. No more than 40 hours to stop burnouts.






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






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






9. One of the linking methods (pragma comment)






10. Downloads without merging.






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






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






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






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






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






16. The linking is already done internally






17. The default nickname for the remote repository.






18. Create a test and then create a function.






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






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






21. Freed heap memory.






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






23. Do not optimize until the very end.






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






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






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






27. Undo changes made since your last commit.






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






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






30. Set of all pending changes.






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






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






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






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






35. CONSTANT






36. Code generation in a lib






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






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






39. Downloads your changes and then merges.






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






41. Weak relationship between two classes. Almost always results in a #include.






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






43. Are what function classes should include.






44. You have to tell it to link






45. Variable doesn't exist.






46. Breaks encapsulation boundaries.






47. Makes a copy of your repository.






48. When a conflict is fixed.






49. Helps to eliminate unnecessary "include chaining."






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