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. Formatted code standards.






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






3. The linking is already done internally






4. Do not optimize until the very end.






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






6. Code whatever it is you need to code.






7. Default branch within your repository.






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






9. CONSTANT






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






11. Breaks encapsulation boundaries.






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






13. Variable doesn't exist.






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






15. Inheritance between object.






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






17. You have to tell it to link






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






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






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






21. Use only through the interface of the object.






22. Link multiple projects together






23. STOP!!






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






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






26. When you type in an object - you can see its attributes.






27. No more than 40 hours to stop burnouts.






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






29. Create a test and then create a function.






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






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






32. Stops when memory changes.






33. Try to find the flaws in your code.






34. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






35. When a conflict is fixed.






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






37. Function doesn't exist.






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






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






40. Weak relationship between two classes. Almost always results in a #include.






41. Puts all headers into a master header.






42. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






43. One of the linking methods (pragma comment)






44. Makes a copy of your repository.






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






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. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






48. Valid input that the program is designed to process.






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






50. No man's land. Guard bytes before the after allocated heap memory.