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. Use only through the interface of the object.






2. Formatted code standards.






3. When GIT cannot merge your data.






4. Puts all headers into a master header.






5. Italicized in UML.






6. Try to find the flaws in your code.






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






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






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






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






11. The linking is already done internally






12. Separating out a section of code into a reusable function or class.






13. Views all previous changes.






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






15. Simply a value.






16. Default branch within your repository.






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






18. What is part of the current scope.






19. Ignores files when pushing.






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






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






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






23. Downloads your changes and then merges.






24. Do not optimize until the very end.






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






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






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






28. You have to tell it to link






29. Plan out your code.






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






31. Variable doesn't exist.






32. Ability to withstand change and what the effects are.






33. NULL memory.






34. Create a test and then create a function.






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






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






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






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






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






40. Quick program.






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






42. 2 Eyes + 2 Minds = AWESOME!






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






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






45. A measure of logical dependency.






46. Fix any problems and then repeat the process.






47. Code whatever it is you need to code.






48. STOP!!






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






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests