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. Connection between a local brand and a remote branch.






2. Try to find the flaws in your code.






3. Helps to eliminate unnecessary "include chaining."






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






5. Whats displayed to the screen






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






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






8. A measure of logical dependency.






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






10. When a class is defined within another class.






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






12. Do not optimize until the very end.






13. Fix any problems and then repeat the process.






14. Default branch within your repository.






15. When doing a - precise task.






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






17. Link multiple projects together






18. STOP!!






19. Current view/ previous line.






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






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






22. NULL memory.






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






24. Variable doesn't exist.






25. Formatted code standards.






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






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






28. The linking is already done internally






29. Having power over inheritance with the flexibility of composition.






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






31. Downloads without merging.






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






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






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






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






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






37. Removes files from the repository.






38. Code generation in a lib






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






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






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






42. One of the linking methods (pragma comment)






43. Classes build off of each other.






44. Set of all pending changes.






45. No more than 40 hours to stop burnouts.






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






47. When a conflict is fixed.






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






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






50. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.