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. Treating a derived class's data members like it's base class's.






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






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






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






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






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






7. Downloads your changes and then merges.






8. STOP!!






9. Code generation in a lib






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






11. Input






12. Italicized in UML.






13. Current line that is executing.






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






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






16. Set of all pending changes.






17. Inheritance between object.






18. Ability to treat a class object as a function by overloading the () operator.






19. Breaks encapsulation boundaries.






20. The default nickname for the remote repository.






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






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






23. Formatted code standards.






24. When GIT cannot merge your data.






25. Create a test and then create a function.






26. Stops when memory changes.






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






28. Application






29. Are what function classes should include.






30. NULL memory.






31. Makes a copy of your repository.






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






33. When doing a - precise task.






34. Initialized heap memory.






35. Helps to eliminate unnecessary "include chaining."






36. When a class is defined within another class.






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






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






39. A function that can load a library






40. Quick program.






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






42. Always do the simplest design that could possibly work.






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






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






45. You have to tell it to link






46. Link multiple projects together






47. Plan out your code.






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






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






50. What is part of the current scope.