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. Always do the simplest design that could possibly work.






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






3. Code whatever it is you need to code.






4. Freed heap memory.






5. Classes build off of each other.






6. Views all previous changes.






7. Undo changes made since your last commit.






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






9. A set of creation and initialization steps useful for a set of different related tests.






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






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






12. Ignores files when pushing.






13. Input






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






15. When a conflict is fixed.






16. Do not optimize until the very end.






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






18. Italicized in UML.






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






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






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






22. Helps to eliminate unnecessary "include chaining."






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






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






25. Breaks encapsulation boundaries.






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






27. Downloads without merging.






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






29. Adds files to the repository.






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






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






32. Create a test and then create a function.






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






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






35. One of the linking methods (pragma comment)






36. CONSTANT






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






38. Will execute all code paths and boundary conditions.






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






40. A measure of logical dependency.






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






42. Formatted code standards.






43. Use only through the interface of the object.






44. Default branch within your repository.






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






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






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






48. Function doesn't exist.






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






50. Set of all pending changes.