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. Keeps a team using a similar naming convention for things.






3. Current view/ previous line.






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






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






6. Breaks encapsulation boundaries.






7. Fix any problems and then repeat the process.






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






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






10. What is part of the current scope.






11. Create a test and then create a function.






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






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






14. Downloads without merging.






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






16. Puts all headers into a master header.






17. Initialized stack memory.






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






19. Formatted code standards.






20. When a conflict is fixed.






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






22. Variable doesn't exist.






23. Makes a copy of your repository.






24. Views all previous changes.






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






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






27. Application






28. Function doesn't exist.






29. When a class is defined within another class.






30. Try to find the flaws in your code.






31. When doing a - precise task.






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






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






34. A function that can load a library






35. Current line that is executing.






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






37. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






38. Inheritance between object.






39. The linking is already done internally






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






41. Ignores files when pushing.






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






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






44. Code whatever it is you need to code.






45. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






47. NULL memory.






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






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






50. Static in C++. Can span all instances of a class.