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. Stand up meetings show who will be valuable and needed.






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






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






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






5. Functionality Tests.






6. Initialized heap memory.






7. Puts all headers into a master header.






8. Freed heap memory.






9. Quick program.






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






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






12. Italicized in UML.






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






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






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






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






17. When a class is defined within another class.






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






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






20. CONSTANT






21. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






22. Classes build off of each other.






23. Ignores files when pushing.






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






25. Will execute all code paths and boundary conditions.






26. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






27. The default nickname for the remote repository.






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






29. 2 Eyes + 2 Minds = AWESOME!






30. Do not optimize until the very end.






31. Uploads changes to your current branch.






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






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






34. Variable doesn't exist.






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






36. Removes files from the repository.






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






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






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






40. Function doesn't exist.






41. No more than 40 hours to stop burnouts.






42. Whats displayed to the screen






43. Black Box - The way the program works is internally unknown.






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






45. Input






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






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






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






49. Use only through the interface of the object.






50. STOP!!