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. Copies all changes from one branch into another branch.






2. Default branch within your repository.






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






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






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






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






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






8. Simply a value.






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






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. A type of library that is used by the code






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






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






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






15. Ignores files when pushing.






16. Classes build off of each other.






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






18. Functionality Tests.






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






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






21. Breaks encapsulation boundaries.






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






23. The linking is already done internally






24. A measure of logical dependency.






25. Input






26. Create a test and then create a function.






27. Puts all headers into a master header.






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






29. Code generation in a lib






30. One of the linking methods (pragma comment)






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






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






33. Application






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






35. 2 Eyes + 2 Minds = AWESOME!






36. When doing a - precise task.






37. Makes a copy of your repository.






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






39. About the interface to an object. Data contained within.






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






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






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






43. Italicized in UML.






44. Ability to treat a class object as a function by overloading the () operator.






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






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






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






48. Downloads without merging.






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






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