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. Black Box - The way the program works is internally unknown.






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






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






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






5. Create a test and then create a function.






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






7. 2 Eyes + 2 Minds = AWESOME!






8. Initialized stack memory.






9. Use only through the interface of the object.






10. Use this to find a memory address or signiture in a dll






11. When GIT cannot merge your data.






12. What is part of the current scope.






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






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






15. Fix any problems and then repeat the process.






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






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






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






19. NULL memory.






20. Plan out your code.






21. Puts all headers into a master header.






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






23. Application






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






25. Downloads your changes and then merges.






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






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






28. A measure of logical dependency.






29. Downloads without merging.






30. Inheritance between object.






31. Input






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






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






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






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






36. Uploads changes to your current branch.






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






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






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






40. Current view/ previous line.






41. Code generation in a lib






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






43. When you type in an object - you can see its attributes.






44. When a class is defined within another class.






45. Freed heap memory.






46. Makes a copy of your repository.






47. You have to tell it to link






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






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






50. Will execute all code paths and boundary conditions.