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. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






2. Code generation in a lib






3. Helps to eliminate unnecessary "include chaining."






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






5. Breaks encapsulation boundaries.






6. When a class is defined within another class.






7. Code whatever it is you need to code.






8. Ignores files when pushing.






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






10. Are what function classes should include.






11. Freed heap memory.






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






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






14. Do not optimize until the very end.






15. Removes files from the repository.






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






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






18. Quick program.






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






20. Default branch within your repository.






21. A measure of logical dependency.






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






23. Set of all pending changes.






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






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






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






27. The default nickname for the remote repository.






28. Ensure a class only has one instance - and provide a global point of access to it






29. Whats displayed to the screen






30. Link multiple projects together






31. Adds files to the repository.






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






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






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






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






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






37. When doing a - precise task.






38. Fix any problems and then repeat the process.






39. CONSTANT






40. Undo changes made since your last commit.






41. Inheritance between object.






42. Ability to accept different types of parameters to bind to different implementations at run-time.






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






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






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






46. Italicized in UML.






47. When a conflict is fixed.






48. NULL memory.






49. Create a test and then create a function.






50. Formatted code standards.