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. Italicized in UML.






2. Initialized stack memory.






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






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






5. STOP!!






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






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






8. Makes a copy of your repository.






9. Code whatever it is you need to code.






10. Default branch within your repository.






11. Current line that is executing.






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






13. You have to tell it to link






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






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






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






17. When doing a - precise task.






18. Classes build off of each other.






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






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






21. Input






22. When a conflict is fixed.






23. NULL memory.






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






25. Whats displayed to the screen






26. The linking is already done internally






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






28. One of the linking methods (pragma comment)






29. Views all previous changes.






30. Will execute all code paths and boundary conditions.






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






32. Uploads changes to your current branch.






33. Allows you to switch your working copy to another branch.






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






35. Fix any problems and then repeat the process.






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






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






38. Function doesn't exist.






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






40. Application






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






42. Helps to eliminate unnecessary "include chaining."






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






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






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






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






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






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






49. Current view/ previous line.






50. Adds files to the repository.