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. A reference. Has and delete dynamic memory. implies ownership (Association does not).






2. Current view/ previous line.






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






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






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






6. Set of all pending changes.






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






8. Stops when memory changes.






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






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






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






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






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






14. Bookmark of a revised set with a title. For easy checkouts.






15. STOP!!






16. Use only through the interface of the object.






17. Plan out your code.






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






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






20. The default nickname for the remote repository.






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






22. When doing a - precise task.






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






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






25. Freed heap memory.






26. Downloads without merging.






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






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






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






30. Application






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






32. Takes information in the index and pushes it onto the stack.






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






34. You have to tell it to link






35. Code whatever it is you need to code.






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






37. Downloads your changes and then merges.






38. Simply a value.






39. Classes build off of each other.






40. No more than 40 hours to stop burnouts.






41. Current line that is executing.






42. Initialized heap memory.






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






44. Inheritance between object.






45. When GIT cannot merge your data.






46. The process of deciding which function definition to link during run-time.






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






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






49. One of the linking methods (pragma comment)






50. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.