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. Simply a value.






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






3. Helps to eliminate unnecessary "include chaining."






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






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






6. Link multiple projects together






7. Italicized in UML.






8. Removes files from the repository.






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






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






11. Whats displayed to the screen






12. When a conflict is fixed.






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






14. Quick program.






15. Will execute all code paths and boundary conditions.






16. Allows consumers to try a system earlier and give early feedback.






17. Set of all pending changes.






18. Stops when memory changes.






19. Initialized heap memory.






20. What is part of the current scope.






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






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






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






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






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






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






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






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






29. Application






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






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






32. Uploads changes to your current branch.






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






34. Downloads without merging.






35. Ask questions and obtain the details and requirements given.






36. STOP!!






37. Do not optimize until the very end.






38. Try to find the flaws in your code.






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






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






41. Current line that is executing.






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






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






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






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






46. Views all previous changes.






47. Plan out your code.






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






49. Undo changes made since your last commit.






50. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.