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. Meetings used to create a release plan - which will lay out the overall project.






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






3. A function that can load a library






4. Static in C++. Can span all instances of a class.






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






6. When we remove redundant or obsolete designs and replace them with a new.






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






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






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






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






11. When doing a - precise task.






12. Inheritance between object.






13. The default nickname for the remote repository.






14. Code generation in a lib






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






16. Code whatever it is you need to code.






17. Use only through the interface of the object.






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






19. CONSTANT






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






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






22. Are what function classes should include.






23. One of the linking methods (pragma comment)






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






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






26. Simply a value.






27. Makes a copy of your repository.






28. Link multiple projects together






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






30. When a conflict is fixed.






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






32. The linking is already done internally






33. Variable doesn't exist.






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






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






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






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






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






39. Figure out what is feasible. Decide whether to use API's or to write from scratch.






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






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






42. Will execute all code paths and boundary conditions.






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






44. When GIT cannot merge your data.






45. Formatted code standards.






46. Default branch within your repository.






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






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






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






50. Functionality Tests.