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. Initialized stack memory.






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






3. Current line that is executing.






4. Adds files to the repository.






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






6. Plan out 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. NULL memory.






9. Uploads changes to your current branch.






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






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






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






13. Removes files from the repository.






14. Try to find the flaws in your code.






15. Variable doesn't exist.






16. One of the linking methods (pragma comment)






17. Quick program.






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






19. Fix any problems and then repeat the process.






20. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






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






22. Are what function classes should include.






23. What is part of the current scope.






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






25. The linking is already done internally






26. Input






27. 2 Eyes + 2 Minds = AWESOME!






28. Downloads your changes and then merges.






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






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






31. You have to tell it to link






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






33. Italicized in UML.






34. Written by the customers as things that the system needs to do for them.






35. Views all previous changes.






36. Downloads without merging.






37. Use only through the interface of the object.






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






39. Makes a copy of your repository.






40. The default nickname for the remote repository.






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






42. Put this before a function name in a dll - and the function name will avoid name mangling






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






44. Classes build off of each other.






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






46. Function doesn't exist.






47. Link multiple projects together






48. Formatted code standards.






49. Do not optimize until the very end.






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







Sorry!:) No result found.

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