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. Whats displayed to the screen






2. Plan out your code.






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. Code whatever it is you need to code.






5. A function that can load a library






6. Simply a value.






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






8. Initialized stack memory.






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






10. Application






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






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






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






14. When a class is defined within another class.






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






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






17. Initialized heap memory.






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






19. Try to find the flaws in your code.






20. Ignores files when pushing.






21. Helps to eliminate unnecessary "include chaining."






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






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






24. Quick program.






25. Link multiple projects together






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






27. Function doesn't exist.






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






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






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






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






32. A pointer or reference. One object needs to know about the other object to work.






33. Current view/ previous line.






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






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






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






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






38. You have to tell it to link






39. Do not optimize until the very end.






40. Classes build off of each other.






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






42. Variable doesn't exist.






43. Breaks encapsulation boundaries.






44. Ability to accept different types of parameters to bind to different implementations at run-time.






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






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






47. When doing a - precise task.






48. The default nickname for the remote repository.






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






50. Freed heap memory.