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. When GIT cannot merge your data.






2. Removes files from the repository.






3. The linking is already done internally






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






5. Ignores files when pushing.






6. Code whatever it is you need to code.






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






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






9. Puts all headers into a master header.






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






11. One of the linking methods (pragma comment)






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






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






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






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






16. Simply a value.






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






18. NULL memory.






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






20. Will execute all code paths and boundary conditions.






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






22. When doing a - precise task.






23. Downloads without merging.






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






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






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






27. About the interface to an object. Data contained within.






28. Stops when memory changes.






29. Function doesn't exist.






30. Do not optimize until the very end.






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






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






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






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






35. When a conflict is fixed.






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






37. Formatted code standards.






38. Application






39. Makes a copy of your repository.






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






41. The default nickname for the remote repository.






42. Breaks encapsulation boundaries.






43. CONSTANT






44. Freed heap memory.






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






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






47. Create a test and then create a function.






48. Try to find the flaws in your code.






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






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