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. Current line that is executing.






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






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






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






5. Try to find the flaws in your code.






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






7. Do not optimize until the very end.






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






9. Use this to find a memory address or signiture in a dll






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






11. Makes a copy of your repository.






12. Classes build off of each other.






13. Create a test and then create a function.






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






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






16. Stops when memory changes.






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






18. Uploads changes to your current branch.






19. No more than 40 hours to stop burnouts.






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






21. Downloads your changes and then merges.






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






23. You have to tell it to link






24. Plan out your code.






25. One of the linking methods (pragma comment)






26. Whats displayed to the screen






27. Will execute all code paths and boundary conditions.






28. Fix any problems and then repeat the process.






29. When doing a - precise task.






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






31. Function doesn't exist.






32. 2 Eyes + 2 Minds = AWESOME!






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






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






35. Italicized in UML.






36. When a class is defined within another class.






37. How many objects that a source object can legitimately reference.






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






39. The default nickname for the remote repository.






40. NULL memory.






41. Adds files to the repository.






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






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






44. The linking is already done internally






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






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






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






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






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






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