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. Stand up meetings show who will be valuable and needed.






2. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






3. Helps to eliminate unnecessary "include chaining."






4. Are what function classes should include.






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






6. Italicized in UML.






7. Views all previous changes.






8. What is part of the current scope.






9. Removes files from the repository.






10. Adds files to the repository.






11. The linking is already done internally






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






13. Do not optimize until the very end.






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






15. Code whatever it is you need to code.






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






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






18. No more than 40 hours to stop burnouts.






19. Current line that is executing.






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






21. When a conflict is fixed.






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






23. Default branch within your repository.






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






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






26. Uploads changes to your current branch.






27. Black Box - The way the program works is internally unknown.






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






29. Formatted code standards.






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






31. Ignores files when pushing.






32. Simply a value.






33. Inheritance between object.






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






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






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






37. Code generation in a lib






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






39. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






40. Use only through the interface of the object.






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






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






43. Link multiple projects together






44. Variable doesn't exist.






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






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






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






48. When GIT cannot merge your data.






49. Developers should be integrated and releasing code into the code repository every few hours.






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