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. Treating a derived class's data members like it's base class's.






2. What is part of the current scope.






3. Fix any problems and then repeat the process.






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






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






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






7. One of the linking methods (pragma comment)






8. Initialized heap memory.






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






10. NULL memory.






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






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






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






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






15. Ignores files when pushing.






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






17. Code whatever it is you need to code.






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






19. Use only through the interface of the object.






20. The linking is already done internally






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






22. Breaks encapsulation boundaries.






23. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






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






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






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






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






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






30. Plan out your code.






31. Removes files from the repository.






32. Initialized stack memory.






33. A function that can load a library






34. Copies all changes from one branch into another branch.






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






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






37. Makes a copy of your repository.






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






39. When doing a - precise task.






40. Views all previous changes.






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






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






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






44. Code generation in a lib






45. Do not optimize until the very end.






46. Are what function classes should include.






47. Adds files to the repository.






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






49. The default nickname for the remote repository.






50. Downloads without merging.