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. Plan out your code.






2. Classes build off of each other.






3. The default nickname for the remote repository.






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






5. A function that can load a library






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






7. Code generation in a lib






8. Functionality Tests.






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






10. Helps to eliminate unnecessary "include chaining."






11. Undo changes made since your last commit.






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






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






14. Current view/ previous line.






15. The linking is already done internally






16. Current line that is executing.






17. Quick program.






18. Connection between a local brand and a remote branch.






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






20. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






21. NULL memory.






22. Create a test and then create a function.






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






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






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






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






27. Views all previous changes.






28. One of the linking methods (pragma comment)






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






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






31. Italicized in UML.






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






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






34. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






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






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






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






39. Inheritance between object.






40. Default branch within your repository.






41. Initialized heap memory.






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






43. Initialized stack memory.






44. Formatted code standards.






45. CONSTANT






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






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






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






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






50. Do not optimize until the very end.