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. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






2. Plan out your code.






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






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






5. Bad! Don't ever use these types of variables!






6. Are what function classes should include.






7. Function doesn't exist.






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






9. Try to find the flaws in your code.






10. No more than 40 hours to stop burnouts.






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






12. Application






13. When a class is defined within another class.






14. You have to tell it to link






15. Ignores files when pushing.






16. When GIT cannot merge your data.






17. Freed heap memory.






18. NULL memory.






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






20. When doing a - precise task.






21. Quick program.






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






23. Link multiple projects together






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






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






26. 2 Eyes + 2 Minds = AWESOME!






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






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






29. Initialized stack memory.






30. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






32. Current view/ previous line.






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






34. Inheritance between object.






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






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






37. When a conflict is fixed.






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






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






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






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






42. Italicized in UML.






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






44. What is part of the current scope.






45. Use only through the interface of the object.






46. Classes build off of each other.






47. Code generation in a lib






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






49. A function that can load a library






50. Adds files to the repository.