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. Downloads your changes and then merges.






2. A type of library that is used by the code






3. Plan out your code.






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






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






6. Uploads changes to your current branch.






7. Breaks encapsulation boundaries.






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






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






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






11. Functionality Tests.






12. The linking is already done internally






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






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






15. The default nickname for the remote repository.






16. When doing a - precise task.






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






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






19. Are what function classes should include.






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






21. When GIT cannot merge your data.






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






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






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






25. Current view/ previous line.






26. Initialized heap memory.






27. Formatted code standards.






28. Current line that is executing.






29. CONSTANT






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






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






32. Variable doesn't exist.






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






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






35. A function that can load a library






36. You have to tell it to link






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






38. Link multiple projects together






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






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






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






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






43. Do not optimize until the very end.






44. When a class is defined within another class.






45. A pointer or reference. One object needs to know about the other object to work.






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






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






48. No more than 40 hours to stop burnouts.






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






50. Inheritance between object.