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. Static in C++. Can span all instances of a class.






2. Whats displayed to the screen






3. Are what function classes should include.






4. Function doesn't exist.






5. Initialized heap memory.






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






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






8. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






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






11. Classes build off of each other.






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






13. Code whatever it is you need to code.






14. The default nickname for the remote repository.






15. Will execute all code paths and boundary conditions.






16. Stops when memory changes.






17. Plan out your code.






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






19. What is part of the current scope.






20. When GIT cannot merge your data.






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






22. Uploads changes to your current branch.






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






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






25. Code generation in a lib






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






27. NULL memory.






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






29. Try to find the flaws in your code.






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






31. One of the linking methods (pragma comment)






32. When a conflict is fixed.






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






34. CONSTANT






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






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






37. 2 Eyes + 2 Minds = AWESOME!






38. Quick program.






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






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






41. Create a test and then create a function.






42. When we remove redundant or obsolete designs and replace them with a new.






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






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






45. A type of library that is used by the code






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






47. Makes a copy of your repository.






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






49. The linking is already done internally






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