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. How many objects that a source object can legitimately reference.






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






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






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






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






6. Fix any problems and then repeat the process.






7. Simply a value.






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






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






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






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






12. Stops when memory changes.






13. The linking is already done internally






14. Adds files to the repository.






15. Views all previous changes.






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






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






18. Link multiple projects together






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






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






21. Quick program.






22. Helps to eliminate unnecessary "include chaining."






23. What is part of the current scope.






24. Makes a copy of your repository.






25. Whats displayed to the screen






26. When a conflict is fixed.






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






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






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






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






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






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






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






34. CONSTANT






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






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






37. Inheritance between object.






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






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






40. One of the linking methods (pragma comment)






41. Uploads all changes staged in the index list into the repository database.






42. Do not optimize until the very end.






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






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






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






46. Code whatever it is you need to code.






47. Initialized heap memory.






48. Undo changes made since your last commit.






49. Formatted code standards.






50. STOP!!