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 GIT cannot merge your data.






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






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






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






5. Fix any problems and then repeat the process.






6. A function that can load a library






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






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






9. Functionality Tests.






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






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






12. STOP!!






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






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






15. Removes files from the repository.






16. Initialized stack memory.






17. Application






18. Quick program.






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






20. Current view/ previous line.






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






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






23. Ignores files when pushing.






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






25. The default nickname for the remote repository.






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






27. CONSTANT






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






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






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






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






32. Create a test and then create a function.






33. Whats displayed to the screen






34. Ability to withstand change and what the effects are.






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






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






37. Developers should be integrated and releasing code into the code repository every few hours.






38. Formatted code standards.






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






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






41. Use this to find a memory address or signiture in a dll






42. Makes a project compile in order of who is dependent on what






43. Inheritance between object.






44. Will execute all code paths and boundary conditions.






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






46. Classes build off of each other.






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






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






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






50. Initialized heap memory.