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. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






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






4. The linking is already done internally






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






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






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






8. Do not optimize until the very end.






9. STOP!!






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






11. Initialized stack memory.






12. Ability to withstand change and what the effects are.






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






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






15. Stops when memory changes.






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






17. Create a test and then create a function.






18. Uploads changes to your current branch.






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






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






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






22. Set of all pending changes.






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






24. NULL memory.






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






26. Will execute all code paths and boundary conditions.






27. Treating a derived class's data members like it's base class's.






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






29. Freed heap memory.






30. A function that can load a library






31. Try to find the flaws in your code.






32. Breaks encapsulation boundaries.






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






34. CONSTANT






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






36. You have to tell it to link






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






38. Ignores files when pushing.






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






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






41. Makes a copy of your repository.






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






43. What is part of the current scope.






44. When a conflict is fixed.






45. Current line that is executing.






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






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






48. Application






49. Puts all headers into a master header.






50. Code generation in a lib