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. Linking to dynamic libraries is usually handled by linking to an ____________.






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






3. When a class is defined within another class.






4. STOP!!






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






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






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






8. Default branch within your repository.






9. Set of all pending changes.






10. NULL memory.






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






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






13. Adds files to the repository.






14. Puts all headers into a master header.






15. Initialized stack memory.






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






17. Views all previous changes.






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






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






20. Are what function classes should include.






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






22. Breaks encapsulation boundaries.






23. Inheritance between object.






24. One of the linking methods (pragma comment)






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






26. Code whatever it is you need to code.






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






28. Input






29. Quick program.






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. Removes files from the repository.






32. Use only through the interface of the object.






33. What is part of the current scope.






34. Try to find the flaws in your code.






35. A measure of logical dependency.






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






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






38. Italicized in UML.






39. Will execute all code paths and boundary conditions.






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






41. Initialized heap memory.






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






43. Undo changes made since your last commit.






44. Downloads without merging.






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






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






47. A function that can load a library






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






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






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