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. Invalid or unexpected input that the program is not designed to process.






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






3. CONSTANT






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






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






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






7. No more than 40 hours to stop burnouts.






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






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






10. The linking is already done internally






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






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






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






14. A function that can load a library






15. Italicized in UML.






16. Set of all pending changes.






17. Puts all headers into a master header.






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






19. When a class is defined within another class.






20. Removes files from the repository.






21. Functionality Tests.






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






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






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






25. Helps to eliminate unnecessary "include chaining."






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






27. Plan out your code.






28. Downloads your changes and then merges.






29. Create a test and then create a function.






30. Adds files to the repository.






31. Uploads changes to your current branch.






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






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






34. Ignores files when pushing.






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






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






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






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






39. Link multiple projects together






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






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






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






43. Fix any problems and then repeat the process.






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






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






46. Default branch within your repository.






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






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






49. Views all previous changes.






50. Use only through the interface of the object.