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. Linking to dynamic libraries is usually handled by linking to an ____________.






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






3. Default branch within your repository.






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. Removes files from the repository.






7. When GIT cannot merge your data.






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






9. A reference. Has and delete dynamic memory. implies ownership (Association does not).






10. Variable doesn't exist.






11. Always do the simplest design that could possibly work.






12. Freed heap memory.






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






14. Link multiple projects together






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






16. Inheritance between object.






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






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






19. You have to tell it to link






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






21. Adds files to the repository.






22. Code generation in a lib






23. What is part of the current scope.






24. When a conflict is fixed.






25. Initialized stack memory.






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






27. Code whatever it is you need to code.






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






29. Current line that is executing.






30. Valid input that the program is designed to process.






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






32. CONSTANT






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






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






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






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






37. Try to find the flaws in your code.






38. Whats displayed to the screen






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






40. Create a test and then create a function.






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






42. Are what function classes should include.






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






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






45. Simply a value.






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






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






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






49. Italicized in UML.






50. Quick program.