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. Undo changes made since your last commit.






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






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






4. Puts all headers into a master header.






5. Create a test and then create a function.






6. Downloads without merging.






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






8. Variable doesn't exist.






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






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






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






12. A function that can load a library






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






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






15. Classes build off of each other.






16. Fix any problems and then repeat the process.






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






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






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






20. Ignores files when pushing.






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






22. Will execute all code paths and boundary conditions.






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






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






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






26. Current view/ previous line.






27. Set of all pending changes.






28. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






29. Input






30. Link multiple projects together






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






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






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






34. Takes information in the index and pushes it onto the stack.






35. What is part of the current scope.






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






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






38. Code generation in a lib






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






40. The linking is already done internally






41. A measure of logical dependency.






42. Default branch within your repository.






43. Adds files to the repository.






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






45. Uploads changes to your current branch.






46. Do not optimize until the very end.






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






48. Whats displayed to the screen






49. When a class is defined within another class.






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