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. Adds files to the repository.






2. Use only through the interface of the object.






3. Downloads without merging.






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






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






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






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






8. When GIT cannot merge your data.






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






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






11. Initialized heap memory.






12. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






14. Will execute all code paths and boundary conditions.






15. Link multiple projects together






16. The linking is already done internally






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






18. Variable doesn't exist.






19. Stops when memory changes.






20. Italicized in UML.






21. Undo changes made since your last commit.






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






23. Inheritance between object.






24. Ability to treat a class object as a function by overloading the () operator.






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






26. What is part of the current scope.






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






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






29. Ignores files when pushing.






30. Black Box - The way the program works is internally unknown.






31. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






32. Functionality Tests.






33. Try to find the flaws in your code.






34. Uploads changes to your current branch.






35. Function doesn't exist.






36. You have to tell it to link






37. Allows consumers to try a system earlier and give early feedback.






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






39. Do not optimize until the very end.






40. Application






41. Current view/ previous line.






42. CONSTANT






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






44. Downloads your changes and then merges.






45. NULL memory.






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






47. How many objects that a source object can legitimately reference.






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






49. Current line that is executing.






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