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. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






2. Freed heap memory.






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






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






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






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






7. Views all previous changes.






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






9. Variable doesn't exist.






10. One of the linking methods (pragma comment)






11. Fix any problems and then repeat the process.






12. NULL memory.






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






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






15. No more than 40 hours to stop burnouts.






16. Classes build off of each other.






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






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






19. Current view/ previous line.






20. What is part of the current scope.






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






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






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






24. Will execute all code paths and boundary conditions.






25. Makes a copy of your repository.






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






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






28. Treating a derived class's data members like it's base class's.






29. Adds files to the repository.






30. CONSTANT






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






32. Code generation in a lib






33. Linking to dynamic libraries is usually handled by linking to an ____________.






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






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






36. When a conflict is fixed.






37. Link multiple projects together






38. Italicized in UML.






39. STOP!!






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






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






42. Use only through the interface of the object.






43. Initialized heap memory.






44. The default nickname for the remote repository.






45. Inheritance between object.






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






47. You have to tell it to link






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






49. Plan out your code.






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