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. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






3. Undo changes made since your last commit.






4. Code whatever it is you need to code.






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






6. Views all previous changes.






7. Freed heap memory.






8. Set of all pending changes.






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






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






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






12. Removes files from the repository.






13. Portioning your changes to commit by inserting them into the index.






14. Downloads without merging.






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






16. 2 Eyes + 2 Minds = AWESOME!






17. Initialized heap memory.






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






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






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






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






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






23. Fix any problems and then repeat the process.






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






25. Initialized stack memory.






26. Makes a copy of your repository.






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






28. Current line that is executing.






29. CONSTANT






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






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






32. Use only through the interface of the object.






33. When a class is defined within another class.






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






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






36. Ability to withstand change and what the effects are.






37. Downloads your changes and then merges.






38. NULL memory.






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






40. What is part of the current scope.






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






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






43. When doing a - precise task.






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






45. Application






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






47. Uploads changes to your current branch.






48. Do not optimize until the very end.






49. Function doesn't exist.






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