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. Ignores files when pushing.






2. Quick program.






3. Separating out a section of code into a reusable function or class.






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






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






6. Downloads your changes and then merges.






7. Initialized stack memory.






8. Variable doesn't exist.






9. Code whatever it is you need to code.






10. When a class is defined within another class.






11. Initialized heap memory.






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






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






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






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






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






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






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






19. Uploads changes to your current branch.






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






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






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






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






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






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






26. Use only through the interface of the object.






27. Create a test and then create a function.






28. 2 Eyes + 2 Minds = AWESOME!






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






30. Whats displayed to the screen






31. Freed heap memory.






32. Helps to eliminate unnecessary "include chaining."






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






34. Inheritance between object.






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






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






37. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






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






40. Downloads without merging.






41. Makes a copy of your repository.






42. Removes files from the repository.






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






44. Link multiple projects together






45. Simply a value.






46. Classes build off of each other.






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






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






49. Current line that is executing.






50. When doing a - precise task.