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 type of library that is used by the code






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






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






4. Helps to eliminate unnecessary "include chaining."






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






6. Are what function classes should include.






7. You have to tell it to link






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






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






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






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






12. Stops when memory changes.






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






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






15. Puts all headers into a master header.






16. Code whatever it is you need to code.






17. Breaks encapsulation boundaries.






18. The default nickname for the remote repository.






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






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






21. Link multiple projects together






22. Classes build off of each other.






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






24. Adds files to the repository.






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






26. Whats displayed to the screen






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






28. Current line that is executing.






29. Written by the customers as things that the system needs to do for them.






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






31. Plan out your code.






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






33. Simply a value.






34. When GIT cannot merge your data.






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






36. Functionality Tests.






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






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






39. Trying to access a location in memory that your computer cannot access.






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






41. What is part of the current scope.






42. Create a test and then create a function.






43. A measure of logical dependency.






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






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






46. Fix any problems and then repeat the process.






47. Code generation in a lib






48. STOP!!






49. Do not optimize until the very end.






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