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 class is defined within another class.






2. The default nickname for the remote repository.






3. No more than 40 hours to stop burnouts.






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






5. Will execute all code paths and boundary conditions.






6. Classes build off of each other.






7. One of the linking methods (pragma comment)






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






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






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






11. When you type in an object - you can see its attributes.






12. 2 Eyes + 2 Minds = AWESOME!






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






14. Stops when memory changes.






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






16. Fix any problems and then repeat the process.






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






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






19. Link multiple projects together






20. Puts all headers into a master header.






21. Current view/ previous line.






22. Create a test and then create a function.






23. Downloads without merging.






24. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






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






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






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






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






29. Uploads changes to your current branch.






30. Are what function classes should include.






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






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






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






34. Current line that is executing.






35. Downloads your changes and then merges.






36. The linking is already done internally






37. Whats displayed to the screen






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






39. Do not optimize until the very end.






40. Adds files to the repository.






41. A measure of logical dependency.






42. Undo changes made since your last commit.






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






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






45. Functionality Tests.






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






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






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






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






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