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. Having power over inheritance with the flexibility of composition.






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






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






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






5. Do not optimize until the very end.






6. Input






7. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






9. Initialized heap memory.






10. Removes files from the repository.






11. One of the linking methods (pragma comment)






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






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






14. 2 Eyes + 2 Minds = AWESOME!






15. Function doesn't exist.






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






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






18. Variable doesn't exist.






19. Helps to eliminate unnecessary "include chaining."






20. Uploads changes to your current branch.






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






22. Ignores files when pushing.






23. Fix any problems and then repeat the process.






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






25. Quick program.






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






27. Stops when memory changes.






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






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






30. Use this to find a memory address or signiture in a dll






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






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






33. Formatted code standards.






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






35. Undo changes made since your last commit.






36. Code whatever it is you need to code.






37. When doing a - precise task.






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






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






40. Current view/ previous line.






41. The linking is already done internally






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






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






44. Freed heap memory.






45. Functionality Tests.






46. Initialized stack memory.






47. Downloads your changes and then merges.






48. You have to tell it to link






49. Current line that is executing.






50. CONSTANT







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