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. Meetings at the beginning of each iteration to produce a plan of programming tasks.






2. CONSTANT






3. Uploads changes to your current branch.






4. A measure of logical dependency.






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






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






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






8. The linking is already done internally






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






10. When a conflict is fixed.






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






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






13. The default nickname for the remote repository.






14. Default branch within your repository.






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






16. Plan out your code.






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






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






19. Removes files from the repository.






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






21. Code generation in a lib






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






23. Fix any problems and then repeat the process.






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






25. Initialized heap memory.






26. Function doesn't exist.






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






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






29. Downloads without merging.






30. Ignores files when pushing.






31. When doing a - precise task.






32. Stops when memory changes.






33. Helps to eliminate unnecessary "include chaining."






34. Downloads your changes and then merges.






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






36. Do not optimize until the very end.






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






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






39. Create a test and then create a function.






40. No more than 40 hours to stop burnouts.






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






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






43. Puts all headers into a master header.






44. Input






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






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






47. NULL memory.






48. You have to tell it to link






49. 2 Eyes + 2 Minds = AWESOME!






50. Variable doesn't exist.