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. Use this to find a memory address or signiture in a dll






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






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






4. Fix any problems and then repeat the process.






5. What is part of the current scope.






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






7. Inheritance between object.






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






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






10. Default branch within your repository.






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






12. Weak relationship between two classes. Almost always results in a #include.






13. STOP!!






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






15. Uploads changes to your current branch.






16. You have to tell it to link






17. Plan out your code.






18. Breaks encapsulation boundaries.






19. Helps to eliminate unnecessary "include chaining."






20. Removes files from the repository.






21. Quick program.






22. Adds files to the repository.






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






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






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






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






27. Makes a copy of your repository.






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






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






30. Stops when memory changes.






31. Function doesn't exist.






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






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






34. The default nickname for the remote repository.






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






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






37. Downloads your changes and then merges.






38. Simply a value.






39. Are what function classes should include.






40. Ignores files when pushing.






41. Use only through the interface of the object.






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






43. When a conflict is fixed.






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






45. When a concrete class inherits from a pure interface.






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






47. A measure of logical dependency.






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






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






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