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. Separating out a section of code into a reusable function or class.






2. What is part of the current scope.






3. Whats displayed to the screen






4. Creates a spin-off of a repository for concurrent development.






5. NULL memory.






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






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






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






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






10. Breaks encapsulation boundaries.






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






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






13. Current view/ previous line.






14. Code generation in a lib






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






16. Current line that is executing.






17. Invalid or unexpected input that the program is not designed to process.






18. Quick program.






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






20. Initialized heap memory.






21. When a class is defined within another class.






22. Put this before a function name in a dll - and the function name will avoid name mangling






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






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






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






26. The linking is already done internally






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






28. Set of all pending changes.






29. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






30. Downloads without merging.






31. Function doesn't exist.






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






33. A measure of logical dependency.






34. Stops when memory changes.






35. Undo changes made since your last commit.






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






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






38. Application






39. Functionality Tests.






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






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






42. Takes information in the index and pushes it onto the stack.






43. Makes a copy of your repository.






44. Freed heap memory.






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






46. When a conflict is fixed.






47. Ignores files when pushing.






48. Use only through the interface of the object.






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






50. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere