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. Use only through the interface of the object.






2. Uploads changes to your current branch.






3. A measure of logical dependency.






4. You have to tell it to link






5. Functionality Tests.






6. What is part of the current scope.






7. Link multiple projects together






8. The default nickname for the remote repository.






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






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






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






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






13. Undo changes made since your last commit.






14. Set of all pending changes.






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






16. When a class is defined within another class.






17. When a conflict is fixed.






18. No more than 40 hours to stop burnouts.






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






20. When doing a - precise task.






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






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






23. The linking is already done internally






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






25. Ignores files when pushing.






26. Current line that is executing.






27. Italicized in UML.






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






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






30. Breaks encapsulation boundaries.






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






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






33. Adds files to the repository.






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






35. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






36. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






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






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






40. Initialized stack memory.






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






42. Create a test and then create a function.






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






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






45. Do not optimize until the very end.






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






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






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






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






50. Function doesn't exist.