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. Developers should be integrated and releasing code into the code repository every few hours.






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






3. You have to tell it to link






4. The default nickname for the remote repository.






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






6. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






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






8. Keeps a team using a similar naming convention for things.






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






10. Italicized in UML.






11. NULL memory.






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






13. No more than 40 hours to stop burnouts.






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






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






16. When doing a - precise task.






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






18. Function doesn't exist.






19. Will execute all code paths and boundary conditions.






20. Undo changes made since your last commit.






21. Functionality Tests.






22. Helps to eliminate unnecessary "include chaining."






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






24. Makes a copy of your repository.






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






26. Initialized stack memory.






27. Adds files to the repository.






28. Inheritance between object.






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






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






31. What is part of the current scope.






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






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






34. Whats displayed to the screen






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






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






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






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






39. Current view/ previous line.






40. Use only through the interface of the object.






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






42. Always do the simplest design that could possibly work.






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






44. A measure of logical dependency.






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






46. Quick program.






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






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






49. Set of all pending changes.






50. Bookmark of a revised set with a title. For easy checkouts.