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. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






2. Code whatever it is you need to code.






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






4. Formatted code standards.






5. When doing a - precise task.






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






7. Plan out your code.






8. The default nickname for the remote repository.






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






10. Views all previous changes.






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






12. Inheritance between object.






13. Bad! Don't ever use these types of variables!






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






15. Stops when memory changes.






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






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






19. STOP!!






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






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






22. You have to tell it to link






23. Quick program.






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






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






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






27. A function that can load a library






28. Link multiple projects together






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






30. Are what function classes should include.






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






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






33. Variable doesn't exist.






34. Ignores files when pushing.






35. Breaks encapsulation boundaries.






36. Freed heap memory.






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






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






39. When a conflict is fixed.






40. CONSTANT






41. Adds files to the repository.






42. Makes a copy of your repository.






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






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






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






46. Whats displayed to the screen






47. A measure of logical dependency.






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






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






50. Downloads without merging.