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. Simply a value.






2. Stand up meetings show who will be valuable and needed.






3. A reference. Has and delete dynamic memory. implies ownership (Association does not).






4. What is part of the current scope.






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






6. Do not optimize until the very end.






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






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






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






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






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






12. Set of all pending changes.






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






14. Default branch within your repository.






15. Initialized heap memory.






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






17. When a class is defined within another class.






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






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






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






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






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






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






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






25. NULL memory.






26. One of the linking methods (pragma comment)






27. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






28. 2 Eyes + 2 Minds = AWESOME!






29. Link multiple projects together






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






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. You have to tell it to link






33. Current line that is executing.






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






35. CONSTANT






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






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






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






39. Puts all headers into a master header.






40. When doing a - precise task.






41. Views all previous changes.






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






43. Italicized in UML.






44. Initialized stack memory.






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






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






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






48. Plan out your code.






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






50. Freed heap memory.