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






2. Ignores files when pushing.






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






4. Puts all headers into a master header.






5. NULL memory.






6. Helps to eliminate unnecessary "include chaining."






7. Try to find the flaws in your code.






8. Ensure a class only has one instance - and provide a global point of access to it






9. Link multiple projects together






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






11. What is part of the current scope.






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






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






14. Stops when memory changes.






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






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






17. Undo changes made since your last commit.






18. Current view/ previous line.






19. Application






20. Functionality Tests.






21. Initialized stack memory.






22. Breaks encapsulation boundaries.






23. When a concrete class inherits from a pure interface.






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






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






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






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






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






29. Downloads without merging.






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






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






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






33. Classes build off of each other.






34. Will execute all code paths and boundary conditions.






35. Default branch within your repository.






36. No more than 40 hours to stop burnouts.






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






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






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






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






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






42. When a class is defined within another class.






43. When a conflict is fixed.






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






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






46. Current line that is executing.






47. Makes a copy of your repository.






48. A measure of logical dependency.






49. Fix any problems and then repeat the process.






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