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. How many objects that a source object can legitimately reference.






2. STOP!!






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






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






5. Whats displayed to the screen






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






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






8. Try to find the flaws in your code.






9. Set of all pending changes.






10. When a concrete class inherits from a pure interface.






11. Create a test and then create a function.






12. Quick program.






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






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






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






16. No more than 40 hours to stop burnouts.






17. 2 Eyes + 2 Minds = AWESOME!






18. Do not optimize until the very end.






19. Current view/ previous line.






20. Simply a value.






21. The linking is already done internally






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






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






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






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






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






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






28. A function that can load a library






29. Ignores files when pushing.






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






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






32. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






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






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






35. Fix any problems and then repeat the process.






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






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






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






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






40. Default branch within your repository.






41. Formatted code standards.






42. Inheritance between object.






43. Undo changes made since your last commit.






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






45. Use only through the interface of the object.






46. Code whatever it is you need to code.






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






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






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






50. Functionality Tests.