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. Ignores files when pushing.






2. Plan out your code.






3. Will execute all code paths and boundary conditions.






4. What is part of the current scope.






5. Function doesn't exist.






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






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






8. Default branch within your repository.






9. The default nickname for the remote repository.






10. Initialized stack memory.






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






12. Application






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






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






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






16. STOP!!






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






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






19. When a conflict is fixed.






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






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






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






23. Puts all headers into a master header.






24. Are what function classes should include.






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






26. Formatted code standards.






27. Uploads changes to your current branch.






28. Set of all pending changes.






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






30. Italicized in UML.






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






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






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






34. NULL memory.






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






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






37. One of the linking methods (pragma comment)






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






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






40. Inheritance between object.






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






42. Simply a value.






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






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






45. Create a test and then create a function.






46. Do not optimize until the very end.






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






48. Variable doesn't exist.






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. Current line that is executing.