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. NULL memory.






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






3. One of the linking methods (pragma comment)






4. Downloads without merging.






5. When doing a - precise task.






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






7. Simply a value.






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






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






10. Puts all headers into a master header.






11. Formatted code standards.






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






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






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






15. Fix any problems and then repeat the process.






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






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






18. Italicized in UML.






19. Removes files from the repository.






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






21. When a class is defined within another class.






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






23. When GIT cannot merge your data.






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






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






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






27. The default nickname for the remote repository.






28. Concept based on limiting the scope of modules to provide better structures.






29. Code generation in a lib






30. How many objects that a source object can legitimately reference.






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






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






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






34. Downloads your changes and then merges.






35. Will execute all code paths and boundary conditions.






36. Current view/ previous line.






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






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






39. Classes build off of each other.






40. Plan out your code.






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






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






43. Makes a copy of your repository.






44. A set of creation and initialization steps useful for a set of different related tests.






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






46. Input






47. Ignores files when pushing.






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






49. Undo changes made since your last commit.






50. Inheritance between object.