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. One of the linking methods (pragma comment)






2. Ignores files when pushing.






3. Downloads without merging.






4. Stops when memory changes.






5. Plan out your code.






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






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






8. Freed heap memory.






9. Initialized heap memory.






10. Functionality Tests.






11. Undo changes made since your last commit.






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






13. When doing a - precise task.






14. Are what function classes should include.






15. STOP!!






16. Default branch within your repository.






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






18. No man's land. Guard bytes before the after allocated heap memory.






19. Code generation in a lib






20. Application






21. What is part of the current scope.






22. Quick program.






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






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






25. The default nickname for the remote repository.






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






27. No more than 40 hours to stop burnouts.






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






29. Adds files to the repository.






30. Create a test and then create a function.






31. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






32. Breaks encapsulation boundaries.






33. You have to tell it to link






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






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






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






37. NULL memory.






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






39. Fix any problems and then repeat the process.






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






41. Downloads your changes and then merges.






42. Uploads changes to your current branch.






43. Link multiple projects together






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






45. Makes a copy of your repository.






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






47. CONSTANT






48. Use only through the interface of the object.






49. When a conflict is fixed.






50. 2 Eyes + 2 Minds = AWESOME!