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






2. When GIT cannot merge your data.






3. No more than 40 hours to stop burnouts.






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






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






6. When a conflict is fixed.






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






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






9. Views all previous changes.






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






11. You have to tell it to link






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






13. Puts all headers into a master header.






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






15. Downloads without merging.






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






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






18. Removes files from the repository.






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






20. Invalid or unexpected input that the program is not designed to process.






21. When doing a - precise task.






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






23. Function doesn't exist.






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






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






26. Are what function classes should include.






27. Makes a copy of your repository.






28. Helps to eliminate unnecessary "include chaining."






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






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






31. Keeps a team using a similar naming convention for things.






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






33. Simply a value.






34. A set of creation and initialization steps useful for a set of different related tests.






35. Functionality Tests.






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






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






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






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






40. Default branch within your repository.






41. Classes build off of each other.






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






43. A measure of logical dependency.






44. STOP!!






45. Code whatever it is you need to code.






46. Variable doesn't exist.






47. Plan out your code.






48. One of the linking methods (pragma comment)






49. The linking is already done internally






50. When a class is defined within another class.