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. Portioning your changes to commit by inserting them into the index.






2. Current view/ previous line.






3. Freed heap memory.






4. Quick program.






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






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






7. 2 Eyes + 2 Minds = AWESOME!






8. Views all previous changes.






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






10. Link multiple projects together






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






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






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






14. Function doesn't exist.






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






16. Set of all pending changes.






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






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






19. One of the linking methods (pragma comment)






20. STOP!!






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






22. Do not optimize until the very end.






23. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






24. A measure of logical dependency.






25. When a conflict is fixed.






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






27. NULL memory.






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






29. Variable doesn't exist.






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






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






32. Puts all headers into a master header.






33. Makes a copy of your repository.






34. Adds files to the repository.






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






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






37. Uploads changes to your current branch.






38. CONSTANT






39. The linking is already done internally






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






41. Having power over inheritance with the flexibility of composition.






42. Current line that is executing.






43. Initialized heap memory.






44. Downloads your changes and then merges.






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






46. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






47. Helps to eliminate unnecessary "include chaining."






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






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






50. Plan out your code.







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