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. Breaks encapsulation boundaries.






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






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






4. NULL memory.






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






6. The process of deciding which function definition to link during run-time.






7. Current line that is executing.






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






9. The default nickname for the remote repository.






10. Link multiple projects together






11. STOP!!






12. 2 Eyes + 2 Minds = AWESOME!






13. Treating a derived class's data members like it's base class's.






14. Whats displayed to the screen






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






16. Set of all pending changes.






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






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






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






20. When a conflict is fixed.






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






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






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






24. No more than 40 hours to stop burnouts.






25. One of the linking methods (pragma comment)






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






27. Default branch within your repository.






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






29. Italicized in UML.






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






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






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






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






34. Try to find the flaws in your code.






35. Downloads without merging.






36. Plan out your code.






37. Classes build off of each other.






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






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






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






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






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






43. Application






44. Stand up meetings show who will be valuable and needed.






45. Are what function classes should include.






46. Initialized heap memory.






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






48. Create a test and then create a function.






49. Removes files from the repository.






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