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. Connection between a local brand and a remote branch.






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






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






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






6. Freed heap memory.






7. Adds files to the repository.






8. When GIT cannot merge your data.






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






10. Quick program.






11. Plan out your code.






12. The default nickname for the remote repository.






13. When a class is defined within another class.






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






15. Downloads your changes and then merges.






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






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






18. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






19. Italicized in UML.






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






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






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






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






24. Ability to accept different types of parameters to bind to different implementations at run-time.






25. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






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






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






28. A set of creation and initialization steps useful for a set of different related tests.






29. A measure of logical dependency.






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






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






32. Set of all pending changes.






33. What is part of the current scope.






34. Makes a copy of your repository.






35. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






36. Fix any problems and then repeat the process.






37. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






38. Simply a value.






39. One of the linking methods (pragma comment)






40. Stops when memory changes.






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






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






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






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






45. Uploads changes to your current branch.






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






47. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






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






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