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. Allows consumers to try a system earlier and give early feedback.






2. Create a test and then create a function.






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






4. Try to find the flaws in your code.






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






6. Current view/ previous line.






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






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






9. Downloads your changes and then merges.






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






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






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






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






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. Developers should be integrated and releasing code into the code repository every few hours.






16. Adds files to the repository.






17. NULL memory.






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






19. No more than 40 hours to stop burnouts.






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






21. Whats displayed to the screen






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






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






24. Default branch within your repository.






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






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






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






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






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






30. Formatted code standards.






31. Link multiple projects together






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






33. A pointer or reference. One object needs to know about the other object to work.






34. Italicized in UML.






35. Are what function classes should include.






36. Puts all headers into a master header.






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






38. Makes a copy of your repository.






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






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






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






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






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






44. Linking to dynamic libraries is usually handled by linking to an ____________.






45. Function doesn't exist.






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






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






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






49. When a class is defined within another class.






50. When doing a - precise task.