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






2. Simply a value.






3. Downloads your changes and then merges.






4. Code generation in a lib






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






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






7. Default branch within your repository.






8. Classes build off of each other.






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






10. When doing a - precise task.






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






12. Ignores files when pushing.






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






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






15. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






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






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






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






19. Set of all pending changes.






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






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






22. Quick program.






23. When a conflict is fixed.






24. Current view/ previous line.






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






26. No man's land. Guard bytes before the after allocated heap memory.






27. Freed heap memory.






28. Link multiple projects together






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






30. Formatted code standards.






31. No more than 40 hours to stop burnouts.






32. Fix any problems and then repeat the process.






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






34. Code whatever it is you need to code.






35. NULL memory.






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






37. Initialized stack memory.






38. Current line that is executing.






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






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






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






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






43. Use only through the interface of the object.






44. You have to tell it to link






45. When a class is defined within another class.






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






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






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






49. Will execute all code paths and boundary conditions.






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