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. Whats displayed to the screen






2. Downloads without merging.






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






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






5. Code whatever it is you need to code.






6. Do not optimize until the very end.






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






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






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






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






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






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






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






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






15. Takes information in the index and pushes it onto the stack.






16. Functionality Tests.






17. No more than 40 hours to stop burnouts.






18. Try to find the flaws in your code.






19. STOP!!






20. Set of all pending changes.






21. Current view/ previous line.






22. Stops when memory changes.






23. Input






24. Valid input that the program is designed to process.






25. The linking is already done internally






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






27. What is part of the current scope.






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






29. Breaks encapsulation boundaries.






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






31. Freed heap memory.






32. Current line that is executing.






33. Helps to eliminate unnecessary "include chaining."






34. Function doesn't exist.






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






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






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






38. Variable doesn't exist.






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






40. Code generation in a lib






41. When a conflict is fixed.






42. Create a test and then create a function.






43. When GIT cannot merge your data.






44. Quick program.






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






46. Italicized in UML.






47. Uploads changes to your current branch.






48. Initialized stack memory.






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






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