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. Are what function classes should include.






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






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






4. Freed heap memory.






5. Will execute all code paths and boundary conditions.






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






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






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






9. Input






10. Plan out your code.






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






12. A function that can load a library






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






14. Views all previous changes.






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






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






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






18. Classes build off of each other.






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






20. Puts all headers into a master header.






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






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






23. Makes a copy of your repository.






24. Function doesn't exist.






25. Set of all pending changes.






26. Uploads changes to your current branch.






27. Create a test and then create a function.






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






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






30. Trying to access a location in memory that your computer cannot access.






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






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






33. Variable doesn't exist.






34. Fix any problems and then repeat the process.






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






36. Initialized stack memory.






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






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






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






40. Downloads without merging.






41. Functionality Tests.






42. Link multiple projects together






43. One of the linking methods (pragma comment)






44. Inheritance between object.






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






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






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






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






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






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