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. A set of creation and initialization steps useful for a set of different related tests.






2. Adds files to the repository.






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






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






5. NULL memory.






6. Code whatever it is you need to code.






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






8. Downloads your changes and then merges.






9. Do not optimize until the very end.






10. No more than 40 hours to stop burnouts.






11. A type of library that is used by the code






12. You have to tell it to link






13. Initialized heap memory.






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






15. Variable doesn't exist.






16. Use this to find a memory address or signiture in a dll






17. Functionality Tests.






18. Will execute all code paths and boundary conditions.






19. Classes build off of each other.






20. Inheritance between object.






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






22. Input






23. What is part of the current scope.






24. 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






25. Ability to treat a class object as a function by overloading the () operator.






26. When a conflict is fixed.






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






28. Initialized stack memory.






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






30. Current line that is executing.






31. Use only through the interface of the object.






32. Removes files from the repository.






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






34. Uploads changes to your current branch.






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






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






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






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






39. Function doesn't exist.






40. Helps to eliminate unnecessary "include chaining."






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






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






43. Italicized in UML.






44. Ignores files when pushing.






45. STOP!!






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






47. A measure of logical dependency.






48. Link multiple projects together






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






50. Simply a value.