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. Variable doesn't exist.






2. NULL memory.






3. Initialized heap memory.






4. Inheritance between object.






5. When a conflict is fixed.






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






7. Static in C++. Can span all instances of a class.






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






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






10. What is part of the current scope.






11. A measure of logical dependency.






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






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






14. Formatted code standards.






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






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






17. Downloads without merging.






18. Views all previous changes.






19. One of the linking methods (pragma comment)






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






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






22. When doing a - precise task.






23. Input






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






25. When a class is defined within another class.






26. Are what function classes should include.






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






28. The default nickname for the remote repository.






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






30. Use only through the interface of the object.






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






32. When GIT cannot merge your data.






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






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






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






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






37. Current line that is executing.






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






39. Puts all headers into a master header.






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






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






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






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






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






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






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






47. STOP!!






48. Code generation in a lib






49. Functionality Tests.






50. Valid input that the program is designed to process.