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. Helps to eliminate unnecessary "include chaining."






2. Initialized stack memory.






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






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






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






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






7. Default branch within your repository.






8. You have to tell it to link






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






10. Puts all headers into a master header.






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






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






13. Inheritance between object.






14. No more than 40 hours to stop burnouts.






15. When GIT cannot merge your data.






16. Current view/ previous line.






17. Use only through the interface of the object.






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






19. When a class is defined within another class.






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






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






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






23. Code generation in a lib






24. NULL memory.






25. STOP!!






26. A function that can load a library






27. Adds files to the repository.






28. CONSTANT






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






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






31. Removes files from the repository.






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






33. Breaks encapsulation boundaries.






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






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






36. Plan out your code.






37. Link multiple projects together






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






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






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






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






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






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






44. When a conflict is fixed.






45. How many objects that a source object can legitimately reference.






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






47. Fix any problems and then repeat the process.






48. The linking is already done internally






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






50. Do not optimize until the very end.