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. Code generation in a lib






2. Adds files to the repository.






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






4. Whats displayed to the screen






5. Views all previous changes.






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






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






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






9. Initialized heap memory.






10. Formatted code standards.






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






12. Uploads changes to your current branch.






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






14. You have to tell it to link






15. Current view/ previous line.






16. Removes files from the repository.






17. Link multiple projects together






18. Plan out your code.






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






20. NULL memory.






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






22. Code whatever it is you need to code.






23. What is part of the current scope.






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






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






26. The process of deciding which function definition to link during run-time.






27. Freed heap memory.






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






29. Fix any problems and then repeat the process.






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






31. When a conflict is fixed.






32. Makes a copy of your repository.






33. The default nickname for the remote repository.






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






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






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






37. Stops when memory changes.






38. Do not optimize until the very end.






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






40. When doing a - precise task.






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






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






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






44. Use only through the interface of the object.






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






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






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






48. When a class is defined within another class.






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






50. Set of all pending changes.