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. What is part of the current scope.






2. When doing a - precise task.






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






4. When a class is defined within another class.






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






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






7. Italicized in UML.






8. Freed heap memory.






9. Put this before a function name in a dll - and the function name will avoid name mangling






10. Figure out what is feasible. Decide whether to use API's or to write from scratch.






11. STOP!!






12. Separating out a section of code into a reusable function or class.






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






14. Initialized stack memory.






15. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






16. Makes a copy of your repository.






17. Input






18. Ignores files when pushing.






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






20. Breaks encapsulation boundaries.






21. 2 Eyes + 2 Minds = AWESOME!






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






23. Are what function classes should include.






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






25. Views all previous changes.






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






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






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






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






30. Uploads changes to your current branch.






31. Set of all pending changes.






32. Undo changes made since your last commit.






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






34. Quick program.






35. Whats displayed to the screen






36. No more than 40 hours to stop burnouts.






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






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






39. Downloads without merging.






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






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






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






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






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






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






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






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






48. Create a test and then create a function.






49. One of the linking methods (pragma comment)






50. Functionality Tests.