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. Downloads without merging.






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






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






4. Set of all pending changes.






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






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






7. 2 Eyes + 2 Minds = AWESOME!






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






9. Stops when memory changes.






10. When a conflict is fixed.






11. Helps to eliminate unnecessary "include chaining."






12. What is part of the current scope.






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






14. Application






15. STOP!!






16. Puts all headers into a master header.






17. Formatted code standards.






18. One of the linking methods (pragma comment)






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






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






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






22. Allows consumers to try a system earlier and give early feedback.






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






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






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






26. Use only through the interface of the object.






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






28. A function that can load a library






29. Italicized in UML.






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






31. You have to tell it to link






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






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






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






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






36. Ignores files when pushing.






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






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






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






40. Breaks encapsulation boundaries.






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






42. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






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






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






46. Default branch within your repository.






47. Freed heap memory.






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






49. A measure of logical dependency.






50. Current line that is executing.