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. Written by the customers as things that the system needs to do for them.






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






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






4. STOP!!






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






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






7. Are what function classes should include.






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






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






10. Having power over inheritance with the flexibility of composition.






11. Puts all headers into a master header.






12. Connection between a local brand and a remote branch.






13. When doing a - precise task.






14. No more than 40 hours to stop burnouts.






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






16. One of the linking methods (pragma comment)






17. Downloads your changes and then merges.






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






19. Current view/ previous line.






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






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






22. Uploads changes to your current branch.






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






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






25. Static in C++. Can span all instances of a class.






26. Use only through the interface of the object.






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






28. Helps to eliminate unnecessary "include chaining."






29. You have to tell it to link






30. Adds files to the repository.






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






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






33. Simply a value.






34. Default branch within your repository.






35. Link multiple projects together






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






37. Set of all pending changes.






38. Functionality Tests.






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






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






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






42. Application






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






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






45. Breaks encapsulation boundaries.






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






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






48. Formatted code standards.






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






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