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. Formatted code standards.






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






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






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






5. Initialized heap memory.






6. A function that can load a library






7. Variable doesn't exist.






8. Concept based on limiting the scope of modules to provide better structures.






9. Takes information in the index and pushes it onto the stack.






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






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






12. Do not optimize until the very end.






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






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






15. A measure of logical dependency.






16. Initialized stack memory.






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






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






19. Downloads your changes and then merges.






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






21. Link multiple projects together






22. You have to tell it to link






23. What is part of the current scope.






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






25. Downloads without merging.






26. STOP!!






27. Having power over inheritance with the flexibility of composition.






28. Inheritance between object.






29. Try to find the flaws in your code.






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






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






32. Input






33. Makes a copy of your repository.






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






35. Set of all pending changes.






36. Uploads changes to your current branch.






37. When a conflict is fixed.






38. Quick program.






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






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






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






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






43. Italicized in UML.






44. 2 Eyes + 2 Minds = AWESOME!






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






46. When GIT cannot merge your data.






47. The default nickname for the remote repository.






48. Create a test and then create a function.






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






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