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. Uploads changes to your current branch.






2. What is part of the current scope.






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






4. Downloads without merging.






5. Current view/ previous line.






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






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






8. Whats displayed to the screen






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






10. Removes files from the repository.






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






12. Undo changes made since your last commit.






13. Downloads your changes and then merges.






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






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






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






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






18. Link multiple projects together






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






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






21. Stand up meetings show who will be valuable and needed.






22. NULL memory.






23. 2 Eyes + 2 Minds = AWESOME!






24. Create a test and then create a function.






25. The default nickname for the remote repository.






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






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






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






29. Functionality Tests.






30. When a class is defined within another class.






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






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






33. Do not optimize until the very end.






34. The linking is already done internally






35. Set of all pending changes.






36. Italicized in UML.






37. Stops when memory changes.






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






39. Freed heap memory.






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






41. Classes build off of each other.






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






43. Formatted code standards.






44. Use only through the interface of the object.






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






46. Input






47. About the interface to an object. Data contained within.






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






49. Are what function classes should include.






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests