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. Downloads your changes and then merges.






2. Application






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






4. NULL memory.






5. Fix any problems and then repeat the process.






6. Freed heap memory.






7. Breaks encapsulation boundaries.






8. Whats displayed to the screen






9. A function that can load a library






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






11. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






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






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






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






15. Stops when memory changes.






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






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






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






19. What is part of the current scope.






20. Use only through the interface of the object.






21. Default branch within your repository.






22. Will execute all code paths and boundary conditions.






23. Input






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






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






26. Set of all pending changes.






27. Formatted code standards.






28. One of the linking methods (pragma comment)






29. Initialized stack memory.






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






31. CONSTANT






32. Removes files from the repository.






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






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






35. Having power over inheritance with the flexibility of composition.






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






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






38. Code generation in a lib






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






40. Undo changes made since your last commit.






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






42. When GIT cannot merge your data.






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






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






45. Views all previous changes.






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






47. Static in C++. Can span all instances of a class.






48. When we remove redundant or obsolete designs and replace them with a new.






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






50. The default nickname for the remote repository.