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. Ask questions and obtain the details and requirements given.






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






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






4. Current view/ previous line.






5. Linking to dynamic libraries is usually handled by linking to an ____________.






6. Ignores files when pushing.






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






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






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






10. Classes build off of each other.






11. Create a test and then create a function.






12. When a concrete class inherits from a pure interface.






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






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






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






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






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






18. Will execute all code paths and boundary conditions.






19. Application






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






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






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






23. Input






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






25. Removes files from the repository.






26. When a class is defined within another class.






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






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






29. A measure of logical dependency.






30. Initialized stack memory.






31. Downloads your changes and then merges.






32. Default branch within your repository.






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






34. Freed heap memory.






35. Set of all pending changes.






36. Inheritance between object.






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






38. Try to find the flaws in your code.






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






40. The linking is already done internally






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






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






43. Breaks encapsulation boundaries.






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






45. Views all previous changes.






46. Puts all headers into a master header.






47. Are what function classes should include.






48. Plan out your code.






49. CONSTANT






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