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. Bad! Don't ever use these types of variables!






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






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






4. Invalid or unexpected input that the program is not designed to process.






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






6. When a class is defined within another class.






7. Breaks encapsulation boundaries.






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






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






10. CONSTANT






11. A reference. Has and delete dynamic memory. implies ownership (Association does not).






12. Link multiple projects together






13. The default nickname for the remote repository.






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






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






16. Do not optimize until the very end.






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






18. Downloads your changes and then merges.






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






20. Helps to eliminate unnecessary "include chaining."






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






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






23. Create a test and then create a function.






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






25. What is part of the current scope.






26. Fix any problems and then repeat the process.






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






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






29. Views all previous changes.






30. Try to find the flaws in your code.






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






32. Code generation in a lib






33. Stops when memory changes.






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






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






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






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






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






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






40. Initialized heap memory.






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






42. Makes a copy of your repository.






43. Input






44. Adds files to the repository.






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






46. Puts all headers into a master header.






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






48. Application






49. Variable doesn't exist.






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