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 withstand change and what the effects are.






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






3. Removes files from the repository.






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






5. 2 Eyes + 2 Minds = AWESOME!






6. When GIT cannot merge your data.






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






8. When a conflict is fixed.






9. NULL memory.






10. What is part of the current scope.






11. Makes a copy of your repository.






12. Downloads your changes and then merges.






13. Stops when memory changes.






14. The default nickname for the remote repository.






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






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






17. Plan out your code.






18. Input






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






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






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






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






23. You have to tell it to link






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






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






26. Classes build off of each other.






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






28. Try to find the flaws in your code.






29. Fix any problems and then repeat the process.






30. Initialized heap memory.






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






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






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






34. Code generation in a lib






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






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






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






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






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






40. Set of all pending changes.






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






42. Puts all headers into a master header.






43. Views all previous changes.






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






45. STOP!!






46. No more than 40 hours to stop burnouts.






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






48. Freed heap memory.






49. The linking is already done internally






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