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. Downloads your changes and then merges.






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






3. Adds files to the repository.






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






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






6. Makes a project compile in order of who is dependent on what






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






8. CONSTANT






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






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






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






12. Link multiple projects together






13. The linking is already done internally






14. Functionality Tests.






15. Uploads changes to your current branch.






16. Plan out your code.






17. Function doesn't exist.






18. Inheritance between object.






19. Meetings at the beginning of each iteration to produce a plan of programming tasks.






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






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






22. Views all previous changes.






23. Quick program.






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






25. Linking to dynamic libraries is usually handled by linking to an ____________.






26. No more than 40 hours to stop burnouts.






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






28. Code whatever it is you need to code.






29. One of the linking methods (pragma comment)






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






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






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






33. Variable doesn't exist.






34. Downloads without merging.






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






36. Makes a copy of your repository.






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






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






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






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






41. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






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






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






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






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






47. Initialized heap memory.






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






49. When doing a - precise task.






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