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. Will execute all code paths and boundary conditions.






2. Helps to eliminate unnecessary "include chaining."






3. Input






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






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






6. Ignores files when pushing.






7. Initialized heap memory.






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






9. You have to tell it to link






10. Weak relationship between two classes. Almost always results in a #include.






11. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






12. Puts all headers into a master header.






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






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






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






16. Try to find the flaws in your code.






17. When a conflict is fixed.






18. Application






19. STOP!!






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






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






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






23. Removes files from the repository.






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






25. Undo changes made since your last commit.






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






27. Current line that is executing.






28. Create a test and then create a function.






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






30. When a class is defined within another class.






31. Do not optimize until the very end.






32. Views all previous changes.






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






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






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






36. When doing a - precise task.






37. Use only through the interface of the object.






38. Downloads without merging.






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






40. The default nickname for the remote repository.






41. The linking is already done internally






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






43. Code generation in a lib






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






45. Set of all pending changes.






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






47. Are what function classes should include.






48. A function that can load a library






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






50. Default branch within your repository.