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 copy of your repository.






2. Current line that is executing.






3. Link multiple projects together






4. Helps to eliminate unnecessary "include chaining."






5. When a conflict is fixed.






6. Code generation in a lib






7. You have to tell it to link






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






9. Trying to access a location in memory that your computer cannot access.






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






11. Formatted code standards.






12. Whats displayed to the screen






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






14. Uploads changes to your current branch.






15. Uploads all changes staged in the index list into the repository database.






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






17. Try to find the flaws in your code.






18. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






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






21. Do not optimize until the very end.






22. Views all previous changes.






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






24. Variable doesn't exist.






25. Default branch within your repository.






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






27. Keeps a team using a similar naming convention for things.






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






29. Downloads without merging.






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






31. Initialized stack memory.






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






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






34. Will execute all code paths and boundary conditions.






35. Are what function classes should include.






36. Fix any problems and then repeat the process.






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






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






39. No more than 40 hours to stop burnouts.






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






41. STOP!!






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






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






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






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






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






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






48. Removes files from the repository.






49. Bookmark of a revised set with a title. For easy checkouts.






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