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. NULL memory.






2. When we remove redundant or obsolete designs and replace them with a new.






3. Removes files from the repository.






4. No more than 40 hours to stop burnouts.






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






6. Link multiple projects together






7. CONSTANT






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






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






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






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






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






13. Freed heap memory.






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






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






16. Helps to eliminate unnecessary "include chaining."






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






18. Do not optimize until the very end.






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






20. Stops when memory changes.






21. Fix any problems and then repeat the process.






22. When a conflict is fixed.






23. Are what function classes should include.






24. Create a test and then create a function.






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






26. Italicized in UML.






27. Code generation in a lib






28. 2 Eyes + 2 Minds = AWESOME!






29. Makes a copy of your repository.






30. Breaks encapsulation boundaries.






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






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






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






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






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






36. Initialized heap memory.






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






38. Function doesn't exist.






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






40. Ignores files when pushing.






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






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






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






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






45. Allows consumers to try a system earlier and give early feedback.






46. Current view/ previous line.






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






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






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






50. A measure of logical dependency.