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. Linking to dynamic libraries is usually handled by linking to an ____________.






2. Do not optimize until the very end.






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






4. No man's land. Guard bytes before the after allocated heap memory.






5. The default nickname for the remote repository.






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






7. When a class is defined within another class.






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






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






10. Inheritance between object.






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






12. NULL memory.






13. Create a test and then create a function.






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






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






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






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






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






19. When doing a - precise task.






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






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






22. Ignores files when pushing.






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






24. Classes build off of each other.






25. When a conflict is fixed.






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






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






28. The linking is already done internally






29. Set of all pending changes.






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






31. Initialized heap memory.






32. Default branch within your repository.






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






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






35. When GIT cannot merge your data.






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






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






38. Function doesn't exist.






39. One of the linking methods (pragma comment)






40. Functionality Tests.






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






42. No more than 40 hours to stop burnouts.






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






44. You have to tell it to link






45. Quick program.






46. Plan out your code.






47. Puts all headers into a master header.






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






49. Downloads without merging.






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