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. Portioning your changes to commit by inserting them into the index.






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






3. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






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






5. Uploads changes to your current branch.






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






7. Simply a value.






8. Initialized heap memory.






9. Undo changes made since your last commit.






10. Whats displayed to the screen






11. Makes a project compile in order of who is dependent on what






12. When doing a - precise task.






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






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






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






16. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






17. Fix any problems and then repeat the process.






18. The linking is already done internally






19. One of the linking methods (pragma comment)






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






21. Are what function classes should include.






22. Helps to eliminate unnecessary "include chaining."






23. Current line that is executing.






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






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






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






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






28. Variable doesn't exist.






29. Initialized stack memory.






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






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






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






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






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






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






36. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






38. Formatted code standards.






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






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






41. NULL memory.






42. A measure of logical dependency.






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






44. Use only through the interface of the object.






45. 2 Eyes + 2 Minds = AWESOME!






46. Function doesn't exist.






47. Italicized in UML.






48. Will execute all code paths and boundary conditions.






49. Creates a spin-off of a repository for concurrent development.






50. STOP!!