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. Stops when memory changes.






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






3. Ignores files when pushing.






4. Initialized heap memory.






5. When GIT cannot merge your data.






6. Adds files to the repository.






7. Current view/ previous line.






8. Try to find the flaws in your code.






9. NULL memory.






10. Helps to eliminate unnecessary "include chaining."






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






12. A measure of logical dependency.






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






14. Set of all pending changes.






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






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






17. Having power over inheritance with the flexibility of composition.






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






19. When doing a - precise task.






20. Puts all headers into a master header.






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






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






23. Input






24. Use only through the interface of the object.






25. When a class is defined within another class.






26. Default branch within your repository.






27. Link multiple projects together






28. When you type in an object - you can see its attributes.






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






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






31. Initialized stack memory.






32. Views all previous changes.






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






34. Inheritance between object.






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






36. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






37. Are what function classes should include.






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






39. Uploads changes to your current branch.






40. Variable doesn't exist.






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






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






43. Code generation in a lib






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






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






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






47. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






48. Freed heap memory.






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






50. Application