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. Try to find the flaws in your code.






2. A function that can load a library






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






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






5. NULL memory.






6. Inheritance between object.






7. Create a test and then create a function.






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






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






10. When a class is defined within another class.






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






12. Undo changes made since your last commit.






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






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






15. Uploads changes to your current branch.






16. One of the linking methods (pragma comment)






17. Helps to eliminate unnecessary "include chaining."






18. The default nickname for the remote repository.






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






20. Classes build off of each other.






21. A measure of logical dependency.






22. STOP!!






23. No more than 40 hours to stop burnouts.






24. When GIT cannot merge your data.






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






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






27. Current view/ previous line.






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






29. Freed heap memory.






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






31. Do not optimize until the very end.






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






33. Puts all headers into a master header.






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






35. Application






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






37. Use only through the interface of the object.






38. Will execute all code paths and boundary conditions.






39. Formatted code standards.






40. Views all previous changes.






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






42. Variable doesn't exist.






43. Default branch within your repository.






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






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






46. Function doesn't exist.






47. Downloads without merging.






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






49. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






50. Fix any problems and then repeat the process.