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 we remove redundant or obsolete designs and replace them with a new.






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






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






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






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






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






7. Uploads changes to your current branch.






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






9. STOP!!






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






11. No man's land. Guard bytes before the after allocated heap memory.






12. No more than 40 hours to stop burnouts.






13. Views all previous changes.






14. Puts all headers into a master header.






15. The linking is already done internally






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






17. Fix any problems and then repeat the process.






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






19. Try to find the flaws in your code.






20. Will execute all code paths and boundary conditions.






21. You have to tell it to link






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






23. Function doesn't exist.






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






25. Do not optimize until the very end.






26. Whats displayed to the screen






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






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






29. Current view/ previous line.






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






31. What is part of the current scope.






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






33. Link multiple projects together






34. A measure of logical dependency.






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






36. When a class is defined within another class.






37. Removes files from the repository.






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






39. Makes a copy of your repository.






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






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






42. Plan out your code.






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






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






45. Quick program.






46. Use only through the interface of the object.






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






48. Current line that is executing.






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






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