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. Ignores files when pushing.






2. Set of all pending changes.






3. Italicized in UML.






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






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






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






7. Are what function classes should include.






8. Create a test and then create a function.






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






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






11. When a conflict is fixed.






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






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






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






15. Initialized heap memory.






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






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






18. Puts all headers into a master header.






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






20. The linking is already done internally






21. Current view/ previous line.






22. Downloads without merging.






23. When a class is defined within another class.






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






25. Removes files from the repository.






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






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






28. Will execute all code paths and boundary conditions.






29. Link multiple projects together






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






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






32. Try to find the flaws in your code.






33. Formatted code standards.






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






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






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






37. Plan out your code.






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






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






40. Classes build off of each other.






41. Helps to eliminate unnecessary "include chaining."






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






43. Uploads changes to your current branch.






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






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






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






47. Undo changes made since your last commit.






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






49. The default nickname for the remote repository.






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