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. Quick program.






2. Code whatever it is you need to code.






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






4. Function doesn't exist.






5. Classes build off of each other.






6. Are what function classes should include.






7. Do not optimize until the very end.






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






9. Simply a value.






10. Trying to access a location in memory that your computer cannot access.






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






12. Initialized stack memory.






13. Current view/ previous line.






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






15. Whats displayed to the screen






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






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






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






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






20. Copies all changes from one branch into another branch.






21. STOP!!






22. CONSTANT






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






24. Adds files to the repository.






25. About the interface to an object. Data contained within.






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






27. NULL memory.






28. Formatted code standards.






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






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






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






32. Functionality Tests.






33. Downloads without merging.






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






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






36. The default nickname for the remote repository.






37. Breaks encapsulation boundaries.






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






39. Variable doesn't exist.






40. What is part of the current scope.






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






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






43. A measure of logical dependency.






44. Use only through the interface of the object.






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






46. A set of creation and initialization steps useful for a set of different related tests.






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






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






49. Current line that is executing.






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