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. Makes a project compile in order of who is dependent on what






2. Downloads your changes and then merges.






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






4. Ignores files when pushing.






5. When we remove redundant or obsolete designs and replace them with a new.






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






7. Input






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






9. Simply a value.






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






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






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






13. When doing a - precise task.






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






15. Initialized stack memory.






16. Code generation in a lib






17. Link multiple projects together






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






19. Variable doesn't exist.






20. Makes a copy of your repository.






21. CONSTANT






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






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






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






25. Application






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






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






28. Current view/ previous line.






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






30. Initialized heap memory.






31. Functionality Tests.






32. Try to find the flaws in your code.






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






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






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






36. STOP!!






37. Downloads without merging.






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






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






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






41. Weak relationship between two classes. Almost always results in a #include.






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






43. Create a test and then create a function.






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






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






46. Puts all headers into a master header.






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






48. Quick program.






49. Inheritance between object.






50. Stops when memory changes.