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. Function doesn't exist.






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






4. Whats displayed to the screen






5. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






6. Variable doesn't exist.






7. Makes a copy of your repository.






8. Uploads changes to your current branch.






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






10. Code whatever it is you need to code.






11. What is part of the current scope.






12. Downloads your changes and then merges.






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






14. A function that can load a library






15. Ensure a class only has one instance - and provide a global point of access to it






16. Classes build off of each other.






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






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






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






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






21. Undo changes made since your last commit.






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






23. Simply a value.






24. You have to tell it to link






25. Set of all pending changes.






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






27. CONSTANT






28. STOP!!






29. Freed heap 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. Use only through the interface of the object.






33. Will execute all code paths and boundary conditions.






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






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






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






37. Default branch within your repository.






38. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






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






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






41. When GIT cannot merge your data.






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






43. The linking is already done internally






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






45. When a class is defined within another class.






46. Are what function classes should include.






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






48. Current line that is executing.






49. Link multiple projects together






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