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. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






3. Application






4. Are what function classes should include.






5. Default branch within your repository.






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






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






8. Breaks encapsulation boundaries.






9. Create a test and then create a function.






10. One of the linking methods (pragma comment)






11. Adds files to the repository.






12. Variable doesn't exist.






13. Functionality Tests.






14. Stops when memory changes.






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






16. A pointer or reference. One object needs to know about the other object to work.






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






18. Whats displayed to the screen






19. Undo changes made since your last commit.






20. Function doesn't exist.






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






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






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






24. The linking is already done internally






25. Inheritance between object.






26. Allows you to switch your working copy to another branch.






27. Helps to eliminate unnecessary "include chaining."






28. No more than 40 hours to stop burnouts.






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






30. The default nickname for the remote repository.






31. Downloads without merging.






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






33. You have to tell it to link






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






35. Quick program.






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






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






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






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






40. Do not optimize until the very end.






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






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






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






44. Bad! Don't ever use these types of variables!






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






46. Initialized heap memory.






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






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






49. Makes a copy of your repository.






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