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. Stand up meetings show who will be valuable and needed.






2. Use only through the interface of the object.






3. Are what function classes should include.






4. The linking is already done internally






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






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






7. Will execute all code paths and boundary conditions.






8. Code generation in a lib






9. Breaks encapsulation boundaries.






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






11. Initialized heap memory.






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






13. Stops when memory changes.






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






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






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






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






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






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






20. Helps to eliminate unnecessary "include chaining."






21. Makes a copy of your repository.






22. You have to tell it to link






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






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






25. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






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






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






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






29. Current line that is executing.






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






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






32. When GIT cannot merge your data.






33. No more than 40 hours to stop burnouts.






34. A measure of logical dependency.






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






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






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






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






39. When we remove redundant or obsolete designs and replace them with a new.






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






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






42. Ignores files when pushing.






43. Plan out your code.






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






45. Freed heap memory.






46. When doing a - precise task.






47. CONSTANT






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






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






50. Quick program.