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. Ability to treat a class object as a function by overloading the () operator.






2. Downloads your changes and then merges.






3. No more than 40 hours to stop burnouts.






4. Undo changes made since your last commit.






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






6. Makes a copy of your repository.






7. Views all previous changes.






8. Code generation in a lib






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






10. Ignores files when pushing.






11. Are what function classes should include.






12. Set of all pending changes.






13. Fix any problems and then repeat the process.






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






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






16. Quick program.






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






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






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






20. Variable doesn't exist.






21. STOP!!






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






23. Freed heap memory.






24. Helps to eliminate unnecessary "include chaining."






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






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






27. Current line that is executing.






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






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






30. You have to tell it to link






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






32. Connection between a local brand and a remote branch.






33. When a conflict is fixed.






34. Puts all headers into a master header.






35. Default branch within your repository.






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






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






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






39. Ask questions and obtain the details and requirements given.






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






41. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






42. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






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






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






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






46. Input






47. Create a test and then create a function.






48. Whats displayed to the screen






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






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