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. Code whatever it is you need to code.






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






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






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






5. A measure of logical dependency.






6. Plan out your code.






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






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






9. Input






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






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






12. You have to tell it to link






13. Downloads without merging.






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






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






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






17. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






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






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






21. A function that can load a library






22. CONSTANT






23. Stops when memory changes.






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






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






26. When doing a - precise task.






27. Use only through the interface of the object.






28. 2 Eyes + 2 Minds = AWESOME!






29. Ensure a class only has one instance - and provide a global point of access to it






30. Formatted code standards.






31. Makes a copy of your repository.






32. One of the linking methods (pragma comment)






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






34. Current view/ previous line.






35. Uploads changes to your current branch.






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






37. Removes files from the repository.






38. Puts all headers into a master header.






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






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. When you type in an object - you can see its attributes.






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






43. Static in C++. Can span all instances of a class.






44. Will execute all code paths and boundary conditions.






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






46. Whats displayed to the screen






47. Having power over inheritance with the flexibility of composition.






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. Put this before a function name in a dll - and the function name will avoid name mangling






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