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. When you type in an object - you can see its attributes.






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






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






4. The linking is already done internally






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






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






7. Formatted code standards.






8. Default branch within your repository.






9. When doing a - precise task.






10. When a class is defined within another class.






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






12. When a conflict is fixed.






13. Will execute all code paths and boundary conditions.






14. Application






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






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






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






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






19. Function doesn't exist.






20. Classes build off of each other.






21. Uploads changes to your current branch.






22. Whats displayed to the screen






23. Stops when memory changes.






24. A measure of logical dependency.






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






26. Views all previous changes.






27. Plan out your code.






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






29. Initialized stack memory.






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






31. You have to tell it to link






32. NULL memory.






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






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






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






36. Are what function classes should include.






37. Variable doesn't exist.






38. Fix any problems and then repeat the process.






39. Try to find the flaws in your code.






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






41. Code generation in a lib






42. Downloads without merging.






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






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






45. Removes files from the repository.






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






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






48. A function that can load a library






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






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