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. STOP!!






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






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






4. Puts all headers into a master header.






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






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






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






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






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






10. No more than 40 hours to stop burnouts.






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






12. Quick program.






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






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






15. When GIT cannot merge your data.






16. Link multiple projects together






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






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






19. Code whatever it is you need to code.






20. Create a test and then create a function.






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






22. Initialized stack memory.






23. Removes files from the repository.






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






25. Input






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






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






28. Freed heap memory.






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






30. Views all previous changes.






31. Ability to accept different types of parameters to bind to different implementations at run-time.






32. When doing a - precise task.






33. You have to tell it to link






34. Undo changes made since your last commit.






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






36. Will execute all code paths and boundary conditions.






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






38. Do not optimize until the very end.






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






40. Classes build off of each other.






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






42. Simply a value.






43. Try to find the flaws in your code.






44. A function that can load a library






45. Variable doesn't exist.






46. When a conflict is fixed.






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






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






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






50. Downloads your changes and then merges.