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. When we remove redundant or obsolete designs and replace them with a new.






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






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






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






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






6. 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.






7. Inheritance between object.






8. STOP!!






9. Italicized in UML.






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






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






12. Try to find the flaws in your code.






13. When doing a - precise task.






14. Stops when memory changes.






15. Use only through the interface of the object.






16. Simply a value.






17. Views all previous changes.






18. Application






19. Initialized heap memory.






20. Function doesn't exist.






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






22. Are what function classes should include.






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






24. One of the linking methods (pragma comment)






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






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






27. Code whatever it is you need to code.






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






29. When a conflict is fixed.






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






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






32. Puts all headers into a master header.






33. Undo changes made since your last commit.






34. The linking is already done internally






35. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






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






38. Variable doesn't exist.






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






40. Ask questions and obtain the details and requirements given.






41. Functionality Tests.






42. Breaks encapsulation boundaries.






43. What is part of the current scope.






44. Downloads without merging.






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






46. You have to tell it to link






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






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






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






50. Ignores files when pushing.